內容簡介
GTM Kit 是一款將 Google Tag Manager 容器代碼輕鬆整合至網站的外掛，無需編寫程式碼。它能將 WooCommerce、Easy Digital Downloads 和 Contact Form 7 的數據推送至數據層，方便用於 Google Analytics 4 和其他 GTM 標籤。
【主要功能】
• 自動生成數據層，支持多種電商事件
• 每日檢查追蹤狀態，確保容器正常運作
• 可從自有域名提供 Google 標籤，提高測量準確性
• 支持靈活的容器實作，延遲載入以提升頁面速度
• 可排除特定頁面，避免不必要的數據追蹤
外掛標籤
開發者團隊
② 後台搜尋「GTM Kit – Google Tag Manager & GA4 integration」→ 直接安裝（推薦）
📦 歷史版本下載
原文外掛簡介
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.
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.
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.
Know when your tracking breaks
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.
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.
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.
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.
eCommerce events tracked with Google Analytics 4
The following GA4 events are automatically included in the dataLayer:
WooCommerce
view_item_list
select_item
view_item
add_to_wishlist [Premium]
add_to_cart
view_cart
remove_from_cart
begin_checkout
add_shipping_info
add_payment_info
purchase
refund [Premium]
order_paid [Premium]
order_processing [Premium]
order_completed [Premium]
order_refunded [Premium]
subscription_started [Premium]
Unlock all features with GTM Kit Premium.
Easy Digital Downloads
view_item
add_to_cart
begin_checkout
purchase
Serve the Google tag from your own domain
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 more of your measurement survives the trip.
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.
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.
Flexible container implementation
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.
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.
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.
Moving from another Google Tag Manager plugin
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.
Before anything is written you see exactly which of your settings will be replaced, and only settings the other plugin actually configured are touched.
Post data
You may specify which post data elements you wish to include in the dataLayer for use in Google Tag Manager.
– Post type: include the type of the current post or archive page.
– Page type: include a defined page type. I.e. post, page, product, category, cart, checkout etc.
– Categories: include the categories of the current post or archive page.
– Tags: include the tags of the current post or archive page.
– Post title: include the post title of the current post.
– Post ID: include the Post ID of the current post.
– Post date: include the post date.
– Post author name: include the post author name.
– Post author ID: include the post author ID.
