Skip to content

Add note about segment_id behavior in Track event tables where ID res fails #7639

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
May 29, 2025
Merged

Add note about segment_id behavior in Track event tables where ID res fails #7639

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
27d58b2
Update tables.md
ksaha873 May 28, 2025
66dc7ff
Update tables.md
ksaha873 May 28, 2025
98ab7bb
Update tables.md
ksaha873 May 28, 2025
e5a3e5d
rewording
pwseg May 29, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 3 additions & 11 deletions src/unify/profiles-sync/tables.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -265,19 +265,11 @@ Follow the steps below to change your schema name:

## Track event tables

Track event tables provide a complete event history, with one table for each unique named Track event. Segment syncs events based on the event sources you've connected to Unify.

These tables include a full set of Track event properties, with one column for each property.

Segment's Identity Resolution has processed these events, which contain a `segment_id`, enabling the data to be joined into a single profile record.

> success ""
> These tables will have two months of historical data on backfill.

> info ""
> To view and select individual track tables, edit your sync settings after you enable Profiles Sync, and wait for the initial sync to complete.
Track event tables provide a complete event history, with one table for each unique Track event name. Segment syncs events based on the sources you’ve connected to Unify, and includes a column for each event property.

Each row also includes a `segment_id`, assigned by Identity Resolution, which you can use to join events to profile records. In rare cases where Identity Resolution fails, the `segment_id` may be `null`.

By default, Segment backfills these tables with two months of historical data. After the initial sync completes, you can view and manage individual track tables by editing your sync settings.

## Tables Segment materializes

Expand Down
Loading