What this is
The Adobe Target (Single Update) integration sends profile attributes out of Zeotap CDP to Adobe Target, one user at a time, as users move through a workflow in Journeys. Adobe Target’s Single Profile Update API sends a profile update for a single user. It is generally used when an update must occur in relation to a transaction occurring in a channel that has not implemented Target. Integrated with Zeotap, Adobe Target manages those profile updates so that audience segmentation is accurately reflected in the data, supporting personalisation and optimisation. To know more about updating the user profile using single or bulk updates, refer here. Adobe Target has three integrations in Zeotap CDP, and they are not interchangeable — all three send data out of Zeotap CDP:- Adobe Target (Single Update) — this page. A real-time integration attached to a Send to Destinations node in Journeys, sending one profile update at a time.
- Adobe Target (Delivery API) — the other real-time integration, which delivers personalised content and offers based on customer data and behaviour.
- Adobe Target (Bulk Update) — the batch integration, which updates user profiles for multiple visitors at once using a batch file and is linked to an audience rather than to a Journeys node.
Supported identifiers and actions
This integration supports Mbox 3rd party Ids. The Mbox 3rd Party ID is a client-specified identifier passed to Adobe Target through an mbox call asmbox3rdPartyId.
The following table lists the available actions for the integration and the features each one supports:
Prerequisites
Have the following ready before you create the destination:- An Adobe Target account, and access to the Adobe Developer Console for the same organisation.
- The Client ID and Client Secret of an OAuth Server-to-Server credential for the Adobe Target API. See Client ID and Client Secret.
- The Client Code of your Adobe Target account. See Client Code.
- The Tenant ID of your organisation in the Adobe Experience Platform (AEP) ecosystem. See Tenant ID.
- A workflow in Journeys with the filters or conditions that select the users you want to send. See Create a Workflow.
Obtain the Adobe Target credentials
Client ID and Client Secret
The Client ID is a unique identifier for the application or service making the request, while the Client Secret is a confidential password that verifies the authenticity of the request. These credentials are used to access and manipulate data in the Adobe Target platform. To obtain the Client ID and Client Secret, log into the Adobe Developer Console and perform the following steps:1
Go to Projects and click Create new project.

2
Under Get started with your new project, click Add API.

3
In the new screen that appears, all the APIs supported by Adobe are listed. Here, click Adobe Target and click Next.

4
Under Choose type of authentication you need, click OAuth Server-to-Server and click Next.

5
In the next screen, choose Default work space and click Next.
6
To view the details of the project that you have created, click OAuth Server-to-Server as shown below.

7
In the next screen, you can find the Client ID. However, to view the Client Secret, click Retrieve client secret.
8
In the next screen that appears, you can copy both the Client ID and Client Secret for your project.
Client Code
A Client Code is a unique identifier assigned to a specific client or user to track and personalise their experiences across different channels and devices. You can obtain the Client Code in Adobe Target by navigating to Administration > Implementation > Account details.
Tenant ID
A Tenant ID is a unique identifier assigned to an organisation or individual to uniquely identify them within the Adobe Experience Platform (AEP) ecosystem. This identifier is used to authorise user access to specific capabilities within AEP. To obtain your Tenant ID, log in to the Adobe Experience Cloud, open Adobe Target and click the Target card. Use the Tenant ID value as noted in the URL subdomain. For example, if your URL when logged in to Adobe Target ishttps://mycompany.experiencecloud.adobe.com/..., then your Tenant ID is mycompany.
The Tenant ID is different from your Client Code. The Tenant ID exists in the URL when you are logged in to Adobe Target.
Create the Adobe Target (Single Update) destination
After you have applied filters or added conditions for your users in Journeys, you can activate them in Adobe Target under Send to Destinations. A new window opens, where you can set up your destination. You can use an already existing destination from the list of Available Destinations or create a new one.
1
Log into the Zeotap CDP App and go to the Destinations application.
2
Click + Create Destination.
3
Under All Destinations, search for Adobe Target - Single Update.
4
Click Adobe Target - Single Update.a. Enter a name for the Destination.b. Enter the Client ID, Client Secret, Client Code and Tenant ID that you have obtained in the above steps and save the Destination.
5
Review the fields entered above and click Next.
6
In the mapping screen that appears, under Choose your Action, select Stream Profile Properties to Adobe Target - Single Profile Update as the action for sending data from the workflow created in Journeys. Under Map the Fields, note that you must mandatorily map Mbox 3rd Party Id. Use + Add Mapping Field to add custom identifiers and attributes you wish to send to Adobe Target (Single Update).
7
Once the mapping is complete, click Create Destination.
Activate the destination in a Journeys workflow
After creating a Destination, link the Destination that you created to the Journeys workflow and map the relevant source fields to the Destination fields in the Destination Settings tab.

Verify the profile updates reached Adobe Target
You can view the profile parameters sent to Adobe Target (Single Update). To do so, log in to Adobe Target and perform the following steps:1
Go to the Audiences tab and click Create Audience.
2
Under Attributes, drag and drop the Visitor Profile to the middle of the screen.
3
Use the drop-down option on the Visitor Profile to verify the presence of the profile parameters that you have shared through Zeotap.
