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.

    NOTE
    Use the Send Beacon action in the Adobe Analytics extension so that the Analytics call waits for the Target call. If you directly call s.t() or s.tl() using custom code, Analytics calls do not wait until Target calls are complete.
  • 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.

Previous pageHow to deploy at.js
Next pageImplement Target without a tag manager

Target


Personalization & Experiementation Excellence with Recommendations and AI

Adobe Customer Success Webinars

Tuesday, Mar 4, 4:00 PM UTC

Adobe Target innovations, including GenAI, and best practices on AI-powered personalization and experimentation at scale.

Register

Connect with Experience League at Summit!

Get front-row access to top sessions, hands-on activities, and networking—wherever you are!

Learn more