Download websites that use Google Tag Manager for WordPress

About Google Tag Manager for WordPress

The interesting figure for Google Tag Manager for WordPress is not how many sites run it but how many different releases are running at once. We record 95 distinct version strings across the installs we can read, which for a plugin whose entire job is to insert a container snippet in the right two places is a striking amount of drift.

Drift on that scale describes the WordPress population more than it describes the plugin. Automatic updates are optional, agencies freeze versions to avoid breaking a client site, and a plugin that keeps working while out of date creates no pressure to touch it. 2.0.2 recurs across a large part of the set, and the long tail behind it consists of sites configured once and never revisited. For anyone selling maintenance, security review or a managed platform, that tail is the addressable market and the version string is the opening line.

Functionally the plugin does something small and load bearing. It places the container in the document head and the fallback in the body without a theme edit, and it pushes structured commerce data into the data layer, which is the part that actually matters. A domain running it has committed to a tag manager as the place where marketing tags live, which implies a marketing function that adds and removes tracking without involving a developer, and very often a commerce plugin underneath supplying the events.

As of October 2026 we see the plugin on 48,173 sites. United States accounts for 17,718 of them and .com runs through the remainder, the ordinary shape for a free plugin distributed through a global repository rather than sold through a channel. Released under GPL v2, written in PHP and available since 2013, the plugin is credited here to Thomas Geiger, though the WordPress ecosystem around tag management includes several separately maintained variants that a fingerprint will not always tell apart. Anyone building a competitive analysis on that attribution should verify it against the plugin header rather than trusting the label.

Two limits apply to the count. A site can load a tag manager without this plugin at all, by pasting the snippet into a theme or a header injection tool, so the list is a subset of tag manager users rather than a measure of them. And the version we read comes from asset query strings that caching and optimisation layers sometimes strip, which leaves a share of installs resolving to presence with no release attached.

The file answers questions a lookup cannot reach. Which agencies deploy the same frozen release across a portfolio of client sites, which hosts concentrate stale installs, which commerce stacks the plugin travels with, and which domains changed their measurement setup between two editions of the data are all aggregate questions, and each one is a prospect list or a research finding depending on who is asking.