What is the Webtrends Optimize Tag?
Sample Tag Code:
This what your tag for Webtrends Optimize will look like. It will be loaded from the Webtrends Optimize CDN, hosted with Microsoft Azure. It should be referenced using a protocol-relative path, and so will function on both secure (HTTPS) and non-secure (HTTP) pages.
Note that you should not attach async or defer attributes to this script, if you’d like to run experiments without content flickering.
- It is essential that this tag placed into the
<head>tag of each page. Alternative integrations are likely to cause Content Flickering.
- If you’re using Schema.org markup or have dataLayers in the
<head>, it is also recommended to place the Webtrends Optimize tag just after it. Doing so will allow this data to be fed into Optimize, to be used for more advanced Segmentation.
Using Tag Management Containers
- Most Tag Managers are loaded asynchronously, and so inherently do not support flickerless testing.
- This means that there is a delay while their own scripts are fetched and run, and a further delay for any scripts that the Tag Manager then loads in. Any delay at all can cause content flickering, and so the problem has already surfaced before any Testing tool can try to intervene.
- Whilst unsupported, the Webtrends Optimize tag typically will function in a Tag Manager if inserted.