TikTok · Web Pixels API replacement · confidence: medium
Dies 2026-08-26
// This pattern covers stores where server-side TikTok Events API is already
// correctly wired, but ttclid (TikTok click ID, needed for click-attribution
// matching) was captured into a cookie by a script injected in
// checkout.liquid or Additional Scripts. That capture point dies Aug 26; the
// Events API server call itself is unaffected once ttclid keeps flowing.
analytics.subscribe('checkout_started', (event) => {
// Read ttclid from the URL the customer arrived with, persisted earlier by
// your ad-click landing page into a first-party cookie BEFORE checkout —
// this subscription re-persists it at checkout start via the sandboxed
// browser.cookie API so it survives through to your order-webhook-based
// server-side Events API call.
browser.cookie.get('ttclid').then((existing) => {
if (existing) {
browser.cookie.set('ttclid', existing);
}
});
});What this does NOT cover
What this does NOT cover: first-touch ttclid capture on the landing page itself — that is a separate, non-checkout script and outside this library's Aug-26 scope.
TikTok Pixel + Events API · Both the client ttq pixel and the server-side TikTok Events API integration.