TikTok Conversion Tracking: Pixel, Events API, and What Optimizes in 2026

Updated July 22, 2026.

TikTok website conversion tracking should start with a TikTok Pixel and standard events, then add Events API when the business can send authoritative server outcomes. The critical distinction is that TikTok custom events can be used for reporting and audience creation but are not eligible for campaign optimization.

Verification boundary. This guide was checked against official TikTok for Business advertiser help, developer documentation, and release notes available on July 22, 2026. It does not rely on agency blogs, community posts, or third-party tutorials. Interface labels can differ during account-level rollouts. Where the official documentation describes a pilot, gradual rollout, regional limit, or incomplete availability, the guide says so rather than assuming access.

TikTok migrated several event names in 2025. This guide uses Lead instead of SubmitForm and Purchase instead of CompletePayment; ClickButton and PlaceAnOrder remain soft-deprecated until 2027.

Choose the data source

Step 1: Create and install the Pixel

1. In TikTok Ads Manager, open Events Manager and create/select a web data source.
2. Choose the TikTok Pixel and the installation method offered: partner, Google Tag Manager or manual code.
3. Copy the Pixel code generated by TikTok and install it in the global site template, or complete the official partner/GTM flow.
4. Verify base page activity in Events Manager and the official Pixel Helper.
5. Keep the same Pixel/data source for related website events unless there is a documented business reason to separate environments.

Step 2: Use current standard events

Current standard event names covered by TikTok’s official April 2026 documentation include:

AddPaymentInfo, AddToCart, AddToWishlist, CompleteRegistration, Contact, Download, InitiateCheckout, Lead, Login, Purchase, Search, StartTrial, SubmitApplication, Subscribe, ViewContent

TikTok also documents legacy-transition events. For new builds, do not start with SubmitForm or CompletePayment; use Lead and Purchase. Avoid new dependence on ClickButton or PlaceAnOrder because TikTok says they are soft-deprecated until 2027.

Step 3: Configure events with Event Builder

TikTok’s Event Builder supports URL and button events.

1. Open the Pixel in Events Manager and choose the event setup option.
2. Enter the website URL and launch Event Builder.
3. For a URL event, define the page condition that uniquely represents completion.
4. For a button event, select the element and choose the closest standard event.
5. Add value/currency or content parameters only when the builder and page expose them correctly.
6. Save, publish and test the event in a clean browser session.

Do not use a button event for a form that can fail validation or a payment button that can be declined. In those cases, fire custom code from the confirmed success state or send the event from the server.

Step 4: Add events with custom code

// Illustrative syntax; use TikTok's current generated code and parameter schema.
ttq.track('Purchase', {
  value: ORDER_VALUE,
  currency: 'USD',
  contents: CONTENT_ARRAY
});

Place the event after the business action succeeds. Map content IDs to the same IDs used in the catalog when product ads or catalog matching depend on them. Keep value and currency data types consistent.

Step 5: Understand custom events

A custom event lets you send a business-specific event name that is not one of TikTok’s standard events. TikTok’s February 2026 help page says custom events can be used for reporting and audience creation, but not for campaign optimization.

Use a custom event for a diagnostic or genuinely unique behavior. Do not use it as the only purchase, lead or subscription signal when a standard event fits, because you would give up optimization eligibility.

Step 6: Configure Events API

Events API supports web, app and offline events. For websites, TikTok recommends using Pixel and Events API together.

1. Create or select the same web data source used by the Pixel.
2. Choose direct Events API or an official partner path.
3. Generate access credentials through TikTok’s current authorized setup.
4. Send standard event name, event time, event source/context, permitted matching keys and event properties required by the current schema.
5. For Pixel + API duplicates, use the current event identifier and duplicate-handling fields specified by TikTok so one business action is counted once.
6. Send a controlled test event and inspect Events Manager diagnostics before production.
7. Monitor latency, match quality and rejected events.

Step 7: Offline and CRM outcomes

Use Events API or an approved integration for qualified leads, sales, call outcomes or other offline events. Preserve TikTok click identifiers and consented first-party matching data at acquisition. Send the actual event time, value and currency, and a stable event ID. Keep raw Lead and later Qualified Lead/Sale definitions separate in your internal taxonomy even when the platform category options differ.

Step 8: App conversions

TikTok supports app measurement through a mobile measurement partner, App Events SDK and App Events API. The official June 2026 App ID guidance says a TikTok App ID is used across these paths.

1. Create or identify the app in TikTok Events Manager and generate the App ID.
2. Choose MMP, SDK or App Events API based on the app stack and campaign objective.
3. Map install/first-open and in-app standard events.
4. Configure privacy framework and mobile platform requirements.
5. Test on real devices and inspect event receipt before optimizing campaigns.

Step 9: Select optimization events

At campaign/ad-group creation, select an eligible standard event from the correct data source. Do not select a custom event and assume the system will optimize toward it. Use a higher-funnel standard event temporarily only when it still predicts value, then graduate toward Purchase, Lead, Subscribe or another business outcome as volume permits.

QA checklist

• One Pixel/data source is installed on the intended site and not duplicated by a partner and manual code.
• New builds use Lead and Purchase rather than migrated legacy names.
• Button events are not used where success can fail after the click.
• Purchase values, currency and content IDs match the order and catalog.
• Custom events are labeled reporting/audience-only in the measurement plan.
• Pixel and Events API copies use TikTok’s current duplicate-handling fields.
• Match keys are permitted, normalized and consented.
• App setup uses the correct TikTok App ID and chosen MMP/SDK/API path.
• The campaign optimization event is a supported standard event.
• Events Manager totals reconcile with order, CRM or app records.

Common failures

Implementation blueprints

Commerce event plan

Lead-generation event plan

Do not build a new taxonomy around SubmitForm or CompletePayment. TikTok’s current migration guidance points to Lead and Purchase, and ClickButton/PlaceAnOrder remain soft-deprecated until 2027.

Event Builder acceptance rules

• A URL rule is unique to completion.
• A selected button cannot fail after the click.
• The element remains stable across responsive layouts.
• Value and content fields are visible and correct.
• A front-end release triggers a regression test.

Release acceptance criteria

• Pixel fires once and the current data source is selected.
• All core outcomes use standard events.
• Custom events are explicitly marked non-optimization.
• Pixel/API duplicate behavior is tested.
• Catalog IDs and Purchase values reconcile with orders.
• App events use the correct TikTok App ID and measurement path.

Verification record

Technically verified: July 22, 2026

Official-source rule: Every platform-specific instruction and feature statement in this article is grounded in an official TikTok for Business source. The implementation recommendations are editorial guidance from The Ad Spend and are labeled as such.

Known limits at publication

• Custom events are not eligible for campaign optimization.
• ClickButton and PlaceAnOrder are soft-deprecated until 2027; implementation should not expand dependence on them.
• App event availability and optimization depend on campaign type, App ID and chosen measurement path.
• Exact Events API fields are versioned; direct integrations must use the current official schema.

Official sources consulted

• Add or edit events with Event Builder and custom code
• Standard events and parameters
• Custom events
• Events API
• Adopt updated standard events
• In-app events
• Measure app activity
• Generate a TikTok App ID

Related conversion tracking references

• conversion tracking library
• standard events
• custom events
• server-side conversion tracking