This topic discusses how to create and publish audiences identified in Customer Journey Analytics (CJA) to Real-time Customer Profile in Adobe Experience Platform for customer targeting and personalization.
Read this overview to familiarize yourself with the concept of CJA audiences.
To create audiences, you have three ways to get started:
|From the main Components > Audiences menu||The Audiences Manager page opens. Click Create audience and the Audience builder opens.|
|From within a Freeform table||Right-click an item in a Freeform table and select Create an audience from selection. Using this method pre-populates the filter with the dimension or dimension item you selected in the table.|
|From the filter creation/editing UI||Check the box that says Create an audience from this filter. Using this method pre-populates the filter.|
Build the audience.
Configure these settings before you can publish the audience.
|Name||The name of the audience.|
|Tags||Any tags that you want assigned to the audience for organizational purposes. You can use a pre-existing tag or enter a new one.|
|Description||Add a good description of the audience, to differentiate it from others.|
|Refresh frequency||The frequency at which you want to refresh the audience.
|Expiration date||When the audience will stop refreshing. The default is 1 year from the creation date. Expiring audiences are treated similarly to expiring scheduled reports - the admin gets an email a month before the audience expires.|
|Refresh lookback window||Specifies how far back in your data window you want to go when creating this audience. The max is 90 days.|
|One-time date range||Date range when you want the one-time audience to be published.|
|Filter||Filters are the main input to the audience. You can add up to 20 filters. These filters can be joined with
|View sample IDs||A sample of IDs in this audience. Use the search bar to search for sample IDs.|
Interpret the data preview.
The audience preview appears in the right rail. It allows for a summarized analysis of the audience you have created.
|Data preview window||The date range for the audience.|
|Total people||A summary number of the total number of people in this audience. It can go as high as 20 Million people. If your audience exceeds 20 Million people, you must reduce the audience size before you can publish it.|
|Audience size limit||Shows how far from the 20 Million limit this audience is.|
|Estimated audience return||This setting is useful for retargeting customers in this audience that come back to your site. (In other words, that are seen in this dataset again.)
Here, you can select the time frame (next 7 days, next 2 weeks, 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 from the drop-down list. We look at the historical churn rate for this audience to predict this number.|
|Preview metrics||This setting allows you to look at specific metrics to see whether this audience contributes a disproportionate amount to this metric, such as ‘Revenue’ or ‘Average time on site’. It gives you the aggregate count of the metric, as well as the percentage of the total it represents. 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 it within the confines of this sandbox.|
Double-check your audience configuration and click Publish.
If everything went well, you will receive a confirmation message that the audience was published. It takes only minute or two for this audience to show up in Experience Platform. (Even for audiences with millions of members, it should take less than 5 minutes.)
Click View audience in AEP within the same message and you will be taken to the Segment UI in Adobe Experience Platform. See below for more information.
After you have created an audience, Adobe creates an Experience Platform streaming segment for each new CJA audience. An AEP streaming segment will only be created 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 CJA||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.||Around 60 minutes|
|4||Refresh frequency for audiences||
|5||Creating destination in AEP: Activating the new segment||1-2 hours|
CJA takes all the namespace and ID combinations from your published audience and streams them into Real-time Customer Profile (RTCP). CJA sends the audience over to Experience Platform with the primary identity set, according to what was selected as the Person ID when the connection was configured.
RTCP 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 will add the namespace and ID to the other IDs in this profile as a segment membership attribute. Now, for example, “firstname.lastname@example.org” can be targeted across all their devices and channels. If a profile is not found, a new one is created.
You can view CJA audiences in Platform by going to Segments > Create segments > Audiences tab > CJA Audiences.
You can drag CJA audiences into the segment definition for AEP segments.
Frequently asked questions on audience publishing.
In this case, an exit event is sent to Experience Platform from CJA.
When a CJA Audience is deleted, that audience will no longer show up in the Experience Platform UI. However, no profiles associated with that audience are actually deleted in Platform.
Yes, it will.
CJA streams the data into RTCP 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 their “Person ID”.
See above. We only send one identity per CJA “person”.
No. We only send one identity per “person”, so there would be no graph edges for RTCP 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, they cannot be configured by users.