TSTrackStack
HomeDocsPricingBlogChangelogSign inGet started
Back to blog
GuidesApril 15, 2026·4 min read·TrackStack Team

LinkedIn and TikTok CAPI: a practical overview

Beyond Meta and Google, LinkedIn and TikTok have server-side conversion APIs with their own payload shapes and match keys. Here is what each expects and where teams get stuck.

  • LinkedIn
  • TikTok
  • CAPI
  • B2B

On this page

  1. LinkedIn Conversions API
  2. TikTok Events API
  3. Shared infrastructure wins
  4. When to prioritize each
  5. Configure and verify

Problem: You run LinkedIn Ads for pipeline and TikTok for top-of-funnel. Meta CAPI is done, but these two platforms still rely on pixels that miss half your conversions.

LinkedIn Conversions API

LinkedIn's server-side API accepts conversion events tied to a conversionRule ID — a numeric identifier you create in Campaign Manager. Unlike Meta's flexible event names, LinkedIn maps each rule to a specific conversion type.

Match keys include hashed email, LinkedIn click ID (li_fat_id), and member ID when available. B2B funnels often have email from gated content or demo requests.

trackstack.capture("SignUp", {
  email: lead.email,
  eventId: `linkedin_${lead.id}`,
});

TikTok Events API

TikTok's Events API mirrors Meta's model: standard events, event_id for dedup, and hashed user data. TikTok is stricter about ttclid — capture it on landing and store in a first-party cookie.

Shared infrastructure wins

Maintaining separate integrations per platform means separate hashing, retries, and monitoring. A conversion router with canonical events maps once and fans out to LinkedIn, TikTok, Meta, and Google.

Your app calls one SDK; the edge handles payload translation and credential rotation.

When to prioritize each

LinkedIn CAPI matters most for B2B with meaningful Sponsored Content spend. TikTok Events API matters for DTC and mobile-first brands where TikTok is a primary channel.

Neither replaces platform-native lead forms — those have separate webhook flows.

Configure and verify

Connect credentials per platform in Configure. Fire test events and confirm 200 responses in Logs before scaling budget.

Key takeaways

  • LinkedIn uses numeric conversion rule IDs; TikTok follows Meta-like event + event_id patterns.
  • Email match keys work for B2B LinkedIn; TikTok benefits strongly from preserved `ttclid`.
  • One canonical event schema routed at the edge beats maintaining N platform integrations.

Sources

Official documentation and references cited in this article.

  • LinkedIn — Conversions API
  • TikTok — Events API
  • Meta — Deduplicate pixel and server events

More in Guides

Guides4 min read

Google Enhanced Conversions for web apps

Enhanced Conversions improves Google's match rate by sending hashed first-party data with each conversion. This guide covers what to hash, where to fire events, and how to verify payloads land.

Read post
Guides4 min read

B2B vs DTC conversion tracking patterns

Pipeline SaaS and e-commerce shops share ad platforms but not conversion logic. Match keys, event timing, and what you optimize for differ — and your tracking setup should reflect that.

Read post
Guides4 min read

How to set up Meta CAPI in Next.js without GTM

Skip Google Tag Manager. Wire first-party Meta CAPI in Next.js with an SDK that handles hashing, deduplication, retries, and delivery logs from your existing app code.

Read post

Ready to fix your conversion pipeline?

Install the TrackStack SDK, route events to Meta and Google, and verify delivery from one dashboard.

Get started freeView quickstart

© 2026 TrackStack. First-party conversion infrastructure.

DocsPricingBlogChangelog