ANALYTICS TAG MONITORING
Tags break quietly. You’ll know first.
Tag Clarity watches every gtag and dataLayer hit across every site you manage. It flags missing GA4 parameters, consent gaps and sudden volume drops before they surface in someone’s report.
- Consent Mode signals
- read on every hit
- GA4 required parameters
- checked per event
- Volume drops
- flagged against the 7-day average
01 · PORTFOLIO
Every site’s tagging health, on one screen.
Projects are grouped by root domain, so a brand’s shop, blog and application flows sit together, including multi-part domains like .co.uk and .com.au. Each shows its status, consent coverage and what needs attention.
02 · WHAT IT CATCHES
Six ways tagging fails. Each one has a name.
Every event and property your sites send is catalogued and checked daily. When something drifts, you get the event, the rule it broke and the numbers behind it, not a vague “data quality” score.
- 01
An event stops firing
An established event recorded no hits yesterday.
missing_eventsnewsletter_signup 0 hits yesterday 7-day avg 41/dayReview required - 02
Volume swings sharply
Yesterday moved 50% or more against the trailing 7-day average.
traffic_changesadd_to_cart 312 vs 655 avg −52%Review required - 03
A required GA4 parameter goes missing
Absent, or present on fewer than 95% of an event’s hits.
missing_propertiespurchase.transaction_id present on 62% of hitsReview required - 04
A parameter changes type
The same property arrives as a string on some hits and a number on others.
type_collisionvalue "84.00" (string) · 84 (number)Review required - 05
A new event appears
First seen in the last 7 days. Expected after a launch, worth a look otherwise.
active_new_eventsloan_calculator_start first seen Tue 22 SepFor awareness - 06
A new property appears
A property first seen on an event in the last 7 days.
active_new_propertiespurchase.coupon_code first seen Wed 23 SepFor awareness
Checks wait until an event is at least 48 hours old with three days of history, so a launch is never reported as a breakage. A user property sent sometimes as text and sometimes as a number is treated as one property, so it is not counted twice.
03 · CONSENT MODE
“No signal” is not the same as “denied”.
Tag Clarity reads the Consent Mode default (gcd) and current state (gcs) on every hit. It reports how many hits carry a usable signal, gives a grant rate for each consent type, and keeps hits with no signal in their own bucket instead of quietly counting them as denials.
For EU traffic, that is the difference between “users declined” and “the banner isn’t wired up”.
- Full consent58%
- Analytics only20%
- Ads only4%
- Both denied9%
- Unparseable1%
- No signal sent8%
Other storage functionality 96% · personalization 71% · security 100%
04 · INSTALL & SECURITY
Quick to install. Straight answers for your implementation review.
Copy your ready-made snippet from the project’s Setup page and add it once. Minimal developer time, and no changes to the tags you already run.
- Domain validation
- Each project accepts hits only from its own domain: exact match, www included, all subdomains, or an explicit wildcard.
- Project keys
- The key in the snippet can send events and nothing else. It cannot read data.
- Debug sessions
- Testing with ?debug=true streams to the Real Time view and is held in memory. It is never written to reporting data.
- Retention
- Collected event data is kept for as long as the project exists, so Dashboard history never expires. Real Time test sessions are never stored.
- Sign-in
- Passwordless: email magic links, or Google, Facebook and Apple accounts.
Put all your tagging under watch.