Everything new in GTM Kit

First public release

Read the release post →

Fixed

• Security hardening: Links served to the settings interface from remote content (upgrade offers, templates, tutorials) and notifications are now validated before they are used for navigation.

Changed

• New gtmkit_settings_registry filter lets add-ons register their settings fields with the GTM Kit settings screen at runtime. The settings screen now exposes its field registry and related metadata, preparing for GTM Kit’s new settings interface.

Read the release post →

Added

• WooCommerce block tracking now loads on block (FSE) themes where Cart, Checkout, Mini Cart, Product Collection, or Related Products are rendered from block templates and template parts. Previously the block tracking bundle could fail to load on these sites, so block ecommerce events never fired.

Added

• New “Engagement events” settings section emits GA4 standard login, sign_up, search, and generate_lead events out of the box. Each event has its own toggle and defaults to on, so customers see the events the moment they upgrade.
• Rebuilt WooCommerce block tracking on stable data-store APIs. Cart, Checkout, Mini Cart, All Products, Product Collection, Single Product, Related Products, the Cart block cross-sells, and product filter blocks now all emit ecommerce events end to end, including add_to_cart and view_cart from the Mini Cart, list and select tracking for the All Products grid and cart cross-sells, and view_item_list re-fires when a filter or pagination control updates a Product Collection.

Fixed

• The Contact Form 7 integration now loads reliably on form pages when “Load JavaScript” is set to the recommended “Only on pages where the Contact Form 7 script is registered” mode, even when a performance plugin (e.g. WP Rocket) defers Contact Form 7’s own scripts until shortcode render. Previously the integration could be skipped on legitimate form pages and gtmkit.CF7MailSent would not fire.

Changed

• New developer filters let extensions tag the method, normalise the search term, assign a lead value, rename the handoff cookie, veto any event, or opt custom search templates into the search event.
• New gtmkit_blocks_supported filter lets developers add custom block names to the list that loads GTM Kit’s block tracking.
• Raised the minimum WooCommerce version to 10.3 for the new block tracking integration. Sites on earlier WooCommerce continue to receive classic-template tracking unchanged.
• Added Vitest and Playwright test harnesses covering the block tracking path, plus PHPUnit coverage for the block detection and Store API extension.

Read the release post →

Fixed

• The “Exclude pages from GTM” feature now also holds back the WooCommerce, Contact Form 7, and Easy Digital Downloads tracking scripts on excluded pages. Previously those add-on scripts could still load on an excluded page and fail, because the core GTM Kit runtime they rely on was withheld there.

Added

• New “Exclude pages from GTM” section on the Container settings page lets you list URL patterns where GTM Kit should stay off. Useful for third-party checkout iframes, partner-hosted subpages, or in-app webview routes that have their own tracking.
• New window.gtmkit.events.push() helper now sits in front of every GTM Kit event push, so an add-on can defer consent-sensitive events in the browser without server-side suppression.

Changed

• The existing gtmkit_container_active filter now receives the actual computed container-active value instead of a hardcoded true, so callbacks that return the value through unchanged automatically honor the new URL exclusion.
• PHP-rendered initial dataLayer content is now emitted through the same client helper, so deferral works the same on full-page-cached and uncached pages.

Read the release post →

Added

• New welcome modal greets fresh installs on their first GTM Kit admin page and links to the documentation. Existing installs are not interrupted.
• GTM Kit can now surface launch and upgrade announcements from gtmkit.com without a plugin release.

Fixed

• Prevent a fatal error on WooCommerce shop and archive pages when another plugin (e.g. WP Grid Builder) re-runs the product loop without a current product in context. GTM Kit now skips its hidden product-data tag instead of crashing the page.
• No more “headers already sent” PHP warning when running WP-CLI commands on sites that use the Cookie Keeper option.

Changed

• New gtmkit_introductions filter and Introduction_Interface contract let add-ons register their own announcement modals through a documented public API.

Read the release post →

Added

• “Exclude tax” toggle now controls every standard e-commerce event the data layer emits: view_cart, begin_checkout, purchase, variation prices on variable product pages (re-fired view_item + add_to_cart), and the per-item coupon discount field.
• Heads up: GA4 numbers may move after this update. Stores with prices entered ex-tax and tax-inclusive cart display will see value change from ex-tax to inc-tax in cart and checkout events.
• New gtmkit_resolve_tax_mode and gtmkit_resolve_item_discount filters let developers override the toggle programmatically (per-event or per-context) and override the per-item coupon discount calculation.
• Minimum required WordPress version is now 6.8 (was 6.7). Sites still on WordPress 6.7 won’t get this update via the dashboard until they upgrade WordPress.

Fixed

• Cart, checkout, variation, and coupon-discount events now follow the “Exclude tax” toggle consistently across value, price, and discount fields. The GTM Kit Woo and GTM Kit Premium add-ons extend the fix to refund and order-paid events in their paired releases.
• Silence the “translation loading triggered too early” notice that WordPress 6.7+ logs against the gtm-kit text domain by registering translations at the very start of init before any other code can request a translated string.
• Close an edge case where a script-dependency notice could still appear under WordPress 6.9.1+ when a consent or CMP plugin toggled the GTM Kit container active mid-request, by asking the WordPress script registry directly which scripts were actually registered instead of re-evaluating the container gate.

Read the release post →

Added

• New gtmkit_consent_admin_badges filter lets add-ons (e.g. Premium’s WP Consent API integration) push status banners onto the Consent settings page so users see immediately when a higher-priority consent source has taken over.

Added

• New “CMP script attributes” section on the Consent settings page lets you toggle Cookiebot, Iubenda, and CookieYes script-blocking attributes with one click and add a custom attribute for any other CMP — no PHP filters required.
• Fresh installs auto-detect a known CMP plugin (Cookiebot, Iubenda, CookieYes) and pre-select the matching toggle so the right attribute is on from day one.
• New “Script gating” mode on the Consent settings page lets you choose between always loading GTM, letting it load under Consent Mode v2 control, or holding it back entirely until consent is granted. Default stays as “Always load” so existing installs see no change.
• Strong-block mode masks the Google Tag Manager container until visitors consent. Works alongside any CMP and falls back gracefully when no consent signal arrives.
• Power users can override which consent categories must be granted before strong-block mode unmasks GTM via the new gtmkit_strong_block_required_categories filter.
• window.gtmkit.consent.state exposes the current consent state so partner scripts and integrators can inspect it without subscribing to events.
• New developer hooks let CMP integrations and consent add-ons plug into GTM Kit’s consent flow without forking the plugin — sites running Cookiebot, CookieYes, WP Consent API or in-house consent solutions can now feed their state straight into GTM Kit.
• Server-side broadcast gtmkit_consent_updated so other plugins can react to consent state changes without polling.
• Per-event gtmkit_event_should_defer filter so future deferral features can hold individual events back when consent is missing.

Fixed

• Eliminate “dependencies that are not registered: gtmkit-container” warnings logged by WordPress 6.9.1+ on sites that have GTM Kit’s container active.

Changed

• The Cookiebot script attribute (data-cookieconsent="ignore") is now configurable via Settings → Consent → CMP script attributes. Existing installs keep the attribute on by default to preserve current behavior; turn it off explicitly if you do not use Cookiebot.

Read the release post →

Added

• Scope Google Consent Mode defaults to specific countries or regions (e.g. DK, DE, US-CA) instead of applying them everywhere. Useful for sites with visitors both inside and outside the EU.
• Consent updates from other plugins or partner scripts can now talk to GTM Kit through a simple JavaScript API, making CMP integrations easier.

Fixed

• Webhooks for Server-side Tracking on the WooCommerce integrations page no longer stay locked after entering an sGTM Container Domain on premium installs.

Changed

• “Wait For Update” is now a proper number field with a sensible 500 ms default on new installs. Your existing value is kept.
• Clearer warning on the Consent Mode page — if Cookiebot, Complianz, CookieYes, or Cookie Information already handles your consent, leave this setting off.
• Introduced an internal automated test suite (PHPUnit + Vitest) and continuous integration across PHP 7.4–8.4 × WordPress 6.9. No functional change — every future release is now verified by unit and integration tests before shipping, raising the bar on quality and reliability.

Read the release post →

Changed

• Declared compatibility with WooCommerce Product Object Caching (product_instance_caching) introduced in WooCommerce 10.5. No functional change; resolves the “incompatible plugins” notice in WooCommerce → Settings → Advanced → Features.
• Tested up to WooCommerce 10.7.
• Tested up to WordPress 7.0.

Fixed

• Add error handling to WooCommerce blocks action handlers to prevent tracking errors from breaking checkout functionality or interfering with third-party plugins.

Changed

• Tested up to WooCommerce 10.6.

Fixed

• Fix undefined array key warning for order-received query var in edge cases like certain payment gateway redirects or bot traffic.

Fixed

• Fixes correct detection of the premium plugin.

Added

• Improved internal handling of plugin settings to make GTM Kit more reliable and easier to maintain, while ensuring full backward compatibility with existing configurations.

Changed

• Tested up to WooCommerce 10.5.
• Require WooCommerce 9.5.

Added

• We have added a new template assistant to help you create your own custom templates for Google Tag Manager.
• Add option to define a custom page that should be detected as the order-received page.
• The debug info now includes a check to determine if WooCommerce purchase events have been recorded in the logs. This information is included in the debug data to assist with troubleshooting and support.

Fixed

• Fix edge case where quantity in the Datalayer was 0. Set a default quantity of 1 when the quantity element is missing.

Changed

• Tested up to WooCommerce 10.3.
• Tested up to WordPress 6.9.
• Require WooCommerce 9.4.
• Require WordPress 6.7.

Read the release post →

Added

• Add tracking on the product collection block.

Changed

• Require WooCommerce 9.2.
• Tested up to WooCommerce 10.2.

Fixed

• Force rounding values to 2 decimal places to fix rounding issues in edge cases.
• In some cases the GTM container would not load after activating and deactivating settings in ‘Server-side Tagging (sGTM)’.

Changed

• Tested up to WooCommerce 10.1.

Fixed

• The add_to_cart event did not fire in the all-products block.

Changed

• Require WooCommerce 9.0.
• Tested up to WooCommerce 10.0.