{"id":3439,"date":"2026-05-20T14:14:00","date_gmt":"2026-05-20T14:14:00","guid":{"rendered":"https:\/\/hyros.com\/updates\/?p=3439"},"modified":"2026-08-03T05:10:10","modified_gmt":"2026-08-03T05:10:10","slug":"tiktok-events-api","status":"publish","type":"post","link":"https:\/\/hyros.com\/updates\/tiktok-events-api\/","title":{"rendered":"TikTok Events API: Why Ecom Brands Need It"},"content":{"rendered":"\n

Nobody talks about this enough: if you are running TikTok ads with only the Pixel, you are flying blind on about a third of your actual conversions. That is not me being dramatic. That is what happens when 31.5% of desktop users run ad blockers and most iPhone users have iOS privacy restrictions active. The algorithm is learning from a broken dataset and making targeting decisions accordingly. The TikTok Events API is TikTok’s server-side tracking interface that sends conversion events — purchases, add-to-carts, form submissions, and other actions — directly from an advertiser’s server to TikTok, without relying on the browser-based TikTok Pixel alone. For ecommerce brands running TikTok ads at any meaningful scale, the Events API is not optional. It is the mechanism that gives TikTok’s optimization algorithm complete purchase data, which affects ad delivery quality and cost per acquisition.<\/p>\n\n\n\n

TL;DR<\/h2>\n

TikTok’s Events API sends your conversion data server-to-server, bypassing the browser entirely. This matters because roughly 31.5% of web visitors run ad blockers that prevent the TikTok Pixel from firing (Statista, 2024), and iOS App Tracking Transparency caused roughly 96% of US iPhone users to initially opt out of cross-app tracking after iOS 14.5 launched in April 2021<\/a> (Flurry Analytics). Current opt-in rates sit at approximately 35-37% (Adjust, Q2 2025), but the majority of iPhone users still block the tracking signals TikTok needs. TikTok recommends running both the Pixel and Events API simultaneously. The exact recovery lift depends on how much browser-side signal your audience is already blocking — the more ad-blocker and ATT opt-out exposure you have, the more the Events API fills in. Three setup paths exist: manual API integration, Shopify’s native TikTok integration, and managed platforms like Hyros that handle server-side tracking across all channels. If you are spending on TikTok ads without the Events API, you are optimizing on incomplete data.<\/p><\/div>\n\n\n\n

What is the TikTok Events API?<\/h2>\n\n\n\n

The TikTok Events API is a server-to-server (S2S) integration that lets you send web conversion events directly from your backend infrastructure to TikTok’s reporting servers. When a customer completes a purchase on your site, your server sends that event data — including the order value, product information, and hashed customer identifiers — to TikTok via an HTTPS POST request. TikTok then matches that event against its user database to determine whether the converting customer previously interacted with one of your ads.<\/p>\n\n\n\n

This is fundamentally different from how the TikTok Pixel works. The Pixel is a JavaScript snippet that runs in the customer’s browser. When the browser loads your thank-you page, the Pixel fires and sends the conversion event to TikTok. The problem is that the browser is an unreliable environment for tracking. Ad blockers prevent the Pixel from loading. Safari’s Intelligent Tracking Prevention caps cookie lifespans. And iOS App Tracking Transparency limits the data TikTok can collect on iPhones.<\/p>\n\n\n\n

The Events API sidesteps all of that. Your server talks directly to TikTok’s server. No browser, no ad blocker, no cookie to expire. The conversion data gets through regardless of what is happening on the client side.<\/p>\n\n\n\n

TikTok reached approximately 1.9 billion monthly active users globally by early 2026 (DemandSage), with around 136 million in the United States. TikTok’s global ad revenue hit approximately $33 billion in 2025, a 40% increase year-over-year. That is a massive advertising surface. And every dollar spent on it is only as good as the data feeding TikTok’s optimization algorithm. Bad data in, bad targeting out.<\/p>\n\n\n\n

Why do ecommerce brands need server-side TikTok tracking?<\/h2>\n\n\n\n
\"Pop-art<\/figure>\n\n\n\n

Three forces have degraded browser-based tracking to the point where Pixel-only measurement is actively misleading.<\/p>\n\n\n\n

iOS App Tracking Transparency destroyed mobile signal.<\/strong> When Apple launched ATT in April 2021, roughly 96% of US iPhone users initially opted out of cross-app tracking (Flurry Analytics, 2021, measuring across over 1 million mobile apps). Opt-in rates have since recovered to approximately 35-37% (Adjust, Q2 2025), but the damage to browser-based tracking was structural. The TikTok Pixel cannot reliably identify iPhone users who have opted out, which means a large percentage of mobile conversions are invisible to Pixel-only tracking. Given that most TikTok usage happens on mobile, this is not a minor gap — it is a fundamental measurement failure.<\/p>\n\n\n\n

Ad blockers erase desktop conversions.<\/strong> Approximately 31.5% of web visitors use ad-blocking extensions (Statista, 2024). These tools prevent the TikTok Pixel’s JavaScript from loading entirely. A customer can click your TikTok ad, browse your store, buy a $200 product, and generate zero conversion data in TikTok Ads Manager. The sale happened. The money hit your Stripe account. But TikTok has no idea, which means it cannot learn from that successful conversion to find more customers like that one.<\/p>\n\n\n\n

Cookie restrictions shrink the window.<\/strong> Safari’s Intelligent Tracking Prevention limits first-party cookies set via JavaScript to 7 days (down to 24 hours in some configurations). Firefox has similar restrictions. A customer who clicks your ad, leaves, and comes back 10 days later to purchase will not have that conversion attributed to TikTok. The cookie expired before the sale happened.<\/p>\n\n\n\n

The combined effect is that Pixel-only tracking on TikTok captures a shrinking fraction of actual conversions. And that is not just a reporting problem. TikTok’s ad algorithm uses conversion events to learn which users, placements, and creatives generate purchases. When it receives incomplete conversion data, it optimizes poorly. It undervalues your best-performing ads and overspends on the worst ones; not because the algorithm is broken, but because the input data is broken.<\/p>\n\n\n\n

According to LayerFive<\/a>, nearly half of marketing spend is wasted due to poor attribution. Server-side tracking exists specifically to close the gap between what actually happens and what your ad platform can see.<\/p>\n\n\n\n

TikTok Events API vs TikTok Pixel: how do they compare?<\/h2>\n\n\n\n
\"Two<\/figure>\n\n\n\n
Feature<\/th>TikTok Pixel<\/th>TikTok Events API<\/th><\/tr><\/thead>
Data source<\/td>Browser (client-side JavaScript)<\/td>Your server (server-to-server HTTPS POST)<\/td><\/tr>
Cookie dependence<\/td>Yes — relies on browser cookies for identity matching<\/td>No — uses hashed PII (email, phone) sent from your server<\/td><\/tr>
iOS ATT resilience<\/td>Low — loses signal on opted-out iPhones<\/td>High — server-side events bypass ATT restrictions<\/td><\/tr>
Ad blocker resistance<\/td>None — blocked JavaScript means zero data<\/td>Full — ad blockers cannot intercept server-to-server requests<\/td><\/tr>
Event deduplication<\/td>Not applicable (single source)<\/td>Required — must match event_id with Pixel events to prevent double-counting<\/td><\/tr>
Setup complexity<\/td>Low — paste JavaScript snippet on your site<\/td>Medium to High — requires API integration, access token, and hashed PII handling<\/td><\/tr>
Data quality<\/td>Depends on browser environment; degrades with privacy tools<\/td>Consistent — you control what data gets sent and how it is formatted<\/td><\/tr>
Offline event support<\/td>No<\/td>Yes — can send CRM and offline events<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The right answer is not one or the other. TikTok recommends running both simultaneously, which they call a “dual setup.” The Pixel captures events when it can, and the Events API captures everything the Pixel misses. Event deduplication (using matching event_id values) prevents double-counting when both systems report the same conversion. The exact performance lift depends on how much your baseline Pixel coverage is being lost to ad blockers, ATT opt-outs, and ITP — typically the more browser-restrictive your audience, the larger the recovery.<\/p>\n\n\n\n

How does the TikTok Events API compare to Meta CAPI?<\/h2>\n\n\n\n
\"Two<\/figure>\n\n\n\n

If you have already set up Meta’s Conversions API, the TikTok Events API will feel familiar. They solve the same problem and use similar mechanics. But there are differences worth understanding.<\/p>\n\n\n\n

Architecture.<\/strong> Both use HTTPS POST requests to send events server-to-server. Both accept hashed PII (email address, phone number) for identity matching. Both require event deduplication with the browser pixel via an event_id field. The implementation patterns are nearly identical at the infrastructure level.<\/p>\n\n\n\n

Attribution windows.<\/strong> TikTok defaults to a 7-day click, 1-day view attribution window — the same default as Meta’s current window. TikTok also offers 1-day and 14-day click options, configurable in the Attribution Manager. Meta’s longest available click window is 7 days (after removing 28-day click in early 2021). TikTok still offers a 14-day click option, which gives advertisers slightly more flexibility.<\/p>\n\n\n\n

Maturity.<\/strong> Meta launched CAPI in 2020 and has a larger ecosystem of third-party integrations, platform-native setups (Shopify, WooCommerce, WordPress plugins), and documentation. TikTok’s Events API launched later and has fewer turnkey integrations, though Shopify’s native TikTok sales channel now supports server-side event forwarding without custom code. For a detailed walkthrough of Meta’s server-side setup, see our guide on Facebook CAPI setup<\/a>.<\/p>\n\n\n\n

Event types.<\/strong> Both support standard ecommerce events (ViewContent, AddToCart, InitiateCheckout, CompletePayment\/Purchase). TikTok uses slightly different event naming conventions than Meta, but the event structure is conceptually identical. Both require SHA-256 hashing for PII fields before transmission.<\/p>\n\n\n\n

Scale.<\/strong> Meta’s ad platform reaches a larger total advertiser base, but TikTok’s ad revenue grew 40% year-over-year to approximately $33 billion in 2025. For DTC ecommerce brands, TikTok is often the second or third largest ad channel after Meta and Google, which means the Events API is not a nice-to-have — it is a requirement for accurate cross-channel measurement. Google has its own server-side solution called Enhanced Conversions<\/a>, which uses a similar hashed-PII approach. If you are running ads across all three platforms, you need server-side tracking on each one.<\/p>\n\n\n\n

For a broader view of how server-side tracking works across all platforms, see our guide on server-side tracking<\/a>.<\/p>\n\n\n\n

How to set up the TikTok Events API<\/h2>\n\n\n\n
\"Bars<\/figure>\n\n\n\n

Setting up the Events API involves five steps. The specifics vary depending on your platform, but the structure is the same regardless of implementation method.<\/p>\n\n\n\n

Step 1: Create a Pixel and enable Events API in TikTok Ads Manager<\/h3>\n\n\n\n

Log into TikTok Ads Manager and go to Assets, then Events, then Web Events. If you do not already have a TikTok Pixel, create one. Once the Pixel exists, go to its settings and enable the Events API toggle. This activates the server-side endpoint that will receive your events.<\/p>\n\n\n\n

Step 2: Generate an access token<\/h3>\n\n\n\n

In TikTok Ads Manager, go to Settings, then select your Pixel, and find the Events API section. Click “Generate Access Token.” This token authenticates your server’s API requests. Store it securely — treat it like a password. If it is compromised, anyone can send events to your TikTok account.<\/p>\n\n\n\n

Step 3: Choose your integration path<\/h3>\n\n\n\n

There are three main options.<\/p>\n\n\n\n

Manual API integration.<\/strong> Your development team writes code that sends HTTPS POST requests to TikTok’s event reporting endpoint. Each request includes the Pixel ID, access token, event name (such as CompletePayment or AddToCart), event timestamp, event value, and hashed customer identifiers (email and phone number hashed with SHA-256). This gives you maximum control but requires engineering resources.<\/p>\n\n\n\n

Shopify native integration.<\/strong> If you run Shopify, the TikTok sales channel supports server-side event forwarding natively. In your Shopify admin, go to the TikTok sales channel settings and set Data Sharing to “Maximum.” This enables the Pixel, Events API, and Advanced Matching without writing any code. Shopify pulls order data directly from its backend and sends it server-side. For brands on Shopify, this is the fastest path; our guide on Shopify attribution<\/a> covers the broader tracking picture.<\/p>\n\n\n\n

Managed platform (Hyros).<\/strong> A platform like Hyros handles TikTok Events API integration as part of its server-side tracking layer. You connect your TikTok account once, and Hyros sends conversion events to TikTok automatically alongside its independent attribution tracking. No API code to maintain, no access tokens to manage, no deduplication logic to debug. Hyros also sends corrected conversion data back to TikTok, which means TikTok’s algorithm receives more complete signals than it would from Events API alone.<\/p>\n\n\n\n

Step 4: Send test events and verify in the Events Manager diagnostics tab<\/h3>\n\n\n\n

Before going live, use TikTok’s Test Events tool in the Events Manager. Send a few test events from your server and confirm they appear in the diagnostics tab. Check that the event names, values, and parameters are correct. Verify that hashed PII fields are being sent properly. TikTok will show you a match quality indicator — aim for the highest possible match rate.<\/p>\n\n\n\n

Step 5: Implement event_id deduplication between Pixel and Events API<\/h3>\n\n\n\n

This step is critical if you are running both the Pixel and Events API simultaneously (which you should be). Every event your Pixel fires and every event your server sends must include the same unique event_id value for the same conversion. TikTok uses this ID to deduplicate — if it receives a Purchase event from the Pixel and a CompletePayment event from the Events API with the same event_id, it counts it once instead of twice.<\/p>\n\n\n\n

Skipping deduplication means double-counted conversions, inflated ROAS, and bad optimization signals. It is one of the most common setup mistakes and one of the easiest to prevent.<\/p>\n\n\n\n

What are the most common TikTok Events API mistakes?<\/h2>\n\n\n\n

Missing event deduplication.<\/strong> Without matching event_id values between the Pixel and Events API, TikTok counts conversions twice. Your reported ROAS doubles overnight, you think your campaigns are performing brilliantly, you increase budget, and then your actual bank account tells a different story. Always implement event_id matching.<\/p>\n\n\n\n

Wrong event names.<\/strong> TikTok uses specific event names: CompletePayment (not Purchase), AddToCart, ViewContent, InitiateCheckout, PlaceAnOrder, CompleteRegistration, ClickButton, Contact, Download, SubmitForm, Subscribe. Sending a “Purchase” event instead of “CompletePayment” means TikTok does not recognize the event type and cannot use it for optimization. Check the TikTok standard events documentation<\/a> before implementing.<\/p>\n\n\n\n

Unhashed PII.<\/strong> TikTok requires email addresses and phone numbers to be hashed with SHA-256 before transmission. Sending raw email addresses violates both TikTok’s Terms of Service and privacy regulations. Most server-side implementations handle this automatically, but if you are building a manual integration, double-check that hashing happens before the API call, not after.<\/p>\n\n\n\n

Low match rate.<\/strong> If you only send hashed email and nothing else, your match rate will be limited to customers who signed up for TikTok with that same email. Sending additional matching parameters — phone number, external ID, IP address, user agent — increases the probability that TikTok can connect your conversion event to the user who saw the ad. More parameters equals better matching.<\/p>\n\n\n\n

Not testing before going live.<\/strong> TikTok’s Test Events tool exists for a reason. Send test events, verify they appear, confirm the data is formatted correctly, and check the match quality indicator before sending real production traffic. Debugging a broken Events API implementation with live ad spend burning is an expensive way to learn.<\/p>\n\n\n\n

Ignoring event timing.<\/strong> Events API events should be sent as close to the actual conversion time as possible. Batching hundreds of events and sending them hours later degrades TikTok’s ability to attribute conversions to the correct ad interaction. Real-time or near-real-time event transmission is the standard.<\/p>\n\n\n\n

How does Hyros handle TikTok server-side tracking?<\/h2>\n\n\n\n

Hyros connects to TikTok’s Events API as part of its broader cross-channel attribution system. But it does something fundamentally different from a standard Events API integration.<\/p>\n\n\n\n

A standard Events API setup sends your conversion data to TikTok so TikTok can attribute it within its own system. The data goes in one direction: from you to TikTok. TikTok then decides, using its own attribution model and its own windows, which ads get credit.<\/p>\n\n\n\n

Hyros tracks conversions independently using first-party identifiers — email addresses, phone numbers — matched through deterministic server-side tracking. When a user clicks a TikTok ad, Hyros captures that click. When they convert — whether that is 3 days later, 30 days later, or 90 days later — Hyros matches the conversion to the original click. It does not rely on TikTok’s attribution window. It does not rely on cookies. It does not rely on the Pixel.<\/p>\n\n\n\n

Then Hyros sends the corrected conversion data back to TikTok through the Events API. This means TikTok’s optimization algorithm receives a more complete picture of which ads are actually driving revenue. The algorithm can then optimize more accurately, targeting users similar to your actual buyers instead of only the buyers it could see through its own limited tracking.<\/p>\n\n\n\n

An independent analysis by CheckThat.ai<\/a> that aggregated 600+ Trustpilot reviews found that Hyros users consistently report tracking 29-33% more conversions than native platform reporting shows. For a brand spending $50,000 per month on TikTok ads, that gap represents $15,000 or more in invisible conversions — sales that are happening but that TikTok cannot see, learn from, or optimize toward.<\/p>\n\n\n\n

According to a published Hyros case study, Dan Henry became 300% more profitable within 72 hours of implementing Hyros and scaled from $20,000 to $300,000 per month in ad spend. That kind of scale requires accurate data across every channel, TikTok included.<\/p>\n\n\n\n

Hyros pricing starts at $230\/month on an annual plan or $379\/month on a monthly plan for the Business pricing tier. The platform includes a 90-day guarantee. For brands spending enough on TikTok ads that a 15-30% tracking gap represents thousands of dollars in invisible conversions per month, the math on attribution tooling tends to be straightforward.<\/p>\n\n\n\n

For a full overview of Hyros and what it does, see our guide on what is Hyros<\/a>.<\/p>\n\n\n\n

FAQ<\/h2>\n\n\n\n

What is the TikTok Events API?<\/h3>\n\n\n\n

The TikTok Events API is a server-to-server integration that sends conversion events (purchases, add-to-carts, sign-ups) directly from your server to TikTok’s servers. Unlike the TikTok Pixel, which runs in the customer’s browser and is vulnerable to ad blockers and iOS privacy restrictions, the Events API transmits data from your backend infrastructure, bypassing client-side limitations entirely. TikTok uses this data for ad attribution, campaign optimization, and audience targeting.<\/p>\n\n\n\n

Is the TikTok Events API the same as Meta CAPI?<\/h3>\n\n\n\n

They solve the same problem and use similar technology (HTTPS POST requests with hashed PII for identity matching), but they are separate systems maintained by different companies. You need to implement each one independently. The event naming conventions differ — TikTok uses “CompletePayment” where Meta uses “Purchase,” for example. If you have already built a Meta CAPI integration, you can reuse much of the infrastructure (hashing logic, server-side event collection) and adapt the API calls for TikTok’s endpoint.<\/p>\n\n\n\n

Do I still need the TikTok Pixel if I use the Events API?<\/h3>\n\n\n\n

Yes. TikTok recommends running both simultaneously. The Pixel captures events in real time from the browser, which TikTok uses for features like dynamic product ads and audience building. The Events API supplements this by capturing conversions the Pixel misses. Deduplication via matching event_id values prevents double-counting when both systems see the same conversion.<\/p>\n\n\n\n

Can I set up TikTok Events API on Shopify without writing code?<\/h3>\n\n\n\n

Yes. Shopify’s native TikTok sales channel supports server-side event forwarding. In your Shopify admin, install the TikTok sales channel, connect your TikTok Ads Manager account, and set the Data Sharing level to “Maximum.” This enables the Pixel, Events API, and Advanced Matching automatically. Shopify pulls confirmed order data from its backend and sends it server-side to TikTok. No custom API code required. For stores not on Shopify, you will need either a developer, a tag management solution like Google Tag Manager Server-Side, or a managed platform like Hyros.<\/p>\n\n\n\n

What is TikTok’s default attribution window?<\/h3>\n\n\n\n

TikTok’s default attribution window is 7-day click, 1-day view. This means TikTok will credit a conversion to an ad if the user clicked within 7 days or viewed within 1 day of the conversion event. TikTok also offers 1-day click and 14-day click windows, configurable in the Attribution Manager. This is the same default as Meta’s current window (7-day click, 1-day view) but shorter than Google Ads’ 30-day click default window.<\/p>\n\n\n\n

How does the Events API improve TikTok ad optimization?<\/h3>\n\n\n\n

TikTok’s ad algorithm learns from conversion events. It analyzes which users converted, what ads they saw, what placements performed, and what creatives drove action. When the Pixel misses conversions due to ad blockers, iOS privacy, or cookie expiration, the algorithm has incomplete data and makes worse optimization decisions. The Events API fills those gaps by providing server-verified conversion data that the Pixel could not capture. More conversion data means the algorithm can identify better audiences, bid more accurately, and distribute budget toward the ads that actually drive revenue.<\/p>\n\n\n\n

What data do I need to send with Events API events?<\/h3>\n\n\n\n

At minimum, each event requires: the Pixel ID, your access token, the event name (such as CompletePayment), the event timestamp, and at least one hashed customer identifier (email or phone number, hashed with SHA-256). For ecommerce events, you should also include the event value (revenue), currency code, content type, content ID (product SKU), and quantity. The more data you send, the higher your match rate. Include hashed email, hashed phone number, IP address, user agent, and an event_id for deduplication.<\/p>\n\n\n\n

How quickly should Events API events be sent after a conversion?<\/h3>\n\n\n\n

Send events as close to real-time as possible. TikTok’s attribution system matches conversion events to ad interactions based on timing. If you batch events and send them hours or days after the conversion, the attribution accuracy degrades. Most well-implemented setups send events within seconds of the conversion occurring — triggered by a webhook from your payment processor or ecommerce platform. If real-time transmission is not possible, aim for a maximum delay of a few hours.<\/p>\n\n\n\n

Standalone Summary<\/h2>\n

The TikTok Events API is a server-to-server integration that sends conversion events directly from an advertiser’s server to TikTok, bypassing the browser-based Pixel and its vulnerabilities to ad blockers (31.5% of web visitors), iOS App Tracking Transparency (roughly 96% initial US opt-out after iOS 14.5, now approximately 35-37% opt-in), and cookie restrictions. TikTok reached approximately 1.9 billion monthly active users globally by early 2026, with $33 billion in ad revenue in 2025. TikTok recommends running the Events API alongside the Pixel simultaneously. The Pixel captures browser-side events in real time; the Events API captures what the Pixel misses due to ad blockers, ATT opt-outs, and cookie restrictions. Event deduplication via matching event_id values prevents double-counting. Setup options include manual API integration, Shopify’s native TikTok sales channel, or managed platforms like Hyros that handle server-side tracking across all channels. TikTok’s default attribution window is 7-day click, 1-day view. Independent attribution layers sit above the platform layer entirely; CheckThat.ai’s independent analysis found Hyros recovers 29-33% more conversions versus platform-side measurement alone.<\/p>\n

\n

See how Hyros tracks every TikTok conversion your Pixel misses. Book a demo<\/a><\/strong><\/p>\n

<\/div>\n\n\n\n