Skip to main content

Shared tracking settings

Facebook Pixel & Conversion API builds on the shared Marketing tracking data layer (the Mirasvit_Tm module). Settings that affect what and how data is collected are configured once here and apply to every Mirasvit tracking extension installed on your store (Google Tag Manager, Facebook Pixel, TikTok Pixel, Mixpanel, …).

Navigate to Stores → Settings → Configuration → Mirasvit Extensions → Marketing tracking.

General settings​

  • Product identifier - the product field reported as the item identifier in tracked events (e.g. SKU or ID). Choose the value that matches how you analyze products in your reports.

  • Identifier resolution - how the product identifier is resolved for cart, checkout, and order-success events (parent or child product).

  • Track view catalog page event - when enabled, category/listing page views are tracked in addition to product, cart, checkout, and purchase events.

  • Track prices in store currency - when enabled, product prices are tracked in the current store-view currency instead of the base currency.

  • Track customer group - when enabled, the customer group is added to the event data of all tracking extensions, allowing audience segmentation.

Attribute mapping​

Mapping product attributes enriches tracked events with additional detail. Mapped attributes are added to the event data of all tracking extensions.

  • Track brand on the category pages - include brand information on category pages.

  • Brand - the product attribute associated with the item_brand field. If left empty, brand tracking is disabled.

  • Track variants - track the specific variation (e.g. size/color) a customer interacts with.

  • Custom dimensions and metrics - map additional product or customer attributes into event data to power more granular reports.

Advanced​

  • Disable events (JS condition) - the body of a JavaScript function evaluated on every page load; return true to stop sending events from all tracking extensions for that visitor (e.g. internal traffic or mobile browsers). Leave empty to track every visitor.

    Examples:

    return /(?:^|;\s*)is_internal=/.test(document.cookie) || /Mobi|Android/i.test(navigator.userAgent);
    return localStorage.getItem('no_track') !== null || window.screen.width <= 767;

    A script error keeps tracking enabled and logs a console warning. Only events produced by Mirasvit tracking extensions are withheld - the tracker libraries themselves (and their built-in page views) still load.

  • Debug mode - enables the shared debug tooling used by all tracking extensions. See How to use the frontend debug panel.