linked audiences use cases mini edit

Author: cmastr

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

@@ -7,54 +7,20 @@ redirect_from:
     - '/unify/linked-profiles/linked-audiences-use-cases'
 ---
 
-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
+Linked Audiences enables data teams and technical marketers to build powerful audiences directly from data in their warehouse, with a powerful audience builder designed to support relational data. Customers can take object data of any kind, (For example: products, bookings, accounts, and more) and relate it back to the profile data that lives within the warehouse, for activation across any channel supported by Engage Foundations.
 
-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
+Below are some example use cases to help you learn more about Linked Audiences.
 
-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
+## Drive Accelerated Onboarding 
 
-This nested entity condition has four levels of relationship depth.
+An orchestrated process simplifies the onboarding experience and empowers customers to make the most of the product, turning them from first time users into loyal subscribers. With Linked Audiences, brands can create custom campaigns based on a customer’s specific account details from the warehouse and usage history from real-time event streams. 
 
-In the Data Graph, `Accounts`, `Credit Cards`, and `Transactions` are defined as entities.
+**Example:** 
+Send a one-time onboarding email when a Business Tier account is opened with getting started directions based on their corporate policies.   
+Personalized Transactional Sends
 
-Relationships are defined between:
-- `Profiles` and `Accounts`
-- `Accounts` and `Credit Cards`
-- `Credit Cards` and `Transactions`
+Including personalized product information in transactional emails improves their open rates over generic marketing messages. For trust personalized, transactional sends are often triggered and then personalized using details of an related entity (account, course, pets, etc). Linked Audiences let you set up triggers based on the value of an entity and make it easy to enrich the message with any personalized content from the warehouse. 
 
-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.
+**Example:** 
+Send a one-time Past Due email to customers whose accounts have just become overdue with a past due amount.
+Send a weekly Course Completion Reminder email to any customer who hasn’t finished their Segment.