Show Menu

at.js integrations

Information about common integrations with Target and their support status with at.js.
If you have a compelling need for an integration that is not supported or mentioned here, please contact your account representative or consultant.

Supported Integrations

Analytics for Target (A4T)
Profiles & Audiences (P&A)
See Audiences in the Core Services User Guide .
Experience Cloud ID Service
Adobe Launch
Launch is the next-generation tag management platform from Adobe and is the preferred method to implement Adobe Target. Launch gives customers a simple way to deploy and manage all of the analytics, marketing, and advertising tags necessary to power relevant customer experiences. See Implementing Target using Adobe Launch .
Dynamic Tag Management (DTM)
See the Best Practices for Implementing Target Using Dynamic Tag Management guide . Important: Adobe Launch is the preferred, up-to-date method for implementing Target and the at.js library. For new Target implementations, use Launch. The following guide is for existing clients using a DTM implementation. Consider the following when using a DTM integration:
  • Library Management: Use the "Custom" hosting option to use at.js. "Automatic" management is not currently supported.
Adobe Experience Manager (AEM) Cloud Service
The AEM Cloud Service enables the creation of A/B tests and Experience Targeting activities within the AEM workflow. Supports at.js with Adobe Experience Manager 6.2 with FP-11577 (or later) . For more information, see Integrating with Adobe Target and select your AEM version.
AEM Experience Fragments
Experience fragments created in AEM in Target activities let you combine the ease-of-use and power of AEM with powerful Automated Intelligence (AI) and Machine Learning (ML) capabilities in Target to test and personalize experiences at scale. AEM brings together all of your content and assets in a central location to fuel your personalization strategy. AEM lets you easily create content for desktops, tablets, and mobile devices in one location without writing code. There’s no need to create pages for every device—AEM automatically adjusts each experience using your content. See AEM experience fragments .

Unsupported Integrations

Legacy Target to SiteCatalyst Integration
This was the integration that sent campaign and recipe ids to SiteCatalyst via the page call so you could do reporting in the SiteCatalyst UI. This functionality is replaced by A4T.
Legacy Target to SiteCatalyst Integration
This was the integration that made mbox calls named "SiteCatalyst: Event" and "SiteCatalyst: Purchase" so you could build success metrics and user profiles based on evars and props. This functionality is replaced by A4T and P&A.
Legacy Audience Manager (AAM) to Target Integration
This was the integration that made a front-end API call to retrieve AAM segments and then sent them as mbox parameters on every mbox call on the page.

Third-Party Integrations

Other Tag Managers
at.js should work with non-Adobe tag management platforms, but be careful using custom integration features that other vendors have developed. Their integrations might be dependent on internal mbox.js functions that no longer exist in at.js.
Third-party data providers (e.g. Demandbase, Bluekai, weather APIs)
Many third-party data providers used to supplement Target's user profiling can be integrated using the at.js Data Providers feature.