GTM Kit puts the Google Tag Manager container code on your website so that you don't need to touch any code. It also pushes data from WooCommerce, Easy Digital Downloads (EDD) and Contact Form 7 to the data layer for use with for Google Analytics 4, Facebook and other GTM tags.<\/p>\n\n
The goal of GTM Kit is to provide a flexible tool for generating the data layer for Google Tag Manager. It is easy to use and doesn't require any coding, but it allows developers to customize the plugin as needed.<\/p>\n\n
The settings are organised around what you are trying to do (Setup, Events & data layer, Commerce, Consent & privacy, and Tools), so related options live together and the setting you need is quick to find.<\/p>\n\n
Tracking fails quietly. A caching plugin strips the container out of the page, a second plugin loads it a second time, a staging copy reports into your live property, and nothing on the settings screen says so.<\/p>\n\n
GTM Kit checks one of your own pages once a day, the way a visitor receives it, and tells you when nothing on your site is loading your container, or when your pages load tracking twice. Where it recognises the plugin or tool adding the second copy, it names it.<\/p>\n\n
WordPress's own Site Health screen reports on GTM Kit directly: whether your container is set up and reaching your pages, whether consent is configured, whether GTM Kit's settings can be saved at all, and, if you serve the Google tag from your own domain, whether that is still working. A GTM Kit section on the Info tab lists your whole configuration on one screen and copies it into a support request with one click.<\/p>\n\n
On sites WordPress reports as staging, development or local, GTM Kit leaves the container out, so test traffic never reaches your live analytics. The data layer is still built there, and a setting loads the container anyway when you are measuring a test site on purpose.<\/p>\n\n
The following GA4 events are automatically included in the dataLayer:<\/p>\n\n
Unlock all features with GTM Kit Premium<\/a>.<\/p>\n\n Ad blockers and browser tracking restrictions treat a script loaded from Google differently from one loaded by your own site. GTM Kit can serve the Google tag from your own domain instead, so the tag loads where a request to Google's domain would have been blocked. The measurement the tag sends still goes to Google; moving that to your domain as well needs Google's tag gateway through a CDN or host that supports it.<\/p>\n\n Before you can switch it on, GTM Kit checks that your server can reach Google and that the address it would serve the tag from is actually reachable, and it repeats both checks once a day afterwards. If either stops working, GTM Kit goes back to loading the container the standard way and tells you, so your tracking never stops without warning.<\/p>\n\n It is off by default, and it is an alternative to pointing GTM Kit at your own server-side container domain rather than something you run alongside one.<\/p>\n\n Depending on how you use Google Tag Manager you can delay the loading of the container script until the browser is idle. This may be relevant to you be if are focusing on pagespeed.<\/p>\n\n You may enter a custom domain name if you are using a custom server side GTM (sGTM) container for tracking. It's also possible to specify a custom loader. GTM Kit has full support for Stape server GTM hosting.<\/p>\n\n You can also exclude specific pages from GTM entirely. Add URL patterns on the Container settings page and GTM Kit holds back the container, the noscript fallback, and its data layer scripts on matching pages. Useful for third-party checkout iframes, partner-hosted subpages, and in-app webview routes that run their own tracking. Glob patterns are supported by default, with optional regex for advanced matching.<\/p>\n\n GTM Kit imports settings from Google Tag Manager for WordPress, Google Tag Manager for WooCommerce, Metronet Tag Manager and other GTM plugins, at any time, from the Tools page. Your container ID, data layer variables, Consent Mode defaults, excluded user roles and container environment come across in one step.<\/p>\n\n Before anything is written you see exactly which of your settings will be replaced, and only settings the other plugin actually configured are touched.<\/p>\n\n You may specify which post data elements you wish to include in the dataLayer for use in Google Tag Manager.\n- Post type: include the type of the current post or archive page.\n- Page type: include a defined page type. I.e. post, page, product, category, cart, checkout etc.\n- Categories: include the categories of the current post or archive page.\n- Tags: include the tags of the current post or archive page.\n- Post title: include the post title of the current post.\n- Post ID: include the Post ID of the current post.\n- Post date: include the post date.\n- Post author name: include the post author name.\n- Post author ID: include the post author ID.<\/p>\n\n If your server-side Google Tag Manager container is hosted on Stape, GTM Kit can use the loader Stape issues for it. This is off by default. When you switch on \"Get the loader from Stape\" under Server-side Tagging, GTM Kit asks Stape's API (api.app.stape.io, or api.app.eu.stape.io for containers in Stape's EU region) for the loader.<\/p>\n\n The request is sent only when you save a change to the settings the loader depends on, or press \"Refresh loader\". It is never sent on a schedule or when a visitor views a page. It contains your sGTM container identifier, your GTM container ID, your sGTM container domain, your data layer name and, when Cookie Keeper is on, the name of the Cookie Keeper cookie. No visitor data is sent.<\/p>\n\n Stape terms of service: https:\/\/stape.io\/terms-conditions\nStape privacy policy: https:\/\/stape.io\/privacy-notice<\/p>\n\n\n Create an account and container in Google Tag Manager<\/a> and get it there.<\/p><\/dd>\n Yes! We strive to support the full feature set of Google Analytics 4 and will implement any future features of Analytics 4.<\/p><\/dd>\n Yes! Pagespeed is one of our main focus points, and we strive to make the plugin compatible with full page caching.<\/p><\/dd>\n You can report security bugs through the Patchstack Vulnerability Disclosure Program. The Patchstack team help validate, triage and handle any security vulnerabilities. Report a security vulnerability.<\/a><\/p><\/dd>\n\n<\/dl>\n\n\n Release date: 2026-09-22<\/p>\n\n Find out about what's new in our our release post<\/a>.<\/p>\n\n Release date: 2026-09-14<\/p>\n\n Find out about what's new in our our release post<\/a>.<\/p>\n\n Release date: 2026-08-24<\/p>\n\n Find out about what's new in our our release post<\/a>.<\/p>\n\n Release date: 2026-08-24<\/p>\n\nEasy Digital Downloads<\/h3>\n\n
\n
Serve the Google tag from your own domain<\/h3>\n\n
Flexible container implementation<\/h3>\n\n
Moving from another Google Tag Manager plugin<\/h3>\n\n
Post data<\/h3>\n\n
External services<\/h3>\n\n
Stape<\/h4>\n\n
\n
\n
Where do I get a GTM Container ID?<\/h3><\/dt>\n
Is Google Analytics 4 (GA4) supported?<\/h3><\/dt>\n
Is this plugin cache friendly?<\/h3><\/dt>\n
How can I report security bugs?<\/h3><\/dt>\n
2.20.0<\/h4>\n\n
New:<\/h4>\n\n
\n
Bugfixes:<\/h4>\n\n
\n
Other:<\/h4>\n\n
\n
2.19.0<\/h4>\n\n
New:<\/h4>\n\n
\n
Bugfixes:<\/h4>\n\n
\n
Other:<\/h4>\n\n
\n
gtmkit_active_cmp<\/code> and gtmkit_cmp_display_name<\/code> filters let a site declare a consent platform GTM Kit cannot detect, such as one loaded by the theme or a code snippet, so Site Health stops reporting consent as unconfigured.<\/li>\nWooCommerce::include_customer_data()<\/code> now takes the order as its second argument, before the order value, and reads every customer field from it. Code that calls this method directly must pass the order.<\/li>\n<\/ul>\n\n2.18.1<\/h4>\n\n
Bugfixes:<\/h4>\n\n
\n
2.18.0<\/h4>\n\n