Skip to content

Commit 2cbe76a

Browse files
LLuque-twilioLLuque-twilio
committed
PR suggestions
1 parent b4edef9 commit 2cbe76a

File tree

1 file changed

+16
-16
lines changed

1 file changed

+16
-16
lines changed

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

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,8 @@
22
title: Data Graph
33
plan: unify
44
redirect_from:
5-
- "/unify/linked-profiles/data-graph"
6-
- "/unify/data-graph/data-graph"
5+
- '/unify/linked-profiles/data-graph'
6+
- '/unify/data-graph/data-graph'
77
---
88

99
The Data Graph acts as a semantic layer that allows businesses to define relationships between various entity datasets in the warehouse — such as accounts, subscriptions, households, and products — with the Segment Profile. It makes these relational datasets easily accessible to business teams for targeted and personalized customer engagements.
@@ -178,7 +178,7 @@ The first step in creating a Data Graph is to define your entities. An entity co
178178
| Parameters | Definition |
179179
| ------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
180180
| `entity` | An immutable slug for the entity, and will be treated as a delete if you make changes. The slug must be in all lowercase, and supports dashes or underscores (e.g `account-entity` or `account_entity`). |
181-
| (Optional) `description` | An optional descriptor used to add additional context to the entity |
181+
| `description` (*Optional*) | An optional descriptor used to add additional context to the entity. |
182182
| `name` | A label displayed throughout your Segment space for Linked Events, Linked Audiences, etc. This name can be modified at any time. |
183183
| `table_ref` | Defines the fully qualified table reference: `[database name].[schema name].[table name]`. Segment flexibly supports tables, views and materialized views. |
184184
| `primary_key` | The unique identifier for the given table. Must be a column with unique values per row. |
@@ -246,12 +246,12 @@ Now define your relationships between your entities. Similar to the concept of [
246246

247247
This is the first level of relationships and a unique type of relationship between the Segment profile entity and a related entity.
248248

249-
| Parameters | Definition |
250-
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
251-
| `relationship` | An immutable slug for the relationship, and will be treated as a delete if you make changes. The slug must be in all lowercase, and supports dashes or underscores (like `user-account` or `user_account`) |
252-
| `name` | A label displayed throughout your Segment space for Linked Events, Linked Audiences, etc. This name can be modified at any time |
253-
| (Optional) `description` | An optional descriptor used to add additional context to the relationship |
254-
| `related_entity` | References your already defined entity |
249+
| Parameters | Definition |
250+
| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
251+
| `relationship` | An immutable slug for the relationship, and will be treated as a delete if you make changes. The slug must be in all lowercase, and supports dashes or underscores (like `user-account` or `user_account`) |
252+
| `name` | A label displayed throughout your Segment space for Linked Events, Linked Audiences, etc. This name can be modified at any time |
253+
| `description` (*Optional*) | An optional descriptor used to add additional context to the relationship. |
254+
| `related_entity` | References your already defined entity |
255255

256256
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:
257257

@@ -313,13 +313,13 @@ data_graph {
313313

314314
For 1:many relationships, define the join on between the two entity tables using the spec below.
315315

316-
| Parameters | Definition |
317-
| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
318-
| `relationship` | An immutable slug for the relationship, and will be treated as a delete if you make changes. The slug must be in all lowercase, and supports dashes or underscores (like `user-account` or `user_account`) |
319-
| `name` | A label displayed throughout your Segment space for Linked Events, Linked Audiences, and so on. This name can be modified at any time |
320-
| (Optional) `description` | An optional descriptor used to add additional context to the relationship |
321-
| `related_entity` | References your already defined entity |
322-
| `join_on` | Defines relationship between the two entity tables `[lefty entity slug].[column name] = [right entity slug].[column name]`. Note that since you’re referencing the entity slug for the join on, you do not need to define the full table reference |
316+
| Parameters | Definition |
317+
| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
318+
| `relationship` | An immutable slug for the relationship, and will be treated as a delete if you make changes. The slug must be in all lowercase, and supports dashes or underscores (like `user-account` or `user_account`) |
319+
| `name` | A label displayed throughout your Segment space for Linked Events, Linked Audiences, and so on. This name can be modified at any time |
320+
| `description` (*Optional*) | An optional descriptor used to add additional context to the relationship. |
321+
| `related_entity` | References your already defined entity |
322+
| `join_on` | Defines relationship between the two entity tables `[lefty entity slug].[column name] = [right entity slug].[column name]`. Note that since you’re referencing the entity slug for the join on, you do not need to define the full table reference |
323323

324324
**Example:**
325325

0 commit comments

Comments
 (0)