This use case explores an interim, manual way of bringing Adobe Experience Platform (AEP) audiences into CJA. These audiences might have been created in the AEP Segment Builder, or Adobe Audience Manager, or other tools, and are stored in Real-time Customer Profile (RTCP). The audiences consist of a set of Profile IDs, along with any applicable attributes/events/etc. and we want to bring them into CJA Workspace for analysis.
Adobe Experience Platform Real-time Customer Profile (RTCP) lets you see a holistic view of each individual customer by combining data from multiple channels, including online, offline, CRM, and third party.
You likely already have audiences in RTCP that may have come from various sources. Pick one or more audiences to ingest into CJA.
In order to export the audience to a dataset that can eventually be added to a connection in CJA, you need to create a dataset whose schema is a Profile Union schema.
Union schemas are composed of multiple schemas that share the same class and have been enabled for Profile. The union schema enables you to see an amalgamation of all of the fields contained within schemas sharing the same class. Real-time Customer Profile uses the union schema to create a holistic view of each individual customer.
Before you can bring an audience into CJA, you need to export it to an AEP dataset. This can only be done using the Segmentation API, and specifically the Export Jobs API Endpoint.
You can create an export job using the audience ID of your choice, and put the results in the Profile Union AEP dataset you created in Step 2. Although you can export various attributes/events for the audience, you only need to export the specific profile ID field that matches the person ID field used in the CJA connection you will be leveraging (see below in Step 5).
The results of the export job need to be transformed into a separate Profile dataset in order to be ingested into CJA. This transformation can be done with AEP Query Service, or another transformation tool of your choice. We only need the Profile ID (that will match the Person ID in CJA) and one or more audience ID(s) to do the reporting in CJA.
The standard export job, however, contains more data and so we need to edit this output to remove extraneous data, as well as move some things around. Also, you need to create a schema/dataset first before you add the transformed data to it.
Here is an example of the export output in the Profile union dataset, before any editing:
Note the following:
This is the format of the Profile dataset that you can send into CJA.
Here are the data elements that need to be present:
_aresprodvalidation string field: Refers to your Organization ID. Yours will be different.
personID string field: This is the standard XDM schema field on Profile datasets to identity the person. Use the Profile ID from the export.
audienceMembershipId string field: The audience ID from the export. NOTE: This field can be named whatever you want (from your own schema).
Add a friendly name for the audience (
audienceMembershipIdName), such as
Add other audience metadata if you desire.
You could create a new connection, but most customers will want to add the Profile dataset to an existing connection. The audience IDs “enrich” the existing data in CJA.
personID to the data view.
You can now report on
personID in Workspace.
audienceMembershipIdfield to convert the comma-separated values string to an array. NOTE: there is currently a limit of 10 values in the array.
audienceMembershipIdswithin CJA Workspace.