Skip to content

Note added on Timestamp column being null during backfill #7652

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.

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 10 commits into from
Jun 13, 2025
Merged
Changes from 7 commits
Commits
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
6 changes: 4 additions & 2 deletions src/unify/profiles-sync/tables.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 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

Expand Down Expand Up @@ -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 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**
Expand Down