检查清单
Meta Pixel and CAPI before Accept: what to check
Check Meta Pixel cookies and requests before Accept, then retest after Reject. Server CAPI can still send events. Not a Meta Ads setup guide.
In brief
Meta marketing can show up in the browser and on the server. Check whether Meta Pixel cookies, storage, or network requests appeared before Accept, and whether Reject All stopped them. Conversions API events can still leave your backend when the browser pixel is delayed. ConsentProbe can store Fresh and Reject packs. A free US-baseline scan is not an EU or California legal conclusion. This page is not a Meta Ads setup guide and not legal advice.
Not legal advice
This guide explains how to observe Meta Pixel activity in the browser and Meta Conversions API (CAPI) activity on the server, relative to Accept and Reject. It is not legal advice (非正式法律意见), not a Meta Ads or Events Manager setup tutorial, and not a GDPR, ePrivacy, CPRA, or other certificate. ConsentProbe reports are technical observations of what fired. They do not say what counsel would allow.
Last updated September 24, 2026. The before-Accept audit owns the general first-load method. The Reject leftovers guide owns a Reject failure. The pre-consent checklist owns the pass order. The marketing-pixels FAQ owns the wider pixel question. This page stays on browser Meta surfaces plus the server CAPI question.
Short answer
Check browser Meta Pixel cookies, storage, and network requests before Accept. Do not assume CAPI is off because the pixel is gated. Conversions API can still send events from your backend when the browser pixel is delayed.
Treat banner text that says marketing is off as a claim. Falsify it with a clean visit. Capture facebook and meta host rows, and related cookies, on Fresh. Repeat after Reject. Note any post-Reject fan-out. Host names here are examples of where a browser test can look. This page does not tell you which host to block.
Server CAPI is harder to see from DevTools alone. Look for storefront or checkout flows that still trigger server events. Ask engineering for CAPI logs labeled by consent state when the browser looks quiet and Ads reporting still shows traffic. ConsentProbe can produce Fresh and Reject packs with request, cookie, and screenshot links. A free US-baseline scan is not an EU or California legal conclusion. ConsentProbe does not install a CMP and does not configure Meta Pixel or CAPI. This page is not a Meta Ads setup guide and not legal advice (非正式法律意见).
Browser pixel versus server CAPI
A browser gate and a server gate are different checks. Stay with pixel request before Accept. Leave legal conclusions to counsel.
| Layer | What you can observe in a browser test | What you may need engineering for |
|---|---|---|
| Meta Pixel (browser) | Cookies, storage, and Network rows to Meta or Facebook hosts before Accept | Nothing extra when those rows are already on screen |
| Meta CAPI (server) | Indirect storefront clues. Full payloads rarely appear in DevTools | CAPI or reporting logs labeled by consent state and timestamp |
| CMP marketing-off UI | A screenshot of the claim | A matching runtime on Fresh and on Reject |
Fresh and Reject on the browser
These steps compare a claimed marketing-off state with cookies and requests. They do not install a pixel, set a parameter, or open Events Manager. The before-Accept audit, the Reject leftovers guide, the pre-consent checklist, and the marketing-pixels FAQ hold the neighboring methods.
- Use a clean profile. Load the storefront once. Do not click Accept.
- Capture cookies, storage, and Network for Meta or Facebook marketing hosts.
- Screenshot the banner state. Label the pack Fresh.
- Open a new clean profile, or clear storage. Click Reject All. Navigate once more.
- Recapture cookies and Network. Label the pack Reject. Compare it with Fresh and, if you ran one, with an Accept control.
- Write one finding sentence per mismatch, such as a Pixel cookie on Fresh, or the same host after Reject.
CAPI when the pixel looks gated
A quiet browser pixel does not prove the server stayed quiet. CAPI can send from checkout, purchase, or other backend hooks even when the page delayed the pixel.
If Fresh and Reject look clean in DevTools and Meta reporting still shows events, ask engineering for CAPI sends tagged by consent state and timestamp. That question is the falsification. This page does not walk through Events Manager, pixel installation, or event parameters.
When hand-checking Meta hosts gets slow
Checking Meta hosts across templates by hand is slow. 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 install or configure Meta Pixel or CAPI, does not install a CMP, and does not issue a certificate.
FAQ
Does Meta Pixel fire before consent?
It often does when the tag is ungated. Verify Network and cookies on a Fresh visit before you treat the banner as proof.
Does gating the browser pixel stop CAPI?
Not by itself. Ask engineering for server sends labeled by consent state.
What if Reject All still shows Meta hosts?
Treat it as a Reject failure. The Reject leftovers guide is the network check. Keep the evidence pack.
Will this page teach Meta Ads setup?
No. This page is a Fresh and Reject check, not a Meta Ads or Events Manager setup guide.
Where is the marketing-pixels FAQ?
The Reject All marketing-pixels FAQ covers whether a refused marketing pixel stayed off. This page adds the browser pixel plus server CAPI split.
Is this legal advice?
No (非正式法律意见). These are technical observations. ConsentProbe does not replace counsel, and it does not install a CMP.
Limits of this page
This page tells you how to check Meta Pixel surfaces before Accept and how to ask whether CAPI continued after the pixel was gated. It is not legal advice (非正式法律意见), not a Meta Ads setup guide, and not a certificate. ConsentProbe reports stay tied to requests, cookies, and screenshots. A free US-baseline scan is not an EU or California legal conclusion.
Related guides
Open the before-Accept audit for the general first load, the Reject leftovers guide when Reject still tracks, the pre-consent checklist for the pass order, and the marketing-pixels FAQ for the wider pixel question.
- Pre-Consent Cookie Audit: A Storefront Checklist
- Reject All Still Tracking: What to Check After You Say No
- Pre-consent audit checklist: what to verify before Accept
- Does Reject All stop marketing pixels?
- What belongs in a cookie consent audit evidence pack?
- CMP claims vs runtime evidence: how do you prove the banner actually works?
- Shopify pre-consent checklist: what to check before Accept
- Which cookie consent test should you run first?
- What does a free US-baseline cookie audit prove vs paid EU or California scans?
- ConsentProbe methodology
- Pricing and listed regional products
Sources
These links cover the platform and regulatory context used in this guide. Applicability still depends on the organization and jurisdiction.
保存一次美国基线技术记录
完成自行检查后，可以跑一次免费美国基线审计：在加州以外做一次浏览器访问，把 Cookie、请求和截图存成证据。这次访问不会跑欧盟拒绝/接受，也不会跑加州 GPC。欧盟、加州和 Global 2 可在登录后的账单页购买。