What it is
The TikTok Pixel reports events to a TikTok Ads account for optimisation and attribution. It may be installed directly, through a container or through a storefront app, so a theme change alone does not prove it was removed.
Ordering in the classifier matters here: analytics.tiktok.com is tested before the general tiktok.com rule, so the pixel is reported as advertising rather than being swallowed by the embed rule.
What a scan matches
A verification scan drives a real browser and records the outbound requests observed during its configured journeys, so TikTok Pixel is identified by request hosts and paths rather than by source-code claims. Requests on unvisited paths, after unperformed interactions or solely on the server remain outside that observation.
- analytics.tiktok.com: the pixel, matched before the generic rule so it is never mistaken for an embed
- tiktok.com and tiktokcdn.com: classified as a media embed, and the /embed path always is, so a video on the page is never reported as the pixel
Cookies are classified by name before domain because many analytics and advertising tags write first-party cookies through the page, which places a vendor-related identifier on your domain. Matching known names helps attribute those values without assuming that every first-party cookie came from your own application.
| Cookie | What it is for |
|---|---|
| _ttp | A first- or third-party TikTok advertising identifier, depending on the domain on which it is set |
| ttcsid_* / ttclid | Current first-party TikTok session/pixel and click-attribution identifiers; TikTok documents a 13-month lifetime |
| _tt_enable_cookie | A legacy or implementation-specific TikTok flag still recognised by the scanner; it is not in TikTok’s current cookie table, so report it only when observed |
Controlling it with consent
With the named adapter, enter the Pixel ID and remove copies installed in theme code, plugins, apps or a container. Before marketing consent the managed pixel is withheld; after approval it loads and grants consent.
On withdrawal the adapter sends the vendor revoke signal, including where a script finishes loading after the withdrawal. Server-side events are a separate integration and are not affected.
This one has a first-class adapter
Enter the identifier in the property’s technology list and the runtime applies that adapter’s control strategy. Depending on the vendor, that means withholding the loader, establishing denied defaults, or loading a functional surface with tracking opted out; the article above describes the exact behavior. Remove copies installed in a theme, plugin, app or tag manager first, or another installation can remain outside that control.
What breaks if it is refused: TikTok campaign measurement for refusing visitors. An embedded TikTok video is a separate, media-category decision.
Verifying it
Check TikTok script requests and test events in every state, and confirm there is a single installation. Storefront apps are the usual source of a second one.
- Before a choice: optional tracking endpoints and optional identifiers are absent; any intentionally loaded necessary or functional surface matches the control model described above
- After rejecting optional categories: optional activity remains absent and the refusal persists across a reload
- After granting the relevant category: the expected loader or embed appears and the feature behaves normally
- After withdrawing: new optional activity stops; where the vendor supports a consent signal, verify that the signal is sent as well as checking network behavior
Common questions
Is an embedded TikTok video the same as the pixel?
No, and the scanner separates them. An embed on the /embed path is media; analytics.tiktok.com is advertising. They belong in different categories and a visitor may reasonably allow one and refuse the other.
Sources and verification
Verified on . Product-behaviour statements were checked against the current implementation and tests. The links below are the verification basis recorded for this article. They support the stated facts, not a legal conclusion for every site or configuration; recheck changing vendor behaviour before relying on it in production.
- TikTok for Business: using cookies with TikTok Pixel
Vendor documentation
Checked
See what your own site is loading
A browser scan reports the requests and storage it observed during the sampled journey. Use configured workspace scans to compare the states and pages that matter to your implementation.