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
|`entity`| An immutable slug for the entity, and will be treated as a delete if you make changes. The slug must be inall lowercase, and supports dashes or underscores (e.g`account-entity`or`account_entity`). |
181
-
|`description` (*Optional*) | An optional descriptor used to add additional context to the entity (E.g. table grain, cadence at which the table/view is refreshed, etc). |
182
-
|`name`| A label displayed throughout your Segment space for Linked Events, Linked Audiences, etc. This name can be modified at any time. |
180
+
|`entity`| An immutable slug for the entity, and will be treated as a delete if you make changes. The slug must be inall lowercase, and supports dashes or underscores (for example,`account-entity`or`account_entity`). |
181
+
|`description` (*Optional*) | An optional descriptor used to add additional context to the entity (for example, table grain, cadence at which the table/view is refreshed). |
182
+
|`name`| A label displayed throughout your Segment space for Linked Events, Linked Audiences. This name can be modified at any time. |
183
183
|`table_ref`| Defines the fully qualified table reference: `[database name].[schema name].[table name]`. Segment flexibly supports tables, views and materialized views. |
184
184
|`primary_key`| The unique identifier for the given table. Must be a column with unique values per row. |
185
185
| (If applicable) `enrichment_enabled = true`| Add this if you plan to reference the entity table for [Linked Events](/docs/unify/data-graph/linked-events/) use cases. |
@@ -248,10 +248,10 @@ This is the first level of relationships and a unique type of relationship betwe
|`relationship`| An immutable slug for the relationship, and will be treated as a delete if you make changes. The slug must be inall 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 |
251
+
|`relationship`| An immutable slug for the relationship, and will be treated as a delete if you make changes. The slug must be inall 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. This name can be modified at any time.|
253
253
|`description` (*Optional*) | An optional descriptor used to add additional context to the relationship. |
254
-
|`related_entity`|References your already defined entity |
254
+
|`related_entity`|This references the already defined entity.|
255
255
256
256
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:
257
257
@@ -315,11 +315,11 @@ For 1:many relationships, define the join on between the two entity tables using
|`relationship`| An immutable slug for the relationship, and will be treated as a delete if you make changes. The slug must be inall lowercase, and supports dashes or underscores (like `user-account`or`user_account`) |
318
+
|`relationship`| An immutable slug for the relationship, and will be treated as a delete if you make changes. The slug must be inall lowercase, and supports dashes or underscores (like `user-account`or`user_account`).|
319
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
320
|`description` (*Optional*) | An optional descriptor used to add additional context to the relationship. |
321
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 |
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.|
323
323
324
324
**Example:**
325
325
@@ -362,10 +362,10 @@ For many:many relationships, define the join on between the two entity tables wi
|`relationship`| An immutable slug for the relationship, and will be treated as a delete if you make changes. The slug must be inall lowercase, and supports dashes or underscores (like `user-account`or`user_account`) |
366
-
|`name`| A label displayed throughout your Segment space for Linked Events, Linked Audiences, and so on. This name can be modified at any time |
367
-
| (Optional) `description`| An optional descriptor used to add additional context to the relationship |
368
-
|`related_entity`|References your already defined entity |
365
+
|`relationship`| An immutable slug for the relationship, and will be treated as a delete if you make changes. The slug must be inall lowercase, and supports dashes or underscores (like `user-account`or`user_account`).|
366
+
|`name`| A label displayed throughout your Segment space for Linked Events, Linked Audiences, and so on. This name can be modified at any time.|
367
+
| (Optional) `description`| An optional descriptor used to add additional context to the relationship.|
368
+
|`related_entity`|This references your defined entity.|
0 commit comments