TikTok Conversion API Setup and Tracking Guide

Your TikTok campaign may look profitable on the surface, while some of its most valuable conversions never appear in the report. A customer can view a product, add it to their cart, complete checkout, or submit a lead form, yet the path behind that action may remain incomplete.

That missing data affects more than reporting. It can influence which ads TikTok prioritises, where you allocate budget, and how confidently you judge campaign performance.

TikTok Conversion API, officially known as Events API, is designed to make that picture clearer. However, getting useful data from it depends on how you set it up, connect it with TikTok Pixel, and handle overlapping events.

The following sections break down the parts that matter, without turning the process into a technical maze.

What Is TikTok Conversion API?

TikTok Conversion API, officially called TikTok Events API, is a server-to-server connection that sends marketing and conversion events from your website, ecommerce platform, app, CRM, server, or offline system directly to TikTok.

Depending on your business and setup, you can report actions such as:

• Product views and searches

• Add to carts and checkout starts

• Purchases and offline sales

• Registrations and form submissions

• Subscriptions and qualified leads

TikTok can use eligible event data to measure conversions, attribute results to ads, optimise delivery, create audiences, and support retargeting. The quality of those outcomes depends on the accuracy, completeness, matching details, and consent status of the information you provide.

Events API has a narrower purpose than TikTok’s other developer products. Marketing API manages advertising functions, TikTok Shop APIs support commerce operations, and Research API provides approved researchers with access to selected public platform data. Events API focuses on sending marketing events.

How Does TikTok Conversion API Work?

TikTok Conversion API passes a recorded customer action from your business systems to TikTok, where it can be matched with an eligible ad interaction and used for measurement.

The process usually follows this sequence:

1. A customer views or clicks your TikTok ad and visits your website or store.

2. They complete an action, such as viewing a product, adding an item to the cart, submitting a form, or placing an order.

3. Your website, ecommerce platform, payment system, or CRM records the action.

4. Your server or integration creates an event containing details such as the event name, time, order value, product information, and available matching data.

5. The event is sent to the TikTok Events API.

6. TikTok uses identifiers such as click data, contact details, browser information, or other eligible matching fields to connect the action with a TikTok user or ad interaction.

7. Matched events may contribute to reporting, attribution, campaign optimisation, retargeting, and audience creation.

For web tracking, the same action may also reach TikTok through Pixel:

TikTok ad → Website visit → Customer action → Pixel event and server event → Deduplication → TikTok Ads Manager

The server event can still report a confirmed outcome when the browser request fails because the Pixel was blocked, the confirmation page did not load, checkout happened elsewhere, or the connection ended too quickly.

However, receiving the event does not guarantee TikTok attribution. TikTok still needs enough valid matching and attribution data to connect that conversion with an eligible ad interaction.

TikTok Pixel vs TikTok Conversion API

TikTok Pixel and Events API collect conversion data through different routes. Pixel records activity in the customer’s browser, while Events API sends events from your server or another connected system. 

TikTok recommends using both for web conversion tracking when possible.

Pixel is better suited to immediate onsite behaviour, while Events API can confirm outcomes recorded after the browser interaction, such as approved payments or qualified CRM leads. 

When both report one conversion, TikTok requires deduplication so Ads Manager counts it once.

What Events and Data Can You Send Through TikTok Events API?

1. Standard Conversion Events

TikTok provides standard event names for common e-commerce and lead generation actions. These predefined events can support reporting, conversion optimisation, and audience creation.

Common events include:

• ViewContent: A visitor opens a product page or another important page.

• Search: Someone searches your website for a product, category, or term.

• AddToWishlist: A shopper saves an item for later.

• AddToCart: A product is successfully added to the cart.

• InitiateCheckout: The customer begins the checkout process.

• AddPaymentInfo: Payment details are submitted during checkout.

• Purchase: A completed purchase is recorded.

• SubmitForm: A visitor successfully sends a lead or enquiry form.

• CompleteRegistration: A user finishes creating an account or registering.

• Subscribe: A customer completes a subscription action.

• StartTrial: A user begins a trial.

The event name alone is not enough. You also need to decide exactly when each event fires.

For example, Purchase may refer to an order being created, payment being authorised, payment being captured, or the order being fulfilled. Choose one trigger and apply it across your website, backend, and reporting systems.

Parameters then add context to the event. Depending on the action, these may include value, currency, quantity, content IDs, and product information. TikTok marks some parameters as required and recommends others because they can improve event quality and campaign performance.

Sending the same event at different stages can overstate conversions and revenue. Standardise the trigger and parameters before launch so Ads Manager receives one consistent version of each customer action.

2. Event Parameters

Once the event trigger is clear, parameters describe what happened and give TikTok the information needed to interpret it correctly.

An event may include:

• Event name: The action being reported, such as AddToCart or Purchase.

• Event time: The time the action occurred.

• Event ID: A unique identifier used to recognise the same event across Pixel and Events API.

• Event source URL: The page where the action took place.

• Currency: The currency used for the transaction.

• Conversion value: The total monetary value attached to the event.

• Product or content IDs: The identifiers for the products involved.

• Content type: The category of content being reported.

• Quantity: The number of units included in the action.

• Order details: Supported purchase information, such as item-level content data.

Product identifiers must follow the same format used in your connected TikTok catalogue. Check whether the catalogue stores product IDs, variant IDs, SKUs, or another platform-specific identifier before mapping events.

Currency and value also need consistent formatting. Missing, static, or incorrectly mapped values can leave purchase events without usable revenue data and weaken return on ad spend reporting.

3. Customer Matching Information

After TikTok receives an event, it needs enough information to connect that action with a customer or an eligible ad interaction.

Common matching identifiers include:

• TikTok click ID: The ttclid value attached to a TikTok ad click.

• Hashed email address: A normalised email address converted using SHA-256.

• Hashed phone number: A consistently formatted phone number converted using SHA-256.

• Hashed external customer ID: Your own customer identifier, prepared according to TikTok’s specifications.

• Customer IP address: The IP recorded when the website action occurs.

• Browser user agent: Information about the customer’s browser and device.

• TikTok first-party identifier: The supported _ttp cookie value, when available.

An event can be accepted by the Events API and still produce weak matching if these fields are absent, invalid, or formatted incorrectly. Stronger matching depends on sending the identifiers you can lawfully collect, not simply sending a larger payload.

Email addresses, phone numbers, and external IDs must be normalised and hashed exactly as TikTok requires. Click IDs, IP addresses, user agents, and supported cookie identifiers follow their own formatting rules. 

Your setup must also respect consent choices, privacy notices, and the data protection requirements that apply in each market.

How TikTok Event Matching and Deduplication Work

Event Matching

TikTok uses match keys to connect a reported conversion with a person who previously interacted with an ad. One useful key is the TikTok click ID, or ttclid, which may be added to the landing page URL after an ad click.

Your website should retain that value as the visitor moves through the buying journey. Saving it with the final order or lead gives TikTok a stronger chance of linking the outcome back to the original interaction.

The click ID may disappear when:

• A redirect removes URL parameters

• Checkout moves to another domain

• A payment provider starts a separate session

• Tracking values are cleaned from the URL

• The original session expires

Contact details and external customer IDs can also support matching, but they must be normalised before hashing. Use the customer’s actual IP address and browser user agent as well. 

Sending placeholder data, a server IP, or a backend user agent gives TikTok information about your system rather than the buyer.

Event Deduplication

When Pixel and Events API both send the same conversion, TikTok needs to recognise that the two records describe one customer action. Deduplication prevents a purchase, lead, or registration from being counted twice.

Both copies must use the same event name and the same unique event ID.

For example:

• Pixel Purchase: order_84739

• Server Purchase: order_84739

TikTok compares those fields to identify overlapping events. The value, currency, and product details should also match, so reporting remains consistent.

An order ID, transaction ID, checkout completion ID, or stable server-generated UUID can work well because each refers to one conversion.

Avoid product IDs, customer IDs, reused session IDs, or separate random IDs generated by the browser and server.

API retries should reuse the original event ID. A new ID can make the retry appear to be another conversion.

How to Set Up TikTok Conversion API

Step 1. Choose an Integration Method

Your first decision is how event data will travel from your business systems to TikTok. The best route depends on your existing platform, available technical support, and how much control you need over event mapping and data quality.

Each method handles a different level of complexity, so compare the options against the way your store already records conversions.

• Commerce platform integration: Usually the simplest route for supported Shopify or WooCommerce stores. The platform manages much of the connection, event mapping, and catalogue setup.

• Data or tracking partner: Suitable when you already use a customer data platform, CRM, tag manager, or server tracking provider. Confirm which events, identifiers, and consent controls the partner supports.

• Direct API integration: Better for custom websites, proprietary checkouts, marketplaces, subscription platforms, or unusual conversion logic. It offers more control but requires development, testing, monitoring, and maintenance.

• Server-side Google Tag Manager: A practical option for teams that already operate a server container and understand tags, triggers, variables, GA4, and cloud hosting. TikTok also provides an interactive setup flow for this method.

Before committing, assess your required events, technical resources, catalogue structure, access to event logs, number of stores, consent setup, and who will maintain the connection after launch.

Step 2. Create an Event Tracking Plan

Before configuring the integration, create a tracking plan that gives every customer action one agreed-upon definition. This keeps developers, marketers, and analytics teams working from the same rules.

Record the following for each event:

• TikTok event name

• What the action means to your business

• The exact condition that triggers it

• Whether it comes from the browser, server, or both

• Data fields that must accompany it

• Available matching information

• Source of the unique event ID

• Consent conditions that apply

Take Purchase as an example. Decide whether it should fire when the store creates an order or only after payment succeeds. For most stores, confirmed payment gives a more dependable view of completed revenue because unpaid and failed orders remain excluded.

Write that rule into the plan, then apply it across your checkout, backend, Pixel, and Events API setup. TikTok supports standard events across both tracking routes, so one shared definition prevents conflicting reports later.

Step 3. Connect the Correct TikTok Data Source

Next, open Events Manager from the advertiser account that will run the campaigns.

Go to Tools, select Events Manager, choose Connect Data Source, and then select Web. Create a new website data connection or open the existing one associated with the correct site.

Before completing the setup, confirm the website URL, Pixel code, advertiser account, and user permissions. This check becomes especially important when several stores or client accounts sit inside one Business Center.

When Pixel and Events API report activity from the same website, connect both to the intended website data connection. Using the wrong destination can send valid events to an unrelated account while leaving the actual campaigns without the data they need.

Step 4. Generate and Secure the Access Token

If you are building a direct Events API integration, generate the access token used to authenticate requests. Partner integrations may manage authentication through their own connection process.

Store the token in a protected server environment, secrets manager, or encrypted configuration file. Only the systems and people responsible for the integration should have access.

Never expose the token in:

• Website source code

• Browser scripts

• Public repositories

• Shared screenshots

• Unprotected logs

A token placed in client-side code can be viewed through browser tools. If one becomes public, replace it promptly and inspect your event activity for unexpected requests.

Document how the credential can be rotated without interrupting event delivery.

Step 5. Capture and Prepare Event Data

With the connection in place, prepare the information TikTok will receive with each event.

Preserve the ttclid from the landing page and carry it through redirects, checkout, and payment steps. Save it with the final order or lead whenever possible.

Next, collect only the customer identifiers your consent setup permits. Normalise email addresses and phone numbers before applying the required hashing method, rather than hashing inconsistent raw values.

The event should also contain the customer’s actual IP address and browser user agent, where permitted. Do not substitute details from your hosting server or backend system.

Finally, generate one stable event ID for each action. Use that same value in the Pixel and server copy so TikTok can recognise them as one conversion.

Step 6. Send Pixel and Server Events

Once the event data is prepared, send the browser and server copies using the same TikTok event name and event ID. That shared identity allows TikTok to recognise overlapping records and count the action once.

Use backend data for the final purchase value, currency, order ID, and product details because your store or payment system holds the confirmed transaction record.

The Purchase event should fire only at the point defined in your tracking plan. For example, send it after payment succeeds or a valid order is confirmed, not when the shopper merely enters checkout or reaches an intermediate payment page.

Before launch, compare both copies of the event and confirm that their names, IDs, values, and order information agree.

Step 7. Test Events in TikTok Events Manager

Before launching campaigns, open the testing tools in Events Manager and complete the actions listed in your tracking plan.

Run a product view, add to cart, checkout, and test purchase. Then verify that:

• Browser and server events reach the intended website data connection

• Event names and timestamps match the actions performed

• Purchase value and currency reflect the test order

• Product IDs follow the connected catalogue format

• Available matching identifiers appear correctly

• Overlapping events carry the same event name and event ID

• Temporary test settings are removed before launch

Review the Diagnostics section as well. An event may arrive successfully while still carrying missing, invalid, or incorrectly formatted information.

After testing, check the deduplication details for matching browser and server records. Events Manager reporting may not update immediately outside the live testing view, so allow for processing time before treating a missing event as a failed request.

Common TikTok Conversion API Problems and Fixes

A received event can still contain incorrect values, weak matching information, or duplicate records. Use the following checks to locate the cause before changing the entire integration.

A lower purchase count in TikTok does not automatically indicate failure. Your store records every order, while Ads Manager reports purchases attributed under TikTok’s selected settings. 

Compare backend purchases, Pixel events, server events, deduplicated records, and attributed purchases to locate the difference.

Make Every TikTok Test More Informed

TikTok Conversion API, officially known as TikTok Events API, can give you a clearer view of what customers do after interacting with your ads. For website campaigns, TikTok recommends using it alongside Pixel so browser and server events can support the same measurement setup.

Useful reporting still depends on the quality of the events you send. Purchase triggers must reflect genuine orders, revenue values need to be accurate, catalogue IDs must match, and duplicate browser and server events need consistent IDs.

Those checks tell you how your campaigns performed. WinningHunter helps with the decisions that come before launch. You can review active TikTok ads, competitor activity, product signals, creative formats, and store data to decide which ideas deserve testing.

Used together, research helps you choose better tests, while accurate conversion data shows which of those tests produced real results.

FAQs

Is TikTok Conversion API the same as Events API?

Yes. Events API is TikTok’s official product name. Advertisers and tracking providers often call it TikTok Conversion API, Conversions API, or TikTok CAPI. These unofficial terms generally refer to the same server connection used to send website, app, CRM, and offline marketing events directly to TikTok.

Do I still need TikTok Pixel when using Events API?

TikTok recommends using Pixel and Events API together for website conversion tracking. Pixel sends activity from the browser, while Events API sends records from a server or connected platform. When both connections report the same customer action, they must share the same event name and event ID so TikTok can remove duplicates.

What is event deduplication in TikTok?

Event deduplication prevents one conversion from being counted twice when Pixel and Events API both report it. TikTok compares the event name and event ID in each copy. When those fields match, TikTok can recognise that both records describe the same purchase, registration, lead, or other customer action.

What should I use as the TikTok event ID?

Use an identifier tied to one specific conversion, such as an order ID, transaction ID, stable checkout completion ID, or server-generated UUID. Pixel and Events API must receive the same value for overlapping events. Any retry of the server request should also reuse that original ID rather than creating another one.

Can I set up the TikTok Events API on Shopify?

Yes. Shopify merchants can connect to TikTok through the supported commerce integration or another compatible tracking provider. Availability and capabilities may vary by market and setup. Before relying on an integration, check which events, customer identifiers, consent signals, revenue fields, and product IDs it sends to TikTok from your store.

Why does TikTok report fewer purchases than Shopify?

Shopify records orders placed across every acquisition source, while TikTok reports purchases attributed to TikTok advertising under the selected attribution settings. Differences may also come from attribution windows, missing match keys, consent choices, event delivery failures, processing delays, or deduplication. Compare received events before assuming the connection is broken.

Does TikTok Events API bypass ad blockers?

Events API is less dependent on browser scripts because the event is sent from a server or connected platform. However, it should not be treated as completely unaffected by ad blockers, browser controls, consent choices, or privacy restrictions. You must still collect and transmit customer data lawfully and follow TikTok’s requirements.

How can I check whether the TikTok Events API is working?

Open TikTok Events Manager and review received server events, parameters, matching information, diagnostics, and deduplication details. Test important actions such as purchases and compare the reported value, currency, product IDs, and event IDs with your store and payment records. Allow for processing time before treating a delayed event as missing.