DocsFor Compliance & Legal
Use Cases

For Compliance & Legal

How privacy and legal teams use Trackingplan to find pixels that fire before consent, trace the CMP change behind it and keep consent checks running.

For privacy, compliance and legal teams who need to know what fires before a visitor consents, by market and by vendor. Ask the agent in a thread: it checks the consent state of every hit (each piece of data your site sends) against what actually fired.

Is any pixel firing before consent in the EU?

The agent checks each advertising tool against the consent category it needs in your consent platform (CMP). It lists the vendors that fired without that consent, with their share of hits. It also separates the causes, for example vendors that started after a CMP change and vendors that were never set to wait for consent.

Follow-ups break it down by country and landing page, show example sessions, or check the consent behavior live on your site. The agent opens your site in a browser only with your approval.

The agent traces pre-consent firing to a CMP change
The agent traces pre-consent firing to a CMP change

Trace the change behind it

Which consent change explains it, and since when?

The answer names the configuration change in the CMP or the tag manager, when it was published and which vendors it affects.

Need something to hand to legal? Ask for the result as a report: + > Report mode in the thread. A consent compliance report can cover the acceptance rate and its trend, the hits sent without the required consent by destination, the causes in the CMP and the tag manager, and the steps to fix them. Share it, or download it as a PDF. See Reports.

Keep checking it

Three consent audits are ready in the Library: Consent implementation, Consent acceptance rate and Cookie banner precision. Set their notifications so your team hears from them by email or Slack only when something needs attention. See Audits.

Was this useful? Write to support@trackingplan.com