A growing channel, fragile tracking
TikTok Ads has become a core channel for e-commerce brands targeting 18-35 year-olds. Budgets are rising: +67% in TikTok ad spend in France between 2024 and 2025 (source: aggregated platform data). But TikTok tracking combines two problems: the same weaknesses as Meta (iOS, ad blockers) and quirks that make it even harder to monitor.
The result: only 10% of e-commerce sites have a TikTok pixel correctly configured across the entire purchase funnel. The other 90% are losing data without knowing it.
Where the data goes missing
iOS and App Tracking Transparency
Since iOS 14.5, Apple requires explicit consent for cross-app tracking. On TikTok, where 60 to 70% of traffic is mobile, the impact is large:
- 30 to 40% of iOS traffic declines tracking
- Conversion events from these users are lost on the pixel side
- TikTok Ads can't attribute them to campaigns
Ad blockers
Ad blockers block requests to analytics.tiktok.com. On desktop, the block rate reaches 25 to 35%. On mobile (browser), it's lower (10-15%) but growing.
Reporting delay
This is TikTok's most dangerous quirk: conversion reporting has a 24 to 48-hour delay. When your pixel breaks on a Friday evening, you won't see conversions drop in TikTok Ads Manager until Sunday, at best. Most teams won't notice until Monday morning.
By comparison, Meta Ads reports conversions in near real time (15-30 minute delay). So does Google Ads. TikTok's delay multiplies reaction time by at least 10.
The impact in figures
For an e-commerce site with a €15,000/month TikTok Ads budget:
| Source of loss | % of data lost | Missing conversions/month | Budget spent blind |
|---|---|---|---|
| iOS ATT (tracking declined) | 30-40% | 90-120 | €4,500 to €6,000 |
| Ad blockers | 15-25% | 45-75 | €2,250 to €3,750 |
| Misconfigured pixel (missing events) | 10-30% | 30-90 | €1,500 to €4,500 |
| Cumulative total | 55-75% | 165-285 | €8,250 to €11,250 |
More than half of the TikTok budget runs without usable conversion data. TikTok's bidding algorithm optimizes on a partial, degraded signal.
Errors specific to the TikTok pixel
Beyond the structural losses (iOS, ad blockers), the TikTok pixel has its own implementation weak spots:
1. Page builder fragmentation. Shopify, WooCommerce and PrestaShop each have their own TikTok integration method. The official plugins don't always cover every event (AddToCart, InitiateCheckout, CompletePayment). Missing events don't generate any error.
2. Event naming. TikTok uses different event names from GA4 and Meta. A GA4 purchase maps to a TikTok CompletePayment. A GA4 add_to_cart maps to a TikTok AddToCart (capitalized). Mapping errors are common and silent.
3. Value parameters. The value field must be a number, not a string. The currency field is mandatory. Many plugins send "85.00" (string) instead of 85.00 (number). TikTok accepts both, but processing may differ.
4. Advanced vs standard mode. The TikTok pixel has two modes: standard (basic events) and advanced (automatic matching with email, phone). Advanced mode requires specific configuration that often breaks after plugin updates.
The diagnosis, symptom by symptom
| Symptom in TikTok Ads Manager | Likely cause | Fix |
|---|---|---|
| 0 conversions for 48 h | Dead pixel (JS error, blocking CMP, plugin disabled) | Check the pixel helper, test in a private window |
| Conversions but value = €0 | value parameter missing or wrongly typed | Inspect the dataLayer, fix the GTM mapping |
| Gap > 50% with actual sales | iOS ATT + ad blockers + missing events | Turn on the TikTok Events API (CAPI) |
| Conversions slowly declining | A plugin or CMS update broke an event | Audit every funnel event (ViewContent → AddToCart → Checkout → Payment) |
| Lots of ViewContent, few AddToCart | AddToCart event not configured or broken selector | Check the trigger in GTM or the native plugin |
| No events on mobile Safari | CMP blocking the pixel on iOS | Test with Consent Mode, check the CMP configuration |
The solution: CAPI + Pixel + monitoring
TikTok Events API (CAPI)
The Events API sends conversion data straight from your server. Combined with the client-side pixel, it recovers 13% more events (source: TikTok for Business). It's the same principle as Meta CAPI: server + client redundancy maximizes coverage.
Implementation involves:
- A server connector (native on Shopify, or sGTM for other platforms)
- Deduplication via
event_id(mandatory to avoid duplicates) - User matching (hashed email, hashed phone) to improve attribution
Real-time monitoring
CAPI improves coverage. But it doesn't tell you when the client-side pixel breaks. And TikTok's reporting delay (24-48 h) means you're blind for longer than on Meta or Google.
Korvus monitors the TikTok pixel the same way it monitors Meta and GA4. The pixel_dead alert fires when the TikTok pixel stops firing while paid TikTok traffic is still landing on the site (detected through the ttclid parameter in the URL). The cost is calculated on the active TikTok Ads budget.
With real-time client-side monitoring, detection time drops from 48-72 hours (reporting delay + human reaction time) to under 30 minutes. On a €15,000/month budget, that's the difference between €8 and €1,500 of wasted budget.
The action plan
Week 1: Full pixel audit. Install TikTok Pixel Helper (Chrome extension). Walk through the entire purchase funnel. Check that every event fires: ViewContent, AddToCart, InitiateCheckout, CompletePayment. Note the missing events.
Week 2: Turn on the Events API. On Shopify, the integration is native. On WooCommerce/PrestaShop, go through sGTM or a third-party connector. Set up deduplication by event_id. Test with TikTok's event testing tool.
Week 3: Continuous monitoring. Set up an automatic check that the pixel fires on paid traffic. TikTok's reporting delay makes this monitoring even more important than for Meta or Google: every hour without detection costs more.
Key takeaways
- 90% of e-commerce sites have a TikTok pixel misconfigured on at least one funnel event
- iOS + ad blockers = 30 to 40% structural data loss
- TikTok's reporting delay (24-48 h) multiplies the impact of every tracking incident
- CAPI + Pixel recovers 13% more events: the bare minimum to turn on
- Real-time client-side monitoring is the only way to detect a broken pixel before TikTok's reporting reveals it