Skip to content

Commit a6972d2

Browse files
authored
Update tables.md
1 parent 889591b commit a6972d2

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/unify/profiles-sync/tables.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ With raw tables, you have full control over the materialization of Profiles in y
107107

108108
Raw tables contain complete historical data when using historical backfill.
109109

110-
Note: `Timestamp` column will be empty for backfilled data. This is because reverse engineer historical profile changes from the current state of the profile.
110+
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.
111111

112112
### The id_graph_updates table
113113

@@ -298,7 +298,7 @@ If you're not using materialized views for Profile Sync and would like to switch
298298
2. **Request a Full Profiles and Events Backfill**
299299
- After enabling the materialized views, you'll need to ensure historical data is populated in the materialized tables.
300300
- Write to [[email protected]](mailto:[email protected]) and request:
301-
- 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.
301+
- 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.
302302
- An **Events Backfill** to include any relevant historical events, including a date range for Segment to pull data in for the events backfill.
303303

304304
3. **Verify Your Data**

0 commit comments

Comments
 (0)