← Back to changelog

GTM Kit 2.16.0: a redesigned settings screen, organised around what you’re trying to do

Free

GTM Kit 2.16.0 gives the settings screen a complete redesign. Instead of a flat list of pages, your settings are now organised by what you are trying to do: Setup, Events & data layer, Commerce, Consent & privacy, Tools, and more. Everything you configured before is exactly where you left it, value for value. It is just easier to find now.

This release also fixes a small Contact Form 7 settings display issue and clarifies the Debug log description. We recommend updating.

What changed

A settings screen organised around capabilities

The old settings layout grew page by page as GTM Kit added features. That worked, but finding the right setting increasingly meant knowing which page it lived on. 2.16.0 reorganises everything around the job you are doing rather than the order features were added.

The new sections group related settings together:

  • Setup: your container ID, how the container loads, and the basics to get tracking live.
  • Events & data layer: the GA4 events GTM Kit emits and the data layer it builds, including engagement events and post data.
  • Commerce: WooCommerce and Easy Digital Downloads tracking in one place.
  • Consent & privacy: Google Consent Mode, CMP script attributes, and script gating.
  • Tools: the template assistant, debug log, and the rest of the utility settings.

Nothing about your tracking changes. Your saved settings, your data layer, and the events GTM Kit fires are all identical to 2.15. The container output is byte-for-byte the same. This is a navigation and presentation change, so the only thing you have to do is enjoy spending less time hunting for a toggle.

If you have bookmarked a specific settings tab, you may need to re-bookmark it after the update.

On a fresh install where you had never saved the Contact Form 7 settings, the “Load JavaScript” option did not visibly mark the recommended choice as selected, even though that is the value GTM Kit uses. 2.16.0 makes the recommended choice show as selected when the setting has never been saved, so what you see matches what runs.

Clearer Debug log description

The Debug log setting description now reflects that it also logs the server-side webhooks GTM Kit sends, not only the purchase event. No behaviour change. The description simply describes what the log already captures.

Developer notes

No new hooks, no removed or changed filters, and no breaking changes in this release. The data layer contract, event names, and payloads are unchanged from 2.15.

There are no minimum WordPress or WooCommerce version changes.

Upgrade notes

Nothing to do. The redesigned settings screen reads your existing configuration as-is; there is no migration step and no settings reset. Classic and block WooCommerce tracking, engagement events, and consent behaviour are all unchanged from 2.15. The Contact Form 7 fix and the Debug log description apply automatically on update.

What’s next

The capability-based layout is the foundation for bringing settings from across the GTM Kit family into one consistent place, so configuration for the add-ons surfaces alongside the core settings rather than on separate screens. More as it lands.