Cookie audit vs pixel audit: what’s the difference?

Not legal advice

This FAQ explains how the labels cookie audit and pixel audit overlap as storefront observation jobs. It is not legal advice, not a ruling that either label is required or sufficient under any statute, and not a GDPR, ePrivacy, CPRA, or other compliance certificate. ConsentProbe reports are technical observations of what fired under labeled visits. They do not say what counsel would allow. Observation is not counsel permission.

Last updated September 30, 2026. The before-Accept audit owns the protocol. The testing hub owns which test is next. The marketing-pixels FAQ owns whether Reject stopped a marketing pixel. The scope FAQ asks whether a cookie audit records pixel surfaces. The evidence pack owns the handoff file. The party-label guide owns first-party versus third-party names. This FAQ only compares the two labels. It does not open a second cookie-audit hub, and it does not launch a pixel-audit product.

Short answer

The labels overlap. One Fresh and Reject pack that records cookies, storage, and Network usually covers both intents. A cookie-table-only pack is a weak answer to a pixel-audit request. A pixel-host-only pack is a weak answer to a cookie-audit request. You rarely need two hubs or two unrelated reports when one pack covers all three surfaces.

Use the scope FAQ when the question is whether pixels sit inside a cookie audit. Use the marketing-pixels FAQ when Reject is the question. Use the hub for which test is next. First-party versus third-party labeling still applies when pixel cookies sit on your domain. This FAQ clarifies overlapping labels. It does not rewrite the scope FAQ. It is not legal advice. Observation is not counsel permission. ConsentProbe is not a CMP.

Two labels, one pack

The table names the label people say, the observation they usually want, and the page that already owns the longer method. Prefer a sentence such as Fresh Network still shows host X. Leave statutory duties with counsel. Do not paste the full how-to or the hub here.

Which label when

Start from the word the stakeholder used, then capture the surface that word tends to drop. Renaming the file does not change the runtime check.

1. If the stakeholder said cookie audit, still capture Network so request-only pixels are not missed. The scope FAQ is that question.
2. If the stakeholder said pixel audit, still capture cookies and storage so first-party aliases and SDK keys are not missed. The party-label guide covers domain names.
3. If Reject is the question, open the marketing-pixels FAQ. Do not stop at the Accept path.
4. Write one finding sentence per unexpected surface, such as an ad host on Fresh, or an _fbp-class cookie after Reject.
5. Hand engineering or counsel an evidence pack when the rows need an owner. Open the hub for which test is next.
6. Keep one hub. This page does not add a second cookie-audit hub, and it does not add a pixel-audit product.

When renaming the deliverable gets slow

Renaming the deliverable does not change the runtime check. ConsentProbe runs Fresh and Reject on the storefront URL. Each finding stays tied to a request, a cookie, or a screenshot.

Use the free US-baseline visit when you want the report format. Use paid EU or California scenarios when those regions are the claims. The free versus paid guide draws that line. ConsentProbe does not sell a separate pixel-audit product here, does not install a CMP, and does not issue a certificate. A free US-baseline scan is not an EU or California legal conclusion.

FAQ

Limits of this page

This FAQ says cookie audit and pixel audit often name the same Fresh and Reject pack when that pack includes cookies, storage, and Network. It is not legal advice, not a second cookie-audit hub, and not a rewrite of the scope FAQ. Observation is not counsel permission. ConsentProbe does not sell a separate pixel-audit product, and it does not install a CMP. A free US-baseline scan is not an EU or California legal conclusion.

Related guides

Open the before-Accept audit for the protocol, the hub for which test is next, the marketing-pixels FAQ when Reject is the question, the scope FAQ for pixel surfaces, the evidence pack for the handoff, and the party-label guide for domain names.

• How to run a cookie audit before Accept
• Cookie audit hub
• Does Reject All stop marketing pixels?
• Does a cookie audit catch tracking pixels?
• Cookie consent evidence pack
• First-party vs third-party cookies
• Cookie audit vs privacy policy claims
• Agency to client cookie audit handoff
• Does a CMP attestation replace a cookie audit?
• Reject All still tracking
• Pre-consent audit checklist
• Meta Pixel and CAPI before Accept
• Free US-baseline vs paid EU and California
• ConsentProbe methodology
• Pricing and listed regional products