Tracking quality on WordPress

Aggregate stats from every public TagEasy audit where we identified the site as WordPress. Refresh hourly.

WordPress sites audited

121

Median score

79 / 100

Mean score

73 / 100

Consent Mode v2

pass rate

What this means for WordPress

# WordPress Tracking Quality Benchmark WordPress sites sit at a median score of 79, but that obscures a critical compliance gap: 93% fail Consent Mode v2 implementation despite 70% running GA4. The typical WordPress stack is heavily weighted toward analytics (GA4 and GTM at 68–70%) and session replay (Hotjar dominates at 67%), with moderate ad-pixel coverage across LinkedIn, Google Ads, and Meta. Error monitoring is sparse (13% for New Relic), and CDP adoption is negligible at just 6%. The weakest vulnerability is that only 7% of audits pass consent checks—most sites deploy these trackers without proper consent signaling to Google. A secondary weakness: 30% of GA4 implementations lack a valid measurement ID, indicating incomplete setup. WordPress operators should audit their Google Tag Manager configuration, implement Consent Mode v2 callbacks for all restricted vendors, and validate their GA4 property IDs before traffic scaling.

Generated from the WordPress-only stats above. Refreshes hourly.

Score distribution

Where the typical WordPress site lands.

0–19 (broken)

0 sites

20–39 (poor)

0 sites

40–59 (mixed)

28 sites

60–79 (decent)

44 sites

80–100 (healthy)

49 sites

Where WordPress sites fail most

Check	Pass	Warn	Fail
Consent Mode v2	7%	0%	93%
GA4 measurement ID	70%	0%	30%
GTM debug mode	95%	0%	5%
GTM container	68%	32%	0%
Meta Pixel	26%	74%	0%
TikTok Pixel	12%	88%	0%
Google Ads conversion	28%	72%	0%
Consent banner	27%	73%	0%
PII in URL	100%	0%	0%
Tracking script weight	99%	1%	0%
HTTPS	100%	0%	0%
Single GA4 property	86%	14%	0%
DataLayer initialised	48%	52%	0%