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:
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.
Solved! Go to Solution.
05-22-2019 05:44 AM - edited 05-22-2019 07:12 AM
The caveat I see with this, is if any tag issue which isn't related to target etc within the utag.js occurs which causes the utag.js to fail to load, then you lose the functionality of all those libraries whereas utag.sync.js remains unaffected with tealiums reccomended outlines. Instead of having multiple functionalties go down or be negatively impacted.
Just a thought :)
05-23-2019 01:45 AM - edited 05-24-2019 05:10 AM
Got this feedback from @corbinspicer through ticketing system:
We do not recommend loading Tealium synchronously regardless of how many sync tags you require. Synchronously loading Tealium may have decremental performance issues on your sites and and our best practice is, and always will be, to load Tealium in an asynchronous manner.
Subsequent question: does this then mean that if we want to use the flicker-free solution for Adobe Target we’ll need to put both the Visitor API and Adobe Target code in the utag.sync.js – thus losing the possibility of an easy update & versioning as when they are deployed as tags, do you confirm?
The Marketing Cloud ID will work as a tag with the wait flag off.
The latest version of our Target tag will automatically inject code into utag.sync.js, so the concept of versioning and easy update still exists. If you use the "Adobe Target" tag in the marketplace and have utag.sync.js enabled, this will be handled automatically.