You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/unify/data-graph/index.md
+14-13Lines changed: 14 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -207,10 +207,10 @@ data_graph {
207
207
208
208
Next, define the profile. This is a special class of entity that represents Segment Profiles, which corresponds to the Profiles Sync tables and models. For Linked Audiences, this allows marketers to filter on profile traits, event history, etc. There can only be one profile for a Data Graph.
|`profile_folder`| Define the fully qualified path of the folder or schema location for the profile tables. |
213
-
|`type`| Identify the materialization method of the profile tables defined in your Profiles Syncconfiguration under [Selective Sync settings](/docs/unify/profiles-sync/profiles-sync-setup/#step-3-set-up-selective-sync): `segment:unmaterialized` or `segment:materialized`.|
|`profile_folder`| Define the fully qualified path of the folder or schema location for the profile tables.|
213
+
|`type`| Use `segment:materialized` to sync materialized views withProfiles Sync. Segment recommends this configuration forall Linked Audiences and Data Graph setups. If you can't sync materialized views, [reach out to Segment support](https://segment.com/help/contact/){:target="_blank"} for help. |
214
214
215
215
**Example:**
216
216
@@ -248,17 +248,18 @@ This is the first level of relationships and a unique type of relationship betwe
248
248
249
249
To define a profile-to-entity relationship, reference your entity table and depending on your table columns, choose to join on one of the following:
250
250
251
-
**Option 1 (Most common) - Join on an external ID:** Use the `external_id` block to join the profile entity with an entity table using external IDs from your [Unify ID resolution](/docs/unify/identity-resolution/externalids/) settings. Typically these identifiers are `user_id`, `email`, or`phone` depending on the column in the entity table that you want to join with.
252
-
-`type`: Represents the [external IDtype](/docs/unify/identity-resolution/externalids/#default-externalids) (`email`, `phone`, `user_id`) in your id-res settings. Depending on if you are using materialized or unmaterialized profiles, these correspond to different columns in your Profiles Sync warehouse tables:
253
-
- [Materialized](/docs/unify/profiles-sync/tables/#the-user_identifiers-table) (Recommended): This corresponds to the `type` column in your Profiles Sync `user_identifiers` table.
254
-
- [Unmaterialized](/docs/unify/profiles-sync/tables/#the-external_id_mapping_updates-table): This corresponds to the `external_id_type` column in your Profiles Sync `external_id_mapping_updates` table.
255
-
-`join_key`: This is the column on the entity table that you are matching to the external identifier.
251
+
**Option 1 (Most common) - Join on an external ID:** Use the `external_id` block to join the profile entity with an entity table using external IDs from your [Unify ID resolution](/docs/unify/identity-resolution/externalids/) settings. Typically these identifiers are `user_id`, `email`, or`phone` depending on the structure of your entity table.
252
+
-`type`: Represents the [external IDtype](/docs/unify/identity-resolution/externalids/#default-externalids) (`email`, `phone`, `user_id`) in your ID resolution settings.
253
+
- This maps to the `type` column in the `user_identifiers` table when using materialized views.
254
+
-`join_key`: The column on the entity table that matches the external ID.
255
+
256
+
> note ""
257
+
> Segment recommends using materialized views with Profiles Sync. However, Segment may still reference unmaterialized tables during setup for schema detection.
256
258
257
259
**Option 2- Join on a profile trait:** Use the `trait` block to join the profile entity with an entity table using [Profile Traits](/docs/unify/#enrich-profiles-with-traits).
258
-
-`name`: Represents a trait name in your Unify profiles. Depending on if you are using materialized or unmaterialized profiles, these correspond to different columns in your Profiles Sync warehouse tables:
259
-
- [Materialized](/docs/unify/profiles-sync/tables/#the-profile_traits-table) (Recommended): The trait name corresponds to a unique value of the `name` column in your Profiles Sync `user_traits` table.
260
-
- [Unmaterialized](/docs/unify/profiles-sync/tables/#the-profile_traits_updates-table): This corresponds to a column in the Profile Sync `profile_trait_updates` table.
261
-
-`join_key`: This is the column on the entity table that you are matching to the trait.
260
+
-`name`: Represents a trait name in your Unify profiles.
261
+
- This maps to the `name` column in the `user_traits` table when using materialized views.
262
+
-`join_key`: The column on the entity table that you're matching to the trait.
0 commit comments