What’s new in GTM4WP 2.1: Easy Digital Downloads tracking, GA4 refunds and AI assistants
GTM4WP 2.1 for Google Tag Manager on WordPress adds Easy Digital Downloads tracking, WooCommerce refunds in GA4, Site Health and AI assistant support.
If your site stopped with a fatal error after updating to 2.1.0, please read GTM4WP 2.1.1 fixes the fatal error some sites got with 2.1.0.
GTM4WP 2.1 is out on wordpress.org. It is a feature release: the plugin now tracks Easy Digital Downloads stores, can send store refunds to Google Analytics 4 from the server, and reports its setup to WordPress Site Health and to AI assistants. A few data layer values have changed, so please read the section on your GTM setup before you update.
Easy Digital Downloads tracking
The full GA4 e-commerce event set, from view_item to purchase, now works on Easy Digital Downloads stores, on the classic shortcodes and on the EDD blocks, with the same options as the WooCommerce integration. It needs EDD 3.0 or newer, is off by default and is marked as beta in the settings screen.
Refunds in Google Analytics 4
A refund issued in WooCommerce or Easy Digital Downloads can now be sent to GA4 as a refund event from the server, through the Google Data Manager API and a Google Cloud service account. This feature is experimental and off by default. This post explains how it works and what to know before you turn it on.
Reports in the default language
With WPML or Polylang, page data, products, downloads and Contact Form 7 form names can be reported in the default language of the site, so that reports combine across translations. These settings are optional.
Site Health
Tools > Site Health now shows the configuration of the plugin and checks it for common problems.
AI assistants
On WordPress 6.9 and newer, an AI assistant connected to your site via MCP can read the plugin configuration, help find out why tracking does not fire, and change a setting after you confirm it.
Ready for WordPress 7.2
WordPress 7.2, planned for December 8, changes how it filters HTML, and that change would remove the <noscript> part of the container code. GTM4WP 2.1 keeps it on the page, as measured on the current 7.2 beta. Google Search Console requires this part if you verified your site through Tag Manager, so please update before 7.2 arrives. A separate post will follow when 7.2 is released.
Check your GTM setup before updating
If a trigger or variable in your container matches one of these values, it needs to be adjusted:
- Device data reports
ChromeandEdgeinstead ofGoogle ChromeandMicrosoft Edge, WindowsosVersionas10.0or11.0, andtabletas adeviceType. Samsung Internet, Silk, Yandex Browser andChrome OSare reported by name. - The WooCommerce
add_to_cartandremove_from_cartevents reportvalueand the itempriceas numbers, rounded to cents, and 0 when a price is missing. pagePostTermsandpagePrimaryCategoryNamecarry plain text instead of HTML-encoded text.- Several visitor variables are left out when they have no value instead of being sent empty.
visitorEmailHashis normalized the way Google matches user-provided data, so it changes for mixed-case and Gmail addresses. - Wistia percentage milestones follow the playhead, as every other video provider does, so seeking ahead fires the milestones passed.
- With trusted proxy addresses configured, the Cloudflare country code is read only for requests that arrived through one of them, so please add Cloudflare’s IP ranges to the list.
- The integration for WebToffee GDPR Cookie Consent v2.x has been removed. WebToffee v3.x and later connect to Google Tag Manager on their own.
How to update
The update arrives through the Plugins screen as usual. The requirements have not changed: WordPress 6.3, PHP 8.0 and, for the WooCommerce integration, WooCommerce 5.0. Please test the update on a staging site first if your tags rely on any of the values listed above.
2.1 replaces 2.0 as the supported version, and the 2.0 line now receives fixes for reported security issues only. 2.1 is the last main release planned for 2026; only bugfix releases are planned for the rest of the year.
The changelog lists every change. Please report anything you find on the support forum or on GitHub.
