Skip to content
This repository has been archived by the owner on Feb 16, 2023. It is now read-only.

Latest commit

 

History

History
19 lines (13 loc) · 1.6 KB

_4_initial_validation.md

File metadata and controls

19 lines (13 loc) · 1.6 KB
Raw

Initial Validation

An important part of the initial data validation is making sure the event data has been configured as expected in the Segment implementation, especially user identifiers contained in the subset of Tracks and Pages tables available. Here is a suggested list:

  1. Verify that all events in Pages and Tracks have an Anonymous Id.
  2. Determine if User Id is part of the dataset, if so proceed. If not, discuss with the customer how they’d like to identify users (IP Address? Only consider discrete visits?).
  3. Verify that any schemas that will be tied together have User IDs in Pages and Tracks that will map.
  4. Verify that User Ids are as expected for the customer. Occasionally customers will change what value is populated for User Id, make sure you are only analyzing data that is correct (occasionally this is after a certain date). This generally is evident in the formatting (a 6 digit number vs a 10 character string, for example).
  5. Verify the events in Tracks (tracks.event) are as expected.
  6. Verify all entries in Pages have context_campaign_source and context_campaign_name for campaign tracking.
  7. Update Segment, Google, and Facebook data schema names in the project manifest file

If you see any deviations from expected behavior, there may be some things that should be configured on the Segment end.

👉 Continue to Applying the Segment Block

👈 Back to Table Structure

🏠 README Table of Contents