Overview

Follow this guide to learn about the mismatched 'event_id' warning from TikTok. This guide explains the nature of the warning, its potential causes, and outlines any possible actions you may need to take. While the warning might suggest issues related to underscores in the event_id, it is primarily caused by multiple identical events being triggered by the same user in quick succession.

What is an event_id?

The event_id is an element in TikTok's event tracking system that is used for deduplication. It should be a unique string chosen for each event, such as order numbers or transaction IDs. If those are not available, a random number can be used, but it must remain consistent across Pixel SDK Events and Events API Events to ensure effective deduplication. When TikTok receives multiple events with the same event_source_id, event type (like CompletePayment or AddToCart), and event_id, it keeps the first event and discards subsequent ones received within 48 hours. If a duplicate event comes in within 5 minutes, TikTok attempts to merge any new data into the first event.

To learn more about event duplication and event_id from TikTok, follow this guide.

Understanding the Mismatched Event ID Warning

What is the Warning?

• Customers may encounter a warning indicating a mismatch in event_id. This message often suggests that underscores within the event_id may be problematic. However, it is essential to clarify that Elevar's Tiktok integration aligns with TikTok’s documentation, is most likely due to multiple of the same event being trigger.
  • (See Figure 1)

_Figure 1_

Potential Causes of the Warning:

• The most common cause of the mismatched event_id warning is when a user triggers multiple identical events in quick succession. TikTok's system may interpret these instances as duplicates, prompting the warning. Both server-side and browser-side implementations are formatted correctly according to TikTok's specifications. Underscores are included in compliance with the guidelines and should not trigger a warning on their own.

Recommended Actions:

• Regularly review your event logs to identify patterns or trends associated with the warnings. Documenting when and how frequently they occur can aid in diagnosing the issue.
• If you need any further assistance, please reach out to our support team. We can provide tailored guidance and help you troubleshoot any specific concerns related to your integration.