Trackingplan shows you how user consent affects your data collection, and alerts you whenever data is sent without the consent it needs.
In practice, Trackingplan:
- Monitors how many users accept and reject consent
- Detects when data is sent without the required consent
- Works out on its own which cookies and destinations require consent
- Alerts you when something is inconsistent or puts you at risk
The same checks that keep your data accurate also cover one of the most sensitive areas of analytics: consent compliance.
To check a Google Consent Mode implementation by hand, one session at a time, see How to debug Google Consent Mode v2.
Prefer to watch? Here’s a quick walkthrough of Consent & Cookie Monitoring.
Real User Monitoring vs Synthetic Tests
Trackingplan uses real user interactions rather than synthetic tests, watching how real people use your websites, apps and other digital assets. So what you see about consent reflects real-world behavior: different user paths, devices, browsers and countries, not a scripted test.
Consent Monitoring
A misconfiguration, a new cookie or a pixel firing when it shouldn’t is detected straight away, so you can act before it becomes a compliance or data quality problem.
This view shows consent acceptance rates across your destinations, cookies, domains and pixels. Here’s what each tab gives you.
Overview Tab

Daily consent acceptance rate
Each day, this rate compares the hits that carry a valid consent signal with all the hits observed for each element.
You also get a breakdown by destinations, cookies, domains, and pixels, so you see at a glance where consent stands:
- Blue: New elements recently detected
- Grey: Optional (no consent required)
- Green: Working as expected (consent properly collected)
- Yellow: Something that requires consent is not respecting it consistently (requires attention)
Warnings
The Overview tab also lists every active consent warning: any consent violation (data sent without proper consent) and any sudden change in consent acceptance rates.
Every consent warning also goes into Trackingplan’s Digests, so your team hears about it even when nobody is looking at the dashboard. You get real-time alerts when consent is not collected, new cookies appear, or pixels behave unexpectedly, and you can act before it becomes a compliance problem.
You can filter consent warnings by status (e.g., muted, resolved). Each one shows:
- What’s happening: a short, clear explanation of the problem.
- Affected elements: whether it affects a specific domain, pixel, provider or cookie.
- Seen: when it was first detected and when it was last seen.
- Notes: context for your team, such as status, who owns it, or anything else worth knowing.

Click any warning in the list to open the Warning Management view, where you can:
- See a detailed graph of what’s happening
- Adjust tolerances if needed
- Share the warning with anyone on your team
From there, Warning Analysis explains exactly what’s going on. The explanation is based entirely on your debug warning data, written so anyone who needs to act can follow it.

Each warning in Warning Analysis includes:
- Summary: the big picture, with all the relevant debug data in one explanation.
- Hypothesis: the most likely root cause, in plain language you can pass on.
- Potential Impact: an estimate of the business impact, beyond the technical details: how it could affect ROAS, conversions, campaign attribution or the reliability of your data.
- Recommended Actions: practical suggestions on what to review or fix.
- When it Happens: when and under which conditions the problem occurs, taken from Trackingplan’s Warning Debug.
Learn more about the Trackingplan AI Debugger.
Destination Tab
The Destination tab shows consent rates destination by destination.
So you can compare consent across your analytics and marketing providers, such as GA4, Google Ads, Meta or other tracking pixels.

Consent Rate
The Consent Rate is the percentage of times users explicitly grant consent.
A sudden drop may point to:
- Problems in your CMP implementation
- Broken consent banners
- Incorrect tagging or blocking logic
You find this metric in every tab of Trackingplan’s Cookie Monitoring, over time, so you can follow trends, spot recurring problems and confirm that a fix worked.
Consent Status
The Consent Status tells you whether a cookie requires user consent. Trackingplan works it out by observing your data, learning its patterns and adapting as your digital stack changes.
It evaluates each cookie over a self-learning period:
- If consent is consistently granted above a certain threshold during that period, the cookie is marked as “Consent Required.”
- If Trackingplan sees no consent activity for a cookie during the learning period, it is marked as “Consent optional.”
So Trackingplan works out which cookies need consent without any manual setup. You can always override its decision and set a cookie to require consent, or not.
Less time classifying cookies by hand, and the final say is still yours.

Cookies Tab

The Cookies Tab lists every cookie detected on your monitored domains. Use it to audit your cookies, spot unexpected or unauthorized ones, and check that your CMP is set up correctly.
It shows:
- Classification: which cookies are required and which are optional.
- Filtering: sort cookies by whether they need user consent.
- Consent visibility: the cookies that are active even without consent.
Reviewing your cookie footprint becomes a quick check instead of a manual audit.
Domains Tab

The Domains Tab works like the Cookies Tab, domain by domain. It shows how cookies and tracking behave on each monitored domain, so you can:
- Check consent rates per domain at a glance.
- Spot unexpected or missing tracking on specific domains.
- Filter and focus on the domains that need attention.
Pixels Tab

The Pixels Tab gathers every tracking pixel on your sites, so you can monitor, audit and manage them in one place:
- Pixel overview: every pixel detected on your monitored domains.
- Consent tracking: which pixels fire with or without user consent.
- Filtering and details: focus on specific pixels, domains or consent status.
- Troubleshooting: spot unexpected or misconfigured pixels that could affect data accuracy.
Continue analyzing in Data and Tracks Explorer
To go further, open Data Explorer and Tracks Explorer. They give you every attribution, so you can cross consent data with user path, language, country and other attributes.
This context shows you why consent fails in a specific case, whether it’s one browser, one device or a new GTM release, so your team knows where to look.
- Review consent at the event or track level.
- Filter and segment data by consent status.
- Analyze discrepancies across pages, destinations, or user paths.
- Correlate consent with other attributes to uncover patterns or problems.
Tracks Explorer also shows the consent attributes of each track, so you can:
- Inspect tracks that were sent with or without consent
- Filter by consent status to focus on potential problems
- Deep dive into event-level discrepancies to identify root causes
With them you can run custom analysis and in-depth investigation, and keep your tracking accurate and compliant on every platform.
Analyze consent with the Trackingplan agent
Click Analyze at the top of the Consent screen, or ask in any thread. The agent checks the consent state of every hit against what actually fired, destination by destination, and answers with the evidence behind it.

Some questions to start with:
- Is any pixel firing before consent in the EU? The agent checks each advertising destination against the consent category it needs in your CMP and lists the vendors that fired without it, with their share of hits.
- Which consent change explains it, and since when? The answer names the change in the CMP or the tag manager, when it was published and which vendors it affects.
- Why did the consent acceptance rate drop? Follow-ups break it down by country, landing page or device, and show example sessions.
The agent can also check the consent behavior live on your site; it opens a page in a browser only with your approval. Ask for the result as a report with + > Report mode, or keep checking it with the Consent implementation, Consent acceptance rate and Cookie banner precision audits.
More use cases in For Compliance & Legal.