Marketing Revolution: setup and help

Upload the release ZIP through Modules > Module Manager > Upload a module, then install it. Open Marketing > Dashboard. Use Marketing > Platforms to configure destinations and Marketing > Settings for shared controls.

Requires PrestaShop 1.6 or later and PHP 7.1 or later.

Start with one destination. Decide whether GA4 will run directly or through your GTM container. If both routes send to the same property, configure them carefully to avoid duplicate events. Review other installed tracking modules and tags as well.

Give employees the appropriate view and edit permissions for the module controllers. Platform saves and actions require edit permission and a valid admin token.

General

Use a consistent identifier across your catalogue feed and events. Shared extraction includes item name, brand, category hierarchy, combination description, price and quantity where available. Order extraction adds currency, tax, shipping, coupons and order identifiers.

Tracking

The log shows the purchases your shop recorded. Check each platform's own reports to see which conversions it accepted.

Consent

Configure a supported consent provider that collects the visitor's choice. The module works with MPR Cookies Revolution and supported Cookiebot, OneTrust and TCF integrations. Consent Mode defaults do not collect consent. Each platform also applies its own consent requirements.

Automation

There are no editable settings under Automation. Resend Missed Purchases, Resend Lookback and Data Language are unavailable. Configure recovery and server delivery on the individual platform forms below.

Check item identifiers before launch

In the shared item extractor, with Product Identifier set to Product ID, a combination uses productID-combinationID, for example 42-7; a product without a combination uses 42. For Reference, EAN-13 / Barcode or UPC, extraction uses available row or catalogue values, including combination values where present. If the selected identifier is missing throughout, the extractor returns an empty identifier. It does not substitute a product ID. Check products with missing references or barcodes and match the identifier format to your destination catalogue before enabling tracking.

Open Marketing > Platforms, choose the platform and open its configuration. Most platform forms have an Enabled switch, initially off. Save the destination ID before enabling it.

Google Tag Manager

Enter GTM Container ID, such as GTM-XXXXXXX. The initial ID is empty. The module supplies ecommerce pushes to dataLayer; you still configure and publish the tags and triggers inside your container.

Track Contact Signals and Track Product Engagement start off. Exclude Employee Browsers also starts off in this suite. Turn it on if your staff visits should be excluded.

For contact and product engagement, test the corresponding controls before enabling them broadly. A GTM container can produce its own page view. The module does not send a separate generic page_view event to GTM for every page.

Google Analytics GA4

For recovery, save the API secret and enable Recover Missing GA4 Purchases. This requires the MPR Cookies Revolution consent integration. Recovery considers purchases recorded after enabling the feature when the customer did not reach the order confirmation page. Orders placed before activation are excluded. Missing buyer identity, consent or a matching destination holds delivery.

Google product engagement controls

GTM and GA4 expose these controls in their own forms:

Test selectors in your actual theme. These controls record observed interactions; they do not establish a purchase or require an advertising conversion label.

Enter Google Ads Conversion ID, such as AW-123456789, and enable the platform. All labels start empty. Fill only the conversion actions you want:

An empty label disables that conversion. The platform also has Track Contact Signals and Exclude Employee Browsers, both off initially. Contact conversions use Phone Click Conversion Label, Chat Start Conversion Label and Confirmed Contact Form Conversion Label, each empty initially. Use the label for the intended action.

Optional refund corrections

Correct Refunded Google Ads Conversions starts off. Configure these fields before enabling it:

The OAuth file must contain the OAuth client ID, client secret and refresh token. Save the fields and check readiness before you enable corrections. Only purchases sent from the browser after setup can be corrected; older conversions are left as they are. The correction task runs only when your cron scheduler runs it.

Open Meta Pixel and enter Pixel ID, initially empty. Enable Facebook Pixel starts off. The suite's Exclude employees default is off. Respect cookie consent starts on. Persist marketing consent withdrawals starts off.

The standard switches Track ViewContent, Track AddToCart, Track InitiateCheckout, Track Purchase, Track Search, Track AddToWishlist and Track CompleteRegistration start on. Disable events your setup does not use. Wishlist and registration events need a supported successful action.

Track custom events starts off. Custom event rules starts empty and accepts the documented JSON trigger rules. Configure and test a rule before enabling it.

Enable Conversions API purchase events starts off on a fresh installation. Add Conversions API access token before enabling it. The token field preserves a saved token when left empty. Test event code starts empty. Graph API version starts at v25.0.

This is server purchase delivery alongside the browser Pixel, with a shared event identity for deduplication. It is not limited to an hourly missed-purchase resend. Check the connection panel, provider queue and Meta's own diagnostics. Clear a temporary test code before production use.

The module also supports these destinations. Their destination credentials start empty and their master switches start off. Use the form for the network you actually use.

Events, privacy and custom rules

Each provider maps the shared events to its supported API. Review its event switches individually. Each advertising platform receives only the events it supports.

Where offered, Track phone-link clicks, Track actual chat starts, Track successful contact forms and Track product engagement start off. Any corresponding Phone target, Chat target, Form target or Engagement target starts empty. Enter the exact account-issued target where the form requires one. Targets are not invented from the Pixel ID.

Send confirmed forms through the server API starts off where supported. A form counts only when the server reports a successful submission; clicking Submit is not enough. Phone clicks and actual chat starts are separate signals. Product engagement thresholds uses the shared defaults of 3 gallery views, 1 variant change, 1 detail click, 45 seconds and 1500 milliseconds. Change its JSON only to match your intended thresholds and theme selectors.

Custom event rules is empty initially and custom tracking starts off where present. Rules can select supported clicks, URLs, controllers or DOM events. Provider restrictions still apply. Criteo, for example, maps to its supported OneTag vocabulary instead of accepting arbitrary new event names.

Review employee exclusion separately on each platform. It is not one universal on-by-default switch. This suite preserves off defaults for Google, Meta, TikTok, Snapchat, Reddit and AdRoll employee exclusion. Consent, outbound-host and ownership checks still apply independently.

Optional server delivery

Server delivery is set up per platform and starts off for the optional routes below. Enter the required credentials and review the platform's consent settings before you enable it.

For Pinterest, Include tax in purchase value, Include shipping in purchase value and Subtract discounts from purchase value each start off. Review these provider-specific values instead of assuming the general price setting decides the purchase total.

Provider test buttons have different behavior. A button named Check test availability or Check test requirements can return guidance without sending an event. Use a provider's documented test route and required test identifiers. A retry action puts eligible failed rows back into processing; it does not repair missing credentials or missing original consent.

Open ChatGPT Ads (OpenAI). Both the global Enable Tracking switch and this form's Tracking enabled must be on for this destination.

Obtain the Pixel ID and Conversions API key for the intended data source. The API key is separate from an Advertiser API key. With required consent, server delivery needs the appropriate advertising-storage grant; the browser also needs the user-data signal. Withdrawal suppresses queued events that are still waiting.

The browser and server use a shared purchase identity to support remote deduplication. The destination handles purchase reporting and attribution. Failed waiting events expire after 6 days and 22 hours in the bundled queue.

Check test-mode availability does not send an event or validate a sample purchase. Retry failed events requeues eligible failed events for the selected shop and Pixel ID.

Turning Browser Pixel off leaves server delivery separately controlled. For a purchase-only setup, leave Purchases on and turn the other commerce events off. Product-and-combination IDs use values such as 42-7; products without a combination retain their product ID.

The optional contact and engagement switches described above also start off here. If the standalone Pixel for ChatGPT Ads module uses the same destination, coordinated ownership decides which module emits and processes the shared queue. Review the ownership status before diagnosing duplicates.

Open its platform form and set:

Test the badge and the survey opt-in on an eligible order confirmation. Your Merchant Center account must support Google Customer Reviews; Google decides that, not the module settings.

These settings support global, shop-group and shop inheritance. Use inherited settings removes local overrides for this platform. Most other module settings are shared across shops. Selecting a shop does not by itself create independent GA4, Meta or OpenAI credentials.

Connect the installed cron infrastructure to regular external execution. The module registers these task identifiers:

Use the authenticated runner or command from the scheduler installed for this shop. Do not expose an unauthenticated write endpoint. The main server workers do not run from visitor traffic. A task runs only when your host actually calls the scheduler, so check that it does.

The storefront receives tracking scripts rather than a new visible widget, except for optional review badge and survey output. Normal integration uses displayHeader, displayBeforeBodyClosingTag, displayOrderConfirmation, displayAfterBodyOpeningTag and media hooks, plus cart/account/order actions and the legacy footer path.

Shared collection covers page views, product views, supported listings and searches, cart views, checkout starts, registrations and logins. Browser tracking supplies confirmed cart additions and supported successful wishlist additions. Check checkout-step signals and other interactions separately; do not assume they are collected automatically. Each provider applies its own supported mappings and gates.

1. Configure one platform with the global switch still off.
2. Check its required credentials and consent integration.
3. Enable the platform and Enable Tracking, then browse as a customer.
4. Verify product IDs, prices, currency and category data in browser requests or GTM preview.
5. Add and remove a product. Check the confirmed event and its quantity.
6. Complete checkout and inspect the purchase destination, value, currency, items and transaction identifier.
7. Check Tracking Log, provider status/queues and remote diagnostics separately.
8. Test refusal, consent withdrawal and your scheduled server route if enabled. Turn Debug Mode off afterwards.

No tracking: check both switches, required credentials, consent, employee/internal-traffic status, outbound-host rules and ownership notices. Tracking is held on unsupported staging/clone routes.

Missing purchases: for browser delivery, check that your checkout shows the normal order confirmation page, which runs the order-confirmation hook. For an enabled API route, check the server queue and the scheduler status. Browser blockers, refused consent and platform outages can still stop tracking.

Duplicate events: review the coordinated owner, older independent modules, hardcoded theme tags and tags published in GTM. Native ps_facebook or ps_googleanalytics integrations with the same destination can still emit duplicate tags and have explicit warnings.

Purchase log says observed: this records the order-confirmation observation and active platform list. It is not a receipt from the external platform.

Unexpected search or customer data: the module sanitizes terms containing email or phone data and applies matching-consent checks. Inspect actual payloads for your setup rather than assuming all data is included.

For custom product cards, keep the product identity available to the supported tracker. The original pattern is:

<article class="product-miniature" data-id-product="123" data-list-name="Category page">
  <h3 class="product-title"><a href="/example-product">Example product</a></h3>
  <span class="price" content="49.99">49.99</span>
</article>

After changing markup, test clicks and real cart additions: the cart event is sent only when a product is actually added, so a matching selector is not enough.

GTM purchase data uses an ecommerce object. For example, a configured container can receive:

dataLayer.push({ ecommerce: null });
dataLayer.push({
  event: 'purchase',
  ecommerce: {
    transaction_id: '123',
    value: 99.99,
    tax: 16.67,
    shipping: 4.99,
    currency: 'EUR',
    items: [{
      item_id: 'SKU-001', item_name: 'Example product',
      item_brand: 'Example brand', item_category: 'Category',
      item_category2: 'Subcategory', price: 99.99, quantity: 1
    }]
  }
});

This illustrates the data shape. Do not paste a second purchase sender into the theme. Configure the container to consume the module's existing output.

Turn Enable Tracking off to stop tracking. Events already in the queue and consent withdrawals are processed on their own schedule. Back up any log or configuration you need before uninstalling.

Uninstall through Module Manager. The module removes its menu, registered tasks, its own database tables, configuration and its queue/attribution ownership through the shared packages. Shared tables follow their package cleanup rules. Previously reported remote events are not erased by uninstalling the module.