Edit in GitHubLog an issue

Implement Target using Adobe Experience Platform

Tags in Adobe Experience Platform are the next generation of tag management capabilities from Adobe. Tags give customers a simple way to deploy and manage 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:

ResourceDetails
Add Adobe TargetThis tutorial provides step-by-step instructions to implement Target in a website with tags in Adobe Experience Platform. Topics include adding the at.js JavaScript library, firing the global mbox, adding parameters, and integrating with other solutions. This article is part of a larger tutorial that shows you how to implement Adobe Experience Platform, and other Adobe Experience Cloud solutions.
Quickstart guideInformation about deploying and managing the analytics, marketing, and advertising tags necessary to power relevant customer experiences.
Adobe Target extension overviewInformation about implementing Target using Adobe Experience Platform.

Advantages of implementing at.js using the Target extension#

The following advantages apply only if you use tags in Adobe Experience Platform to implement at.js. For this reason, Adobe strongly suggests that you use tags in Adobe Experience Platform rather than a manual implementation of at.js.

  • Solves Adobe 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. This sequencing can lead to incorrect data. The Target extension ensures that the Analytics beacon call waits until the Target call completes, successfully or not. Using tags in Adobe Experience Platform solves the data inconsistency customers can experience when implementing manually.
  • Prevents incorrect redirect offer handling: If you have Target and Analytics on the page, and there is a redirect offer executed by Target, you can experience a situation in which 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 tags in Adobe Experience Platform, you’ll not experience this issue. Using tags in Adobe Experience Platform, Target instructs Analytics to abort the Analytics beacon request.
Was this helpful?
  • Privacy
  • Terms of Use
  • Do not sell my personal information
  • AdChoices
Copyright © 2022 Adobe. All rights reserved.