The Audit tab includes a cookies section that lists every tracking cookie on the active page, attributed to the platform that owns it. Pixel Auditor reads document.cookie on the active tab — nothing is sent anywhere.
Cookies detected per platform
| Platform | Cookie names |
|---|---|
| Google Analytics 4 | _ga, _ga_XXXXXXXXXX, _gid, _gat |
| Google Ads | _gcl_au, _gcl_aw, _gcl_dc, FPGCLAW, FPGCLDC |
| Google Tag Manager | _dc_gtm_* |
| Meta Pixel | _fbp, _fbc, fr, datr |
| LinkedIn Insight | li_oatml, li_sugr, UserMatchHistory, AnalyticsSyncHistory, lidc, BizoID |
| Microsoft Bing UET | _uetsid, _uetvid, MUID, MR, SRM_B |
| Microsoft Clarity | _clck, _clsk, CLID, ANONCHK, SM |
| Other vendor cookies | Server-side and edge-tag platforms are detected by cookie signature and grouped under "Other" |
Cookie polling after consent
Many tag libraries set their cookies asynchronously after consent is granted. Pixel Auditor polls document.cookie every 2 seconds for 30 seconds following any consent_update event with granted values. New cookies that appear in this window are flagged as "set on consent grant".
Cookie audit columns
| Column | Meaning |
|---|---|
| Name | Cookie name |
| Platform | Attributed platform (or "unknown") |
| Set at | When Pixel Auditor first saw it: page-load / on-consent / runtime |
| HttpOnly | Whether the cookie is HttpOnly (Pixel Auditor can't read these from JS — listed only when seen via Network) |
| Domain | Cookie domain — useful for spotting first-party vs third-party |
why
If a tag is set to fire only after consent, but its cookies appear at page-load, that's a misconfiguration — the cookies are leaking ahead of consent.