Paid

TikTok Ads integration for digital marketing agencies

TikTok Ads is the fastest-moving ad platform in 2026 — and the one most digital marketing agencies treat as an afterthought in their tracking infrastructure. Misfiring TikTok pixels or missing Events API integration silently underreports conversions, which makes TikTok campaigns look worse than they are and pushes budget back to Meta and Google by accident. Recording TikTok pixels and their Events API setup explicitly is how an agency spots this.

How Phloz models TikTok Ads

What Phloz records about TikTok Ads on each client's tracking map, and what it doesn't. Only GA4, Google Tag Manager and Google Ads connect to Phloz (read-only, through a connected Google account); everything else is recorded by your team. Health states are set by the person who checks, the structural audit re-runs weekly, and graph relationships show what each node connects to — so a node marked broken or overdue for verification shows up in the cross-client tracking-health view.

  • TikTok pixel as a typed node with pixel code and Events API / Advanced Matching on-off flags
  • The Events API path recorded as a flag on the pixel, or as a conversion-API endpoint node linked to it
  • TikTok ads account node (advertiser ID, Business Center, currency) — the audit flags an ad account with no pixel on the map
  • Health status and last-verified date per pixel, set by your team — no match-rate or event-delivery data comes from TikTok

Common TikTok Ads configuration gotchas

The configuration mistakes agencies most often make with TikTok Ads, surfaced here as a checklist agencies can run at every client onboarding. Honest, useful, not gated behind a sales pitch — these are real and you should audit for them regardless of whether you use Phloz.

  • Events API left in test mode: a test_event_code kept in the production payload after validation sends every real event down TikTok's test pipeline, which never reaches reporting. Remove it at go-live and confirm events on Events Manager's overview, not the test tab.
  • Advanced Matching parameters: TikTok requires hashed email/phone formatted differently than Meta's SHA-256 — same hash function, different field naming convention. Verify at rollout.
  • Pixel placement on Shopify: TikTok's native Shopify app installs the pixel on storefront pages but not on the checkout-success page in newer Shopify themes. Add manually if conversions are missing.

Guides on TikTok Ads

At launch (V1)

TikTok ads accounts and pixels as typed nodes on the map, with Events API and Advanced Matching recorded as on/off flags on the pixel. There is no TikTok connection — Phloz reads no TikTok data.

Not built yet

TikTok Marketing API sync: pixel health, event count, conversion lift.

Why we built the integration this way

Most agency CRMs treat third-party tools as text fields: "GA4 Property ID" goes in a custom column on the client record. That works at one or two clients and breaks at five. With TikTok Ads recorded on each client's tracking map — as its own typed node where Phloz has one, as fields and notes where it doesn't — the agency can answer "is this client's TikTok Ads setup documented, and when was it last verified?" per client, and see every client ranked by tracking health.

Most of it is entered by hand at onboarding: only GA4 properties, GTM containers and Google Ads accounts can be imported from a connected Google account, and nothing syncs afterwards. The manual pass forces explicit verification at the exact moment the agency takes over the client's tracking — the cheapest moment to catch the gotchas listed above, before they become production issues.

When to use this in your client onboarding flow

The pattern we recommend: at every new client onboarding (see the client onboarding audit use case), spend 30 minutes documenting the client's TikTok Ads configuration on the tracking map — IDs, tracking-code installations, conversion setup, the relationships to other systems. Verify each one fires by triggering a test event, then mark the node verified so the date is recorded. Add a recurring task (monthly, say) for the re-check, assigned to whoever owns tracking — the audit flags anything unverified for 30+ days either way.

Thirty minutes at onboarding costs far less than finding the same tracking issues during the first month of campaign optimisation — when finding them would mean a refund conversation. See the broader tracking infrastructure map use case for the agency-wide pattern.

Frequently asked questions

The three questions agencies ask most often about Phloz's TikTok Ads integration. Honest answers — same data we'd give a friend evaluating the integration.

How does TikTok's tracking compare to Meta's for agency setup?
Architecturally similar (pixel + server-side events API, audiences, custom events) but the developer ecosystem is younger. Documentation gaps are the biggest agency friction; recording the configuration explicitly in Phloz gives the team one place to check it against.
Does Phloz integrate with TikTok Spark Ads tracking?
No. Spark Ads click-through tracking is part of the TikTok pixel's standard event surface, and the click attribution is handled by TikTok's native attribution. Phloz doesn't model campaigns or Spark Ads — the map records the ad account and pixel that the tracking depends on.
What about TikTok Shop integration?
There isn't one. TikTok Shop tracking lives at the Shopify app level for agencies running TikTok Shop alongside their main store. Phloz has no TikTok Shop or catalog node — record the shop as a custom node, or in the e-commerce platform node's notes, next to the store it sells from.

Other integrations

Other paid and adjacent tools, and how Phloz handles each.

Start your free trial

14 days free for new workspaces · No credit card · Starter tier free forever