GTM Kit Premium adds a Google Tag Manager container to a WordPress site without editing code. It builds a flexible data layer and can pass information from WooCommerce, Easy Digital Downloads, and Contact Form 7 to Google Analytics 4 (GA4), Facebook, and other tags configured in Google Tag Manager. Developers can personalize the extension when needed.

Set up the container and data layer

Configure the add-on through its Setup, Events & data layer, Commerce, Consent & privacy, and Tools sections. Choose which post data to include in the data layer, such as post type, page type, categories, tags, title, ID, date, and author details. Consent settings include Google Consent Mode and CMP script attributes.

Choose commerce events for measurement

For WooCommerce, GTM Kit Premium adds GA4 events for product discovery, cart activity, checkout, orders, refunds, and subscriptions:

• Product and cart: view_item_list, select_item, view_item, add_to_wishlist, add_to_cart, view_cart, and remove_from_cart.
• Checkout: begin_checkout, add_shipping_info, and add_payment_info.
• Orders and subscriptions: purchase, refund, order_paid, order_processing, order_completed, order_refunded, and subscription_started.

Easy Digital Downloads includes view_item, add_to_cart, begin_checkout, and purchase. Use these events as a starting point for configuring analytics and advertising tags in Google Tag Manager.

Control where the container loads

When WordPress identifies a site as staging, development, or local, GTM Kit leaves out the container so test traffic does not reach a live analytics property. The data layer is still built, and a setting lets you load the container when you intend to measure a test site.

You can also exclude pages using URL patterns. Glob patterns are supported, with optional regex for advanced matching. On excluded pages, the plugin holds back the container, its noscript fallback, and its data layer scripts.

Choose a tag delivery method

You can delay loading the container script until the browser is idle. GTM Kit can also serve the Google tag from your own domain. Before enabling this option, it checks whether your server can reach Google and whether the serving address is reachable. These checks repeat daily. If one fails, the plugin returns to standard container loading and notifies you. This option is off by default and is an alternative to using a custom server-side GTM container domain. The tag's measurement requests still go to Google; routing those requests through your domain requires a Google tag gateway supported by your CDN or host.

For a custom server-side GTM container, you can enter its domain and specify a custom loader. GTM Kit works with the loader provided by Stape. If enabled, the plugin requests that loader when you save settings it depends on or choose “Refresh loader.” The request includes configuration details, not visitor data.

Verify tracking and settings

Once a day, GTM Kit checks one of your pages as a visitor would receive it. It reports when no container loads or when tracking loads twice. When it recognizes the plugin or tool adding a duplicate, it identifies it.

WordPress Site Health checks container setup and delivery, consent configuration, whether settings can be saved, and whether Google tag delivery from your domain is working. The Info tab shows the full configuration on one screen and can copy it into a support request.

Import settings when switching add-ons

From the Tools section, you can import settings from other Google Tag Manager extensions, including Google Tag Manager for WordPress, Google Tag Manager for WooCommerce, and Metronet Tag Manager. The import can bring across configured container details, data layer variables, Consent Mode defaults, excluded user roles, and container environment. Before saving, review which settings will be replaced. Only settings configured by the other plugin are changed.

Install and confirm the setup

Install GTM Kit Premium through the WordPress plugin installation workflow, open its settings, and complete Setup with your container details. Review Events & data layer, Commerce, Consent & privacy, and Tools, then confirm the configuration using the available diagnostics.