Google Analytics GA4: setup and help

Follow the steps in Quick start.

Open Configure in Module Manager. Use Settings for IDs and tracking controls. Use Diagnostics for checks. Separate License, Support, Update and Integrity pages are present.

Enhanced Conversions hashes email, phone, first name, last name, city, region and postcode after trimming and lowercasing. Country ISO is sent without hashing. Address fields come from the customer's first address when available. This option is separate from hashed customer-ID tracking.

Product engagement

The shared tracker also recognizes variant changes and product detail interactions. Its default behavior limits high intent to once per product/session. Keep this separate from your primary purchase conversion setup.

When Cookies Revolution is active, the module detects it and can move itself last on displayHeader so the CMP initializes Consent Mode first. Use Repair hook order in Diagnostics if needed.

Without that detected CMP, the module emits Consent Mode defaults denying analytics, advertising, ad user data and personalization storage, while security storage is granted. This is a default snippet. It does not create a banner or obtain a consent grant. Configure consent updates through your consent tool.

The browser eligibility gate skips non-front controllers, recognized bots/audit tools, excluded employees and a browser with mpr_notrack=1. To opt out a test browser:

document.cookie = 'mpr_notrack=1; path=/; max-age=31536000; SameSite=Lax';

Server purchases require the buyer’s captured analytics consent, original GA client and session IDs, and permission for this module to send to the configured GA4 property. Browser opt-outs and employee exclusions also apply. Server-Side Purchase Fallback is off by default. To enable it, enter valid credentials and set Purchase recovery hostname to your production shop’s HTTPS hostname, without a scheme or path.

The module loads GA4 asynchronously through displayHeader. It sends ecommerce events through these paths:

There are no separate switches for these standard ecommerce events in this settings form. Their presence depends on the corresponding hooks and theme flow.

Purchase data includes the order reference as transaction_id, value, currency, tax, shipping, coupons and line items. Available item fields include ID, name, price, quantity, brand, category, variant and discount. Review these values against a test order with your tax, discount and shipping setup.

Track custom events defaults to No. Custom event rules starts empty. Add rules, enable the switch and save:

[
  {"event":"gallery_browse","trigger":"click","selector":".product-images img,.images-container img","params":{"component":"product_gallery"},"once":false},
  {"event":"checkout_page_seen","trigger":"url","contains":["/order"],"params":{"area":"checkout"},"once":true},
  {"event":"module_page_seen","trigger":"controller","controllers":["module"],"modules":["mprwishlist"]},
  {"event":"size_guide_opened","trigger":"event","dom_event":"shop:size-guide-opened","params":{"component":"size_guide"},"once":false}
]

document.dispatchEvent(new CustomEvent('shop:size-guide-opened'));

Use event and parameter names starting with a letter, containing letters, digits or underscores, with at most 40 characters. Reserved names and prefixes are rejected. Personal-data-like parameter keys are filtered. Click selectors can have up to 500 characters. once defaults to false for clicks and true for URL, controller and DOM-event rules. Match the controller/module filters to your actual route.

Order validation records eligible purchases for recovery. After 30 minutes without a browser confirmation, the shared cron task queues and sends eligible Measurement Protocol purchase events using the buyer data captured at checkout:

task: send_ga4_measurement_protocol
callable: mprgoogleanalytics::cronProcessMeasurementProtocolQueue
schedule: every:300
context: any
timeout: 30

Ensure your shared MPR cron runner executes this task. Check the event log in Diagnostics and the shared conversion queue. Log rows use your database prefix followed by mpr_analytics_events; ps_ is only the usual example prefix. Retention cleanup runs after eligible order validation. Purchase recovery expires 72 hours after the order. Recovery record retention follows Log Retention (days).

Browser and server purchases use the order reference as transaction_id. A shared delivery record assigns each purchase to one channel. Server recovery handles only orders still missing a browser confirmation after 30 minutes.

Server client and session IDs come from the original GA cookies captured before the order. Missing or unusable IDs hold recovery; the module does not generate replacement identities. The queue does not make browser-only events server-side.

Open Diagnostics and use Run checks. Review required configuration, custom rule validity, hook order, module group visibility, CMP detection, duplicate scripts, exclusions and Measurement Protocol status. Use Repair hook order or Repair module group where relevant.

Use a normal customer browser to check network requests and GA4 DebugView. Bot/audit user agents can be deliberately excluded. Test product view, cart changes, checkout, login, signup, search and a complete order. Verify the transaction reference and item totals.

If no tag loads, check Enable Tracking, the Measurement ID, employee/opt-out exclusions, hook execution and duplicate ownership. If a theme omits displayProductActions or displayBeforeCarrier, the related event may be absent.

If the server purchase is missing, check the fallback switch, ID, secret, capability ownership, queue worker and recent HTTP/error log. An empty secret leaves browser tracking available. GA4 totals can differ from PrestaShop because of blocked scripts, consent, attribution, reporting delays and refunds. This module's purchase tracking is not an accounting reconciliation system.

Set Enable Tracking to No and save to pause this integration. Uninstall through Module Manager to remove its menu, cron registration and module configuration. The shared queue table is kept if another module uses the conversion package; otherwise its uninstall helper drops that table. Manage the GA4 property and its historical data in Google Analytics. The event log uses shared storage; do not drop a shared table manually.

Use the setting names above when a reference screenshot differs from your installed version.