Lifecycle of the MXO Tag

  1. MXO Tag code loads from server, or in most cases, from the browser cache.
  2. MXO Tag code begins executing after all non-asynchronous code executes.
  3. The MXO Tag retrieves the 1st party cookie, one__randomid, from the current site, and sends it to the MXO server
  4. The MXO Server uses the cookie and other contextual information to process the request and deliver track, capture, and optimize instructions back to the browser. The one__randomid cookie may also be updated for future requests.
  5. When the browsers DOM-ready state is reached, the MXO Tag executes the track, capture, and optimize instructions and, in the case of optimize instructions, may replace or overlay existing content with personalized content from the MXO server.
  6. For track and capture instructions, MXO attaches listeners to the relevant UI components. When elements are clicked (for track instructions), or changed or displayed (for capture instructions) the MXO Tag sends these events back to the MXO server for storage. These events are sent using a 1px image request to the MXO server to minimize any disruption to page speed or processing.