Overview of the MXO Tag

The MXO Tag is a single line of JavaScript, added to a web page, that allows MXO content to be injected into that page at runtime.

The MXO Tag uses HTTPS to secure all communications, is automatically updated to the latest version when available, and served directly from the MXO server.

The MXO Tag supports all major desktop and mobile browsers, including Internet Explorer 7.

You can see an example of the MXO Tag by clicking See an Example on the MXO Tag page.

GSG - Tag code

Why do I need the MXO Tag?

To make it easy to track, capture and optimize across web and mobile web sites with minimum configuration, deployment and maintenance effort while also ensuring no adverse impact on a web visitors experience.

How do I enable the MXO Tag?

Add the tag to every page of the web site or mobile web site you want to optimize.

The tag is the same on every page and can easily be added using a shared theme or template within your existing CMS or SMS, avoiding the need for custom tagging associated with many other web analytic implementations.

Once the tag is deployed across the required web pages, all further configuration within web and mobile web sites can be managed through your existing business interfaces.

How does the MXO Tag work?

  1. The MXO Tag is added to a web page.
  2. The customers browser keeps a copy of the one-tag.js file in its cache for 20 minutes before checking for an updated version.
  3. The script executes at page load time, but does not block or delay the loading of the page:
    • The script sends details about the current interaction to the MXO server.
    • The MXO server sends back a response telling the script which content to inject into the page.
  4. Further tracking requests use a 1px gif to send information between the MXO Tag and the MXO server.

The tag requests a small JavaScript file from MXO . This file is compressed and optimized for size and cached for 20 minutes by a visitors browser. This means that for every subsequent page load from a site, there is no network or page load overhead beyond the actual web data-tracking request made by the script.

How and when is the MXO Tag updated?

The ~product Tag, one-tag.js, is hosted on the thunderhead.com domain and undergoes frequent update cycles to allow for security, performance, and feature improvements. These updates happen automatically and do not require you to update any code on your end. The MXO Tag installed on your Touchpoints is specific to your brand, ensuring that updates also occur when you make your own configuration changes, including any customizations you make to the default version or your tag. The customerApi JavaScript SDK contract, as well as the variables available for customized MXO Tag development, are well-established and not subject to change.

New versions of the MXO Tag are announced in our Release Notes and made available on the MXO Tag page in the main UI,

Although not a requirement, we recommend updating the MXO Tag, whenever a new version is released. Note, however, that all pre-existing versions of the tag will continue to function and are fully backwards-compatible.