Skip to content

Commit ee39462

Browse files
authored
data graph updates
1 parent 8e528c8 commit ee39462

File tree

1 file changed

+22
-39
lines changed

1 file changed

+22
-39
lines changed

src/unify/linked-profiles/data-graph.md

Lines changed: 22 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -6,17 +6,19 @@ hidden: true
66
---
77

88
> 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.
1010
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.
1212

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/).
1414

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"}.
1716

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.
2022
2123
## Breaking changes
2224

@@ -29,62 +31,45 @@ Editing the Data Graph may lead to errors with data consumers. If there’s a br
2931
## Prerequisites
3032

3133
To use the Data Graph, you'll need the following:
34+
3235
- A supported data warehouse.
3336
- [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.
4038

4139
## Step 1: Set up required permissions in your data warehouse
4240

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+
4443
- [Snowflake](/docs/unify/linked-profiles/setup-guides/snowflake-setup/) is supported by both Linked Events and Linked Audiences.
4544
- [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.
4645

4746
Linked Profiles uses [Segment's Reverse ETL](/docs/connections/reverse-etl/) infrastructure to pull data from your warehouse.
4847

4948
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.
5049

51-
5250
## Step 2: Connect your warehouse to the Data Graph
5351

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-
6052
To connect your warehouse to the Data Graph:
6153

6254
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.
6456
2. Click **Connect warehouse**.
6557
3. Select your warehouse type.
66-
- Note that Linked Audiences only supports Snowflake.
58+
**Note:** Linked Audiences only supports Snowflake.
6759
4. Enter your warehouse credentials.
6860
5. Test your connection, then click **Save**.
6961

7062
## Step 3: Build your Data Graph
7163

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.
7965

8066
### Define entities
8167

8268
Use the parameters, definitions, and examples below to help you define entities.
8369

84-
8570
#### Profile
8671

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.
8873

8974
The parameters are:
9075

@@ -142,7 +127,6 @@ profile {
142127

143128
Use the following relationship, parameters, and examples to help you relate entities.
144129

145-
146130
#### Relate Entity to Profile
147131

148132
| Parameters | Definition |
@@ -234,7 +218,7 @@ data_graph {
234218

235219
#### Relating entities with a junction table
236220

237-
If you're relating entities with a junction table:
221+
If you're relating entities with a junction table:
238222

239223
| Parameters | Definition |
240224
| ----------- | --------------------------------------------------------------------- |
@@ -244,10 +228,10 @@ If you're relating entities with a junction table:
244228
| `left_join_on` | Defines the relationship between the two entity tables: `[left entity name].[column name] = [junction table column name]`. |
245229
| `right_join_on` | Defines the relationship between the two entity tables: `[junction table column name] = [right entity name].[column name]`. |
246230

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.
248232

249233
> 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.
251235

252236
Example:
253237

@@ -275,7 +259,7 @@ data_graph {
275259
}
276260

277261
```
278-
## Data Graph Example
262+
## Data Graph example
279263

280264
<img src="/docs/unify/images/data-graph-example.png" alt="An example of a Data Graph" width="5888"/>
281265

@@ -358,5 +342,4 @@ A data consumer refers to a Segment feature referencing entities and relationshi
358342

359343
## Next steps
360344

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

Comments
 (0)