Before you implement

Several changes occur in your data collection process when enabling Analytics as the reporting source for Target (A4T).

Before you decide to use this integration, review the following sections and consider the impact to your reporting processes:

Implementation requirements


Before you can begin using A4T, you need to request that your account be provisioned for the integration. Use the Marketing Cloud Integrations Provisioning Form to request to be provisioned.

This A4T integration requires that you implement the following library versions (or newer), depending on whether you want to use redirect offers with A4T or not:

Requirements needed if not using redirect offers with A4T

This integration requires that you implement the following library versions (or newer) if you do not plan on using redirect offers with A4T. The order listed is the order of operations.

  • Experience Cloud Visitor ID Service: visitorAPI.js version 1.8.0
  • Adobe Target (depending on your implementation): at.js version 0.9.1 or mbox.js version 61
  • Adobe Analytics: appMeasurement.js version 1.7.0

Requirements needed if using redirect offers with A4T

To use redirect offers with A4T, you must implement the following library versions (or newer). The order listed is the order of operations.

  • Experience Cloud Visitor ID Service: visitorAPI.js version 2.3.0

  • Adobe Target: at.js version 1.6.2

    Note: The mbox.js library does not support redirect offers with A4T. Your implementation must use at.js.

  • Adobe Analytics: appMeasurement.js version 2.1

Download and deployment instructions are listed in Analytics for Target Implementation.

Things to know before you implement

  • This integration is enabled on new activities when you select to use Analytics as the reporting source. After you make the implementation changes described in this document, your existing activities are not impacted.
  • The process of setting up Analytics as the reporting source for Target includes several implementation steps, followed by a provisioning step. It is a good idea to read through the process as described below before implementing. After you complete these steps, you will be ready to use Analytics as your reporting source as soon as it is enabled for you. The provisioning process can take up to five business days.
  • The Visitor ID service creates a shared Visitor ID across the Adobe Experience Cloud. Although it does not replace the Target mboxPC id or Audience Manager UUID, it does replace the way Analytics identifies new visitors. If set up properly, returning Analytics visitors should also be identified via their old Analytics ID to prevent visitor cliffing. Similarly, because the Target mboxPCid remains intact, no Target visitor profile data is lost when you upgrade to the Visitor ID service.
  • The Visitor ID service must execute before your Analytics and Target page code. Make sure that VisitorAPI.js appears above the tags for all other Experience Cloud solutions.


After this integration is enabled, you will experience an additional 5-10 minutes of latency in Analytics. This latency increase allows data from Analytics and Target to be stored on the same hit, allowing you to break down activities by page and site section.

This increase is reflected in all Analytics services and tools, including the live-stream and real-time reporting, and applies in the following scenarios:

  • For live stream, real-time reports & API requests, and current data for traffic variables, only hits with a supplemental data ID are delayed.
  • For current data on conversion metrics, finalized data, and data feeds, all hits are delayed an additional 5-7 minutes.

Be aware that the latency increase starts after you implement the Experience Cloud visitor ID service, even if you have not fully implemented this integration.

Supplemental ID

All Target calls used by an A4T activity to deliver content or record the goal metric must have a corresponding Analytics hit that shares the same supplemental ID for A4T to work properly.

Hits that contain data from Analytics and Target contain a supplemental data ID. You can see this ID in the Adobe Experience Cloud Debugger as the sdid parameter. For example: sdid=2F3C18E511F618CC-45F83E994AEE93A0. This ID is generated anytime the following criteria are in place:

  • The visitor ID service is in implemented
  • A version of mbox.js that supports this integration is implemented.

When troubleshooting, be sure to confirm that the supplemental ID is present on Analytics hits.

Client-side Analytics logging

By default, when at.js, the Experience Cloud Visitor ID Service, and appMeasurement.js are on the page, Analytics and Target correctly stitch events for reporting and analytics purposes in the backend as long as the correct supplemental ID is included from the page, as mentioned above. You won’t need to manage and perform any additional operations for A4T to function correctly.

However, there are cases when you might want to have more control on when and how to send analytics data related to Target to Analytics for reporting purposes. You might have an in-house analytics tool that you leverage for internal purposes but also want to send the analytics data to Analytics via your in-house analytics product so that other members of your organization can continue to utilize Analytics as a visual reporting source. See Step 7: Reference at.js or mbox.js on all site pages in Analytics for Target Implementation for more information.

Shared audiences

While filling in the Marketing Cloud Integrations Provisioning Form, be aware of the following important information concerning the Shared Audiences option listed under “For which capabilities are you requesting provisioning?”

Request form

When you request Shared Audiences, you enable Target and Adobe Audience Manager (AAM) to share information, in this case audiences.


This integration between Target and AAM comes with additional costs. You will be billed for each Target call in AAM.

On this page