Merge pull request #6297 from segmentio/master

CO Master back to develop 03_26_24

Author: cmastr

src/_data/sidenav/main.yml

@@ -321,21 +321,6 @@ sections:
       title: Sample Queries
     - path: /unify/profiles-sync/tables
       title: Tables & Materialized Views
-  - section_title: Linked Profiles 
-    slug: unify/linked-profiles
-    section:
-    - section_title: Setup Guides
-      slug: unify/linked-profiles/setup-guides
-      section: 
-        - path: /unify/linked-profiles/setup-guides/bigquery-setup
-          title: BigQuery Setup
-        - path: /unify/linked-profiles/setup-guides/snowflake-setup
-          title: Snowflake Setup
-        - path: /unify/linked-profiles/setup-guides/redshift-setup
-          title: Redshift Setup
-    - path: /unify/linked-profiles/linked-events
-      title: Linked Events
- 
   - section_title: Traits
     slug: unify/traits
     section:

src/engage/audiences/linked-audiences-use-cases.md

@@ -0,0 +1,61 @@
+---
+title: Linked Audiences Use Cases
+plan: engage-foundations
+beta: true
+hidden: true
+redirect_from: 
+    - '/unify/linked-profiles/linked-audiences-use-cases'
+hidden: false
+---
+
+Below are some example use cases to help you learn more about Linked Audiences.
+
+## Use case 1: Build an audience of users who have a credit card with an outstanding balance
+
+To build this audience, define a nested entity condition to relate a `Profile` to their:
+- `Account` entity
+- `Credit Card` entity where `credit_card.balance` is "Outstanding"
+
+In the Data Graph, `Account` and `Credit Card` are defined as entities and represented as separate tables in your data warehouse. 
+
+Relationships are defined between:
+- `Profile` and `Account`
+- `Account` and `Credit Card` 
+
+In the warehouse, `credit_card.balance` is a column in the `Credit Card` table. By filtering against the `credit_card.balance` column for the "Outstanding" value, marketers can return a list of users that have a credit card with an outstanding balance.
+
+## Use case 2: Build an audience of cat owners who are also a part of the platinum membership tier
+
+To build this audience, define a nested entity condition to relate a `Profile` to their:
+- `Household` entity
+- `Pet` entity where `pet.type` is "Cat"
+
+Define an audience membership condition to filter for users that are a member of the "Platinum membership tier" audience.
+
+In the Data Graph, `Households` and `Pets` are defined as entities and are represented as separate tables in your data warehouse.
+
+Relationships are defined between:
+- `Profiles` and `Households`
+- `Households` and `Pets`
+
+In the warehouse, `pets.type` is a column in the `pets` table. By filtering against the `pets.type` column for the "cat" value, marketers can return a list of users that have a cat.
+
+Then, adding the audience membership condition allows marketers to further refine their audience to only include users who are part of the "Platinum membership tier" audience.
+
+## Use case 3: Build an audience of credit card holders with a certain number of transactions
+
+To build this audience, define a nested entity condition to relate a `Profile` to their:
+- `Accounts` entity
+- `Subscriptions` entity where `subscriptions.tier` is "Premium"
+- `Transactions` entity where `transactions.count` is greater than five
+
+This nested entity condition has four levels of relationship depth.
+
+In the Data Graph, `Accounts`, `Credit Cards`, and `Transactions` are defined as entities.
+
+Relationships are defined between:
+- `Profiles` and `Accounts`
+- `Accounts` and `Credit Cards`
+- `Credit Cards` and `Transactions`
+
+In the warehouse, `subscriptions.tier` is a column in the `Subscriptions` table, and `transactions.count` is a column in the `Transactions` table. By filtering against the `subscriptions.tier` column for the "Premium" value, and the `transactions.count` column for values greater than five, marketers can return a list of users that have a premium account where there are greater than five transactions.

src/engage/audiences/linked-audiences.md

@@ -5,8 +5,8 @@ beta: true
 hidden: true
 ---
 
-> info "Segment's Data Graph is in private beta"
-> The Data Graph is in private beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. 
+> info "Segment's Data Graph is in public beta"
+> The Data Graph is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. 
 
 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. 
 
@@ -18,6 +18,13 @@ Make this relational data accessible to marketers and business stakeholders to e
 > success ""
 > 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"}.
 
+## Breaking changes 
+
+A breaking change occurs when deleting an entity or relationship that is being referenced by a data consumer. Note that an entity or relationship slug is immutable and treated as a delete if you make changes. Data consumers affected by breaking changes will fail on the next run. 
+
+### 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. 
 
 ## Prerequisites
 
@@ -347,11 +354,7 @@ To edit your Data Graph:
 1. Navigate to **Unify > Data Graph**.
 2. Select the **Builder** tab, and click **Edit Data Graph**.
 
-Deleting entities and relationships are not yet supported. 
-
-> info ""
-> While you can edit entities and relationships in the Data Graph, this may lead to errors in downstream services referencing these entities and relationships. Segment recommends you recreate your existing Linked Audience and/or remove the entity from your existing Linked Events mappings.
-
+A data consumer refers to a Segment feature referencing entities and relationships from the Data Graph.
 
 ## Next steps 
 

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

@@ -2,6 +2,7 @@
 title: Linked Events
 beta: true
 plan: unify
+hidden: true
 ---
 
 > info "Linked Events is in private beta"

src/unify/linked-profiles/linked-events.md

@@ -2,6 +2,7 @@
 title: BigQuery Setup
 beta: true
 plan: unify
+hidden: true
 ---
 
 > info "Linked Events is in private beta"

src/unify/linked-profiles/setup-guides/BigQuery-setup.md

@@ -2,6 +2,7 @@
 title: Redshift Setup
 beta: true
 plan: unify
+hidden: true
 ---
 
 > info "Linked Events is in private beta"

src/unify/linked-profiles/setup-guides/redshift-setup.md

@@ -2,6 +2,7 @@
 title: Snowflake Setup
 plan: unify
 beta: true
+hidden: true
 ---
 
 > info "Linked Profiles is in private beta"

src/unify/linked-profiles/setup-guides/snowflake-setup.md

@@ -28,12 +28,12 @@ The following table shows the supported Profiles Sync warehouse destinations and
 
 | Warehouse Destination      | Required steps    
 | -------------- | ----------- |
-| [Snowflake](/docs/connections/storage/catalog/snowflake/#getting-started) | Follow the steps in [Snowflake Getting Started](/connections/storage/catalog/snowflake/#getting-started) |
-| [Redshift](/docs/connections/storage/catalog/redshift/#getting-started)   | Follow the steps in [Redshift Getting Started](/connections/storage/catalog/redshift/#getting-started) |
-| [BigQuery](/docs/connections/storage/catalog/bigquery/) |                  
-| [Azure](/docs/connections/storage/catalog/azuresqldw/)                    | Follow the steps in [Azure Synapse Analytics Getting Started](/connections/storage/catalog/azuresqldw/#getting-started)  |
-| [Postgres](/docs/connections/storage/catalog/postgres/)                   | Follow the steps in [Postgres getting started](/docs/connections/storage/catalog/postgres/).                                                      |
-| [Databricks](/docs/unify/profiles-sync/profiles-sync-setup/databricks-profiles-sync/)  | Follow the steps in the [Databricks for Profiles Sync](/docs/unify/profiles-sync/profiles-sync-setup/databricks-profiles-sync/) guide.                  |
+| [Snowflake](/docs/connections/storage/catalog/snowflake/#getting-started) | Follow the steps in [Snowflake Getting Started](docs/connections/storage/catalog/snowflake/#getting-started). |
+| [Redshift](/docs/connections/storage/catalog/redshift/#getting-started)   | Follow the steps in [Redshift Getting Started](docs/connections/storage/catalog/redshift/#getting-started). |
+| [BigQuery](/docs/connections/storage/catalog/bigquery/) |                  Follow the steps in [BigQuery Getting Started](/docs/connections/storage/catalog/bigquery/#getting-started).
+| [Azure](/docs/connections/storage/catalog/azuresqldw/)                    | Follow the steps in [Azure Synapse Analytics Getting Started](docs/connections/storage/catalog/azuresqldw/#getting-started).  |
+| [Postgres](/docs/connections/storage/catalog/postgres/)                   | Follow the steps in [Postgres Getting Started](/docs/connections/storage/catalog/postgres/).                                                      |
+| [Databricks](/docs/unify/profiles-sync/profiles-sync-setup/databricks-profiles-sync/)  | Follow the steps in the [Databricks Getting Started](/docs/unify/profiles-sync/profiles-sync-setup/databricks-profiles-sync/#getting-started)).                   |
 
 After you’ve finished the required steps for your chosen warehouse, you’re ready to connect your warehouse to Segment. Because you’ll next enter credentials from the warehouse you just created, **leave the warehouse tab open to streamline setup.**