Download websites that use ExactMetrics

About ExactMetrics

A plugin whose only job is to install someone else's tracking code says two things at once, and both of them are useful to know.

ExactMetrics connects Google Analytics to a WordPress site and pulls the reports back into the WordPress dashboard, so whoever publishes the content also sees the numbers without leaving the admin screen. Published by ExactMetrics LLC under the GPL v2 license and dating to 2012, the plugin is written in PHP and handles the parts of an analytics deployment that people get wrong by hand, including the tracking snippet, ecommerce events, form conversions, outbound link tracking and custom dimensions. Presence implies a live analytics property behind the site and an operator who chose configuration over code.

As of September 2026 the plugin runs on 47,779 sites, 17,586 of them on domains registered in United States, with the set weighted to .com. The release picture is unusually detailed for a plugin of this kind, since 195 distinct versions are in circulation and installs cluster on 10.1.3. Update behaviour is the real story in that spread. An analytics plugin sits close to a moving target, because tracking libraries, consent rules and event schemas change on Google's schedule rather than the site owner's, and a site running a release from several cycles ago often collects less than its owner believes.

There is a second thing the plugin reveals, and it concerns the site rather than the software. Analytics can be added with a snippet pasted into a template, and plenty of sites do exactly that. Choosing a plugin instead means the operator wanted reports inside the dashboard, wanted ecommerce and form events configured without touching code, and accepted a dependency to get them. Presence therefore separates sites where somebody reads the numbers regularly from sites where a tracker was installed once and never opened again.

The release column is where the commercial reading sits. Consent management vendors, analytics consultancies, server side tagging providers and privacy tooling all sell into sites that already measure something, and a plugin release indicates roughly when the site last had attention paid to its measurement stack. A site on a current release has an owner who maintains things. A site far behind has an owner who set analytics up once and moved on, and those two prospects need entirely different conversations.

A single domain lookup tells you that a site uses the plugin. The list answers the population questions instead. Which hosts and countries concentrate WordPress sites tracking ecommerce events. How the plugin overlaps with consent banners and tag managers. How much of the base sits on releases old enough to predate the current tracking model, and which of those sites also run a checkout worth measuring.

One more limit deserves stating. Detection reads the asset paths and inline markup the plugin emits, so a site that concatenates its scripts aggressively, proxies analytics through a first party endpoint or strips version query strings can run the plugin without being counted, or be counted without revealing its release. Undercounting is the direction of error, and the release distribution describes the sites that expose a version string rather than the whole base.