|
| 1 | +--- |
| 2 | +title: Adobe Target Cloud Mode Destination |
| 3 | +hide-boilerplate: true |
| 4 | +hide-dossier: false |
| 5 | +hidden: true |
| 6 | +beta: true |
| 7 | +id: 61aa712b857e8c85c3b5a849 |
| 8 | +--- |
| 9 | +Adobe Target is the A/B testing and personalization component of Adobe Experience Cloud. Segment’s Adobe Target integration enables customers to send data from Segment to Adobe Target to create and update user profiles. You can leverage these profiles in Adobe Target to construct audiences and personalize onsite visitor experiences. |
| 10 | + |
| 11 | +Segment offers two destinations for Adobe Target: |
| 12 | +- [Adobe Target Web](/docs/connections/destinations/catalog/actions-adobe-target-web/) |
| 13 | +- [Adobe Target Cloud Mode](/docs/connections/destinations/catalog/actions-adobe-target-cloud/) |
| 14 | + |
| 15 | +> success "" |
| 16 | +> **Good to know**: This page is about Segment's Adobe Target Cloud Mode destination. There's also a page about Segment's [Adobe Target Web destination](/docs/connections/destinations/catalog/actions-adobe-target-web/). **In order to use Adobe Target Cloud Mode, you must have a parallel web integration with Adobe Target as profiles can only be created by the Adobe Target `at.js` web script.** |
| 17 | +
|
| 18 | +## Getting started |
| 19 | + |
| 20 | +The Adobe Target Cloud Mode destination sends user information to the Adobe Target API in order to update user profiles. **You must use the [Adobe Target Web destination](/docs/connections/destinations/catalog/actions-adobe-target-web/) for initial profile creation.** |
| 21 | + |
| 22 | +1. From the Segment web app, click **Catalog**, then click **Destinations**. |
| 23 | +2. Search for **Adobe Target Cloud Mode** in the Destinations Catalog, and select the destination. |
| 24 | +3. Click **Configure Adobe Target Cloud Mode** in the top-right corner of the screen. |
| 25 | +4. Select the source that will send data to Adobe Target Cloud Mode and follow the steps to name your destination. |
| 26 | +5. On the **Settings** tab, input your Adobe Target destination settings. |
| 27 | +6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings). |
| 28 | +7. Enable the destination and configured mappings. |
| 29 | + |
| 30 | +{% include components/actions-fields.html %} |
| 31 | + |
| 32 | +## Relationship between Adobe Target Web and Adobe Target Cloud Mode |
| 33 | + |
| 34 | +Adobe Target is unique because you must have a web integration with Adobe Target in order to utilize the Target server-side API for profile updates. This is because Adobe Target only allows creation of user profiles via client-side web. |
| 35 | + |
| 36 | +To support this, Segment provides an [Adobe Target Web destination](/docs/connections/destinations/catalog/actions-adobe-target-web/) for user profile creation, updates, and page/event tracking and an Adobe Target Cloud Mode destination for additional profile updates. The cloud mode destination is useful if you would like to send Personas data to Adobe Target as profile parameters. |
| 37 | + |
| 38 | +### How does it work? |
| 39 | +Adobe Target’s `at.js` script identifies each visitor uniquely through a `PCID`, which is auto-generated in the visitor’s cookies. Since Segment doesn't expect you to include the `PCID` on your Segment events, Segment updates profiles using the `mbox3rdPartyId` instead. |
| 40 | + |
| 41 | +Segment recommends setting the `mbox3rdPartyId` to `userId` (falling back on `anonymousId`) and sets this as the default for your implementation. This allows for a common identifier that can be used to tie server-side data back to the original profile that was created on the web. |
| 42 | + |
| 43 | +Depending on your user's typical journey, a few scenarios can occur when using web and cloud mode together. |
| 44 | + |
| 45 | +#### Scenario 1. Anonymous user never becomes known. |
| 46 | +When an anonymous user arrives on your website, one Adobe Target profile will be created and the `mbox3rdPartyId` will be equal to the Segment `anonymousId`. |
| 47 | + |
| 48 | +If the same anonymous user visits on a different device, they will have a new `anonymousId` and therefore a different `mbox3rdPartyId`, and a separate Adobe Target profile will be created. This is in line with how Adobe’s `PCID` behavior works too. |
| 49 | + |
| 50 | +#### Scenario 2. The user is known from the first point of contact. |
| 51 | +This scenario assumes that your users authenticate and have a `userId` upon arriving on your website. When the user arrives on your website, one Adobe Target profile will be created and the `mbox3rdPartyId` will be equal to the Segment `userId`. |
| 52 | + |
| 53 | +If the same known user visits on a different device, assuming they authenticate immediately, they will have the same `userId` and therefore the same `mbox3rdPartyId`. This means you can target known users across devices. |
| 54 | + |
| 55 | +#### Scenario 3. Anonymous user becomes a known user. |
| 56 | +When an anonymous user first arrives on your website, one Adobe Target profile will be created and the `mbox3rdPartyId` will be equal to the Segment `anonymousId`. However, once the user is identified, they will be assigned a new `mbox3rdPartyId` equal to the Segment `userId`. There will be two profiles in Adobe Target; both will be available for targeting. |
| 57 | + |
| 58 | +### How to use Adobe Target with Personas |
| 59 | +Adobe Target Cloud Mode operates as an [Event Destination](/docs/personas/using-personas-data/#personas-destination-types-event-vs-list/). This means Personas sends computed traits and audiences as traits in `identify` calls or properties in `track` calls. Please see [this example](/docs/personas/using-personas-data/#audience-generated-events/) of the payload Personas would send to Adobe Target. |
| 60 | + |
| 61 | +When you connect Adobe Target Cloud Mode to a Personas space, you will need to set up a mapping for Update Profile. Within the Update Profile mapping, please ensure you have something mapped to Profile Attributes. If you plan to send multiple Personas computed traits and/or audiences to Adobe Target, you can click **Edit Object** and set Profile Attributes to the entire `traits` object. This ensures any audience Personas generates sends to Adobe Target. |
| 62 | + |
| 63 | +You can use Profile Attributes in the Adobe Target Audience builder to construct audiences. For example, if you send an audience for `first_time_shopper` to Adobe Target, select **Visitor Profile** in the Audience Builder and look for the `first_time_shopper` attribute. Setting the `first_time_shopper` attribute to `true` replicates the audience for usage in Adobe Target Activities. |
| 64 | + |
| 65 | +> info "" |
| 66 | +> Segment does not set Profile Attributes to `traits` by default to avoid unintentionally sending PII to Adobe Target. [Adobe recommends that PII is hashed](https://experienceleague.adobe.com/docs/core-services/interface/services/customer-attributes/privacy-mac.html?lang=en){:target="_blank"} prior to sending to Adobe so please hash your data upstream if you choose to send PII. |
| 67 | +
|
| 68 | +## Viewing Segment data in Adobe Target |
| 69 | +To view and use your Segment data in Adobe Target, navigate to **Adobe Target > Audiences > Create Audience > Add Rule**. |
| 70 | + |
| 71 | +- Profile Attributes appear under the **Visitor Profile** attributes. |
| 72 | +- Page Parameters appear under **Custom** attributes. Fields have `page.` prepended to the key. |
| 73 | + |
| 74 | +Audiences can then be used in Adobe Target Activities, such as A/B Testing and Experience Targeting. Please note that while Standard and Premium Adobe Target packages allow access to the SDK and API, certain personalization functionality may only be available with Adobe Target Premium. |
| 75 | + |
| 76 | +## FAQ |
| 77 | +### Why am I getting a `Profile Not Found` error? |
| 78 | +The Adobe Target API can only be used for profile updates. Profiles must be created on the web first, either using Segment’s [Adobe Target Web destination](/docs/connections/destinations/catalog/actions-adobe-target-web/) or a native implementation of `at.js`. Please ensure you are creating profiles via `at.js` first. |
| 79 | + |
| 80 | +Segment’s Adobe Target Web destination sends data in realtime, but it may take up to 1-hour for a user to be available via the Adobe Target API. This means you may see delivery errors for `Profile Not Found` in Adobe Target Cloud until the profile is available for API updates. |
| 81 | + |
| 82 | +In addition, Adobe Target visitor profiles expire after 14 days. [Profile lifetime](https://experienceleague.adobe.com/docs/target/using/audiences/visitor-profiles/visitor-profile-lifetime.html){:target="_blank"} could be another reason a profile is not found. |
0 commit comments