Integration · TikTok Events API
TikTok Events API, delivered server-side.
AdsPing sends every Purchase, AddToCart, and Lead to TikTok's Events API from the server — immune to ad blockers and Safari ITP — while the TikTok browser pixel runs in parallel with automatic deduplication.
Why server-side
TikTok's browser pixel suffers the same fate as Meta's: ad blockers strip it, Safari ITP caps its cookies, and iOS privacy features starve it of signals. TikTok's algorithm needs dense, accurate conversion data to find buyers — feed it half your conversions and your CPA pays the difference.
TikTok's Events API fixes this by accepting events server-to-server, but a correct implementation needs access-token management, ttclid capture, payload hashing, event_id deduplication, and retry handling.
AdsPing handles all of it: pb.js captures the ttclid from ad clicks, stores it first-party, and the backend forwards every conversion to the Events API with hashed identifiers — deduplicated against the browser pixel it auto-injects.
How it works
- 01
Install pb.js or the Shopify app
One script tag or one-click Shopify install. pb.js captures ttclid from TikTok ad clicks and persists it in a first-party cookie.
- 02
Connect TikTok
Add your TikTok pixel ID and Events API access token from TikTok Ads Manager — the docs walk through it in about three minutes.
- 03
Events flow server-side
Every conversion is forwarded to the Events API with hashed email/phone, ttclid, IP, and user agent. The auto-injected ttq browser pixel fires in parallel; TikTok dedups by event_id.
- 04
Verify in real time
The AdsPing dashboard shows delivery status per event; TikTok Events Manager shows the server events arriving within seconds.
What you get
ttclid capture + persistence
The TikTok click ID is captured on landing and stored first-party, so conversions that happen days later still attribute to the ad click.
Automatic ttq pixel injection
Configure TikTok as a destination and AdsPing injects the official browser pixel with shared event IDs — full dedup, zero extra code.
First-party custom domain
Collect events through your own subdomain so blocker lists never match. Growth and Scale plans include CNAME setup.
Shopify checkout coverage
Purchases fire from Shopify webhooks server-side — including checkout.shopify.com sales the browser pixel physically cannot see.
Delivery health + alerts
Per-platform delivery status and failure reasons in real time; proactive email alerts when a token expires or delivery degrades.
Runs alongside Meta & Google
One pixel, parallel destinations: the same event fans out to TikTok, Meta CAPI, GA4, and Google Ads with per-destination status.
Frequently asked questions
- What is the TikTok Events API?
- TikTok's server-to-server endpoint for reporting conversions — the equivalent of Meta's Conversions API. Events sent through it bypass ad blockers and browser privacy restrictions entirely.
- Do I need the TikTok browser pixel too?
- AdsPing auto-injects it when TikTok is configured and dedups it against the server events by event_id. If you already have a ttq snippet installed, AdsPing detects it and won't double-inject.
- How do conversions attribute back to TikTok ads?
- Via the ttclid click ID (captured on landing and persisted first-party) plus hashed email/phone matching. Server events carry both, so attribution survives cookie loss.
- Does this work for Shopify stores?
- Yes — the AdsPing Shopify app registers order webhooks, so every Purchase and Refund reaches TikTok server-side even though Shopify's checkout domain blocks third-party scripts.
- How long does setup take?
- Typically under 10 minutes: install the tag or app, paste the pixel ID and access token from TikTok Ads Manager, fire a test event, and confirm it in Events Manager.
Stop losing conversions today.
14-day free trial on every plan. Full feature set from day one.