|
| 1 | +--- |
| 2 | +title: Linked Audiences |
| 3 | + |
| 4 | +--- |
| 5 | + |
| 6 | +With Linked Audiences, you can use the relational data you've defined in your Data Graph to build audiences and send them to your downstream destinations. |
| 7 | + |
| 8 | +From the relationships you've defined between a profile and entities, you can filter on profile traits, entity attributes, and associated events to create audiences. |
| 9 | + |
| 10 | +> success "" |
| 11 | +> Before you build Linked Audiences, be sure you've defined entities in your [Data Graph](/docs/unify/linked-profiles/data-graph/). |
| 12 | +
|
| 13 | + |
| 14 | +## Getting started |
| 15 | + |
| 16 | +To help you get started with Linked Audiences, keep the following guidelines in mind. |
| 17 | + |
| 18 | +- It may be helpful to first identify an entity that is directly associated with your users, such as `Accounts`, `Households`, or `Organizations`. |
| 19 | +- From there you can define relationships between this entity with any of the other entities that may be directly associated with it, such as how `Accounts` can have the following: |
| 20 | + - `Subscriptions` |
| 21 | + - `Purchases` |
| 22 | + - `Carts` |
| 23 | +- You can create entity relationships up to four levels in depth. For example, you can build an entity condition that queries for relationships between `Profiles`, `Accounts`, `Credit Cards`, and finally `Transactions`. |
| 24 | +- Along the way, identify column values that you might also want to filter your entities by to further refine your audiences. |
| 25 | + |
| 26 | +## Use Cases |
| 27 | + |
| 28 | +Below are some example use cases to help you learn more about Linked Audiences. |
| 29 | + |
| 30 | +### Build an audience of cat owners |
| 31 | + |
| 32 | +Build an audience with `Households` and `Pets` where: |
| 33 | +- `pets.type` equals "cat". |
| 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 | + |
| 44 | +### Build an audience of users with premium subscriptions |
| 45 | + |
| 46 | +Build an audience with `Accounts` and `Subscriptions`, where the following are true: |
| 47 | +- `subscription.status` equals "active" |
| 48 | +- `subscription.tier` equals "premium" |
| 49 | + |
| 50 | +In the Data Graph, `Accounts` and `Subscriptions` are defined as entities. Relationships are defined between: |
| 51 | +- `Profiles` and `Accounts` |
| 52 | +- `Accounts` and `Subscriptions` |
| 53 | + |
| 54 | +In the warehouse, `subscription.status` is a column in the `subscriptions` table. Marketers can refine their audience by filtering against the `subscription.status` and `subscription.tier` columns to return a list of users that have an active subscription to their premium offering. |
| 55 | + |
| 56 | + |
| 57 | +### Build an audience of credit card holders with a certain number of transactions |
| 58 | + |
| 59 | +Build an audience with `Accounts`, `Credit Cards`, and `Transactions` where the following are true: |
| 60 | +- `credit_cards.name` equals "Owly Card" |
| 61 | +- `transactions.count` is greater than five |
| 62 | + |
| 63 | +In the Data Graph, `Accounts`, `Credit Cards`, and `Transactions` are defined as entities. Relationships are defined between: |
| 64 | +- `Profiles` and `Accounts` |
| 65 | +- `Accounts` and `Credit Cards` |
| 66 | +- `Accounts` and `Subscriptions` |
| 67 | + |
| 68 | +In the warehouse, `credit_cards.name` is a column in the `credit_cards` table, and `transactions.count` is a column in the `transactions` table. Marketers can create hyper-targeted user segmentations by filtering by column values or attributes, such as "Owly Card" and integers. |
| 69 | + |
| 70 | + |
| 71 | +## Build a Linked Audience |
| 72 | + |
| 73 | +Use the Audience overview page to build or maintain a Linked Audiences. |
| 74 | + |
| 75 | +1. Navigate to **Engage > Audiences** |
| 76 | +2. Click **+ New audience**, then select **Audience**. |
| 77 | +3. On the Select Type screen, select **Linked audience**, then click **Next**. |
| 78 | +4. Click the **associated with entity** field to add your entity. |
| 79 | +- To view your entities, navigate to **Unify > Data Graph > Entities**. |
| 80 | +5. Enter an entity to associate your audience with, then finish building your Linked Audience. Once you're done, click **Next**. |
| 81 | +6. Enter an Audience name and description, then click **Create Audience**. |
| 82 | + |
| 83 | +> warning "" |
| 84 | +> At this time, Linked Audiences can't be edited or deleted. Create a new audience to update conditions. To disable an audience, navigate to **Engage > Audiences > Settings** and toggle the **Enabled** button off. |
| 85 | +
|
| 86 | + |
| 87 | +## Activate your Linked Audience |
| 88 | + |
| 89 | +Use the Audience overview page to build or maintain Linked Audiences. |
| 90 | + |
| 91 | +> info "" |
| 92 | +> The following steps apply to non-preset destinations. If you're using Braze, Iterable, or Customer io, use [these setup steps](#). <!-- What's the flow here? --> |
| 93 | +
|
| 94 | +### Step 1: Add an actions destination |
| 95 | + |
| 96 | +To activate your Linked Audience, you'll first need to add an actions destination. |
| 97 | + |
| 98 | +From the Add destination window, select your actions destination and click **Next**. |
| 99 | + |
| 100 | +### Step 2: Select event |
| 101 | +After adding an actions destination, select what type of event you want to send to the destination. Events update the destination about changes to your entity or audiences. |
| 102 | + |
| 103 | +You can send events: |
| 104 | +- When an [entity on a profile changes](#entity-update) |
| 105 | +- Based on profile [audience membership updates](#audience-update) |
| 106 | + |
| 107 | +> info "" |
| 108 | +> Note that you can't send events before you identify people. Ensure you're making the profile(s) known in the destination before you send events. You can do this by sending an `Audience Membership Changed` event first, or by creating a standard Identify event in Connections. |
| 109 | +
|
| 110 | +#### Entity update |
| 111 | + |
| 112 | +Select to send an event when any of the following updates occur to an entity on a profile: |
| 113 | + |
| 114 | +1. Entity added |
| 115 | + |
| 116 | +Send an action to a destination when an entity associated with a profile matches the audience condition. Use these actions to orchestrate campaigns in other tools. |
| 117 | + |
| 118 | +Example use cases: |
| 119 | +- Send a reminder to a customer when a credit card associated with their profile has an outstanding balance. |
| 120 | +- Notify a traveler when a flight associated with their profile is delayed. |
| 121 | +- Notify a customer when a product associated with their profile's wishlist is back in stock. |
| 122 | + |
| 123 | +2. Entity removed |
| 124 | + |
| 125 | +Send an event to a destination when an entity assoacited with the profile no longer matches the audience condition. Use these events to orchestrate campaigns in other tools. |
| 126 | + |
| 127 | +Example use cases: |
| 128 | +- Send a confirmation to a customer when a credit card associated with their profile has been paid off. |
| 129 | +- Send a confirmation to the primary doctor when each of their associated patients completes their annual check up. |
| 130 | + |
| 131 | +#### Audience update |
| 132 | + |
| 133 | +Select to send an event based on the following profile audience membership updates: |
| 134 | + |
| 135 | +1. Audience Entered |
| 136 | + |
| 137 | +Send a Track event to a destination when a profile matches the audience condition. Use these events to orchestrate campaigns in other tools. |
| 138 | + |
| 139 | +Example use cases: |
| 140 | + |
| 141 | +- Send a congratulatory email when a travel qualifies for premium status. |
| 142 | +- Send a discount to all customers with a particular product on their wishlist. |
| 143 | + |
| 144 | +<!-- removed? |
| 145 | +#### Audience membership changed |
| 146 | +
|
| 147 | +Send an Identify event when a profile enters or exits the audience. |
| 148 | +
|
| 149 | +Example use case: |
| 150 | +- Update a user profile in a destination with the most recent audience membership. |
| 151 | +--> |
| 152 | +2. Audience exited |
| 153 | + |
| 154 | +Send a Track event to a destination when a profile no longer matches the audience condition. Use these events to orchestrate campaigns in other tools. |
| 155 | + |
| 156 | +Example use cases: |
| 157 | + |
| 158 | +- Send an email to credit card owners to confirm that their credit cards have been paid in full. |
| 159 | +- Send a confirmation to a patient when they have completed all their pre-screening forms. |
| 160 | + |
| 161 | +#### Audience entered and exited |
| 162 | + |
| 163 | +Send events when a profile enters and exits the audience. |
| 164 | + |
| 165 | +<!-- add use cases here --> |
| 166 | + |
| 167 | + |
| 168 | +### Step 3: Select an action |
| 169 | + |
| 170 | +Next, you'll select the destination action to call when the event happens. |
| 171 | + |
| 172 | +Segement displays available actions based on the destination action you've connected with your Linked Audience. |
| 173 | + |
| 174 | +Visit the [destination actions docs](/docs/connections/destinations/actions/) learn more about destination actions, and view available actions for your destination. |
| 175 | + |
| 176 | +### Step 4: Configure the event |
| 177 | + |
| 178 | +Finally, you'll configure your event and select additional entity context you want to send to the destination. |
| 179 | + |
| 180 | +To configure your event: |
| 181 | + |
| 182 | +1. Selecting additional properties to include in each event. |
| 183 | +- As you're configuring your event, you can view a preview of the enriched event based on your property selections. |
| 184 | +2. Next, map your event from your audience to your destination. |
| 185 | +- You can preview what the event will look like in your destination. |
| 186 | +3. Click **Save** to save your changes, or **Save and enable** to save the configuration and enable the events. |
| 187 | + |
| 188 | +After saving, you'll be redirected to a destination sidesheet where you can view all configured events and their corresponding actions. |
| 189 | + |
| 190 | +## Confirm the payload in your destination |
| 191 | + |
| 192 | +Linked Audiences will send events to your destination after Segment computes the audience. |
| 193 | + |
| 194 | +To confirm your destination is receiving events, Segment recommends that you log in to your destination and perform one of the following: |
| 195 | +- Monitor the event activity |
| 196 | +- Search for the `UserID` or `Event Name` (for example, `Entity Added`) |
| 197 | + |
| 198 | + |
| 199 | + |
0 commit comments