Skip to content

Commit 0f4e692

Browse files
authored
Update profile sync docs to include 3 steps
And provide additional guidance on materialization of views in the main docs page for Profile Sync
1 parent c4d4ff4 commit 0f4e692

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

src/profiles/profiles-sync/index.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -69,6 +69,19 @@ Profiles Sync sends Profiles to your warehouse on an hourly basis, beginning aft
6969

7070
By default, Segment includes identity graph updates, external ID mapping tables, and two months of the events table in the initial warehouse sync made during setup. Reach out to Segment support if your use case exceeds the scope of the initial setup backfill.
7171

72+
73+
### Step 3: Materialize key views using a SQL automation tool
74+
75+
To start seeing unified profiles in your warehouse and build attribution models, you'll need to materialize the tables landed by Profile Sync into three key views:
76+
77+
* `id_graph`: shows the current state of relationships between segment ids
78+
* `external_id_mapping`: current-state mapping between each external identifier you’ve observed and its corresponding, fully-merged `canonical_segment_id`
79+
* `profile_traits`: the last seen value for all custom traits, computed traits, SQL traits, audiences, and journeys associated with a profile in a single row
80+
81+
Please visit the [Tables you materialize](https://segment.com/docs/profiles/profiles-sync/tables/#tables-you-materialize) section of our Profile Sync docs for more inforamation on how to materialize these views either on your own, or with [Segment's open source dbt models](https://github.com/segmentio/profiles-sync-dbt)
82+
83+
84+
7285
## Working with synced warehouses
7386

7487
<!-- add transition line here -->

0 commit comments

Comments
 (0)