From 27d58b2ef79175bf0f2b472b96d38535043ebfe7 Mon Sep 17 00:00:00 2001 From: ksaha873 Date: Wed, 28 May 2025 20:49:26 +0530 Subject: [PATCH 1/4] Update tables.md ### What: Adding warning for null ```segment_id``` in Track event tables in cases where ID resolution has failed. ### Why: Request for change in documentation following this issue: [Null segment_ids in tables](https://twilio-engineering.atlassian.net/browse/PS-403). --- src/unify/profiles-sync/tables.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/unify/profiles-sync/tables.md b/src/unify/profiles-sync/tables.md index e7d563b0d0..05c319035c 100644 --- a/src/unify/profiles-sync/tables.md +++ b/src/unify/profiles-sync/tables.md @@ -277,6 +277,9 @@ Segment's Identity Resolution has processed these events, which contain a `segme > 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. +> warning "" +> These tables may have null segment_id in rare cases where ID resolution has failed, which could happen due to multiple reasons. + ## Tables Segment materializes From 66dc7ff0f2d20c4388ddc2dcc08bc5653f8b49bf Mon Sep 17 00:00:00 2001 From: ksaha873 Date: Wed, 28 May 2025 20:52:48 +0530 Subject: [PATCH 2/4] Update tables.md --- src/unify/profiles-sync/tables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/unify/profiles-sync/tables.md b/src/unify/profiles-sync/tables.md index 05c319035c..af4ddc392f 100644 --- a/src/unify/profiles-sync/tables.md +++ b/src/unify/profiles-sync/tables.md @@ -278,7 +278,7 @@ Segment's Identity Resolution has processed these events, which contain a `segme > To view and select individual track tables, edit your sync settings after you enable Profiles Sync, and wait for the initial sync to complete. > warning "" -> These tables may have null segment_id in rare cases where ID resolution has failed, which could happen due to multiple reasons. +> These tables may have null segment_id in situations where ID resolution has failed, which is a very rare but possible occurrence. From 98ab7bb94a17820985c132012bd55a29aaf578b7 Mon Sep 17 00:00:00 2001 From: ksaha873 Date: Wed, 28 May 2025 20:53:20 +0530 Subject: [PATCH 3/4] Update tables.md --- src/unify/profiles-sync/tables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/unify/profiles-sync/tables.md b/src/unify/profiles-sync/tables.md index af4ddc392f..30c6530724 100644 --- a/src/unify/profiles-sync/tables.md +++ b/src/unify/profiles-sync/tables.md @@ -278,7 +278,7 @@ Segment's Identity Resolution has processed these events, which contain a `segme > To view and select individual track tables, edit your sync settings after you enable Profiles Sync, and wait for the initial sync to complete. > warning "" -> These tables may have null segment_id in situations where ID resolution has failed, which is a very rare but possible occurrence. +> These tables may have null segment_id in situations where ID resolution has failed, which is a rare but possible occurrence. From e5a3e5df83d4d71e32ca7ad3063209c649e19cc2 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Thu, 29 May 2025 16:20:29 -0500 Subject: [PATCH 4/4] rewording --- src/unify/profiles-sync/tables.md | 17 +++-------------- 1 file changed, 3 insertions(+), 14 deletions(-) diff --git a/src/unify/profiles-sync/tables.md b/src/unify/profiles-sync/tables.md index 30c6530724..a40ddab975 100644 --- a/src/unify/profiles-sync/tables.md +++ b/src/unify/profiles-sync/tables.md @@ -265,22 +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. - -> warning "" -> These tables may have null segment_id in situations where ID resolution has failed, which is a rare but possible occurrence. +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