# Adobe Target

## About this integration

Adobe Target is a crucial element of Adobe’s Experience Cloud suite, offering A/B testing and personalization features. This destination uses source data to create or update user profiles within Adobe Target that you can use to build target audiences and customize the user experience for your website visitors.

[Mode How we forward source data to the destination: through Customer.io's servers or directly from our JavaScript client.](/cdp/destinations/getting-started/#connection-mode)

[Web sources Indicates whether or not this integration supports our the JavaScript client.](/cdp/sources/getting-started/#types-of-sources)

[API sources Indicates whether or not this integration supports our server libraries (Go, NodeJS, Python), API, Mobile SDK, and other data sources.](/cdp/sources/getting-started/#types-of-sources)

[Supported calls The API methods this integration supports.](/cdp/sources/source-spec/source-events/)

[Integration name The name of this integration if you want to enable or disable it in the `integrations` object.](/cdp/sources/source-spec/common-fields/#the-integrations-object)

Standard

[identify](/api/cdp/#operation/identify), [track](/api/cdp/#operation/track), [page](/api/cdp/#operation/page), [group](/api/cdp/#operation/group), and [alias](/api/cdp/#operation/alias)

Adobe Target Cloud Mode

Web

[identify](/api/cdp/#operation/identify), [page](/api/cdp/#operation/page), and [track](/api/cdp/#operation/track)

adobe-target-web

## Getting started: Web integration[](#getting-started-web-integration)

The Adobe Target “Web” integration loads Adobe’s `at.js` script alongside our JavaScript client source so that you can upsert user profiles, trigger views, and track events.

1.  Go to **[Data & Integrations > Integrations](https://fly.customer.io/workspaces/last/journeys/integrations/all/directory)** and select the **Adobe Target** entry in the *Directory* tab.
    
2.  (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration.
    
3.  Configure your integration.
    
    1.  **Client Code**: Your Adobe Target client code. To find your client code in Adobe Target, navigate to **Administration > Implementation**. The client code is shown at the top under Account Details.
        
    2.  **Admin Number**: Your Adobe Target admin number. To find your admin number, please follow the instructions in [Adobe Docs](https://experienceleague.adobe.com/docs/target/using/implement-target/client-side/at-js-implementation/deploy-at-js/implementing-target-without-a-tag-manager.html).
        
    3.  **Version**: The version of ATJS to use. Defaults to 2.8.0.
        
    4.  **Mbox Name**: The name of the Adobe Target mbox to use. Defaults to `target-global-mbox`.
        
    5.  **Cookie Domain**: The domain from which you serve the mbox. Adobe Target recommends setting this value to your company's top-level domain.
        
4.  Click **Enable Destination**.
    

## Getting started: Support all sources[](#getting-started-support-all-sources)

The standard Adobe Target integration only updates existing profiles in Adobe Target. If you want to add new profiles and send events, you’ll need to use the [web version of this integration](#getting-started-web-mode) instead.

1.  Go to **[Data & Integrations > Integrations](https://fly.customer.io/workspaces/last/journeys/integrations/all/directory)** and select the **Adobe Target** entry in the *Directory* tab.
    
2.  (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration.
    
3.  Configure your integration.
    
    1.  **Client Code**: Your Adobe Target client code. To find your client code in Adobe Target, navigate to **Administration > Implementation**. The client code is shown at the top under Account Details.
        
    2.  **Bearer Token**: If you choose to require authentication for Adobe Target's Profile API, you will need to generate an authentication token. Tokens can be generated in your Adobe Target account under the Implementation Settings tab or via the [Adobe.IO Authentication Token API](https://developers.adobetarget.com/api/#authentication-tokens). Input the authentication token here. Note: Authentication tokens expire so a new token will need to be generated and updated here prior to expiration.
        
4.  Click **Enable Destination**.
    

## Supported Actions[](#supported-actions)

We support, and have default mappings for the following actions.

**Web integration**:

*   [Create or update profile (upsert)](#upsert-profile)
*   [Trigger View](#trigger-view)
*   [Track Event](#track-event)

**Supporting non-JS sources**:

*   [Update person](#update-person)

### Create or update person (upsert)[](#upsert-profile)

This action only works with the web version of this integration and creates or updates user profiles in Adobe Target. By default, we send this action based on `identify` calls from your web source(s).

Field

Type

Description

Mbox 3rd Party ID

string

A user’s unique visitor ID. Setting an Mbox 3rd Party ID allows for updates when you use this integration outside the web mode.

Profile Attributes

object

Profile parameters specific to a user. If you send personally identifiable information to Adobe Target, you should hash it first.

### Trigger view[](#trigger-view)

This action only works with the web version of this integration and sends page views to Adobe Target. By default, we send this action based on `page` calls from your web source(s).

Field

Type

Description

View Name\*

string

Name of the view or page.

Page Parameters

object

Parameters specific to the view or page.

Send Notifications to Adobe Target

boolean

By default, notifications are sent to the Adobe Target backend for incrementing impression count. If false, notifications are not sent for incrementing impression count.

Mbox 3rd Party ID

string A user’s unique visitor ID. Setting an Mbox 3rd Party ID allows for updates if you also use the standard version of this integration.

### Track Event[](#track-event)

This action only works with the web version of this integration and sends user actions—like clicks, conversions, and so on— to Adobe Target. By default, we send this action based on `track` calls from your web source(s).

Field

Type

Description

Event Type

string

The event type. The type event type must be registered and available in Adobe Target.

Event Name

string

The `event_name` in Adobe Target.

Event Parameters

object

Parameters specific to the event.

Mbox 3rd Party ID

string

A user’s unique visitor ID for the person who performed the event. Setting an Mbox 3rd Party ID allows for updates if you also use the standard version of this integration.

### Update Person[](#update-person)

This action is available when you set up this integration in the normal, non-web version of this integration. It updates user profiles in Adobe Target. By default, we send this action based on `identify` calls from your web source(s).

Field

Type

Description

Mbox 3rd Party ID

string

A user’s unique visitor ID. Setting an Mbox 3rd Party ID allows for updates via the Adobe Target Integration. For more information, please see our Adobe Target Integration documentation.

Profile Attributes

object

Profile parameters specific to a user. If you send personally identifiable information to Adobe Target, you should hash it first.

## You probably want to use the web integration[](#you-probably-want-to-use-the-web-integration)

You may need to set up both the web and non-web versions of this integration to get the most out of Adobe Target, but you *must* use the web integration if you want to create profiles in Adobe Target.

Adobe Target only supports profile creation with their client-side library. We only load this library when you use the [web integration](#getting-started-web-mode), so you have to use the web integration if you want to create new profiles in Adobe Target.

You can use this integration outside of web-only use cases to update existing profiles. When you set up your integration this way, we can’t create new profiles in Adobe Target, but it may be helpful to use this integration to augment information that you capture from your web integration with data from other sources.

### How does it work?[](#how-does-it-work)

Our JavaScript client library loads Adobe Target’s `at.js` script. While this script identifies people using a `PCID` we recommend that you identify people using the `mbox3rdPartyId` instead. In your integration, you should leave this value mapped to the default `userId` value (falling back to `anonymousId` for people you haven’t identified yet).

This provides a common identifier that ties data back to the original profiles created from your JavaScript client. Depending on your users’ journeys, they could generate multiple profiles in Adobe Target.

When an anonymous user arrives on your website, we’ll create an Adobe Target profile setting the `mbox3rdPartyId` to our `anonymousId`. If the same anonymous user visits your site on a different device, they’ll generate a new `anonymousId` and, therefore, a different `mbox3rdPartyId`. This results in a separate Adobe Target profile. This is Adobe’s standard `PCID` behavior.

When you identify a user—like when they log into your service—the person is assigned a new `mbox3rdPartyId` corresponding to their `userId`. If this profile doesn’t already exist, they’ll have a another profile.

If you identify people immediately upon their arrival—like in a single page app where people must login before they enter your website—then it’s likely that your users will always have the same `userId` and `mbox3rdPartyId` across devices (because you’ll always know exactly who they are).

## Finding data in Adobe Target[](#finding-data-in-adobe-target)

Go to **Adobe Target > Audiences > Create Audience > Add Rule** to find and use your data in Adobe Target.

*   Attributes appear under **Visitor Profile** attributes.
*   Page Parameters show up as **Custom** attributes. Fields have `page.` prepended to the key.

You can use Adobe Target audiences in activities, like A/B Testing and Experience Targeting.