Implement Target using 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.

The following table lists the various sources where you can get more information about Launch:

Resource Details

Adobe Target Extension

Information about implementing Target using Launch.

Launch by Adobe Reference Architectures

Guides that provide best practices and instructions on how to implement Adobe Analytics, Adobe Target, Adobe Audience Manager, and the Experience Cloud ID Service using Launch in a variety of web architectures.

Adobe Launch Documentation

Information about deploying and managing all of the analytics, marketing, and advertising tags necessary to power relevant customer experiences.

Advantages of Implementing at.js Using the Target Launch Extension

The following advantages apply only if you use Adobe Launch to implement at.js. For this reason we strongly suggest that you use Adobe Launch rather than DTM or a manual implementation of at.js.

  • Allows for Asynchronous Deployment of Target: For more information, see "Adobe Target Extension with an Asynchronous Deployment" in Adobe Target Extension.

  • Solves Analytics and Target Race Condition: Because the Analytics call could be fired before the Target call, the Target call is not stitched to the Analytics call, which can lead to incorrect data. Starting with Launch 0.6.0, the Target Launch extension ensures that the Analytics beacon call will wait until the Target call completes, successfully or not. This should solve the data inconsistency customers might have experienced.

  • Prevents Incorrect Redirect Offer Handling: When you have both Target and Analytics on the page, and there is a redirect offer being executed by Target, you might run into a situation when the Analytics tracker fires a request when it shouldn’t, because the user is being redirected to a different URL. If you implement Target and Analytics via Launch, you’ll not experience this issue, because using Launch, Target will instruct Analytics to abort the Analytics beacon request.