These are actually several questions:
a) Is this only possible if the utag.sync.js file is included as well (and above the existing Webtrends tag in the head of the page)?
b) Could I for example set additional parameters via a synchronously loading JS Extension that the Webtrends Base tag uses then?
c) Is it possible at all to include synchronously loading JS via Tealium? I can't find a "sync" Scope in JS Extensions.
d) Is it mandatory to include the utag.sync.js at the start of the body tag? So far, I had always thought it has to go into the head? Could it go into the head above the existing Webtrends head tag for example?
2. I also read that it is not possible to test utag.sync.js via switching to another environment via Web Companion. What is the best practise to to test utag.sync.js deployments then?
3. I need to add a Webtrends tag to a website to enable us to do some additional Event Tracking. When I do this though, the Webtrends tag by Tealium gets overridden by the Webtrends tag that is already on the page (in the HTML template, not included via Tealium). I can see that when I block the existing tag, i.e. /js/webtrends.load.js, via Fiddler, my Tealium tag fires.
I would probably need to set the main Object of Webtrends to a different name to avoid that. But I don't see such an option in the WT tag configuration settings in Tealium.
Thanks for any help!