TikTok Conversion Discrepancy: Why Ads Manager, Events API, and Your Tracker Show Different Numbers

What Counts as a Discrepancy

Marketers typically compare three data sources:

1. TikTok Ads Manager - the platform's own reporting UI.
2. Events API logs - raw server-side events you send to TikTok.
3. Third-party tracker (Keitaro, Voluum, RedTrack) - records postbacks and click IDs independently.

Each system applies its own filters before counting a conversion. Understanding those filters is the key to reconciling the numbers. For where conversions get dropped inside a tracker, see the Keitaro postback troubleshooting checklist.

Root Cause 1: Attribution Window Mismatch

TikTok's attribution window determines how long after a click or view a conversion is credited to an ad. The default settings are:

• Click-through window: 7 days
• View-through window: 1 day

If your tracker records conversions for 30 days but TikTok only credits 7, every conversion on days 8-30 shows up in the tracker but never reaches Ads Manager. This is the most common source of a TikTok conversion discrepancy.

Check your attribution settings in Ads Manager under Assets > Attribution. Compare the configured windows against your tracker's attribution logic. More detail on window mechanics is in attribution window concepts.

Root Cause 2: Deduplication Dropping Events

TikTok's deduplication logic matches events from the browser Pixel and the server-side Events API using the event_id field. If the two fire paths produce different event_id values for the same user action, TikTok treats them as separate events and may count the conversion twice. Conversely, if a stale event_id collides with a new event, a legitimate conversion gets dropped.

Pixel event:      event_id = "abc-123"
Events API call:  event_id = "abc-999"   <-- mismatch, no dedup

To verify, pull your Events API logs and confirm that every server event carries the same event_id as its browser counterpart. Official guidance: About Event Deduplication.

Root Cause 3: Event-Matching Failures

The Events API relies on user information parameters to match a conversion back to an ad interaction. Sending events without click_id (ttclid) or with poorly hashed email/phone fields drops the match rate. Unmatched events still appear in your raw logs but never surface in Ads Manager reporting.

Audit your match rate in Events Manager > Data Sources > [your source] > Event Match Quality. Aim for a match rate above 60%. If it is lower, add click_id passthrough from your tracker's postback. See TikTok Pixel setup guide for the integration path.

Root Cause 4: Postback Delays and Timezone Gaps

TikTok's reporting pipeline is not instantaneous. Conversions can take 24-72 hours to appear in Ads Manager, especially during high-traffic periods. Your tracker records the postback the moment it fires. Comparing numbers same-day will always show the tracker leading.

Additionally, Ads Manager uses the timezone set at the ad-account level, while most trackers default to UTC. A 3-hour timezone offset can shift conversions between calendar days, making daily comparisons look mismatched even when totals eventually align.

Root Cause 5: Tracker-Side Filtering and Redirect Loss

Keitaro and similar trackers can reject clicks or conversions based on IP blacklists, bot signatures, or missing parameters. When a conversion is filtered on the tracker side, no postback fires, and the event never reaches your reporting. Meanwhile, TikTok still counts it.

Review your tracker's log for rejected events. In Keitaro, check Streams > Filters and the trash log. Tracking down conversions dropped by filters is covered by the Keitaro postback troubleshooting checklist.

Diagnostic Workflow

Follow this sequence to locate the leak:

1. Export raw Events API logs for a 7-day period from Events Manager.
2. Pull the same period from Ads Manager reporting (use UTC dates).
3. Grab tracker conversions for identical date bounds.
4. Compare Events API count vs. Ads Manager count. A gap here points to deduplication or event-matching issues (Root Causes 2-3).
5. Contrast Ads Manager count vs. tracker count. A gap here points to attribution windows or tracker filtering (Root Causes 1, 5).
6. If all three differ, check timezone alignment and the 72-hour delay before deeper investigation (Root Cause 4).

Events API raw:    1 042 conversions
Ads Manager:         861 conversions   <-- dedup / match loss
Tracker (Keitaro):   790 conversions   <-- filter / window loss

For teams running multiple ad accounts, MOST automates this reconciliation by pulling Events API logs and tracker postbacks into a single pipeline, flagging mismatches in real time. If you only need to activate a Pixel manually on a landing page without a full tracker stack, Pixel Activator handles the browser-side setup.

Preventing Future Discrepancies

• Set your tracker's attribution window to match TikTok's configured window exactly.
• Generate a single event_id per user action at the point of conversion and pass it to both Pixel and Events API.
• Schedule weekly match-quality audits in Events Manager.
• Wait at least 72 hours before comparing daily conversion totals.
• Normalize all exports to UTC before building reconciliation reports.

Sources