Marketing Revolution

You can use either approach, or both. If you prefer Google Tag Manager, enable the GTM platform and enter your container ID — all ecommerce events will be pushed to the dataLayer in GA4 Enhanced Ecommerce format. If you prefer direct GA4 tracking without GTM, enable the GA4 platform and enter your Measurement ID. You can even run both simultaneously — GTM for custom tags and triggers, GA4 direct for native event tracking.

Marketing Revolution is designed to be lighter than running multiple separate tracking modules. Instead of 8-15 separate JavaScript SDKs each making their own DOM queries and event listeners, you get one unified event dispatch layer. The module also shares gtag.js between GA4 and Google Ads when both are active, avoiding duplicate script loads. That said, each enabled platform does add its own SDK script. If you enable all 15 platforms, that is more JavaScript than enabling 3. Only enable the platforms you actually use.

Meta Conversions API sends purchase events from your server directly to Meta, bypassing the browser entirely. This means ad blockers, privacy browsers, and iOS tracking restrictions cannot prevent the event from reaching Meta. You do not strictly need it — the standard Meta Pixel works fine for most visitors — but CAPI significantly improves attribution accuracy. Meta increasingly relies on server-side signals for ad optimization. To use it, generate an Access Token in Meta Events Manager → Settings → Conversions API. The module handles the rest.

The module logs every tracked purchase. A cron job runs every hour and compares completed orders against the tracking log. Any order that exists in PrestaShop but was never tracked (because the customer closed the browser, an ad blocker prevented the pixel, or a network error occurred) is automatically resent via the GA4 Measurement Protocol and/or Meta Conversions API. You can configure the lookback window from 6 to 72 hours. This requires API keys configured for GA4 and/or Meta — without server-side API credentials, there is nothing to resend through.

Yes, it has a built-in Consent Mode v2 bridge that works with four consent management platforms: our own MPR Cookies Revolution (auto-detected, zero config), Cookiebot/Cybot, IAB TCF v2 (used by many European CMPs), and OneTrust. The bridge sets default consent to "denied" for both analytics and ads (configurable), then updates to "granted" when the user consents. This ensures Google respects the user's choice while still collecting modeled data for consented users.

You should not run two modules that inject the same tracking script. If you enable GA4 direct in Marketing Revolution, disable or uninstall any other GA4 module to avoid duplicate events and inflated metrics. The same applies to Meta Pixel, TikTok, etc. Marketing Revolution is designed to be your single tracking module — that is the whole point. If you only want to use it for some platforms (e.g., TikTok and Pinterest) while keeping a separate GA4 module, that works fine as long as you do not enable overlapping platforms in both modules.

By default, the PrestaShop product ID is used as the item_id in all tracking events. You can change this in Settings → Product Identifier to use the product Reference, EAN-13 barcode, or UPC instead. This is important for Google Merchant Center / Shopping campaigns where your product feed uses a specific identifier format — the tracking events should match your feed for proper attribution.

The module is multistore-aware — the tracking log records the shop ID, and category hierarchy queries include the shop context. However, platform configuration (pixel IDs, API keys) is currently global, not per-shop. If your multistores share the same advertising accounts, this is fine. If each store has separate GA4 properties or Meta pixels, you would need to configure for the primary store. Per-shop platform configuration is on the roadmap.

Enable Debug Mode in Settings → Debug tab. This logs all events to the browser console, making them visible in Chrome DevTools. You can also use the Debug Inspector (accessible from the Dashboard when debug is on) to look up any order and see the exact JSON payload that was dispatched. For Meta, use the Test Event Code field — events will appear in Meta Events Manager → Test Events. For GA4, use the Realtime report or DebugView in Google Analytics.

The add_shipping_info and add_payment_info events use a MutationObserver to detect checkout step changes by watching for elements with the .-current CSS class inside #checkout or .checkout-process. This works with the standard PrestaShop 1.7+ checkout. Heavily customized checkout modules (including our own Checkout Revolution) may use different markup, in which case these two specific events may not fire. All other events (begin_checkout, purchase, etc.) work regardless of checkout module.

Yes, Marketing Revolution supports PrestaShop 1.6.0.0 and above. On PS 1.6, there are minor limitations: the displayAfterBodyOpeningTag hook does not exist, so noscript fallbacks for GTM, Meta, and Pinterest are not rendered. Add-to-cart tracking uses click interception on cart buttons rather than the PS 1.7+ updateCart event system, which is slightly less reliable with heavily customized themes. All server-side tracking, purchase events, and platform integrations work identically across all versions.

Google Ads uses conversion labels to distinguish between different conversion actions (e.g., a purchase vs. an add-to-cart). In the Google Ads platform config, you can set separate labels for purchase, add_to_cart, begin_checkout, view_item, page_view (remarketing), sign_up, and search events. Only events with a configured label will fire conversions — empty labels are skipped. You create these labels in Google Ads → Tools & Settings → Conversions → Tag setup.

The module tracks the standard GA4 Enhanced Ecommerce event set, which covers the full purchase funnel. Custom events (like "video_play" or "form_submit") are not supported in the current version. If you use Google Tag Manager, you can add custom event tags in GTM that run alongside Marketing Revolution's dataLayer events without conflict.

Uninstalling removes the tracking log table and platform configuration from your database. Historical data already sent to Google Analytics, Meta, etc. remains in those platforms — uninstalling the module does not delete data from external services. If you plan to reinstall later, export your platform configuration first (pixel IDs, API keys) so you do not need to look them up again.

Yes. Google Customer Reviews (GCR) is included as the 15th platform. Configure your Merchant Center ID, set the estimated delivery days, and choose the badge position (bottom-right, bottom-left, or inline). After each purchase, customers see an opt-in to receive a Google survey. The trust badge displays your aggregate rating. Note: GCR only fires on the order confirmation page — it does not track standard ecommerce events like the other platforms.