Skip to main content

Cookie Audit Checklist

Every Third-Party Cookie, Traced to a Vendor Agreement

Map each vendor's role, confirm the DPA or controller terms that match it, and treat a missing agreement as a blocking finding.

You ran the scan, but you still cannot prove the paperwork is on file

Your cookie scan surfaces doubleclick.net, facebook.com, and a dozen ad-tech domains you did not place yourself. Surfacing them is only the first step. For each one you need to know who the vendor is, whether they act as a processor, independent controller, or joint controller, and whether the agreement that matches that role is current. Third-party cookies carry the highest compliance risk in any audit, and an advertising identifier firing with no valid consent basis is a direct exposure under GDPR Article 5(1)(a) and CCPA opt-out rules.

What's inside

What the third-party and vendor-agreement steps cover

Tracing each third-party cookie back to the specific tag or pixel that fires it, not just the setting domain
Determining each vendor's role: processor, independent controller, or joint controller
Confirming the matching agreement is on file and current: an Art. 28 DPA, controller-to-controller terms, or an Art. 26 arrangement
Checking transfer mechanisms for data leaving the UK or EEA, including adequacy decisions, SCCs, and the UK IDTA or Addendum
Verifying third-party tags are gated by a consent trigger before they fire, tested across no-consent, rejected, and accepted states
Escalating unattributable cookies and unexpected trackers as blocking findings, not archiving them

The outcome

What you can do once you have worked through it

Answer the ownership question for every cookie

For any advertising cookie on your site, you can name the vendor, their role, and the exact agreement that authorises it.

Spot the gaps a scan alone hides

CNAME-cloaked cookies, tag manager misfires, and pixels injected by partners without notice get logged and reviewed as third-party exposure.

Produce a defensible consent record

You close each cycle with a dated, version-controlled register, a findings log with owners and deadlines, and evidence a regulator can review.

Repeat the process every cycle

A concrete, numbered task list replaces inconsistent one-off audits, so the next scan starts from a documented baseline rather than scratch.

Credibility

Grounded in named frameworks and regulator guidance

GDPR / UK GDPR & ePrivacy

Cites Articles 5(1)(a), 5(2), 6, 7, 9, 13, 26 and 28; ePrivacy Directive Article 5(3); and Article 29 Working Party Opinion 04/2012.

Four-category model

Uses the classification model attributed to the ICC UK Cookie Guide and referenced in ICO guidance.

CNIL & EDPB guidance

The CNIL 13-month cookie-lifetime recommendation and enforcement on pre-consent firing and CNAME cloaking, plus the EDPB Cookie Banner Taskforce report (Jan 2023) on Reject All prominence.

Real regimes & signals

Names CCPA/CPRA, Quebec Law 25, Brazil LGPD, Global Privacy Control, and IAB TCF v2.3.

Concrete identifiers & vendors

Google _gcl_aw / _gcl_au, Meta _fbp / _fbc, DoubleClick IDE / DSID, The Trade Desk TDID.

Published with full disclaimer

Published October 2026 with a full legal and informational disclaimer.

Frequently asked questions

It is a concrete, numbered task list of 27 steps across 9 sections, built to be repeated each audit cycle rather than read once. It includes ready-to-use table structures for the cookie register, the findings log, and the CMP consent-record fields.

Cookie Audit Checklist

Trace every third-party cookie to its vendor agreement

Instant access to the full 27-step checklist across all 9 sections.