GTM Kit – Google Tag Manager & GA4 integration

Descripción

GTM Kit añade el contenedor de Google Tag Manager en tu sitio web para que no tengas que tocar ningún código. También envía datos de WooCommerce, Easy Digital Downloads (EDD) y Contact Form 7 a la capa de datos para su uso con Google Analytics 4, Facebook y otras etiquetas de GTM.

El objetivo de GTM Kit es proporcionar una herramienta flexible para generar la capa de datos para Google Tag Manager. Es fácil de usar y no requiere codificación, pero permite a los desarrolladores personalizar el plugin según sea necesario.

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.

Eventos de ecommerce rastreados con Google Analytics 4

Los siguientes eventos GA4 se incluyen automáticamente en 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

Implementación flexible del contenedor

Según cómo utilices Google Tag Manager, puedes retrasar la carga del script del contenedor hasta que el navegador esté inactivo. Esto puede ser importante si te centras en la velocidad de la página.

Puedes introducir un nombre de dominio personalizado si estás utilizando un contenedor GTM Server-side (sGTM) personalizado para el seguimiento. También es posible especificar un cargador personalizado. GTM Kit tiene soporte completo para el alojamiento GTM Server-side de Stape.

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.

Datos de las entradas

Puedes especificar qué elementos de datos de entradas deseas incluir en el dataLayer para usar en Google Tag Manager.
– Post type: incluye el tipo de publicación actual o página de archivo.
– Page type: incluye un tipo de página definido, es decir, entrada, página, producto, categoría, carrito, pago, etc.
– Categories: incluye las categorías de la publicación actual o página de archivo.
– Tags: incluye las etiquetas de la publicación actual o página de archivo.
– Post title: incluye el título de la entrada actual.
– Post ID: incluye el ID de la publicación actual.
– Post date: incluye la fecha de la publicación.
– Post author name: incluye el nombre del autor de la publicación.
– Post author ID: incluye el ID del autor de la publicación.

Capturas

Instalación

  1. Instala GTM Kit a través del repositorio de plugins de WordPress.org o subiendo los archivos a tu servidor.
  2. Activa el plugin a través del menú «Plugins» en WordPress
  3. Introduce tu ID de contenedor de GTM y haz clic en «Guardar cambios».

FAQ

¿Donde puedo conseguir el ID del contenedor de GTM?

Crea una cuenta y un contenedor en Google Tag Manager.

¿Es compatible con Google Analytics 4?

¡Sí! Nos esforzamos por ofrecer compatibilidad con todas las funciones de Google Analytics 4 e implementaremos todas sus funciones futuras.

¿Es compatible con plugins de caché?

¡Sí! PageSpeed ​​es uno de nuestros principales puntos de atención y nos esforzamos por hacer que el plugin sea compatible con el almacenamiento en caché de páginas completas.

How can I report security bugs?

You can report security bugs through the Patchstack Vulnerability Disclosure Program. The Patchstack team help validate, triage and handle any security vulnerabilities. Report a security vulnerability.

Reseñas

23 de abril de 2026
Every now and then, plugins cause problems after updates requiring you to work with developers to fix bugs – but this one has worked reliably for years.
21 de enero de 2026 1 respuesta
It’s not working. Instead of this I have to paste script into header of page to have GA4 live again. I spend 4 days with it and it’s not working at all. It was a waste of my time.
16 de octubre de 2024
After years of using GTM4WP I started having troubles tracking the purchase events of my woocommerce. GTM Kit solved every issue in 5 minutes. It’s straightforward to set up. It also imports settings from GTM4WP at first activation, and finally, all my e-commerce events are tracked properly.
26 de septiembre de 2024
I have been using gtm4wp for years and didn’t think I would find anything better. But I did. And with great support. It also fixed the issue with Bricks Builder right away. It looks really great.
Leer todas las 20 reseñas

Colaboradores y desarrolladores

«GTM Kit – Google Tag Manager & GA4 integration» es un software de código abierto. Las siguientes personas han colaborado con este plugin.

Colaboradores

«GTM Kit – Google Tag Manager & GA4 integration» está traducido en 4 idiomas. Gracias a los traductores por sus contribuciones.

Traduce «GTM Kit – Google Tag Manager & GA4 integration» a tu idioma.

¿Interesado en el desarrollo?

Revisa el código , echa un vistazo al repositorio SVN o suscríbete al registro de desarrollo por RSS.

Registro de cambios

2.16.4

Release date: 2026-06-29

Descubre las novedades en nuestra entrada sobre la versión.

Bugfixes:

  • When the Template Assistant cannot generate a container, the page now shows the reason reported by the server inline (and logs the full detail to the browser console), instead of a generic «Error generating template» message that hid what actually went wrong.

Other:

  • The settings screen now ships an sGTM Preview test-send control that GTM Kit Premium registers into the Setup Environment section, so Premium users can send a server-side webhook event to their server container’s Preview/Debug panel.
  • The Event Deferral setting no longer warns about Consent Mode when a consent platform supplies consent through the WP Consent API. The notice now appears only when neither Consent Mode nor the WP Consent API can release deferred events, and its wording names both consent sources instead of implying Consent Mode is required.

2.16.3

Release date: 2026-06-23

Descubre las novedades en nuestra entrada sobre la versión.

New:

  • The Event Deferral setting now warns when it is switched on while Consent Mode is off, because deferred events have no consent signal to wait on and never release in that state.

Bugfixes:

  • The Commerce «Brand» selector now lists your product brand taxonomies again, instead of showing only «(not set)». The redesigned settings screen stopped loading the taxonomy and page lists, so the Brand selector (and other taxonomy- or page-based options) appeared empty regardless of how brands were configured.

2.16.0

Release date: 2026-06-23

Descubre las novedades en nuestra entrada sobre la versión.

New:

  • The settings screen now uses a redesigned, capability-based interface, organising everything into Setup, Events & data layer, Commerce, Consent & privacy, Tools and more.

Bugfixes:

  • The Contact Form 7 «Load JavaScript» setting now shows the recommended choice as selected when the setting has never been saved.

Other:

  • Clarified the Debug log setting description so it reflects that it also logs the server-side webhooks GTM Kit sends, not only the purchase event.

2.15.0

Release date: 2026-06-12

Find out about what’s new in our our release post.

Bugfixes:

  • 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.

Other:

  • 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.

2.14.1

Release date: 2026-06-03

A maintenance fix for the 2.14 line; see the 2.14 release post for what 2.14 introduced.

Bugfixes:

  • 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.

2.14.0

Fecha de lanzamiento: 2 de junio de 2026

Find out about what’s new in our release post.

New:

  • 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.

Bugfixes:

  • 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.

Other:

  • 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.
  • Prepare the settings and setup-wizard bootstrap for React 19, which WordPress will ship in a future release. No behaviour change under the current React 18.

Earlier versions

Para consultar el registro de cambios de versiones anteriores, consulta el registro de cambios en gtmkit.com.