Skip to content

Commit f9e352b

Browse files
committed
some more fixes
1 parent 703d2c0 commit f9e352b

File tree

1 file changed

+15
-14
lines changed

1 file changed

+15
-14
lines changed

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

Lines changed: 15 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -19,28 +19,29 @@ relational data into actionable insights, making it accessible to marketers and
1919

2020
To use the Data Graph, you'll need the following:
2121

22-
- A supported data warehouse with appropriate Data Graph permissions
23-
- For Linked Audiences, [Profiles Sync](/docs/unify/profiles-sync/) will need to be set up for a Unify space with ready-to-use [data models and tables](/docs/unify/profiles-sync/tables/) in your warehouse. When setting up selective sync, Segment recommends the following settings for Linked Audiences:
24-
- Under **Profile materialized tables**, select all the tables (`user_identifier`, `user_traits`, `profile_merges`) for faster and more cost-efficient Linked Audiences computations in your data warehouse.
25-
- Under **Track event tables**, select "Sync all Track Call Tables" to enable filtering on event history for Linked Audiences conditions.
22+
- A supported data warehouse with the appropriate Data Graph permissions
2623
- Workspace Owner or Unify Read-only/Admin and Entities Admin permissions
24+
- For Linked Audiences, set up [Profiles Sync](/docs/unify/profiles-sync/) in a Unify space with ready-to-use [data models and tables](/docs/unify/profiles-sync/tables/) in your warehouse. When setting up selective sync, Segment recommends the following settings for Linked Audiences:
25+
- Under **Profile materialized tables**, select all the tables (`user_identifier`, `user_traits`, `profile_merges`) for faster and more cost-efficient Linked Audiences computations in your data warehouse.
26+
- Under **Track event tables**, select **Sync all Track Call Tables** to enable filtering on event history for Linked Audiences conditions.
2727

2828
## Step 1: Set up Data Graph permissions in your data warehouse
2929
> warning ""
30-
> Data Graph, Reverse ETL, Profiles Sync require different warehouse permissions.
30+
> Data Graph, Reverse ETL, and Profiles Sync require different warehouse permissions.
31+
> info ""
32+
> Data Graph currently only supports workspaces in the United States.
3133
3234
To get started with the Data Graph, set up the required permissions in your warehouse:
33-
| Warehouse | Linked Audiences | Linked Events |
34-
| ----------- | --------------------------------------- | ------------------------------ |
35-
| [Snowflake](/docs/unify/data-graph/setup-guides/snowflake-setup/) |:white_check_mark: | :white_check_mark: |
36-
| [Databricks](/docs/unify/data-graph/setup-guides/databricks-setup/) | :white_check_mark: | :white_check_mark: |
37-
| [Redshift](/docs/unify/data-graph/setup-guides/redshift-setup/) | 📆 Coming soon| :white_check_mark: |
38-
| [BigQuery](/docs/unify/data-graph/setup-guides/BigQuery-setup/) | 📆 Coming soon| :white_check_mark: |
3935

40-
> info ""
41-
> Data Graph currently only supports workspaces in the United States.
36+
| Warehouse | Linked Audiences | Linked Events |
37+
| ------------------------------------------------------------------- | ------------------ | ------------------ |
38+
| [Snowflake](/docs/unify/data-graph/setup-guides/snowflake-setup/) | :white_check_mark: | :white_check_mark: |
39+
| [Databricks](/docs/unify/data-graph/setup-guides/databricks-setup/) | :white_check_mark: | :white_check_mark: |
40+
| [Redshift](/docs/unify/data-graph/setup-guides/redshift-setup/) | 📆 Coming soon | :white_check_mark: |
41+
| [BigQuery](/docs/unify/data-graph/setup-guides/BigQuery-setup/) | 📆 Coming soon | :white_check_mark: |
42+
4243

43-
To track what data has been sent to Segment on previous syncs, Segment leverages [Reverse ETL](/docs/connections/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.
44+
To track the data sent to Segment on previous syncs, Segment uses [Reverse ETL](/docs/connections/reverse-etl/) infrastructure to store diffs in tables within a dedicated schema called `_segment_reverse_etl` in your data warehouse. You can choose which database or project in your warehouse this data lives in.
4445

4546
## Step 2: Connect your warehouse to the Data Graph
4647

0 commit comments

Comments
 (0)