Skip to main content
TrackingConsulting
Now booking · 2–4 day turnaround

TikTok Events API · Conversion tracking

TikTok Events API reference

TikTok's Events API follows the same shape as the other server-side conversion APIs: an event name, a timestamp, an event ID for deduplication against the browser pixel, hashed user identifiers for matching, and event properties carrying value and currency. The failure modes are the same too — an event ID that isn't shared with the pixel, identifiers hashed before they were normalized, and a click identifier that was never captured on landing so the strongest matching signal is simply absent.

✓ 30-minute call · No commitment · You leave with a written remediation plan even if we’re not the right fit.

Built in 2–4 daysOne-time fee95% accuracy guaranteed400-day cookie lifetime1st-party server-side

Written guarantee

95%+ conversion accuracy on TikTok Events API

Measured against your own order records at handover. Miss it and we keep working at no cost until it’s met.

Built on — and certified for — the platforms that matter

Stape

Pro Partner

Meta

Tech Provider

Google

Tag Manager

TikTok

Events API

Microsoft

UET Partner

LinkedIn

CAPI Partner

Pinterest

CAPI Partner

Built on the same partner stack used by enterprise DTC brands.

Ariful Islam — Founder, Tracking Consulting

Meet your consultant

Ariful Islam

Founder · 8+ years in paid media & tracking

Verified earnings

$200K+

earned on Upwork

Top Rated Plus
4.9/5 on Upwork · 300+

Verify the receipts

You work directly with Arif — no SDR, no account manager.

By the numbers

No fake testimonials.Just the math.

70+

Platforms supported

Shopify · Woo · Magento · BigCommerce · 65 more

8+ / 10

Meta EMQ guaranteed

in writing — keep working free until hit

2–4d

Build to live

accurate data flowing within 7 days

$0

Monthly fees, ever

one-time fixed price · you own the stack

400d

Cookie lifetime

max RFC 6265bis allows · 57× Safari ITP

9

Ad channels covered

Meta · Google · TikTok · MS · LI · Pin · Snap · Reddit · X

95%+

Tracking accuracy

verified vs Stripe · GA4 · ad-platform reports

30 min

Free founder call

no SDR · no pitch deck · written remediation plan

Every figure above is either a commitment we put in writing or a countable fact. What your own setup is losing is not on this list, because we haven’t measured it yet — that happens on the call, against your own order records.

Real clients · real videos · real outcomes

Don’t take our word for it. Watch the receipts.

Founders, marketers, and agency owners describing the before-and-after of their TikTok Events API tracking rebuild — in their own words, on camera.

The problem

Where teams get this wrong

TikTok Events API-specific issues
Leak #01

No shared event ID with the pixel

Both paths count independently, exactly as with Meta.

Leak #02

Hashing identifiers without normalizing

A valid hash of a malformed value matches nothing and errors nowhere.

Leak #03

ttclid never captured

TikTok's click identifier has to be captured on landing and persisted, or the strongest matching signal is missing.

Who this is for

Honest about who we’re a fit for.

We don’t take every project. Here’s how to tell if we’re right for you.

Good fit

You’re a great fit if…

  • You run TikTok Events API (or are migrating to it)
  • You spend $5K+/month on paid ads (Meta, Google, TikTok, Microsoft, LinkedIn)
  • Your reported ROAS doesn’t match what your bank account is saying
  • You want to own your tracking stack — no monthly SaaS fees forever
  • You have 2–4 days to do this once and never think about it again
Not a fit

Skip us if…

  • You spend less than $500/month on paid ads (browser pixel is fine)
  • You want a SaaS dashboard with monthly fees forever (Triple Whale, Hyros)
  • You need attribution modeling — we fix the data foundation, not multi-touch reports
  • You want a 6-month enterprise consulting engagement (we ship in 4 days)
  • You expect us to manage your ad accounts (we don’t — that’s a different service)

If you’re still unsure,book the call anyway— we’ll tell you straight whether we can help.

Our position

If yourreported ROASdisagrees with your bank account, you don’t have an attribution problem.You have a data foundation problem.No SaaS dashboard fixes that — only a rebuilt 1st-party server-side stack does.

Ariful Islam — Founder
The outcome

What a correct implementation looks like

A shared event ID on both paths

Server-side

The order ID works, as everywhere else.

Identifiers normalized then hashed

8+ EMQ

Lowercase, trimmed, phone in E.164.

ttclid captured on landing and forwarded

Deduped

Persisted like any other click identifier.

value and currency on monetary events

Backend-verified

From the order record.

The full transformation report

Before vs after — built in 2–4 days, accurate data within 7 days

This is what changes structurally, not a promise about your numbers. The figures specific to your account come from the reconciliation we run against your own order records before the build and again after — the two commitments below are the ones we put in writing.

Attribution accuracy

  • Reported conversions vs your order records
    BeforeWhatever today's reconciliation shows — most have never run one
    After95%+ match, guaranteed in writing
  • Where the purchase event comes from
    BeforeThe browser, if it survives the redirect
    AfterYour backend order record
  • Click IDs across redirects and domains
    BeforeCommonly dropped at the first hop
    AfterCaptured at first touch, persisted first-party
  • Server-attributed conversions
    BeforeNone — browser only
    AfterEvery order, sent server-side

Audience quality

  • Meta Event Match Quality
    BeforeWhatever Events Manager shows you today
    After8+ / 10, guaranteed in writing
  • Cookie lifetime in Safari
    Before7 days — ITP's cap on JavaScript-set cookies
    AfterUp to 400 days — the RFC 6265bis maximum
  • Identity sent with a purchase
    BeforeWhatever the browser happened to hold
    AfterEmail, phone, name, city, state, zip, external ID — hashed
  • Lookalike and retargeting seeds
    BeforeBuilt from the conversions that survived
    AfterBuilt from every order in your backend

Bidding performance

  • What bidding optimizes toward
    BeforeThe events that happened not to be blocked
    AfterEvery conversion, including offline outcomes
  • Conversion value
    BeforeOften missing, or a total that doesn't match your revenue
    AfterThe amount actually charged, with currency
  • Refunds and cancellations
    BeforeNever reported back, so ROAS stays inflated
    AfterReversed at every destination
  • Duplicate conversions
    BeforeUndetectable without an order ID
    AfterDeduplicated on a shared event ID

Compliance & ownership

  • Consent behavior under audit
    BeforeUntested — tags commonly fire before consent is set
    AfterVerified: nothing leaves before consent
  • Consent Mode v2 wiring
    BeforeNot configured
    AfterFully wired + verified
  • 3rd-party cookie deprecation ready
    BeforeNo
    AfterYes
  • Data ownership
    BeforeVendor-locked
    After100% yours

Server-side

money events from your backend

8+ / 10

Meta EMQ guaranteed

95%+

tracking accuracy

A typical engagement

The shape of a typical TikTok Events API rebuild

We’re not going to invent a fake testimonial here. Instead — here’s the realistic pattern of what happens, anonymized but accurate to engagements we ship.

Day 0 — They arrive

A 7-figure TikTok Events API store spending ~$25K/month on Meta. Reported ROAS shows 4.1× in Ads Manager. Their bookkeeper’s number says 2.6×. The founder doesn’t know which is real, so they keep doubling down on what looks like a winning campaign — except cash flow tells a different story.

Day 1 — Audit

We screen-share. Within 20 minutes we’ve found the leaks: native pixel firing twice on iOS, CAPI dedup using the wrong event_id (Meta is double-counting), GA4 showing 38% (not set), and the Customer Events API never enabled. The 1.5× ROAS gap explains itself.

Day 2–3 — Build

Server-side GTM container goes live on data.theirstore.com. Meta CAPI rebuilt with full advanced matching. Google Enhanced Conversions wired. TikTok Events API turned on. All event_ids deterministic. iOS recovered.

Day 4 — Launch

Live-fire test purchases through every funnel step. Meta Event Match Quality goes from 4.5 to 8.7 — verified live in Events Manager. They get a Notion runbook + Loom walkthrough so their dev team can extend it.

Day 5–7 — Accuracy

Conversion data starts flowing cleanly. Day 7: reported ROAS reads 2.8× (matches Stripe within 5%). Lookalike audiences grow because Meta finally has clean seed data. Their CAC dashboard makes sense for the first time in a year.

Day 30 — The math compounds

Smart Bidding has 30 days of clean signal. CPA drops 18%. They scale Meta budget 40% because they finally trust the data. Net new revenue from the recovered tracking: roughly $14K/mo above what they were getting before.

Numbers above are realistic averages from engagements we’ve shipped. Your specific recovery depends on your iOS share, ad-blocker rate, and current setup — we’ll quantify it on the call.

The cookie window unlock

400-day cookie lifetime — the longest your browser allows

Default TikTok Events API setups put cookies on a 7–30 day timer. Safari ITP caps client-set cookies at 7 days. That kills your retargeting windows, shrinks lookalike audiences, and starves Smart Bidding of historical signal.

We set 1st-party cookies via HTTP headers on your own subdomain — exempt from ITP’s 7-day cap. Lifetime: 400 days. The maximum Chrome, Firefox and Safari currently permit.

  • 57× longer retargeting window vs Safari default

    Reach users who saw your ad 6 months ago instead of last week.

  • Bigger lookalike seed pools

    More retained users in your custom audience = better lookalike quality on Meta, Google, TikTok.

  • Smart Bidding has 13× more signal history

    Algorithms optimize on 400 days of behavior, not 7 days. CPA stabilizes faster.

  • Critical for high-AOV / long-consideration purchases

    If your average buyer takes 30+ days to convert, default cookies miss them. 400-day cookies don’t.

Cookie lifetime — head to head

How long cookies survive in real-world traffic

Safari ITP (default)7 days
Chrome / Firefox (typical)30 days
Meta default retargeting window90 days
Google Ads default cookie540 days(but capped by browser)
Our 1st-party server-side400 days

400 days is the hard maximum enforced by RFC 6265bis (Chrome 104+, Safari 17+, Firefox 110+). We set it via HTTP Set-Cookie: Max-Age=34560000 on your subdomain. Survives Safari ITP’s 7-day client-side cap.

Under the hood

What’s actually happening on your server-side stack

Six capabilities your default TikTok Events API setup doesn’t have. Built on the same Stape Pro stack used by enterprise DTC brands.

Cookie window

Cookie Keeper

400-day 1st-party cookies

Set via HTTP headers on your subdomain — the maximum browsers allow. Survives Safari ITP’s 7-day cap that kills retargeting.

Ad-block resistance

Custom Loader

Custom-loaded GTM scripts

Your gtm.js and analytics scripts load through a custom path on YOUR domain. uBlock, AdBlock Plus, Brave can’t identify them as trackers.

Attribution

Click ID Restorer

Click ID restoration

fbclid / gclid / ttclid / wbraid recovered from the URL and persisted server-side. Multi-redirect funnels stop dropping attribution. Safari user IDs restored.

Profit signal

POAS Data Feed

POAS — Profit on Ad Spend

Send actual profit data (not revenue) to Meta / Google. Smart Bidding optimizes for the metric that matters: net margin, not gross revenue.

Identity

User ID

Cross-session User ID

Stable userID generated server-side from IP + UA + SSL fingerprint. Stitches anonymous → known → returning visitors across 400 days.

Audience signal

GEO Headers

GeoIP enrichment

Country, region, city, postal code passed to Meta / Google CAPI from your server — without exposing the raw user IP to the browser.

Compliance

Anonymizer

PII hashing by default

Email, phone, name, address are SHA-256 hashed on your server before they leave for Meta or Google. Zero raw PII in transit.

Quality filtering

Bot Detection

Bot traffic detection

Bot/scraper traffic identified at the gateway and blocked from polluting your audiences. Smart Bidding optimizes against humans, not bots.

Reliability

Dedup logic

Browser ↔ server dedup

Deterministic event_id and event_time so Meta / Google never double-count. Your reported ROAS stops contradicting Stripe.

Reputation

Dedicated IP

Dedicated outbound IP

Your sGTM gets a dedicated static IP for outgoing CAPI requests. Better deliverability to Meta, Google, TikTok — no shared-IP noise.

Residency

Multi-region

EU / US region routing

GDPR-conscious stores route their CAPI traffic through EU regions (Stape EU or self-hosted GCR europe-west). No US data hop.

Data warehouse

BigQuery export

BigQuery + Looker dashboard

Server logs + GA4 raw events streamed to BigQuery. Looker Studio dashboard branded for your team. Premium tier.

We’re official Stape Pro partners — every Power-Up above is enabled and configured for you. Or we self-host the equivalent on your Cloud Run / GKE if your traffic justifies the cost crossover. You pick.

Live data flow

What your stack is doing —right now

Every conversion fires through your subdomain, gets enriched with hashed identity params, deduped against the browser pixel, then forwarded to Meta CAPI, Google EC, TikTok Events API and Microsoft UET in parallel.

You see this stream live in your sGTM debug console — not a SaaS dashboard you rent. It’s your data, on your server, on your subdomain.

  • p99 latency< 80ms
  • Avg. event payload9 identity params
  • Browser → Server dedupDeterministic event_id
  • Failure handlingRetry · queue · dead-letter
sgtm-debug · data.tiktok.com
streaming
10:42:18[INFO]evt=PageView | id=ev_a3f2.. | ua=ios17 | ip_hash=ok
10:42:18[OK]→ meta.capi status=200 emq_pred=8.6
10:42:18[OK]→ google.ec status=200 match=enhanced
10:42:24[INFO]evt=AddToCart | id=ev_b1c8.. | val=$84.00
10:42:24[DEDUP]browser↔server merged on event_id=b1c8..
10:42:24[OK]→ meta.capi status=200 emq_pred=8.7
10:42:24[OK]→ tiktok.eventsapi status=200
10:42:31[INFO]evt=Purchase | id=ev_c9d4.. | val=$184.00
10:42:31[POAS]profit=$58.42 sent (margin 31.7%)
10:42:31[OK]→ meta.capi status=200 emq=8.8 ✓
10:42:31[OK]→ google.ec status=200 ✓
10:42:31[OK]→ microsoft.uet status=200 ✓
10:42:33[BOT]blocked: ua=AhrefsBot · 1 evt suppressed
uptime: 99.98%all channels healthy
Every paid-media channel · 1st-party server-side

CAPI / Events API ready for every ad platform you run

One server-side gateway. Every major ad platform fed real conversion data, deduped, with full identity match.

Meta

Conversions API

Server-side

Google

Enhanced Conv.

Server-side

TikTok

Events API

Server-side

Microsoft

UET Server

Server-side

LinkedIn

CAPI

Server-side

Pinterest

CAPI

Server-side

Snapchat

CAPI

Server-side

Reddit

CAPI

Server-side

X / Twitter

Events API

Server-side
What you get

The checklist

Item 01

Event ID shared between pixel and Events API

Byte-identical on one real conversion.

Item 02

User identifiers normalized before hashing

The most common matching failure on every platform.

Item 03

ttclid captured on landing

And persisted through your forms.

Item 04

value and currency present

On every monetary event.

Item 05

Event names matching TikTok's standard set

Verify against current documentation.

The honest math

Three ways to fix your tracking. One of them makes sense.

Option 1

Hire a senior tracking engineer

$15K–$25Kin dev cost

or 2–4 weeks of senior FTE time

  • 2–4 weeks before anything ships
  • Misses iOS / Safari / dedup edge cases
  • No EMQ guarantee — it’s “done” when they say so
  • Pixel debugging is not their day job

Option 2

Triple Whale / Hyros / Northbeam

$300–$2,000/month forever

$18K–$120K over 5 years

  • You rent a dashboard — they own your data
  • Cancel and you lose attribution overnight
  • Per-event / per-visitor pricing surprises
  • Still doesn’t fix your underlying tracking
Recommended

Option 3 — us

Done-for-you 1st-party server-side

$400–$1,800one-time

pay once · own the stack forever

  • Live in 2–4 days · accurate data within 7
  • iOS / Safari / dedup all handled by default
  • Meta EMQ 8+ guaranteed in writing
  • You own everything — server, container, runbook

We’re upfront: if you have a senior in-house dev with capacity and 4 weeks, hiring is fine. If you spend $1M+/yr on ads and want a SaaS dashboard layered on top, Triple Whale works. For most paid-ad advertisers between, we’re the math that makes sense.

Pricing

Pick the package that fits your ad spend

Fixed-fee, no surprises. If your ad spend is meaningful,server-side tracking is what we recommend— it’s the only setup that survives iOS, Safari ITP and ad blockers.

Tier 01

Browser-side starter

$400One-time fee · lifetime ownership

Repairs and verifies your existing browser-side setup against this reference, on a live conversion.

  • Implementation checked against the spec
  • Verified on a live conversion
  • Reconciled against your own records
  • Written handover
Have mine checked
Tier 02
Recommended

1st-party server-side

$800One-time fee · most popular

Save $18K–$120K over 5 years vs Triple Whale / Hyros

Money events sent from your own records through a first-party container on your subdomain, built to this specification.

  • First-party server container on your own subdomain
  • Events from your records, not the browser
  • Deduplicated on a shared event ID at every destination
  • First-party cookies beyond Safari's 7-day cap
  • 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Have it built properly
Tier 03

Full 1st-party stack

$1,800One-time fee · lifetime ownership

Every paid channel server-side plus the offline loop, documented to this standard.

  • Everything in 1st-party server-side
  • Pinterest, Snapchat, Reddit and LinkedIn CAPI
  • CRM and offline conversion loop
  • Refunds and cancellations reversed everywhere
  • Monitoring so the next break surfaces in days
Get the full stack

Not sure which tier fits?Book a 30-min scoping call— we’ll tell you straight, no upsell pressure.

From the founder’s desk
Ariful Islam — Founder
Available now

Ariful Islam

Founder & lead engineer

  • Experience8+ years in tracking
  • Engagements300+ DTC brands shipped
  • Specialty1st-party sGTM · CAPI
  • PartnerStape Pro · Meta Tech

“I’ll personally walk through your tracking on the call.No SDR.No sales pitch.”

I’ve spent 8 years rebuilding tracking for DTC brands, SaaS founders, agencies, and one thing I’ve learned: most tracking problems aren’t technical — they’re trust problems. You don’t know who to believe. Your current vendor swears it’s fine. Meta’s reports look great. Stripe says otherwise.

On our call, I’ll personally show you exactly what’s leaking, exactly what it would cost to recover, and whether you should hire us at all. If your current setup is genuinely fine, I’ll tell you. If a $400 browser-side fix is enough, I’ll say so. No upsell pressure.

Book the call. Worst case, you walk away with a free 47-point audit checklist. Best case, we deliver your 1st-party server-side stack in 2–4 days and your data is fully accurate within 7 days.

Arif— Founder

How it works

Built in 2–4 days. Accurate data within 7.

We deliver the entire 1st-party server-side stack in 2–4 business days. You start collecting accurate, deduped conversion data the moment it goes live — and within 7 days every signal is flowing cleanly to Meta, Google, TikTok and the rest.

1Day 1

Kickoff + audit

30-min call. We map your current pixels, GTM, dataLayer, consent setup, and ad-platform integrations. You get a written report of every leak.

2Day 2–3

Build the stack

Server-side GTM container deployed on your subdomain. Meta CAPI · Google EC · TikTok Events API · Microsoft UET wired. Identity match + dedup configured.

3Day 4

QA + go-live

Live-fire test purchases across every funnel step. Meta EMQ verified at 8+. Tag Assistant + Pixel Helper passes. Side-by-side report delivered.

4Day 5–7

Verify accuracy

Your data flows clean. Within 7 days every signal — Meta, Google, TikTok, Microsoft — is fully accurate. Notion runbook + Loom walkthrough handoff.

Architecture

How the payload is structured

The structural elements common to every server-side conversion API. TikTok publishes the current field names and they change — verify before building.

  1. Step 1

    Event name

    TikTok's standard event set. Use the standard names rather than custom ones where a standard fits.

  2. Step 2

    Event timestamp

    When the event happened, not when it was sent. A delayed send with a stale timestamp is correct.

  3. Step 3

    Event ID

    Shared with the browser pixel. This is what deduplicates, and it's the most common omission.

  4. Step 4

    User identifiers

    Hashed email, hashed phone, external ID, plus the click identifier where captured.

  5. Step 5

    Click identifier (ttclid)

    Captured on landing from the URL and forwarded. The strongest matching signal available.

  6. Step 6

    Event properties

    value, currency and content details for monetary events.

Diagnostic sequence

Common mistakes and how to validate each

Ordered by how often we find them. Each one has a specific check rather than a general instruction to be careful.

  1. 1

    Pixel and API each generating their own event ID

    Capture both payloads from one conversion and compare.

  2. 2

    Values hashed with case or whitespace intact

    Read the raw value before hashing on a live conversion.

  3. 3

    ttclid missing

    Click one of your own TikTok ads and check whether the parameter is captured on landing.

  4. 4

    Sent timestamp instead of event timestamp

    Check what a delayed send reports. It should be the original event time.

  5. 5

    Custom event names where standard ones exist

    List your active events and compare against TikTok's standard set.

Source-of-truth validation

How to prove your implementation is right

Against your own records and a live payload, not against a preview screen.

Source of truthyour backend order records, matched on order ID
  • Identical event ID confirmed on pixel and API for one real conversion.
  • ttclid confirmed captured on landing and present in the payload.
  • Identifiers confirmed normalized before hashing.
  • Conversion count within a few percent of backend orders for a closed week.
  • Checked on a live conversion, not in preview mode.
  • Reconciled over a fully closed window, matched per record.
  • Re-checked 30 days later.

Straight talk

What this reference deliberately leaves out

Stated openly, because a reference that's silent about its own gaps is the dangerous kind.

  • TikTok's exact current field names and standard event list are in their documentation and change more often than the other major platforms'. We've described the structure rather than reproducing a field table that would go stale.
  • TikTok's deduplication window isn't a figure we'll guess at. Keep send latency low and verify against your own records.
  • Advanced matching options beyond the core identifier set are omitted.
  • Vendor documentation is the authority, not this page. Where the two disagree, the vendor is right and we'd like to know so we can correct it.
  • Parameter names and behaviour change. Anything here is accurate as we last verified it; verify against the current documentation before you rely on it for a build.

Got questions?

The honestanswers.

No buzzwords, no upsell. If we don’t know, we say so.

01Does TikTok deduplicate like Meta?

The principle is the same: a shared event ID between the pixel and the server events. Verify the exact behaviour in TikTok's current documentation before building.

02What is ttclid?

TikTok's click identifier, appended to your landing URL. Capture it on landing and persist it — it's the strongest matching signal available.

03Should I use standard or custom event names?

Standard where one fits. Custom events lose you optimization and reporting that's built around the standard set.

04Why is this page less detailed than the Meta one?

Because TikTok's field names change more often, and we'd rather describe the structure accurately than publish a table that's wrong in three months.

Still have questions?Book a 30-min call— bring them all.

The call

What happens on your free 30-min call

No pitch deck, no SDR, no upsell pressure. Founder-led. Bring your ad-platform screens and yourTikTok Events API setup — we’ll work through it together.

Min 1–5

We get the lay of your store

What you sell, what you spend on ads, who handles dev. Quick context-gathering — no questionnaire upfront.

Min 5–15

We audit your tracking live

Screen-share. We open your Meta Events Manager, GTM, and ad reports. You see exactly which conversions are leaking.

Min 15–25

We map a fix

What needs rebuilding, what stays. The exact TikTok Events API setup we'd ship and what it would recover for you.

Min 25–30

Decide. Or don’t.

If we're a fit, we send a 1-page proposal in writing. If not, you walk away with a free remediation plan you can hand to anyone.

No pitch deckFounder-led, not SDRYou leave with a written planZero commitment
Free · 30 minutes · No commitment

Get TikTok server-side events built correctly

Book a free 30-minute call. We check your implementation against this reference on your own account, live, and you leave with a written list — including the option that it's already fine.

Free · 30-min consultation · No commitment · Replies in under 2 hours · Available worldwide via WhatsApp

95% guarantee · from $400