This is actually quite interesting for us as well. We have the following setup: utag.sync.js, loaded synchrounously in the <head> - define Marketing Cloud Visitor ID Service and initialize it with our tracking servers (copied+pasted the whole library in the file) - load the mbox.js via <script> tag to prevent flickering <body> tag - load Adobe Analytics tag But the Marketing Cloud Visitor Service bloats the utag.sync.js file quite a bit and due to the 5 minute cached lifetime of the utag.sync.js this adds some extra request payload for returning visitors (after the cache timeout has expired). What I don't get yet is why there is a tag for the Marketing Cloud ID Service if it required to load synchronously before Target, Audience Manager, Analytics, etc. Is this somehot not a standalone tag in the classic way and instead rendered directly into the utag.js? And if used, if see this correctly that will only work with the asynchronous version of Target, correct? Cheers, Björn
... View more