Google Tag Manager: setup and help

Follow the steps in Quick start.

Open Configure from Module Manager. The form has Core, Server-side, Events, Traffic and Consent tabs. Use the separate Diagnostics page for checks. License, Support, Update and Integrity controllers are also present.

Remove duplicate manual container loaders from your theme or other modules. The module also checks which MPR integration owns the configured container and GA4 destination. Resolve ownership before testing delivery.

Configure your GTM workspace yourself. Map the module's dataLayer event names and parameters to the tags you want to send, and set the appropriate consent requirements. Installing the module does not publish those GTM tags.

The module loads gtm.js through the shared browser runtime. The displayAfterBodyOpeningTag hook remains registered, but its current body template contains no noscript iframe. Do not use an iframe as your installation check.

Each standard switch defaults to Yes. Disable the events you do not need.

Cart events record successful quantity changes, rather than unsuccessful attempts to add a product. Test successful quantity changes in your theme.

Contact and product engagement

Product engagement uses defaults of 3 gallery interactions, 1 variant change, 1 detail interaction or 45 seconds. High intent is limited per product per page without session-storage deduplication in this GTM integration. Use GTM consent requirements for any receiving tags.

Enhanced Conversions is attached to eligible purchase data. It is not an unconditional separate enhanced_conversions_data event on every logged-in page. The module checks buyer matching permission before constructing that data.

Custom event rules

[
  {"event":"gallery_browse","trigger":"click","selector":".product-images img,.images-container img","params":{"component":"product_gallery"},"once":false},
  {"event":"promo_page_seen","trigger":"url","contains":["/special-offer"],"params":{"campaign_area":"landing_page"}},
  {"event":"checkout_seen","trigger":"controller","controllers":["order","order-opc"]},
  {"event":"gallery_open","trigger":"event","dom_event":"mpr:gallery-open","params":{"component":"product_gallery"}}
]

document.dispatchEvent(new CustomEvent('mpr:gallery-open'));

Names must start with a letter, use letters, digits or underscores, and have at most 40 characters. Reserved names/prefixes and personal-data-like parameter keys are filtered or rejected. Click selectors have a 500-character limit. once defaults to false for clicks and true for URL, controller and DOM-event rules. Configure GTM triggers for the exact custom names.

Exclude logged-in employees defaults to Yes. The runtime checks staff/opt-out policy when it sends; shared public HTML can still contain static configuration for an excluded visitor. The private event endpoint applies its own eligibility checks.

Bot, crawler, audit-tool and headless-browser user agents are recognized by the traffic helper. A request made with curl is not equivalent to a normal customer-browser test.

To opt out a browser:

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

Emit Consent Mode fallback (when no CMP installed) defaults to Yes. The form describes the default-denied fallback for a shop without Cookies Revolution. Repair hook order is an action that moves this module last on displayHeader after the CMP. It is not a stored switch.

The active shared Google runtime also establishes denied defaults and reads live consent. GTM's container/dataLayer path delegates downstream tag consent to your GTM configuration. Private cart/pending events and purchase authorization require the applicable explicit analytics/service decision. Configure both the container's consent behavior and your CMP; a fallback is not a consent banner.

Test consent refusal, grant and withdrawal with the actual CMP and GTM tags. The runtime contains support for additional CMP readers, but this module's hook-order helper specifically detects Cookies Revolution. A missing buyer decision holds private/server purchase delivery.

Save both credentials before enabling the fallback. It covers purchase only. The module records the buyer's GA client ID and analytics consent when the order is validated and checks them again before sending. A purchase without the buyer's own GA client ID is not sent; no replacement ID is generated. Staff orders, missing buyer data, ownership conflicts, outbound restrictions or a withdrawal can hold a purchase.

Order validation admits purchases to a durable queue; it does not directly send an HTTP request to GA4. The registered worker also discovers eligible recent purchases:

task: send_ga4_measurement_protocol
callable: mprgoogletagmanager::cronProcessMeasurementProtocolQueue
schedule: every:300
context: cron
timeout: 30

Make sure your shared MPR cron runner executes this task. The worker sends batches of 20; there is no batch-size field on this settings screen. The worker uses the buyer data recorded at checkout, never the cookies of the person running cron.

Browser and server payloads use the order reference as transaction_id, and a shared ledger stops the same order from being sent twice. Place a test order and check how it appears in your destination, including values and items.

Use Diagnostics > Run checks to review configuration, duplicate containers, hook order, module group visibility, custom JSON and server status. Use Repair hook order or Repair module group when indicated.

In GTM Preview, confirm each event name and inspect ecommerce.currency, ecommerce.value and ecommerce.items. Purchase data includes transaction reference, tax, shipping, coupons and available item fields such as ID, name, brand, category, variant, price and quantity. The integration clears the previous ecommerce object before pushing another ecommerce event.

Public output holds static configuration. Customer/cart/pending data is obtained through the authenticated private endpoint. Check that your cache does not serve private responses to another visitor. Check a test order in Preview and in the receiving analytics account after configuring and publishing the container.

If the container is missing, check the master switch, Container ID, destination ownership, browser staff policy, blocked scripts and missing shared assets. The current body template is intentionally empty.

If events are absent, check their switches, theme hook execution, the private endpoint response and consent. Use a successful cart change; the retained before-update hook does not emit events. A custom checkout may require its own rule or integration.

If server purchases are held, check the saved credentials, that the worker runs, the recorded buyer data, the original GA client ID and withdrawals. Check diagnostics and recent event logs. The log table uses your configured database prefix followed by mpr_analytics_events.

Set Enable Google Tag Manager to No and save to pause the module's integration. Uninstall through Module Manager to remove its menu, module configuration and cron registration. This uninstall method does not explicitly delete event-log or queue rows. Shared infrastructure follows its schema retention rules; do not drop tables manually. Your GTM container and Google Analytics history remain in those services.

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