Checklist
Does the TikTok Pixel fire before Accept?
Check TikTok Pixel cookies and requests before Accept, then retest after Reject. Events API can still send. Not a TikTok Ads setup guide.
In brief
TikTok marketing can show up in the browser and on the server. Check whether TikTok Pixel cookies, storage, or network requests appeared before Accept, and whether Reject All stopped them. Events API can still send from 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 TikTok Ads setup guide and not legal advice.
Not legal advice
This guide explains how to observe TikTok Pixel activity in the browser and TikTok Events API activity on the server, relative to Accept and Reject. It is not legal advice, not a TikTok Ads or Events Manager setup tutorial, and not a GDPR, ePrivacy, CPRA, or other compliance 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. The Meta Pixel and CAPI page is the sibling pattern. This page stays on TikTok.
Short answer
Check browser TikTok Pixel cookies, storage, and network requests before Accept. Do not assume Events API is off because the pixel is gated. Events 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 tiktok and analytics.tiktok 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 Events API is harder to see from DevTools alone. Look for storefront or checkout flows that still trigger server events. Ask engineering for Events API logs labeled by consent state when the browser looks quiet and TikTok reporting still shows traffic. The Meta page uses the same browser-plus-server split for Meta Pixel and CAPI. Do not copy that page's install notes here. 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 TikTok Pixel or Events API. This page is not a TikTok Ads setup guide and not legal advice.
Browser pixel versus Events API
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 |
|---|---|---|
| TikTok Pixel (browser) | Cookies, storage, and Network rows to TikTok hosts before Accept | Nothing extra when those rows are already on screen |
| TikTok Events API (server) | Indirect storefront clues. Full payloads rarely appear in DevTools | Events API 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 an event parameter, or open TikTok Ads 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 TikTok 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.
Events API when the pixel looks gated
A quiet browser pixel does not prove the server stayed quiet. Events API 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 TikTok reporting still shows events, ask engineering for Events API sends tagged by consent state and timestamp. That question is the falsification. This page does not walk through Ads Manager, pixel installation, or event parameters. The Meta Pixel and CAPI guide is the sibling for that vendor. Keep Meta's body on that page.
When checking TikTok hosts gets slow
Checking TikTok hosts across templates by hand takes a long time. 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 TikTok Pixel or Events API, does not install a CMP, and does not issue a certificate.
FAQ
Does the TikTok 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 Events API?
Not by itself. Ask engineering for server sends labeled by consent state.
What if Reject All still shows TikTok hosts?
Treat it as a Reject failure. The Reject leftovers guide is the network check. Keep the evidence pack.
Will this page teach TikTok Ads setup?
No. This page is a Fresh and Reject check, not a TikTok Ads or Events Manager setup guide.
How does this relate to Meta Pixel and CAPI?
The Meta page is the sibling pattern. This page stays on TikTok Pixel and Events API.
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 TikTok Pixel surfaces before Accept and how to ask whether Events API continued after the pixel was gated. It is not legal advice, not a TikTok 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, the marketing-pixels FAQ for the wider pixel question, and the Meta page for that sibling.
- 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?
- Meta Pixel and CAPI before Accept: what to check
- What belongs in a cookie consent audit evidence pack?
- CMP claims vs runtime evidence: how do you prove the banner actually works?
- 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.
Save a US-baseline technical record
After a DIY check, run a free US-baseline audit: one browser visit outside California, with cookies, requests, and screenshots stored as evidence. That visit does not run EU reject/accept or California GPC. EU, California, and Global 2 audits can be purchased from Billing after sign-in.