Resources
There are 2 design patterns to choose from in this repo, one involving sessions from Tracks only, the other from both Pages and Tracks.
NOTE: If you are not using Segment Warehouses, but a partner to ETL the data or custom ETL, the schema may look a bit different.
Customization
When applying the Segment template, it will need to be tailored to the underlying data, not a simple copy/paste. A few notes on that below:
- Schema names will be distinct to the Segment implementation, so the names in the template will need to be replaced.
- Because not all Segment implementations include all of the stock tables, the view files will need to be customized accordingly, which we’ll go through in this doc
- You’ll also want to consider how you’d like to define your sessions, which could include:
- Whether they come from only Tracks or both Pages and Tracks
- Session timeout/Requirements for a new session
- Custom info from
<schema>.eventtables that is of importance
👉 Continue to User ID Consolidation
👈 Back to Initial Validation
🏠 README Table of Contents