GTM templates

Domain

Prefills your tagging server URL and the building blocks

Tagging server URL

DestinationsWhere your data is sent

TransportHow events travel from the web container to the server container

Google tag (GA4)The standard setup: events travel as GA4 hits to the GA4 client, and every server tag fires on them Measurebase data tag (masked)Every event travels masked to the Measurebase data client: no readable data, hashes or known tracking path in the request, so filter lists have nothing to match · names, email and phone are hashed in the browser · GA4, Google Ads and every other server tag fire on it, Profit Tracking included · picked automatically without GA4 Both, per eventThe Google tag stays and sends most events · the events you pick below travel masked through the data tag, so an ad blocker that stops the Google tag does not stop them · GA4 sees one visitor and one session

ConfigurationWhat rides along, and how the data is shaped

Ecommerce eventsThe standard GA4 ecommerce events, reading the data layer Enrichment headersThe geo and device headers from your tagging server, attached to GA4 as event parameters · on when this domain's enrichment power-up is Shopify app data layerBuilt for the Measurebase Shopify app · maps every ecommerce field explicitly (the checkout ignores the "Send Ecommerce data" checkbox), wires the pre-hashed customer data for enhanced conversions, and adds the optional nc_purchase / rc_purchase segment events · triggers follow the event-name prefix (default mb_) on the storefront and checkout events · the order id as mb_event_id on purchase for browser-vs-server dedup WordPress plugin data layerBuilt for the Measurebase WordPress plugin · standard GA4 ecommerce via the data layer, triggers on the plugin's prefixed events (default mb_), lead-form events from Contact Form 7 / WPForms / Gravity / Ninja / Fluent / Elementor, hashed-email enhanced conversions and browser-vs-server purchase dedup on mb_event_id Shopware plugin data layerBuilt for the Measurebase Shopware plugin · the five events it renders (product, add to cart, cart, checkout, purchase) on the plugin's prefixed names (default mb_), hashed-email enhanced conversions on purchase, and the order number as mb_event_id on purchase for browser-vs-server dedup · event IDs come from the Unique Event ID gallery variable like every other block

Web container ID

GA4 measurement ID

Google Ads conversion ID

Meta Ads CAPI

TikTok Ads Events API

Microsoft Ads

Pinterest Ads

Snapchat Ads CAPI

ChatGPT Ads

LinkedIn Ads

Microsoft Clarity

Hotjar

ContainersWhich side you are importing into

Web + serverTwo files, the complete setup Web onlyJust the browser side Server onlyJust the tagging server side

Your templates Generated locally in your browser · nothing is uploaded anywhere

A complete container import, built for your setup

Build your import