Use the Pega Customer Decision Hub destination in Adobe Experience Platform to send profile attributes and audience membership data to Pega Customer Decision Hub for next-best-action decisioning.
Profile audience membership from Adobe Experience Platform, when loaded into Pega Customer Decision Hub, can be used as predictor in adaptive models and help deliver the right contextual and behavioral data for next-best-action decisioning purposes.
This destination connector and documentation page are created and maintained by Pegasystems. For any inquiries or update requests, please contact Pega directly here.
To help you better understand how and when you should use the Customer Decision Hub destination, here are sample use cases that Adobe Experience Platform customers can solve by using this destination.
A marketer wants to leverage insights from data science model-based next best action as delivered by Pega Customer Decision Hub for customer engagement. Pega Customer Decision Hub is heavily reliant on customer intent – for example “Interested_In_5G”, “Interested_in_Unlimited_Dataplan” or “Interest_in_iPhone_accessories”.
A marketer wants to optimize the offers for customers who subscribed or unsubscribed from Pension Plan or Retirement Plan newsletters. Financial services companies can ingest multiple Customer IDs from their own CRMs into Adobe Experience Platform, build audiences from their own offline data, and send profiles that are entering and exiting the audiences to Pega Customer Decision Hub for next-best-action (NBA) decisioning in outbound channels.
Before you can use this destination to export data out of Adobe Experience Platform, make sure you complete the following prerequisites in Pega Customer Decision Hub:
Pega Customer Decision Hub supports the activation of custom user IDs described in the table below. For more details, see identities.
|CustomerID||Common User Identifier that uniquely identifies a profile in Pega Customer Decision Hub and Adobe Experience Platform|
Refer to the table below for information about the destination export type and frequency.
|Export type||Profile-based||Export all members of an audience with identifier (CustomerID), attributes (last name, first name, location, etc.) and Audience Membership data.|
|Export frequency||Streaming||Streaming destinations are always-on API-based connections. As soon as a profile is updated in Experience Platform, based on audience evaluation, the connector sends the update downstream to the destination platform. For more information, see streaming destinations.|
To connect to this destination, follow the steps described in the destination configuration tutorial. In the configure destination workflow, fill in the fields listed in the two sections below.
Fill in the fields below and select Connect to destination:
After establishing the authentication connection to the Pega Customer Decision Hub, provide the following information for the destination:
To configure details for the destination, fill in the required fields and select Next.
See Activate audience data to streaming profile export destinations for instructions on activating audiences to this destination.
In the Select attributes step, Adobe recommends that you select a unique identifier from your union schema. Select the unique identifier and any other XDM fields that you want to export to the destination.
Below is an example of correct identity mapping when exporting profiles to Pega Customer Decision Hub.
Selecting source fields:
Selecting target fields:
CustomerIDnamespace as target identity.
A successful audience membership update for a profile would insert the audience identifier, name and statuses in the Pega marketing audience membership datastore. The membership data is associated to a customer using Customer Profile Designer in Pega Customer Decision Hub, as shown below.
The audience membership data is used in Pega Next-Best-Action Designer Engagement polices for next-best-action decisioning, as shown below.
The customer audience membership data fields are added as predictors in Adaptive models, as shown below.
See Setting up an OAuth 2.0 client registration in Pega Customer Decision Hub.
See Creating a real-time run for data flows in Pega Customer Decision Hub.
All Adobe Experience Platform destinations are compliant with data usage policies when handling your data. For detailed information on how Adobe Experience Platform enforces data governance, see the Data Governance overview.