Implement Target using ÃÛ¶¹ÊÓƵ Experience Platform
Tags in ÃÛ¶¹ÊÓƵ Experience Platform are the next generation of tag management capabilities from ÃÛ¶¹ÊÓƵ. 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:
Advantages of implementing at.js using the Target extension
The following advantages apply only if you use tags in ÃÛ¶¹ÊÓƵ Experience Platform to implement at.js. For this reason, ÃÛ¶¹ÊÓƵ strongly suggests that you use tags in ÃÛ¶¹ÊÓƵ Experience Platform rather than a manual implementation of at.js.
-
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. 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 ÃÛ¶¹ÊÓƵ Experience Platform solves the data inconsistency customers can experience when implementing manually.
note note NOTE Use the Send Beacon action in the ÃÛ¶¹ÊÓƵ Analytics extension so that the Analytics call waits for the Target call. If you directly call s.t()ors.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 ÃÛ¶¹ÊÓƵ Experience Platform, you’ll not experience this issue. Using tags in ÃÛ¶¹ÊÓƵ Experience Platform, Target instructs Analytics to abort the Analytics beacon request.