|
| 1 | +--- |
| 2 | +title: Linked Audiences Use Cases |
| 3 | +plan: engage-foundations |
| 4 | +beta: true |
| 5 | +hidden: true |
| 6 | +redirect_from: |
| 7 | + - '/unify/linked-profiles/linked-audiences-use-cases' |
| 8 | +hidden: false |
| 9 | +--- |
| 10 | + |
| 11 | +Below are some example use cases to help you learn more about Linked Audiences. |
| 12 | + |
| 13 | +## Use case 1: Build an audience of users who have a credit card with an outstanding balance |
| 14 | + |
| 15 | +To build this audience, define a nested entity condition to relate a `Profile` to their: |
| 16 | +- `Account` entity |
| 17 | +- `Credit Card` entity where `credit_card.balance` is "Outstanding" |
| 18 | + |
| 19 | +In the Data Graph, `Account` and `Credit Card` are defined as entities and represented as separate tables in your data warehouse. |
| 20 | + |
| 21 | +Relationships are defined between: |
| 22 | +- `Profile` and `Account` |
| 23 | +- `Account` and `Credit Card` |
| 24 | + |
| 25 | +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. |
| 26 | + |
| 27 | +## Use case 2: Build an audience of cat owners who are also a part of the platinum membership tier |
| 28 | + |
| 29 | +To build this audience, define a nested entity condition to relate a `Profile` to their: |
| 30 | +- `Household` entity |
| 31 | +- `Pet` entity where `pet.type` is "Cat" |
| 32 | + |
| 33 | +Define an audience membership condition to filter for users that are a member of the "Platinum membership tier" audience. |
| 34 | + |
| 35 | +In the Data Graph, `Households` and `Pets` are defined as entities and are represented as separate tables in your data warehouse. |
| 36 | + |
| 37 | +Relationships are defined between: |
| 38 | +- `Profiles` and `Households` |
| 39 | +- `Households` and `Pets` |
| 40 | + |
| 41 | +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. |
| 42 | + |
| 43 | +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. |
| 44 | + |
| 45 | +## Use case 3: Build an audience of credit card holders with a certain number of transactions |
| 46 | + |
| 47 | +To build this audience, define a nested entity condition to relate a `Profile` to their: |
| 48 | +- `Accounts` entity |
| 49 | +- `Subscriptions` entity where `subscriptions.tier` is "Premium" |
| 50 | +- `Transactions` entity where `transactions.count` is greater than five |
| 51 | + |
| 52 | +This nested entity condition has four levels of relationship depth. |
| 53 | + |
| 54 | +In the Data Graph, `Accounts`, `Credit Cards`, and `Transactions` are defined as entities. |
| 55 | + |
| 56 | +Relationships are defined between: |
| 57 | +- `Profiles` and `Accounts` |
| 58 | +- `Accounts` and `Credit Cards` |
| 59 | +- `Credit Cards` and `Transactions` |
| 60 | + |
| 61 | +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. |
0 commit comments