TikTok Pixel and Events API

What This Page Answers

TikTok Pixel and Events API are TikTok's browser-side and server-side systems for sending web, app, offline, and CRM events into TikTok Ads. Together, they improve measurement, optimization, audience building, and event resilience.

Pixel vs Events API

SystemSourceStrengthWeakness
TikTok PixelBrowserCaptures website behavior and is easier to deployCan be affected by browsers, blockers, consent, and connectivity
TikTok Events APIServer, CRM, app, offline sourceMore reliable connection to advertiser dataRequires implementation and deduplication discipline

TikTok recommends using Events API with an existing Pixel integration for website connections to maximize performance benefits.

Why Events API Matters

TikTok's Events API can help:

  • Capture conversions missed by browser-side tracking.

  • Send web, app, offline, store, and CRM events through one API.

  • Improve optimization and targeting signals.

  • Support measurement when browser signals are incomplete.

  • Share richer event and customer information where permitted.

For TikTok Web Conversions objectives, Pixel or Events API setup is a prerequisite.

Deduplication

If the same event is sent through both Pixel and Events API, deduplication is required. TikTok requires the same event_id parameter through both Pixel and Events API when duplicate copies of the same conversion are shared. TikTok's documentation explains that overlapping events can be deduplicated across:

  • Pixel to Pixel

  • Events API to Events API

  • Pixel to Events API

For Pixel and Events API overlap, events with identical event and event_id parameters can be merged or deduplicated within TikTok's stated timing windows.

Event Design

Use events that match real business outcomes. Common ecommerce events:

  • ViewContent

  • AddToCart

  • InitiateCheckout

  • CompletePayment

Common lead events:

  • ViewContent

  • SubmitForm

  • Lead

  • Qualified lead through CRM/offline connection where possible

Common app or subscription events:

  • Install

  • CompleteRegistration

  • Subscribe

  • Purchase

Implementation Checklist

  1. Install TikTok Pixel.

  2. Add Events API through partner integration, server-side tag manager, or direct API.

  3. Use the same event_id for duplicate browser and server events.

  4. Send value, currency, content details, and customer parameters where allowed.

  5. Validate events in TikTok Events Manager.

  6. Check deduplication diagnostics.

  7. Compare TikTok event counts with backend source of truth.

  8. Monitor event quality after site, checkout, app, or CRM changes.

Common Failure Modes

  • Pixel and Events API send the same purchase with different event IDs.

  • Events API sends server events late or inconsistently.

  • Event names differ across browser and server.

  • Value or currency is missing.

  • CRM quality events are never passed back.

  • Consent handling is inconsistent.

  • Event volume is too low for optimization.

Source Notes