The script executes at page loading time but does not block or delay the actual rendering of the page. It collects information about the page, such as the current URL. Optionally, it can be configured to collect additional metadata from the page.

The MXO Tag also enables personalized MXO content to be injected into a page at runtime, replacing and integrating with existing content as the page loads. In the unlikely event that the MXO server is unavailable, or the visitors browser does not support JavaScript, the existing page content is rendered ensuring visitors receive the default web experience as a fall back. If the MXO Tag does not get a response from the MXO server within a 1 second timeframe, the MXO Tag will not inject any content returned after that point ensuring there is no delayed injection on a web page.

You can put the MXO Tag anywhere on a web page. Be aware, though, that each location has it's own pro's and con's.

The MXO Tag operates correctly when used in either the HEAD or BODY of a page. Using the recommended script tag, ensures the loading and execution if the tag is asynchronous and optimal.

The location of the MXO Tag in the page may have an effect on how quickly optimized content loads. If the tag is located at the end of the page, it may not execute as quickly as desired, causing a delay in optimized content loading from the MXO server. Therefore, the further up the page the MXO Tag is placed, the better the performance of optimized content. For this reason, we recommend placing the MXO Tag in the HEAD of a page. It is important to remember, however, that the tag loads asynchronously and placing it in the HEAD may not completely prevent loading or rendering issues.

All data collected by the MXO Tag is stored on Tenant/Space combination with which that data is associated. This also applies to data collected from the Mobile SDKs and MXO APIs. Data is stored only on the secure servers used to host the MXO platform; storage of any data exported from or sent to other servers is controlled by your organization.

MXO cookies are cached for 2 years to allow for effective tracking of customers. No state information or encoded customer information, however, is placed into these cookies. They simply hold MXO customer identifiers and the timestamp of the last request to the MXO Server. In addition to leaving 1st party cookies against the domain of each site, the MXO server also utilizes a 3rd party cookie which is held against the MXO servers domain to achieve efficient tracking between web Touchpoints.

Use the MXO Tag page in the main MXO UI to add the MXO Tag your website.

1. In *MXO *, choose Welcome.
2. On the Welcome page, click Add the MXO Tag to your website.
3. Copy and paste the MXO Tag html from the MXO Tag page into the header on the first page of your website, just before the closing header tag.You can see an example of what the MXO Tag should look like when added to a page on your website correctly, by clicking See an Example on the MXO Tag page.{{< image text="GSG - MXO Tag code" src="Getting Started Guide/GSG - ONE Tag code.png" >}}
4. Repeat Step 4 for each page of your website that you want to optimize.Alternatively, add the script to the website's shared theme or template so it can be accessed by each of the website's pages.

If you add new pages to your website, be sure to add the MXO Tag to those new pages.

By default, the timeout period for the MXO Tag is set to one second. The timeout occurs if the time it takes MXO to return a response to the browser is greater than the time it takes the browser's own DOM Ready event to trigger, plus one second. If MXO is unable respond before the timeout period expires, optimizations are not shown to customers.

With data centers located in both the EU and US, we can ensure optimal performance, regardless of your organizations geographical location.

If the MXO Tag is unable to locate an element or cookie on a page, it returns a DOM failure error to MXO . DOM failures occur if, for example, the MXO Tag is unable to locate an Activity Capture, Activity Tracking, or Optimization Point in the DOM at the given Interaction Point. In the case of cookie capture, DOM failures occur if the MXO Tag is unable to locate the relevant cookie in the users browser at that Interaction Point.

The MXO Tag will attempt to locate a page element or cookie three times, before returning a DOM failure error.