Tracking quality on WordPress

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

WordPress audits

Median score

79 / 100

Mean score

72 / 100

Consent Mode v2

pass rate

What this means for WordPress

# WordPress Tracking Quality: Consent Crisis on Custom Pixels WordPress sites show a median tracking score of 79, but this masks a severe compliance breakdown. Every single site audited fails to implement consent on custom pixels, and 93 percent lack Consent Mode v2—despite Google's September 2024 mandate. The stack is heavily concentrated in analytics (GA4 and GTM run on 74 and 69 percent of sites) and session replay (Hotjar dominates at 68 percent), but ad pixel adoption is fragmented across Meta, Google, and LinkedIn at 31, 31, and 29 percent respectively. Notably, CDP penetration sits at just 7 percent, suggesting most WordPress operators aren't building unified data layers. The compliance debt is immediate: custom pixels firing without user consent expose these sites to GDPR and regulatory fines. Audit your WordPress installation for undeclared tracking, then layer in Consent Mode v2 before your next campaign.

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)

13 sites

60–79 (decent)

32 sites

80–100 (healthy)

23 sites

Where WordPress sites fail most

Check	Pass	Warn	Fail
Consent on custom pixels	0%	0%	100%
Consent Mode v2	7%	0%	93%
GA4 measurement ID	74%	0%	26%
Tracking on deep pages	90%	0%	10%
GTM debug mode	97%	0%	3%
Meta Pixel	31%	69%	0%
TikTok Pixel	10%	90%	0%
Google Ads conversion	31%	69%	0%
Consent banner	28%	72%	0%
DataLayer initialised	51%	49%	0%
GTM container	69%	31%	0%
PII in URL	100%	0%	0%
Tracking script weight	99%	1%	0%
HTTPS	100%	0%	0%
Single GA4 property	84%	16%	0%
Duplicate GA4 event tags	0%	100%	0%
Purchase event carries revenue	100%	0%	0%