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/linked-profiles/data-graph.md
+22-39Lines changed: 22 additions & 39 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,17 +6,19 @@ hidden: true
6
6
---
7
7
8
8
> info "Segment's Data Graph is in public beta"
9
-
> The Data Graph is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.
9
+
> Data Graph is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.
10
10
11
-
With Linked Profiles, you can build a Data Graph that defines relationships between any entity data set in the warehouse and the Segment Profiles you send with Profiles Sync.
11
+
With Linked Profiles, you can build a Data Graph that defines relationships between any entity data set in the warehouse and the Segment Profiles you send with Profiles Sync. Make this relational data accessible to marketers and business stakeholders to empower them with the data they need to create targeted and personalized customer engagements.
12
12
13
-
Make this relational data accessible to marketers and business stakeholders to empower them with the data they need to create targeted and personalized customer engagements.
13
+
Segment's Data Graph powers [Linked Events](/docs/unify/linked-profiles/linked-events/)and [Linked Audiences](/docs/engage/audiences/linked-audiences/).
14
14
15
-
> info ""
16
-
> Segment's Data Graph powers [Linked Events](/docs/unify/linked-profiles/linked-events/) and [Linked Audiences](/docs/engage/audiences/linked-audiences/).
15
+
To help you get started with the Data Graph, [view this short setup demo](https://drive.google.com/file/d/1oZNvs0raYaxK6tds3OEF0Ri3NGVCoXys/view?pli=1){:target="_blank"}.
17
16
18
-
> success ""
19
-
> To help you get started with the Data Graph, [view this short setup demo](https://drive.google.com/file/d/1oZNvs0raYaxK6tds3OEF0Ri3NGVCoXys/view?pli=1){:target="_blank"}.
17
+
> > info ""
18
+
> Linked Profiles follows zero-copy principles, and doesn't copy entities to store in Segment. Segment stores and processes all data in the United States.
19
+
20
+
> warning ""
21
+
> Don't send any personal health information with the Data Graph.
20
22
21
23
## Breaking changes
22
24
@@ -29,62 +31,45 @@ Editing the Data Graph may lead to errors with data consumers. If there’s a br
29
31
## Prerequisites
30
32
31
33
To use the Data Graph, you'll need the following:
34
+
32
35
- A supported data warehouse.
33
36
-[Profiles Sync](/docs/unify/profiles-sync/) set up with ready-to-use [data models and tables](/docs/unify/profiles-sync/tables/) in your warehouse.
34
-
35
-
> info ""
36
-
> Linked Profiles follows zero-copy principles, and doesn't copy entities to store in Segment. Segment stores and processes all data in the United States.
37
-
38
-
> warning ""
39
-
> Don't send any personal health information with the Data Graph.
37
+
- Workspace Owner or Unify Read-only/Admin and Entities Admin permissions.
40
38
41
39
## Step 1: Set up required permissions in your data warehouse
42
40
43
-
To get started, you'll need to navigate to the appropriate guide below to set up the required permissions in your data warehouse:
41
+
To get started, set up the required permissions in your data warehouse using the instructions below:
42
+
44
43
-[Snowflake](/docs/unify/linked-profiles/setup-guides/snowflake-setup/) is supported by both Linked Events and Linked Audiences.
45
44
-[Redshift](/docs/unify/linked-profiles/setup-guides/redshift-setup/) and [BigQuery](/docs/unify/linked-profiles/setup-guides/BigQuery-setup/) are currently supported for Linked Events.
46
45
47
46
Linked Profiles uses [Segment's Reverse ETL](/docs/connections/reverse-etl/) infrastructure to pull data from your warehouse.
48
47
49
48
To track what data has been sent to Segment on previous syncs, Segment stores delta/diffs in tables within a single schema called `_segment_reverse_etl` in your data warehouse. You can choose which database/project in your warehouse this data lives in.
50
49
51
-
52
50
## Step 2: Connect your warehouse to the Data Graph
53
51
54
-
> warning "Segment user permissions"
55
-
> You must have Workspace Owner or Unify Read-only/Admin and Entities Admin permissions to set up Linked Profiles.
56
-
57
-
> success ""
58
-
> Before getting started with the Data Graph, be sure to set up your warehouse permissions.
59
-
60
52
To connect your warehouse to the Data Graph:
61
53
62
54
1. Navigate to **Unify > Data Graph**.
63
-
-This should be a Unify space with Profiles Sync already set up.
55
+
This should be a Unify space with Profiles Sync already set up.
64
56
2. Click **Connect warehouse**.
65
57
3. Select your warehouse type.
66
-
-Note that Linked Audiences only supports Snowflake.
58
+
**Note:** Linked Audiences only supports Snowflake.
67
59
4. Enter your warehouse credentials.
68
60
5. Test your connection, then click **Save**.
69
61
70
62
## Step 3: Build your Data Graph
71
63
72
-
> warning ""
73
-
> Warehouse schemas are case sensitive, so you'll need to reflect the schema, table, and column names based on how you case them in the warehouse.
74
-
75
-
The Data Graph is a semantic layer that represents a subset of relevant business data that you'll use for audience targeting and personalization in downstream tools.
76
-
77
-
Use the configuration language spec below to add models to build your Data Graph. The Data Graph currently supports 4 layers of depth, including the Profile entity.
78
-
64
+
The Data Graph is a semantic layer that represents a subset of relevant business data that you'll use for audience targeting and personalization in downstream tools. Use the configuration language spec below to add models to build your Data Graph. The Data Graph currently supports 4 layers of depth, including the Profile entity. Warehouse schemas are case sensitive, so you'll need to reflect the schema, table, and column names based on how you case them in the warehouse.
79
65
80
66
### Define entities
81
67
82
68
Use the parameters, definitions, and examples below to help you define entities.
83
69
84
-
85
70
#### Profile
86
71
87
-
The profile is a special class of entity. The profile is always defined at the top of the Data Graph, and there can only be one profile for a Data Graph. The profile entity corresponds to the Profiles Sync tables and models, such as profile traits.
72
+
The profile is a special class of entity that is always defined at the top of the Data Graph, and there can only be one profile for a Data Graph. The profile entity corresponds to the Profiles Sync tables and models, such as profile traits.
88
73
89
74
The parameters are:
90
75
@@ -142,7 +127,6 @@ profile {
142
127
143
128
Use the following relationship, parameters, and examples to help you relate entities.
144
129
145
-
146
130
#### Relate Entity to Profile
147
131
148
132
| Parameters | Definition |
@@ -234,7 +218,7 @@ data_graph {
234
218
235
219
#### Relating entities with a junction table
236
220
237
-
If you're relating entities with a junction table:
221
+
If you're relating entities with a junction table:
@@ -244,10 +228,10 @@ If you're relating entities with a junction table:
244
228
|`left_join_on`| Defines the relationship between the two entity tables: `[left entity name].[column name] = [junction table column name]`. |
245
229
|`right_join_on`| Defines the relationship between the two entity tables: `[junction table column name] = [right entity name].[column name]`. |
246
230
247
-
Note that `schema.table`is implied within the junction table column name and doesn't need to be provided.
231
+
**Note:**`schema.table`is implied within the junction table column name and doesn't need to be provided.
248
232
249
233
> warning ""
250
-
> Attributes from a junction table are not referenceable with the Audience Builder. If you'd like to reference an additional column on the junction table for filtering, you must first define it as an entity and explicitly define a relationship name.
234
+
> Attributes from a junction table are not referenceable with the Audience Builder. If you'd like to reference an additional column on the junction table for filtering, you must first define it as an entity and explicitly define a relationship name.
251
235
252
236
Example:
253
237
@@ -275,7 +259,7 @@ data_graph {
275
259
}
276
260
277
261
```
278
-
## Data Graph Example
262
+
## Data Graph example
279
263
280
264
<img src="/docs/unify/images/data-graph-example.png" alt="An example of a Data Graph" width="5888"/>
281
265
@@ -358,5 +342,4 @@ A data consumer refers to a Segment feature referencing entities and relationshi
358
342
359
343
## Next steps
360
344
361
-
After you've set up your Data Graph, get started with [Linked Audiences](/docs/engage/audiences/linked-audiences/) and [Linked Events](/docs/unify/linked-profiles/linked-events/).
362
-
345
+
After you've set up your Data Graph, get started with [Linked Events](/docs/unify/linked-profiles/linked-events/) and [Linked Audiences](/docs/engage/audiences/linked-audiences/).
0 commit comments