Description

AnalyticsBadger digs relentlessly into your analytics implementation and does not stop until it finds every broken tag, every misfiring event, and every silent misconfiguration that is costing you real money.

73% of GA4 implementations have silent misconfigurations. No error messages. No red flags. Just wrong data quietly flowing into every report you use to make decisions. On WordPress the problem is worse: security plugins block tracking scripts, caching plugins serve stale containers, and WooCommerce hooks break after updates.

AnalyticsBadger surfaces all of it. One click. Clear results. Actionable fixes.

Why “Badger”?

Honey badgers are relentless. They dig deeper than any other animal, and they do not stop until they find what they are looking for. That is exactly how AnalyticsBadger approaches your analytics implementation.

AnalyticsBadger is built by DopeThemes, makers of FeedProof for WooCommerce.

What it checks (free)

GA4 Measurement ID detection (present, missing, or multiple found)
Duplicate tag detection (Tag Manager plus a direct gtag conflict)
GA4 loading on the front end, verified in a real browser
GA4 page-type coverage (homepage, single posts, archives)
Tag Manager container detection
Enhanced Measurement reminder
Search engine visibility check
Admin-logged-in tracking warning (your own visits skewing the data)
Security plugin conflict scan (Wordfence, Solid Security, All In One Security, BBQ, Sucuri)
Caching plugin conflict scan (WP Rocket, W3 Total Cache, LiteSpeed, SG Optimizer, WP Super Cache)
Analytics script delivery inspection

Built right

Admin only. AnalyticsBadger never adds scripts, styles, or queries to your storefront.
No external services. Audits run locally against your own site configuration.
Lightweight. No build step, no bloat, no tracking of your visitors.

External Services

This plugin does not make any external HTTP requests. All checks are performed locally against the WordPress installation’s own configuration, database, and settings.

The only network request the plugin makes is to your own site: during an audit it briefly opens your own front end and reports the result back to your own WordPress REST API endpoint (/wp-json/), secured by a logged-in administrator nonce. No data is sent to AnalyticsBadger, DopeThemes, Google, or any other third party.

Screenshots

The audit dashboard: your analytics health score, with passing checks and suggestions at a glance.

Every suggestion comes with a plain, one-line fix you can act on. — The audit dashboard: your analytics health score, with passing checks and suggestions at a glance.

Installation

Upload the analytics-badger folder to /wp-content/plugins/, or install it from the Plugins screen in your dashboard.
Activate the plugin through the Plugins screen.
Open the AnalyticsBadger menu in your admin sidebar and run your first audit.

FAQ

Does this replace MonsterInsights or Site Kit?: No. AnalyticsBadger is an auditor, not a tracking plugin. It checks whatever analytics setup you already have and tells you what is broken. Keep using your current tools.
Will it track my visitors?: No. AnalyticsBadger runs only in wp-admin and adds nothing to your public pages. It reads your configuration; it never collects visitor data.
Does it need WooCommerce?: No. WooCommerce is optional. WooCommerce-specific tracking checks are planned for a future release and skip cleanly when WooCommerce is not active.
How does AnalyticsBadger check my live pages?: When you run an audit, AnalyticsBadger briefly opens your own front end in a hidden frame and reads what loads in the browser, then reports back to your dashboard. This probe is served only to you, the logged-in administrator, and only during an audit. It is never shown to real visitors and it never collects or stores visitor data.
A security plugin seems to block the check. What should I do?: Some firewalls block the REST API or admin-ajax, which can stop the front-end probe from reporting. AnalyticsBadger falls back automatically where it can, and tells you when verification is unavailable. Allowlist the REST API (/wp-json/) and admin-ajax in your security plugin so the check can complete.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“AnalyticsBadger: Analytics Auditor” is open source software. The following people have contributed to this plugin.

Translate “AnalyticsBadger: Analytics Auditor” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

1.1.1

Added an External Services section to the readme. The plugin makes no third-party HTTP requests: every check runs locally, and the only network request is to your own site’s REST API during an audit.

1.1.0

Major accuracy and trust overhaul. The health score now tells the truth: a site with no working analytics can no longer score a passing grade, and “could not verify” is shown honestly instead of being counted as near-perfect.
Detection is far more precise. IDs are read from the exact plugin fields and real tag code that hold them, so look-alike text (a “G-Suite” label, a “GTM-Setup-Guide” link) is never mistaken for a measurement ID.
Added detection for WooCommerce Google Analytics, Jetpack, CAOS, and more, so fewer real setups are missed.
Server-side and real-browser results are now reconciled into one verdict per fact, so the dashboard never says “missing” and “loading fine” about the same tag.
The browser check now allows for consent mode, delayed JavaScript, and admin-excluded tracking, reporting “not verified” instead of a false failure.
Added the official AnalyticsBadger logo to the dashboard.

1.0.1

Fixed a PHP warning when building the front-end probe targets on sites where the first post or category was not at the expected array position.

1.0.0

First public release. Eleven free checks across server-side detection and real-browser verification, a 0 to 100 health score with letter grade, and clear one-line fixes.
Privacy-safe front-end probe, security-reviewed nonces and capability checks, full translation support, and an accessible, responsive dashboard.

0.9.0

Release candidate hardening: separated the audit nonces so each background action verifies its own, after an independent security review.
Final accessibility and standards pass ahead of the 1.0 release.

0.8.0

Prepared for WordPress.org: full readme with FAQ, a generated translation template, and a clean security and standards pass.
Added FAQ entries explaining the privacy-safe front-end probe and what to do when a security plugin blocks it.

0.7.0

Polished the dashboard: results grouped by severity (Critical, Warnings, Suggestions, Passing) with collapsible sections and expandable fix steps.
Added accessible labels, clear focus styles, reduced-motion support, and a responsive layout for smaller screens.

0.6.0

Completed the free check set: GA4 page-type coverage (homepage, single posts, archives), Tag Manager container detection, and an Enhanced Measurement reminder.
The front-end probe now checks multiple page types in one run, so template-specific tracking gaps are caught.

0.5.0

Added the front-end detector: a read-only probe that loads only for a logged-in administrator who runs an audit, never for visitors, and verifies in the browser what actually loads (GA4, Tag Manager, dataLayer, consent mode).
Added a nonce-secured REST endpoint to receive probe results, with an admin-ajax fallback for sites where a security plugin blocks the REST API.
Added a GA4 front-end loading check that confirms tags fire on live pages, or reports clearly when verification is unavailable.

0.4.0

Added security plugin conflict detection (Wordfence, Solid Security, All In One WP Security, BBQ, Sucuri).
Added caching plugin conflict detection (WP Rocket, W3 Total Cache, LiteSpeed, SG Optimizer, WP Super Cache and more), including a warning when WP Rocket delay JavaScript is on.
Added an analytics script delivery check. Conflict detection reads the active plugin list, never remote probes.

0.3.0

Added the first four checks: GA4 measurement ID detection, duplicate tag conflict, robots.txt rules, and an admin traffic tracking warning.
Added server-side analytics detection across popular analytics plugins, header and footer code, theme settings, and registered scripts. No external requests.

0.2.0

Added the audit engine: check interface, result objects, a check registry, and a 24-hour cached audit run.
Added a 0 to 100 health score with letter grade and a status breakdown.
Added the Run Audit button, dashboard results view, and a settings screen for the expected measurement ID and per-check toggles.

0.1.0

Initial foundation: plugin scaffold, admin menu, activation and uninstall lifecycle, and internationalization setup.