Configuration
Configuration
Settings inside WP Admin → GTM Kit: container, consent, dataLayer, and exclusions. For storefront-side wiring, see Integrations.
The basics
Set up the container, choose what fires, and verify the dataLayer is correct.
Consent
Cookiebot, Complianz, OneTrust, and the generic JS API.
- 1Conflicts with cache and consent plugins
- 2Push consent updates from custom code
- 3Scope Consent Mode to specific countries or regions
- 4Script gating mode
- 5Set per-category consent defaults
- 6Turn on Google Consent Mode v2 defaults
- 7Why the consent default must run before the GTM containerIf the Consent Mode default command fires after Google Tag Manager loads, your first tags run without consent instructions. How to fix the ordering on WordPress.
Server Side
- 1Duplicate transaction protection
- 2Order-status webhook events
- 3Serve the Google tag from your own domainThe Google tag gateway loads the Google tag from your own domain instead of from Google, so ad blockers and browser tracking restrictions interfere with your measurement less.
- 4Server-side consent for webhooks
- 5The server-side purchase webhook
Other articles
- 1Configure the GTM container script and noscript
- 2Delay JavaScript execution in GTM
- 3Disable container injection
- 4Engagement events
- 5Exclude logged-in users from tracking
- 6Exclude pages from GTM
- 7sGTM – Server Side Tracking
- 8Staging and development sites
- 9Why your GA cookies reset every 7 days for Safari usersSafari's Intelligent Tracking Prevention caps JavaScript-set cookies at 7 days. Here is what that does to your GA4 data on WordPress, and how to fix it.
Stuck on something specific?
Premium subscribers get same-day email replies on weekdays.
Contact support →