Hello Support, We have to define new guidelines for the best Tealium web implementation across the whole organisation, which also uses Adobe products (Visitor API, Target, Analytics, Audience Manager). We have some questions that are underlined. We currently see two alternatives: utag.sync.js included in a synchronous way, then data layer definition, then utag.js loaded asynchronously: this looks like the approach Tealium recommends the most, however requires some tags to be hard-coded in the utag.sync.js template to have them working flawlessly (e.g. Adobe Experience Cloud Visitor ID Service and Adobe Target) Optional utag.sync.js included in a synchronous way (should be empty), then data layer definition, then utag.js loaded synchronously (which then loads most of the tags asynchronously): this could slightly slow down the page (we guess Load Rules are evaluated synchronously; is any Extension loaded synchronously as well - e.g. Pre-Loader, All Tags...?), but allows using the Adobe Exp. Cloud Visitor ID Service and Adobe Target tags through the standard TiQ management (flagged to be loaded synchronously). The fact that Load Rules, Extensions, etc. have exception handling, should prevent any impact on the user experience (do you confirm?) As you may understand from what's above, we tend to prefer option #2, however we would like to understand with you Tealium guys (and the Community) if we took into consideration all the possible issues and if you can recommend this implementation similarly to the "standard" one. Looking forward to hearing from you. Thanks, Lorenzo
... View more
Expand/CollapseMenu
