Skip to content

Commit 90adb66

Browse files
authored
Merge pull request #6968 from segmentio/la-activation-updates
Update Linked Audiences Activation Content
2 parents d09bd43 + 634b1f5 commit 90adb66

File tree

1 file changed

+43
-30
lines changed

1 file changed

+43
-30
lines changed

src/engage/audiences/linked-audiences.md

Lines changed: 43 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -1,31 +1,29 @@
11
---
22
title: Linked Audiences
33
plan: engage-foundations
4-
beta: true
54
redirect_from:
65
- '/unify/linked-profiles/linked-audiences'
7-
hidden: true
86
---
9-
> info "Linked Audiences is in public beta"
10-
> Linked Audiences is in public beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.
117

12-
Linked Audiences allows you to build a warehouse-first solution that powers individualized customer experiences using the relational data you've defined in your [Data Graph](/docs/unify/linked-profiles/data-graph/).
8+
Linked Audiences empowers marketers to effortlessly create targeted audiences by combining behavioral data from the Segment Profile and warehouse entity data within a self-serve, no-code interface.
139

14-
You can:
10+
This tool accelerates audience creation, enabling precise targeting, enhanced customer personalization, and optimized marketing spend without the need for constant data team support.
11+
12+
With Linked Audiences, you can:
1513

1614
- Preserve rich relationships between all the data in your warehouse by creating connections with any entity data back to your audience profile.
1715
- Build advanced audience segments that include the rich context needed for personalization downstream.
1816
- Use a low code builder, enabling marketers to activate warehouse data without having to wait for data pull requests before launching campaigns to targeted audiences.
1917

20-
To learn more about specific use cases you can set up with Linked Audiences, see the [Linked Audiences Use Cases](/docs/engage/audiences/linked-audiences-use-cases/) topic.
18+
To learn more about specific use cases you can set up with Linked Audiences, see [Linked Audiences Use Cases](/docs/engage/audiences/linked-audiences-use-cases/).
2119

2220
## Prerequisites
2321

2422
Before you begin setting up your Linked Audience, ensure you have:
2523

2624
- [Set up Profiles Sync](/docs/unify/profiles-sync/profiles-sync-setup/).
27-
- Set up your warehouse permissions using [Snowflake](/docs/unify/linked-profiles/setup-guides/snowflake-setup/).
28-
- [Ensure someone has set up your data graph](/docs/unify/linked-profiles/data-graph/).
25+
- Set up your warehouse permissions using [Snowflake](/docs/unify/data-graph/setup-guides/snowflake-setup/).
26+
- [Ensure someone has set up your data graph](/docs/unify/data-graph/data-graph/).
2927
- Workspace Owner or Unify Read-only, Engage User, Entities Read-only, and Source Admin [roles in Segment](/docs/segment-app/iam/roles/).
3028

3129
## Setting up Linked Audiences
@@ -35,7 +33,8 @@ To set up your Linked Audience, complete the following steps:
3533
- [Step 1: Build a Linked Audience](#step-1-build-a-linked-audience)
3634
- [Step 2: Activate your Linked Audiences](#step-2-activate-your-linked-audience)
3735
- [Step 3: Send a test event to your destination](#step-3-send-a-test-event-to-your-destination)
38-
- [Step 4: Enable your Linked Audience](step-4-enable-your-linked-audience)
36+
- [Step 4: Enable your Linked Audience](#step-4-enable-your-linked-audience)
37+
- [Step 5: Monitor your Activation](#step-5-monitor-your-activation)
3938

4039
## Step 1: Build a Linked Audience
4140

@@ -139,13 +138,16 @@ To activate your Linked Audience:
139138

140139
### Step 2a: Connecting to a destination
141140

142-
[Destinations](/docs/connections/destinations/) are the business tools or apps that Segment forwards your data to. Adding a destination allows you to act on your data and learn more about your customers in real time. To fully take advantage of Linked Audiences, you must connect and configure at least one destination.
141+
[Destinations](/docs/connections/destinations/) are the business tools or apps that Segment forwards your data to. Adding a destination allows you to act on your data and learn more about your customers in real time. To fully take advantage of Linked Audiences, you must connect and configure at least one destination.
142+
143+
> info "Linked Audiences destinations"
144+
> Linked Audiences only supports [Actions Destinations](/docs/connections/destinations/actions/#available-actions-based-destinations).
143145
144146
**Note:** Ensure your [destination has been enabled](/connections/destinations/catalog/) in Segment before you begin the steps below.
145147

146148
1. Navigate to **Engage > Audiences**.
147149
2. Select the Linked Audience you set up in the previous step.
148-
3. Select **Add destination**.
150+
3. Select **Add destination**.
149151
4. Select a destination from the catalog.
150152
5. Click **Configure data to send to destination**.
151153

@@ -159,13 +161,15 @@ Select the Destination Action to call when the event happens, then click **Next*
159161

160162
Configure how and when events are produced with each audience run. Select the entities referenced in the audience builder to act as a trigger for your events.
161163

162-
Event Selection |Definition |Examples
163-
--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
164-
Profile enters audience | Send an event when a profile matches the audience condition. | Send a congratulatory email when a traveler qualifies for premium status with a mileage program.<br>Send a discount to all customers with a particular product on their wishlist.
165-
Profile exits audience | Send an event when a profile no longer matches the audience condition. | Send an email to credit card owners to confirm that their credit cards have been paid in full.<br> Send a confirmation to a patient when they have completed all their pre-screening forms.
166-
Entity enters audience | Send an event when an entity condition associated with a profile matches the audience condition. With this event, you must select the entity that triggers Segment to send the event. | Send a reminder to a customer when a credit card associated with their profile has an outstanding balance.<br> Notify a traveler when a flight associated with their profile is delayed.<br> Notify a customer when a product associated with their profile's wishlist is back in stock.
167-
Entity exits audience | Send an event when an entity condition associated with a profile no longer matches the audience condition. You must select the entity that triggers Segment to send the event| Send a confirmation to a customer when a credit card associated with their profile has been paid off.<br> Send a confirmation to the primary doctor when each of their associated patients completes their annual check up.
168-
Profile enters or exits audience| Send an event when a profile's audience membership changes. | Update a user profile in a destination with the most recent audience membership.
164+
| Trigger | Event type | Definition | Examples |
165+
| -------------------------------- | ---------- | ---------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
166+
| Profile enters audience | Track | Send an event when a profile matches the audience condition. | Send a congratulatory email when a traveler qualifies for premium status with a mileage program. Send a discount to all customers with a particular product on their wishlist. |
167+
| Profile exits audience | Track | Send an event when a profile no longer matches the audience condition. | Send an email to credit card owners to confirm that their credit cards have been paid in full. Send a confirmation to a patient when they have completed all their pre-screening forms. |
168+
| Entity enters audience | Track | Send an event when an entity condition associated with a profile matches the audience condition. | Send a reminder to a customer when a credit card associated with their profile has an outstanding balance. Notify a traveler when a flight associated with their profile is delayed. Notify a customer when a product associated with their profile's wishlist is back in stock. |
169+
| Entity exits audience | Track | Send an event when an entity condition associated with a profile no longer matches the audience condition. | Send a confirmation to a customer when a credit card associated with their profile has been paid off. Send a confirmation to the primary doctor when each of their associated patients completes their annual check up. |
170+
| Profile enters or exits audience | Identify | Send an event when a profile's audience membership changes. | Update a user profile in a destination with the most recent audience membership. |
171+
172+
169173

170174
### Step 2d: Configure the event
171175

@@ -181,13 +185,11 @@ As you're enriching your events in Linked Audiences, you should view a preview o
181185

182186
![A screenshot of the Add activation page, where you can review your payload data.](/docs/engage/images/linked_audience_payload.png)
183187

184-
**Important:** It is important to make a copy of the data from your final payload schema; you will need this data later when you set up your destination.
185-
186188
#### Map event
187189

188-
Only required fields are displayed. All optional & pre-filled fields are hidden.
190+
Only required fields are displayed. All optional & pre-filled fields are hidden, though you can view hidden fields by clicking **Show hidden fields**.
189191

190-
These fields are pre-filled with properties that will work by default.
192+
These fields are pre-filled with properties configured by default.
191193

192194
## Step 3: Send a test event to your destination
193195

@@ -197,16 +199,11 @@ Enter the destination User id for the profile you want to use to test the event,
197199

198200
The Event content drop-down shows you a preview of what the data sent to your destination might look like.
199201

200-
### Step 3a: Configure your multi-channel marketing campaign
201-
202-
If you're using a multi-channel marketing tool, set up your email campaign before continuing. See detailed instructions for [Braze](/docs/engage/audiences/linked-audiences-braze/) or [Iterable](/docs/engage/audiences/linked-audiences-iterable/) for more details.
203-
204202
## Step 4: Enable your Linked Audience
205203

206-
After building your Linked Audience, choose **Save and Enable**. You'll be redirected to the Audience Overview page, where you can view the audience you created. Segment automatically disables your audience so that it doesn't start computing until you're ready. A compute is when Segment runs the audience conditions on your data warehouse and sends events downstream.
204+
After building your Linked Audience, choose **Save and Enable**. You'll be redirected to the Audience Overview page, where you can view the audience you created. Segment automatically disables your audience so that it doesn't start computing until you're ready. A run is when Segment runs the audience conditions on your data warehouse and sends events downstream.
207205

208-
To enable your audience:
209-
Select the **Enabled** toggle, then select **Enable audience**.
206+
To enable your audience, select the **Enabled** toggle, then select **Enable audience**.
210207

211208
### Run Now
212209

@@ -226,3 +223,19 @@ You can maintain your run schedule at any time from the audience's **Settings**
226223
You can also click **Run Now** on the Audience Overview page at any time (even if the run schedule is **Interval** Overview **Day and time**) to manually trigger a run on your warehouse and send data to enabled destinations.
227224

228225
There may be up to a 5 minute delay from the configured start time for audiences that are configured with the **Interval** and **Day and time** run schedules. For example, if you configured an audience with the **Day and time** compute schedule to run on Mondays at 8am, it can compute as late as Monday at 8:05am. This is to help us better manage our system load.
226+
227+
## Step 5: Monitor your activation
228+
229+
With your Linked Audience activated, follow these steps to monitor your activation:
230+
231+
1. From the Audience Overview page, selected one of your connected destinations.
232+
2. Under the **Settings** tab, click **Destination delivery**, which then opens the Linked Audiences Delivery Overview.
233+
234+
### Delivery Overview for Linked Audiences
235+
236+
Delivery Overview shows you four steps in your data activation pipeline:
237+
238+
- **Events from Audience**: Events that Segment created for your activation. The number of events for each compute depends on the changes detected in your audience membership.
239+
- **Filtered at Destination**: The activation pipeline is rich with features that let you control which events make it to the destination. If any events aren't eligible to be sent (for example, due to destination filters, insert function logic, and so on), Segment will show them in Filtered at Destination.
240+
- **Failed Delivery**: Events that Segment attempted but failed to deliver to your destination. Failed Delivery indicates an issue with the destination, like invalid credentials, rate limits, or other error statuses received during delivery.
241+
- **Successful Delivery**: Events that Segment successfully delivered to your destination. You'll see these events in your downstream integration.

0 commit comments

Comments
 (0)