I use the following code within my analytics tool and never have an issue with events firing or anything, hopefully it might be of some use.var suiteId //store the s.account if(location.host == ("sitea.com"))  { suiteId = 'mycompany-sitea-prod'; } else if (location.host == ("siteb.com")){ suiteId= '...

I use an JS IF statement within custom code section:Very basic and cut down version of what I use: if(Stage == "abc") { s.events = "event42"; } else if (Stage == "def") { s.events = "event43"; }If you're doing it for non pageviews the code is slightly different due to the way s.tl works

You would simply enter the IP address(es) given to the user on the VPN connection in to the exclude by IP section of Admin. Usually they are the same IP addresses as given to users when connected to the network from a business location.

I've got this open with customer care. Hoping to be fixed in the July MR but not heard for definite yet. 

We've had ongoing issues around this for a year now, increasing the timeout did help a lot but it's definitely not sorted the issue at all.

Thanks for the support, link is: https://apply.youandb.co.uk/cyb/account-opening?applyFor=IM136I do have a funny feeling you're on to something. For reference the function within the react application which loads DTM is: const attachAms = config => {    if (!config.trackingId) {        return;    } ...

Thanks for the reply and the help,I've checked and DTM is set to load Target synchronouslyI get the following console logs when I load the page:SATELLITE: Test & Target: InitializingsatelliteLib-*****.js:10 Failed to execute 'write' on 'Document': It isn't possible to write into a document from an a...

Whenever I load at.js in to DTM and then load a page I get: "Failed to execute 'write' on 'Document': It isn't possible to write into a document from an asynchronously-loaded external script unless it is explicitly opened." for the at.js script and of course Target fails to load.

Cheers unfortunately I can't even get mbox.js or at.js to load! :(

It looks like it's fixed now, just checked and bounce rate was showing as a decimal number but now coming up as percentage again.