This topic discusses how to create and publish audiences identified in Customer Journey Analytics to Real-Time Customer Profile in Adobe Experience Platform for customer targeting and personalization.
Read this overview to familiarize yourself with the concept of Customer Journey Analytics audiences.
To create and publish an audience, do one of the following:
Creation method | Details |
---|---|
From within the Audiences interface. | Select Components > Audiences from the main Customer Journey Analytics menu. The Audiences interface displays. Select Create audience creaand the Audience builder opens. |
From a visualization in Analysis Workspace | Many visualizations in Analysis Workspace allow you to create an audience using the context menu. For example, you can select Create audience from the context menu of an item in a Freeform table or a node in Journey canvas. Using this method pre-populates the filter in the Audience builder with the dimension or dimension item that you selected. The following visualizations allow you to create an audience using the right-click menu: Note: Audiences cannot include calculated metrics. If you try to create an audience that contains a calculated metric, the calculated metric is not included in the audience definition. |
From the filter creation/editing UI | Check the box that says Create an audience from this filter. Using this method pre-populates the filter. See Create filters for more information. |
Build the audience using the Audience builder.
Interpret the data using the Date preview panel.
Select View sample IDs to view a sample of IDs in this audience. In the Sample IDs dialog you can use Search sample IDs to search for sample IDs.
Double-check your audience configuration and select Publish.
You receive a confirmation message that the audience is published. Publication takes only a minute or two for this audience to show up in Experience Platform.
Select View audience in AEP within the same message and you are taken to the Segment UI in Adobe Experience Platform. See below for more information.
Configure these settings to define or update your audience.
Setting | Description |
---|---|
Select a data view to use for the audience creation. | |
Name | The name of the audience. For example, Really Interested in Potential Car Buyers |
Tags | Any tags that you want to assign to the audience for organizational purposes. You can select one or more pre-existing tags or enter a new one. |
Description | A description of the audience, to differentiate it from others. For example, Build an audience of really interested potential car buyers |
Refresh frequency | The frequency at which you want to refresh the audience.You can choose between
|
Filter | Filters are the main input to the audience. Drag and drop one or more filters from the left Filter panel on to the Filter area. You can use the Search filters to search for filters. You can add up to 20 filters. Filters can be joined with And or Or operators. When creating an audience from a visualization in Analysis Workspace (such as a freeform table or Journey canvas), any filters applied to the panel or to the column are preserved. You can remove any filters that are automatically applied. |
Data preview | Select to show or hide the Data preview for the selected date range. |
The Data preview panel provides the following information.
Element | Description |
---|---|
Total people | A summary number of the total number of people in this audience. The maximum size is 20 million people. If your audience exceeds 20 million people, you must reduce the audience size before you can publish. |
Audience size limit | Visualization to show how far from the 20 million limit this audience is. |
Estimated audience return | You can use this value to retarget people in this audience that come back to your site, mobile app or other channel. You can select the time frame (Next 7 days, Next 2 weeks, or Next month) for the estimated number of customers who may return. |
Estimated to return | This number gives you an estimated number of returning customers over the time frame that you selected. This number is predicted using the historical churn rate for this audience. |
Preview metrics | You can select a specific metric to see how data for that metric is based on the audience you define. Each Preview metric displays a total for the metric based on the audience. And a percentage of the audience based metric from the overall total of the metric, as defined by the data view. For example, 381 people (the metric you selected) are the result of your audience definition, which is 5% of the total people available in the data view. You can select any metric that is available in your data view. |
Namespaces included | The specific namespaces that are associated with the people in your audience. Examples include ECID, CRM ID, email addresses, etc. |
Sandbox | The Experience Platform sandbox in which this audience resides. When you publish this audience to Platform, you can only work with the audience within the confines of this sandbox. |
After you create and publish an audience in Customer Journey Analytics, the audience is available in Experience Platform. An Adobe Experience Platform streaming segment is created only if your organization is set up for streaming segmentation.
At several points prior to, during, and after audience publishing, latencies can occur. Here is an overview of possible latencies.
Latency point | Latency duration | |
---|---|---|
Not shown | Adobe Analytics to Analytics source connector (A4T) | Up to 30 minutes |
1 | Data ingestion into Data Lake (from Analytics source connector or other sources) | Up to 90 minutes |
2 | Data ingestion from Experience Platform Data Lake into Customer Journey Analytics | Up to 90 minutes |
3 | Audience publishing to Real-Time Customer Profile, including automatic creation of the streaming segment, and allowing the segment to be ready to receive the data. | A few seconds |
4 | Refresh frequency for audiences |
|
5 | Creating destination in Adobe Experience Platform: Activating the new segment | 1-2 hours |
Customer Journey Analytics takes all the namespace and ID combinations from your published audience and streams them into Real-Time Customer Data Platform . Customer Journey Analytics sends the audience to Experience Platform with the primary identity set, according to what was selected as the Person ID when the connection was configured.
Real-Time Customer Data Platform then examines each namespace/ID combination and looks for a profile that it may be part of. A profile is basically a cluster of linked namespaces, IDs and devices. If it finds a profile, it adds the namespace and ID to the other IDs in this profile as a segment membership attribute. For example, user@adobe.com can be targeted across all their devices and channels. If a profile is not found, a new one is created.
To view Customer Journey Analytics audiences in Platform:
Expand Customer in the left panel, then select Audiences.
Select the Browse tab.
To locate the audience that you published from Customer Journey Analytics, do any of the following:
Sort the table by the Origin column to view audiences that show Customer Journey Analytics as the origin.
Filter on Origin and select Customer Journey Analytics.
Use the search field.
For more information about using Audiences in Platform, see the Audiences section in the Segment Builder UI guide in the Experience Platform documentation.
Frequently asked questions on audience publishing.
In this case, an exit event is sent to Experience Platform from Customer Journey Analytics.
When a Customer Journey Analytics Audience is deleted, that audience is no longer shown in the Experience Platform UI. However, profiles associated with that audience are not deleted in Experience Platform.
Yes, it will.
Customer Journey Analytics streams the data into Real-Time Customer Data Platform via pipeline, and this data is also collected into a system dataset in the data lake.
Whichever identity/namespace pairs that were specified in the Connection setup. Specifically, the step when a user selects the field they want to use as the Person ID.
See above. Only one identity per Customer Journey Analytics person is sent.
No. Only one identity per person is sent, so there would be no graph edges for Real-Time Customer Data Platform to consume.
The timing of the refresh is based on when the original audience was published and anchors to that time of day (and day of week or month).
No, users cannot configure the time of refresh.