Tag Installation

What is the Webtrends Optimize Tag?

It is a JavaScript file that must be installed on your website’s server, to run across all pages. Doing so will enable Webtrends Optimize to communicate with Users web page, for Optimization or Measurement activities as required.

Recommended Integration:

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.


Tag Placement:

  • 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.


Content Security Policies:

Modern web development has seen the introduction of content security policies, which restrict the domains you can call data from.
If you have a CSP in place, please make sure you whitelist the Webtrends Optimize services. If you do not do so, your policies will block calls made to us, and mean experiences are unlikely to load. This should include:

  • *.webtrends-optimize.com – our core services are accessed through this domain.
  • *.azurewebsites.net – some of our custom solutions on more anonymous domains are accessed via. this domain. We can mask them behind our primary domain if needed, and can also let you know which subdomain calls will be made to/from as services are built.