From 889591bcb14fcb46f6bde60bf3572e4ed0cbfc74 Mon Sep 17 00:00:00 2001 From: ksaha873 Date: Fri, 30 May 2025 17:28:29 +0530 Subject: [PATCH 01/10] Update tables.md --- src/unify/profiles-sync/tables.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/src/unify/profiles-sync/tables.md b/src/unify/profiles-sync/tables.md index a40ddab975..f10f49df2b 100644 --- a/src/unify/profiles-sync/tables.md +++ b/src/unify/profiles-sync/tables.md @@ -105,7 +105,9 @@ Profile raw tables contain records of changes to your Segment profiles and Ident With raw tables, you have full control over the materialization of Profiles in your warehouse, as well as increased observibility. -Raw tables contain complete historical data when using historical backfill. +Raw tables contain complete historical data when using historical backfill. + +Note: `Timestamp` column will be empty for backfilled data. This is because reverse engineer historical profile changes from the current state of the profile. ### The id_graph_updates table @@ -296,7 +298,7 @@ If you're not using materialized views for Profile Sync and would like to switch 2. **Request a Full Profiles and Events Backfill** - After enabling the materialized views, you'll need to ensure historical data is populated in the materialized tables. - Write to [friends@segment.com](mailto:friends@segment.com) and request: - - A full **Profiles Backfill** to populate historical profiles data. + - A full **Profiles Backfill** to populate historical profiles data. Materialized views will have nil `Timestamp` for the same reason as Profile events table, discussed above. - An **Events Backfill** to include any relevant historical events, including a date range for Segment to pull data in for the events backfill. 3. **Verify Your Data** From a6972d2b400b8a3dfad7d99436dea28be296d5cc Mon Sep 17 00:00:00 2001 From: ksaha873 Date: Fri, 30 May 2025 17:33:26 +0530 Subject: [PATCH 02/10] Update tables.md --- src/unify/profiles-sync/tables.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/unify/profiles-sync/tables.md b/src/unify/profiles-sync/tables.md index f10f49df2b..62de487d25 100644 --- a/src/unify/profiles-sync/tables.md +++ b/src/unify/profiles-sync/tables.md @@ -107,7 +107,7 @@ With raw tables, you have full control over the materialization of Profiles in y Raw tables contain complete historical data when using historical backfill. -Note: `Timestamp` column will be empty for backfilled data. This is because reverse engineer historical profile changes from the current state of the profile. +Note: `Timestamp` column will be empty for backfilled data. This is because reverse engineer historical profile changes from the current state of the profile, and do not have access to the actual event timestamps. ### The id_graph_updates table @@ -298,7 +298,7 @@ If you're not using materialized views for Profile Sync and would like to switch 2. **Request a Full Profiles and Events Backfill** - After enabling the materialized views, you'll need to ensure historical data is populated in the materialized tables. - Write to [friends@segment.com](mailto:friends@segment.com) and request: - - A full **Profiles Backfill** to populate historical profiles data. Materialized views will have nil `Timestamp` for the same reason as Profile events table, discussed above. + - A full **Profiles Backfill** to populate historical profiles data. Materialized views will have nil `Timestamp` for the same reason as in Profile events table, discussed above. - An **Events Backfill** to include any relevant historical events, including a date range for Segment to pull data in for the events backfill. 3. **Verify Your Data** From 8884c7570fb9391c125212b6a95f7081bf37732e Mon Sep 17 00:00:00 2001 From: ksaha873 Date: Fri, 30 May 2025 17:36:25 +0530 Subject: [PATCH 03/10] 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 62de487d25..6224c42170 100644 --- a/src/unify/profiles-sync/tables.md +++ b/src/unify/profiles-sync/tables.md @@ -107,7 +107,7 @@ With raw tables, you have full control over the materialization of Profiles in y Raw tables contain complete historical data when using historical backfill. -Note: `Timestamp` column will be empty for backfilled data. This is because reverse engineer historical profile changes from the current state of the profile, and do not have access to the actual event timestamps. +Note: `Timestamp` column will be empty for backfilled data. This is because we reverse engineer historical profile changes from the current state of the profile, and do not have access to the actual event timestamps. ### The id_graph_updates table From 307d5fc55b667defe158c7dcc59be2a96926406a Mon Sep 17 00:00:00 2001 From: ksaha873 Date: Fri, 30 May 2025 17:37:01 +0530 Subject: [PATCH 04/10] 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 6224c42170..d1891b5b38 100644 --- a/src/unify/profiles-sync/tables.md +++ b/src/unify/profiles-sync/tables.md @@ -107,7 +107,7 @@ With raw tables, you have full control over the materialization of Profiles in y Raw tables contain complete historical data when using historical backfill. -Note: `Timestamp` column will be empty for backfilled data. This is because we reverse engineer historical profile changes from the current state of the profile, and do not have access to the actual event timestamps. +Note: `Timestamp` column will be empty for backfilled data. This is because we reverse engineer historical profile changes from the current state of the profile, and do not have access to the actual change timestamps. ### The id_graph_updates table From 6e7f1bce78c95ce188c6cfec06e25166100595de Mon Sep 17 00:00:00 2001 From: ksaha873 Date: Fri, 30 May 2025 17:37:38 +0530 Subject: [PATCH 05/10] 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 d1891b5b38..5e9e13b114 100644 --- a/src/unify/profiles-sync/tables.md +++ b/src/unify/profiles-sync/tables.md @@ -298,7 +298,7 @@ If you're not using materialized views for Profile Sync and would like to switch 2. **Request a Full Profiles and Events Backfill** - After enabling the materialized views, you'll need to ensure historical data is populated in the materialized tables. - Write to [friends@segment.com](mailto:friends@segment.com) and request: - - A full **Profiles Backfill** to populate historical profiles data. Materialized views will have nil `Timestamp` for the same reason as in Profile events table, discussed above. + - A full **Profiles Backfill** to populate historical profiles data. Materialized views will have null `Timestamp` for the same reason as in Profile events table, discussed above. - An **Events Backfill** to include any relevant historical events, including a date range for Segment to pull data in for the events backfill. 3. **Verify Your Data** From e2d6a544441cce8606373c3b1cffb7faa9e03182 Mon Sep 17 00:00:00 2001 From: ksaha873 Date: Fri, 30 May 2025 17:41:57 +0530 Subject: [PATCH 06/10] 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 5e9e13b114..196ea67af4 100644 --- a/src/unify/profiles-sync/tables.md +++ b/src/unify/profiles-sync/tables.md @@ -107,7 +107,7 @@ With raw tables, you have full control over the materialization of Profiles in y Raw tables contain complete historical data when using historical backfill. -Note: `Timestamp` column will be empty for backfilled data. This is because we reverse engineer historical profile changes from the current state of the profile, and do not have access to the actual change timestamps. +Note: `Timestamp` column will be empty for backfilled data. This is because we reverse engineer historical profile changes from the current state of the profile, and do not use the actual change timestamps. ### The id_graph_updates table From 20f63b70a5b439c7b239db669909b21a823f51fa Mon Sep 17 00:00:00 2001 From: ksaha873 Date: Fri, 30 May 2025 17:43:01 +0530 Subject: [PATCH 07/10] 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 196ea67af4..29ca239bf0 100644 --- a/src/unify/profiles-sync/tables.md +++ b/src/unify/profiles-sync/tables.md @@ -107,7 +107,7 @@ With raw tables, you have full control over the materialization of Profiles in y Raw tables contain complete historical data when using historical backfill. -Note: `Timestamp` column will be empty for backfilled data. This is because we reverse engineer historical profile changes from the current state of the profile, and do not use the actual change timestamps. +Note: `Timestamp` column will be empty for backfilled data. This is because we reverse engineer historical profile changes from the current state of the profile, and do not refer to the actual change history. ### The id_graph_updates table From ae95ff58efb500b9a3ae24a3fe5e1a7775f43cc3 Mon Sep 17 00:00:00 2001 From: ksaha873 Date: Thu, 12 Jun 2025 19:57:05 +0530 Subject: [PATCH 08/10] Update tables.md --- src/unify/profiles-sync/tables.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/unify/profiles-sync/tables.md b/src/unify/profiles-sync/tables.md index 29ca239bf0..b96ac9aa56 100644 --- a/src/unify/profiles-sync/tables.md +++ b/src/unify/profiles-sync/tables.md @@ -107,7 +107,7 @@ With raw tables, you have full control over the materialization of Profiles in y Raw tables contain complete historical data when using historical backfill. -Note: `Timestamp` column will be empty for backfilled data. This is because we reverse engineer historical profile changes from the current state of the profile, and do not refer to the actual change history. +Note: `Timestamp` column will be empty for backfilled data. This is because we infer historical profile changes from the current state of the profile, and do not refer to the actual change history. ### The id_graph_updates table @@ -298,7 +298,7 @@ If you're not using materialized views for Profile Sync and would like to switch 2. **Request a Full Profiles and Events Backfill** - After enabling the materialized views, you'll need to ensure historical data is populated in the materialized tables. - Write to [friends@segment.com](mailto:friends@segment.com) and request: - - A full **Profiles Backfill** to populate historical profiles data. Materialized views will have null `Timestamp` for the same reason as in Profile events table, discussed above. + - A full **Profiles Backfill** to populate historical profiles data. - An **Events Backfill** to include any relevant historical events, including a date range for Segment to pull data in for the events backfill. 3. **Verify Your Data** From 8e8f01c5173bf935b9b88efd1b024120310164aa Mon Sep 17 00:00:00 2001 From: ksaha873 Date: Thu, 12 Jun 2025 19:58:52 +0530 Subject: [PATCH 09/10] 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 b96ac9aa56..c667834d2e 100644 --- a/src/unify/profiles-sync/tables.md +++ b/src/unify/profiles-sync/tables.md @@ -107,7 +107,7 @@ With raw tables, you have full control over the materialization of Profiles in y Raw tables contain complete historical data when using historical backfill. -Note: `Timestamp` column will be empty for backfilled data. This is because we infer historical profile changes from the current state of the profile, and do not refer to the actual change history. +Note: `Timestamp` column will be empty for backfilled data. This is because during backfill, we infer historical profile changes from the current state of the profile, and do not refer to the actual change history. ### The id_graph_updates table From f31b8c6990775ff307ee5c2aebb22d6b1969d2c4 Mon Sep 17 00:00:00 2001 From: ksaha873 Date: Fri, 13 Jun 2025 15:45:48 +0530 Subject: [PATCH 10/10] Update src/unify/profiles-sync/tables.md Co-authored-by: Sharon Adewusi --- 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 c667834d2e..379cdb140b 100644 --- a/src/unify/profiles-sync/tables.md +++ b/src/unify/profiles-sync/tables.md @@ -107,7 +107,7 @@ With raw tables, you have full control over the materialization of Profiles in y Raw tables contain complete historical data when using historical backfill. -Note: `Timestamp` column will be empty for backfilled data. This is because during backfill, we infer historical profile changes from the current state of the profile, and do not refer to the actual change history. +The `Timestamp` column will be empty for backfilled data because, during backfill, historical profile changes are inferred from the current state of the profile and do not reflect the actual change history. ### The id_graph_updates table