Retracks FAQ

What is a retrack?

Monetate evaluates experience and action eligibility on each trackData call that is made on a page. Typically this call is deployed natively on the page and triggered on each page load. If you need to serve content adjustments without a page load, you must add a retrack.

Retracks are used to send page updates to Monetate that may occur without a new page load.

Here are the steps of a retrack:

  1. Create the window.monetateQ object.
  2. Push relevant API methods into that object, such as setPageType, addProductDetails, or addCartRows.
  3. Send data to Monetate using trackData.

The following are some common scenarios and retrack solutions:

  • For an Add to Cart button that adds an item without triggering a page load, use addCartRows in a retrack to pass cart details
  • For a Quick View button that shows product details without triggering a page load, use addProductDetails to pass product details
  • When updates to item color or size selections on a product details page don't trigger a new page load, use addProductDetails to pass updated product details
  • For a single checkout page that calls new forms onto the page (typically using AJAX) without triggering a new page load, use setPageType for cart, shipping, and billing pages
  • For a lazy-loading index page on which new products are called onto the page, trigger addProductDetails to send all product IDs now present on the page on scroll

The monetateQ object is emptied on each trackData call, so you must include all relevant API methods to pass the page attributes you want to evaluate in the trackData call.

Do retracks impact the Average page views metric in analytics?

Each trackData call made to Monetate through the API or a custom integration built by Monetate registers as a page view. (It also triggers the viewPage event in the Monetate Inspector tool.) Therefore, if more than one trackData call happens on a single page, page views may be inflated in the platform's internal analytics.

You can use an optional {'nonPageView': true} parameter for the trackData call to prevent it from counting as a page view.

// Example Track
    "nonPageView": true

The optional {'nonPageView': true} parameter defaults to false.

See AJAX Site Updates for more information about retracks.

What is a rollback?

Rollback is functionality that can be added to a domain implementation that removes actions that have already been served to a page when a retrack occurs without triggering a new page load. It rolls back the action from the page.