Cookie audit
Free cookie audit tool: what loads before Accept
A cookie audit tool opens your store in a real browser and records cookies and network requests before anyone clicks Accept.
The free audit runs one US-baseline visit; the $49 EU audit adds Fresh, Reject, and Accept runs.
How the cookie audit tool works
The tool is a browser record of one public storefront URL. It does not install a banner, change your theme, or write a legal opinion. You submit the URL, a browser opens that page, and the report lists what that visit stored and sent.
- Submit the storefront URL in the box above. The free run is one US-baseline visit from outside California, and it starts after you sign in.
- The browser loads the page and records cookies, storage, network requests, scripts, and screenshots before anyone clicks Accept.
- Open the report for that visit. It lists technical findings and the evidence behind them. It is not a CMP and it is not legal advice.
The free visit does not click Reject All or Accept All, open a second browser profile with the GPC header set to 1, crawl the checkout, the admin, or a page that requires a login, or read server-side events that never reach the browser.
Read the report as a technical file. Scope names the region path and the scenarios that actually ran. A finding should point at a cookie row, a request, or a screenshot from that same visit. If the file is a free US-baseline visit, do not describe it as an EU Reject result or a California GPC result. The sample report shows the layout with an anonymized store label.
Quick free checks
Reject All, GPC, and a TC String decoder. The full browser record still starts below.
- Still tracking after Reject All?
The free US-baseline visit records one fresh load. It does not click Reject All. Fresh vs Reject is in the $49 EU audit.
- Is your browser sending GPC?
Shows whether your browser sends Sec-GPC and what navigator.globalPrivacyControl reads.
- Decode a TCF v2 TC String
Purposes, vendors, and legitimate interest, in the browser. The string is what the CMP stored, not proof of the requests the page made.
| Layer | What it proves |
|---|---|
| Banner screenshot | Visitor-facing consent UI at that moment (Reject/Accept/GPC affordances visible). Does not prove Network stopped. |
| CMP copy / UI state | What the CMP claimed (e.g. Reject recorded, "GPC detected"). Does not prove storefront request/cookie change. |
| Fresh / Reject Network | Hosts and requests observed on Fresh vs Reject (or GPC on/off). Technical behavior for eng tickets; not a legal finding. |
Full browser record still starts at /audits/new. Free US-baseline is not an EU or California conclusion. Not legal advice. Not a CMP.
Free vs paid audits
Each row is a product on the pricing page. The price column links there. Evidence is what the browser record for that product includes. None of these rows is a legal conclusion about a store.
| Scenarios | Evidence | Price |
|---|---|---|
| US baseline | Cookies, requests, screenshots | $0 |
| Fresh, Reject All, Accept All | Cookies, requests, CMP actions, screenshots | $49 |
| California baseline and GPC | Cookies, requests, screenshots | $49 |
| Global 2: EU trio and California GPC pair | Cookies, requests, CMP actions, screenshots | $79 |
The US baseline is the free audit. EU and California are separate paid audits. Global 2 runs the EU trio and the California pair in one order. A locale, a timezone, or a vendor dashboard does not replace the region path of the visit. A single US-baseline visit cannot stand in for an EU Reject run or a California GPC pair.
What published runs found
The rows below copy counts from articles already published on this site. Each row links to that article. Store letters are labels in those articles. The table does not name a shop, and it does not turn a request count into a legal finding.
| Scenario | What loaded | Source article |
|---|---|---|
| Store J, Reject All, 2026-10-15 | analytics.tiktok.com (of which /api/v2/shopify_pixel POSTs): Reject run 1, 8 (4); Reject run 2, 11 (5) | Rebuy after Reject All |
| Store I, Reject All, 2026-10-13 | Two Reject runs each sent 4 requests, all 200, to us-east-1.hightouch-events.com: page and consent_updated on the reloaded home page and the next product page. | Hightouch after Reject All |
| Store I, Reject All, 2026-10-13 | api-cdn.yotpo.com requests went from 23 to 0 | Yotpo reviews after Reject All |
| Store C, Reject All, 2026-10-05 | The browser still sent /collect POST requests, 11 before reload, 12 on the reloaded home page, and 23 on a product page. | Clarity after Reject All |
| Store H, after Decline, 2026-10-09 | Six third-party services still received 46 requests over the next 144.2 seconds. | Decline on Shopify's banner |
Technical record. Not legal advice.
Related guides
The before-Accept protocol, which test to run next, and how to read the report.
Common questions
What does a cookie audit record before Accept?
A Fresh visit records cookies, storage, network requests, scripts, and screenshots before any Accept click.
What does the free audit cover?
One US-baseline visit outside California. That visit does not produce EU or California regional conclusions.
Is the report a legal opinion?
No. The report lists technical findings, detected tracking behavior, potential compliance risk, and recommended fixes.
Is this a blog cookie-audit hub?
No. This page is the product landing. The hub that picks which test to run is the cookie consent testing hub.
Is the cookie audit tool free?
The US-baseline visit is free after you sign in. EU and California audits are paid. The pricing page lists each product. This page is not legal advice.
Does the cookie audit tool test Reject All?
The free visit does not click Reject All. It records one fresh US-baseline load. The paid EU audit adds Fresh, Reject, and Accept runs on the same URL.