For months, two pieces of feedback kept coming back from people using ConsentGuard. The reports were too detailed for the people who needed them most, and the score was too harsh: a single mis-fired tracking request could drag a tracker from clean to red. From the 9th of June, 2026, both of those have changed.
A plain-English overview, sitting where the technical report used to
Every results URL now opens on a new overview page first. One card per tracker (Google Ads, GA4, server-side GA4, Microsoft Ads), a Consent Mode v2 card with the binary checks that matter, and a GDPR card aggregating cookie issues from across the report. Each card shows, in plain English, how many tracking requests fired, how many handled consent correctly, and what to fix when something is broken.
The technical report you're used to is still one click away ("Technical Details" in the top right) and still carries the full per-request and per-cookie diagnostics. The overview just sits in front of it, so the everyday question (is my tracking OK?) doesn't require reading a full report.
A note on the GDPR card
One card behaves differently from the rest: the GDPR card has no score. GDPR is a complex topic that goes well beyond cookies, and ConsentGuard is not a GDPR compliance tool. We list the GDPR-relevant issues we find (forbidden cookies set before consent, Meta or TikTok pixels firing before the user accepts), but an empty card doesn't mean your site is compliant. For where Consent Mode v2 actually fits into GDPR, see our GDPR compliance guide.
A score that scales with severity, not perfectionism
The old score was unforgiving. One bad tracking request out of dozens could pull a tracker into single digits, even though almost everything was working correctly. We listened.
The new compliance score takes the lowest of two numbers: how your Consent Mode v2 is configured, and how your ad-platform tracking is reaching Google. If you run everything server-side via Server-side GA4, we pick that up instead. The number now reflects the worst meaningful signal on your site, rather than amplifying a single misfire.
One related change: GDPR findings that aren't a Consent Mode failure no longer move the overall score. Facebook or TikTok pixels firing before consent, or tracking cookies set on a vendor's own domain, still appear on the GDPR card so you can act on them, but they don't pull the headline number down. The score is a Consent Mode v2 measure now; the GDPR card is where the broader compliance picture lives.
What happens to your old scores
We've recomputed all your historical scans with the new formula. For three months, every report shows the new score alongside the old one as "Previously: X / 100", so you can see how the same scan reads under both methodologies. After the 10th of September, 2026, the old number disappears.
Open your most recent check to see how it reads under the new score.