Skip to content

Commit e6a15c9

Browse files
Update data-graph.md
- Updated several descriptions - Updated some tab names - Updated compatible LA/LE warehouses to a table
1 parent 89346a7 commit e6a15c9

File tree

1 file changed

+16
-13
lines changed

1 file changed

+16
-13
lines changed

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

Lines changed: 16 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,9 @@ redirect_from:
77
- '/unify/linked-profiles/data-graph'
88
---
99

10-
The Data Graph is a semantic layer unifying all your customer datasets. You can define relationships between any entity data set in the warehouse and the Segment Profiles you send with Profiles Sync. The Data Graph enables businesses to map and understand the relationships between different datasets about their customers (accounts, subscriptions, households, products, etc.), and tie rich entity context back to the profile. Once defined, it allows you to make this relational data accessible to marketers and business stakeholders to empower them with all the data they need to create targeted and personalized customer engagements.
11-
- **[Linked Audiences](/docs/engage/audiences/linked-audiences/)**: Enables marketers to self-serve and build targeting logic based on any data sets mapped to the Data Graph. Start by building a [Data Graph](/docs/unify/data-graph/data-graph/) that defines relationships between any data set in the warehouse and the Segment Profiles you send with Profiles Sync. From there, use Linked Audiences to unlock a world of new hyper-personalized campaigns.
12-
- **[Linked Events](/docs/unify/data-graph/linked-events/)**: Enables data teams to enrich event streams, in real time, with any data set coming from a data warehouse or data lake, and send those enriched events to any Destination. Start by building a [Data Graph](/docs/unify/data-graph/data-graph/) with the data models you want to use, and then use set up the enrichment in Destinations or Functions.
10+
The Data Graph is a semantic layer unifying all your customer datasets, enabling you to define relationships between any entity data set in the warehouse (i.e. accounts, subscriptions, households, products, etc) with the Segment Profiles you send with Profiles Sync. Once defined, the Data Graph allows you to make this rich relational data accessible to marketers and business stakeholders to empower them to create targeted and personalized customer engagements.
11+
- **[Linked Audiences](/docs/engage/audiences/linked-audiences/)**: Enables marketers to self-serve and build targeting logic based on any data sets defined in the Data Graph unlocking a world of new hyper-personalized campaigns.
12+
- **[Linked Events](/docs/unify/data-graph/linked-events/)**: Enables data teams to enrich event streams, in real time, with any data set coming from a data warehouse or data lake, and send those enriched events to any Destination. Available for Destinations Actions and Functions.
1313

1414
> info ""
1515
> Data Graph currently only supports workspaces in the United States.
@@ -27,9 +27,12 @@ To use the Data Graph, you'll need the following:
2727
> Data Graph, Reverse ETL, Profiles Sync require different warehouse permissions.
2828
2929
To get started with the Data Graph, set up the required permissions in your warehouse:
30-
31-
- [Snowflake](/docs/unify/data-graph/setup-guides/snowflake-setup/) and [Databricks](/docs/unify/data-graph/setup-guides/databricks-setup/) are supported by both Linked Events and Linked Audiences.
32-
- [Redshift](/docs/unify/data-graph/setup-guides/redshift-setup/) and [BigQuery](/docs/unify/data-graph/setup-guides/BigQuery-setup/) are currently supported for Linked Events.
30+
| Warehouse | Linked Audiences | Linked Events |
31+
| ----------- | --------------------------------------- | ------------------------------ |
32+
| [Snowflake](/docs/unify/data-graph/setup-guides/snowflake-setup/) |:white_check_mark: | :white_check_mark: |
33+
| [Databricks](/docs/unify/data-graph/setup-guides/databricks-setup/) | :white_check_mark: | :white_check_mark: |
34+
| [Redshift](/docs/unify/data-graph/setup-guides/redshift-setup/) | :x:| :white_check_mark: |
35+
| [BigQuery](/docs/unify/data-graph/setup-guides/BigQuery-setup/) | :x:| :white_check_mark: |
3336

3437
To track what data has been sent to Segment on previous syncs, Segment leverages Reverse ETL infrastructure to store diffs in tables within a single schema called `_segment_reverse_etl` in your data warehouse. You can choose which database or project in your warehouse this data lives in.
3538

@@ -38,7 +41,7 @@ To track what data has been sent to Segment on previous syncs, Segment leverages
3841
To connect your warehouse to the Data Graph:
3942

4043
1. Navigate to **Unify > Data Graph**. This should be a Unify space with Profiles Sync already set up.
41-
2. Click **Connect warehouse**.
44+
2. Click **Add warehouse**.
4245
3. Select your warehouse type.
4346
4. Enter your warehouse credentials.
4447
5. Test your connection, then click **Save**.
@@ -51,9 +54,9 @@ The Data Graph is a semantic layer that represents a subset of relevant business
5154
- Validate your Data Graph using the **Preview** tab
5255

5356
### Data Graph structure
54-
- Define your entities. This corresponds to tables in your warehouse.
57+
- Define your entities. Each entity corresponds to a table in your warehouse.
5558
- Define the profile. This maps to the Segment Profiles tables synced via Profiles Sync.
56-
- Define the relationship type.
59+
- Define the relationship.
5760
- The Data Graph supports three relationship types: 1) profile:entity 2) 1:many, and 3) many:many.
5861
- It currently supports 6 layers of depth, including the profile. There are no limits on the breadth of your Data Graph.
5962
- Relationships are nested under the profile.
@@ -140,7 +143,7 @@ data_graph {
140143

141144
### c) Define relationships
142145

143-
Now define your relationships across your entities. The Data Graph supports three types of relationships:
146+
Now define your relationships between your entities. The Data Graph supports three types of relationships:
144147
- Profile-to-entity relationship. This is the first level of relationships
145148
- 1:many relationship
146149
- Many:many relationship
@@ -398,19 +401,19 @@ data_graph {
398401
To edit your Data Graph:
399402

400403
1. Navigate to **Unify > Data Graph**.
401-
2. Select the **Builder** tab, and click **Edit Data Graph**.
404+
2. Select the **Overview** tab, and click **Edit Data Graph**.
402405

403406
### View Data Graph data consumers
404407

405408
A data consumer refers to a Segment feature (e.g. Linked Events, Linked Audiences) referencing datasetes, such as entities and/or relationships, from the Data Graph. You can view a list of data consumers in two places:
406409
- Under **Unify > Data Graph**, click the **Data consumers** tab
407-
- Click into a node on the Data Graph preview and a side sheet will pop up with the list of data consumers for the respective relationship
410+
- Under **Unify > Data Graph > Overview** or the **Data Graph editor > Preview**, click into a node on the Data Graph preview and a side sheet will pop up with the list of data consumers for the respective relationship
408411

409412
### Understand changes that may cause breaking and potential breaking changes
410413

411414
Upon saving changes to your Data Graph, a modal will pop up to warn of breaking and/or potential breaking changes to your data consumers. You must acknowledge and click **Confirm and save** in order to proceed.
412415
- **Definite breaking change**: Occurs when deleting an entity or relationship that is being referenced by a data consumer. Data consumers affected by breaking changes will fail on the next run. Note: The entity and relationship `slug` are immutable and treated as a delete if you make changes. You can modify the `label`.
413-
- **Potential breaking change**: Editing the Data Graph may lead to errors with data consumers. If there’s a breaking change, the data consumer will fail on the next run. Unaffected data consumers will continue to work.
416+
- **Potential breaking change**: Some changes such as updating the entity 'table_ref' or 'primary_key', may lead to errors with data consumers. If there’s a breaking change, the data consumer will fail on the next run. Unaffected data consumers will continue to work.
414417

415418
### Detect warehouse breaking changes
416419

0 commit comments

Comments
 (0)