Checklist
What analytics.tiktok.com received after Reject on 3 Shopify stores
After Reject, analytics.tiktok.com still got EngagedSession events from Store AY's home page. On Stores AK and AV it got nothing more. 27 runs, 3 stores.
In brief
On three Shopify stores, analytics.tiktok.com received TikTok pixel events before anyone touched the cookie banner: Pageview and LandingPageView on the home page, in every run. After the visitor rejected, the stores split. On Store AK (Reject All Cookies) and Store AV (Deny), the browser sent nothing more to analytics.tiktok.com, on the home page or the product page, in all three runs. On Store AY (Decline), the home page still sent EngagedSession events 5.1 to 6.5 seconds after the click, in all three runs, and the product page then sent nothing. Every request counted here got an HTTP 200 response. We tested on November 17, 2026 from a US connection. Technical observation, not legal advice.
What analytics.tiktok.com is
This section comes from TikTok's developer docs.
analytics.tiktok.com is the host that serves and receives the TikTok Pixel. TikTok's page on Content Security Policy tells site owners to allow analytics.tiktok.com, analytics-ipv6.tiktokw.us and ads.tiktok.com for scripts, images and connections, or the pixel may not work. TikTok's pixel base code loads its script from https://analytics.tiktok.com/i18n/pixel/events.js.
TikTok's Pixel Cookie consent mode page describes three calls a site can make. ttq.holdConsent() queues events without sending them until the visitor decides. ttq.grantConsent() sends them. ttq.revokeConsent() "will prevent events from being shared to the TikTok server, including previously queued events in that session." The same page says revoking "does not affect data shared with the TikTok server", so anything sent before the click has already gone.
TikTok's cookie help article lists _ttp and ttcsid as first-party cookies on the store's own domain, each kept for 13 months from last use.
The paths we saw
TikTok does not publish what each path does. The descriptions below are what the request bodies held on these three stores.
Swipe to see stores
Paths the browser used on these three stores.
| Path | How the browser sent it | Field names in the body | Stores |
|---|---|---|---|
/i18n/pixel/events.js and its static/*.js files | GET, script | none (script file) | AY |
/i18n/pixel/shopify.js and its static/shopify.*.js file | GET, script | none (script file) | AK, AV |
/api/v2/pixel | POST, beacon (DevTools type "ping") | event, event_id, message_id, timestamp, context, properties | AY |
/api/v2/shopify_pixel | POST, fetch | the same, plus partner | AK, AV |
/api/v2/pixel/act | POST, beacon | action, auto_collected_properties; no event | AY |
/api/v2/pixel/inter | POST, beacon | action, auto_collected_properties; no event | AY |
analytics-ipv6.tiktokw.us/ipv6/enrich_ipv6 | POST, fetch | event (EnrichIpv6), trigger_event | AK, AV |
On Store AY the pixel ran twice on every page: one copy the page loaded itself, and one inside Shopify's web pixel sandbox, which is how apps connected through Shopify's customer events run. Both copies posted to /api/v2/pixel. Stores AK and AV loaded TikTok's Shopify app script, shopify.js, and posted to /api/v2/shopify_pixel.
How we tested
We ran headless Chrome from a US connection, with a new profile for every run and HTTP/1.1 only. Each store got nine runs on November 17, 2026: Fresh (no click), Reject and Accept, three times each. Each run opened the home page, waited for the banner, clicked the store's own button after about four seconds, and read Shopify's Customer Privacy API every quarter second for eight seconds. Then it scrolled, opened a product page from the home page, and stayed there about a minute. We did not add anything to the cart.
The reject buttons were Decline on Store AY (Pandectes), Reject All Cookies on Store AK (Ketch) and Deny on Store AV (CookieFirst). We counted every request to analytics.tiktok.com and analytics-ipv6.tiktokw.us and took status codes from Chrome's network log.
Before the click
All three stores sent TikTok events before the click, in all nine runs per store.
Store AY's home page sent Pageview, LandingPageView and one early EngagedSession from the page copy, plus Pageview and LandingPageView from the sandbox copy, while Shopify's API still read empty. Store AK sent Pageview and LandingPageView to /api/v2/shopify_pixel plus one IPv6 enrich request; Shopify's API there already read "yes" for all four fields before any click. Store AV sent the same three requests while Shopify's API read empty.
The browser had cookies named _ttp and ttcsid on all three stores before the click.
What Reject changed on each store
Swipe to see the product page
Fresh, Reject and Accept on Stores AY, AK and AV.
| Store | Reject button | Shopify's API, before to after | analytics.tiktok.com on the home page after the click | Product page, Fresh | Product page, Reject | Product page, Accept |
|---|---|---|---|---|---|---|
| AY | Decline | empty to "no" for marketing, analytics, preferences in 0.26 to 0.27 s; sale_of_data stayed empty | EngagedSession: 4, 1, 4 | 8 events (Pageview 5, ViewContent 3) | 0 requests | 8 events |
| AK | Reject All Cookies | "yes" to "no" for all four in 0.26 to 0.54 s | 0 | 2 events (Pageview, ViewContent) | 0 requests | 2 events |
| AV | Deny | empty to "no" for all four in 0.76 to 1.03 s | 0 | 2 events (Pageview, ViewContent) | 0 requests | 2 events |
Each cell holds three runs. All counted requests returned 200.
Store AY, where EngagedSession arrived after Decline
After Decline, Store AY's home page sent EngagedSession 5.1 to 6.5 seconds after the click. Runs one and three sent four (three from the page copy, one from the sandbox copy). Run two sent one, from the sandbox copy. One or two /api/v2/pixel/inter requests went out in two of the runs.
These events came 9.7 to 12 seconds after the home page loaded. In the Fresh runs, with no click at all, EngagedSession arrived 9.9 to 12.9 seconds after load, and in the Accept runs 6.9 to 10.7 seconds after load. On this store the timing follows the page load, not the click.
The product page opened after Decline sent no requests to analytics.tiktok.com in any of the three runs. Neither pixel script loaded there. After Accept, the same product page sent eight events, the same as Fresh.
Our Pandectes test of this store on November 16 saw four EngagedSession events in each Decline run and one /api/v2/pixel/inter request on the product page. On November 17 the counts were four, one and four, with none on the product page.
Stores AK and AV, where TikTok went quiet
On Store AK, Shopify's API read "yes" before any click. After Reject All Cookies, all four fields read "no" within 0.54 seconds, and the browser sent no further requests to analytics.tiktok.com. The product page did not load shopify.js. After Accept, the product page sent Pageview and ViewContent.
On Store AV, Shopify's API went from empty to "no" within 1.03 seconds of Deny, and the result matched Store AK: zero requests on the home page after the click and zero on the product page, in all three runs. Our CookieFirst test covers the rest of this store's banner.
Both stores load TikTok through TikTok's Shopify app script, and on both the script stopped loading once Shopify's API read "no". How Shopify's customer events differ from the Privacy API covers how apps read that value.
What the request body held
We recorded field names, never values. Event posts carried event, event_id, message_id, timestamp, context and properties, plus _inspection, is_onsite and signal_diagnostic_labels. Inside context were ad, device, library, page, pageview_id, pixel, session_id, user, userAgent and variation_id. On product pages, properties on Stores AK and AV held content_id, content_name, content_type, currency, price and brand; on Store AY it held content_type, contents, currency and value. The script URLs carried two query names, sdkid and lib.
Check your own store in DevTools
- Open a private window, open DevTools, go to Network, turn on Preserve log, and type
tiktokin the filter. - Load your home page without clicking the banner. Look for
events.jsorshopify.js, then POSTs to/api/v2/pixelor/api/v2/shopify_pixel. Click one and readeventunder Payload. - In Console, run
Shopify.customerPrivacy.currentVisitorConsent()and note the four values. - Click your banner's reject button and note the time. Run the same line again.
- Stay on the page for 15 seconds. If a new POST appears, check its
eventand when it arrived. On Store AY, EngagedSession came 7 to 13 seconds after the page loaded, click or no click. - Open a product page and count requests to analytics.tiktok.com.
- Repeat in a new private window with Accept, and compare the product page.
- Under Application, then Cookies, look for
_ttpandttcsid.
Beacon requests show "ping" in the Type column, so set the filter to All.
Limits
This covers three Shopify stores, one US connection, one day and nine runs per store, in headless Chrome. We did not add to cart, check out or send a Global Privacy Control signal. A browser log cannot show TikTok's Events API, which sends from a store's server. We read cookie names but did not compare values before and after the click. The path descriptions are our reading of the request bodies; TikTok does not document them.
Related reading
FAQ
What is analytics.tiktok.com?
It is the host for the TikTok Pixel. Stores load the pixel script from it, and the pixel posts events such as Pageview and ViewContent back to it. TikTok's Content Security Policy page lists it with analytics-ipv6.tiktokw.us and ads.tiktok.com.
Does analytics.tiktok.com stop receiving requests after Reject?
It depended on the store. On Store AK and Store AV it received nothing after the click in all three runs. On Store AY the home page still sent EngagedSession events 5.1 to 6.5 seconds after Decline, and the product page then sent nothing.
Why did Store AY send EngagedSession after Decline?
On that store EngagedSession arrived 7 to 13 seconds after the home page loaded, whether the visitor clicked Decline, clicked Accept or did nothing. The timing followed the page load. We did not see the store's pixel code, so we cannot say which call queued it.
What is /api/v2/shopify_pixel?
It is the path TikTok's Shopify app script posted events to on Stores AK and AV. The body had the same field names as the standard pixel path, plus a field called partner. TikTok does not document the path.
Does TikTok's revokeConsent recall events already sent?
No. TikTok's consent mode page says calling it does not affect data already shared with the TikTok server. It stops queued and later events.
Are the _ttp and ttcsid cookies gone after Reject?
On all three stores the cookie names were still in the browser at the end of every Reject run. We did not read or compare their values.
Does this page say any store breaks the law?
No. It records what the browser sent, when, and the response code. Technical observation, not legal advice.
Sources
These links cover the platform and regulatory context used in this guide. Applicability still depends on the organization and jurisdiction.