Skip to content

Update tables.md #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.

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

Open
wants to merge 7 commits into
base: develop
Choose a base branch
from
Open

Update tables.md #7652

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
889591b
Update tables.md
ksaha873 May 30, 2025
a6972d2
Update tables.md
ksaha873 May 30, 2025
8884c75
Update tables.md
ksaha873 May 30, 2025
307d5fc
Update tables.md
ksaha873 May 30, 2025
6e7f1bc
Update tables.md
ksaha873 May 30, 2025
e2d6a54
Update tables.md
ksaha873 May 30, 2025
20f63b7
Update tables.md
ksaha873 May 30, 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
6 changes: 4 additions & 2 deletions src/unify/profiles-sync/tables.md
View file
Open in desktop
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.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So we do not want to set to the current timestamp also? Also what is this timestamp? What does it refer to?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

timestamp refers to the instant at which the event wad ingested into Segment. For backfill, we don't refer to individual events, but to the final profile state. So we don't have access to the original event timestamps.


### 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 [[email protected]](mailto:[email protected]) 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