TagEasy tracking audit
stripe.com
Needs attention
Mostly there (WooCommerce) (running 4 ad pixels and 1 session-replay tool), but missing Consent Mode v2 drops the score.
Email me the full report
We'll send this report to your inbox now, then re-audit stripe.com on the cadence you pick and email you if the score falls 15 points or more. No account, no password.
Unsubscribe anytime. We won't share your address.
Vendors detected (7)
Across the homepage HTML and the GTM container (if one is loaded). Grouped by category.
Top 44% of WooCommerce sites we've audited
Across 9 audited WooCommerce domains, the median score is 64. stripe.com sits above the median by 0 points.
What we found
Consent Mode v2
FailNo Consent Mode v2 signals detected. Required for EU traffic since March 2024.
How TagEasy helps: TagEasy audits your container against Consent Mode v2 + flags ad tags missing the signal.
Purchase event carries revenue
FailThe GA4 purchase tags in this container are configured without e-commerce data and without explicit value + currency parameters. Purchases will be counted, but they'll arrive worth nothing — revenue reports and ROAS will read zero while the event count looks perfectly healthy.
How TagEasy helps: Either enable "Send Ecommerce data" on the tag, or map value and currency explicitly in the event parameters.
Meta Pixel
WarnNo Meta Pixel detected — fine if you don’t advertise on Meta.
How TagEasy helps: TagEasy auto-configures Meta Pixel + Conversions API if you want it.
TikTok Pixel
WarnNo TikTok Pixel — fine if TikTok ads aren’t part of your stack.
How TagEasy helps: TagEasy auto-configures the TikTok Pixel if you need it.
Consent banner
WarnNo consent-management platform detected. If you serve EU/UK traffic, you almost certainly need one.
How TagEasy helps: TagEasy's container audits flag tags that fire before consent is granted.
DataLayer initialised
WarnNo `window.dataLayer` initialisation detected in the initial HTML. Most templating libraries don't do this for you.
How TagEasy helps: TagEasy's install snippet sets this up correctly.
Tracking on deep pages
WarnNo GA4 or GTM on the homepage, so there was nothing to compare /blog/introducing-our-agentic-commerce-… against.
Duplicate GA4 event tags
Warn3 GA4 event names are fired by more than one live tag in this container (activate_account_step ×3, scroll ×2, purchase ×2). Sometimes deliberate, more often double-counting that inflates conversions and teaches ad platforms to bid on traffic that didn't convert.
How TagEasy helps: Check whether both tags fire on the same trigger — if they do, one of them is counting the same action twice.
GA4 measurement ID
PassFound G-SEKFWD1C9J.
GTM container
PassContainer GTM-WK8882T is loading.
PII in URL
PassNo emails or phone numbers detected in the URL.
Google Ads conversion
PassFound AW-848119022.
Tracking script weight
Pass0 B across identified analytics + tag-manager scripts.
GTM debug mode
PassNo GTM debug/preview parameters exposed.
HTTPS
PassPage served over HTTPS — tracking pixels can set secure cookies and Consent Mode v2 works correctly.
Single GA4 property
PassExactly one GA4 property loading.
Want this fixed?
TagEasy walks you through fixing each issue above, ships you a working container, and monitors it forever after.
The demo is a real workspace with sample data — no signup, no card, nothing to uninstall.
Audit another site
Reports are public + shareable. See recent audits →