I want to deduplicate a specific event based on one of it's properties

Hi Zeyad Y., Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋

To deduplicate a specific event based on one of its properties in Mixpanel, you need to use the $insert_id property. The $insert_id is a unique identifier for each event that Mixpanel uses for deduplication purposes.Here's how you can achieve this: 1. When tracking your event, include a unique $insert_id property that is based on the specific property you want to use for deduplication.2. Ensure that events with the same combination of event name, time, distinct_id, and $insert_id are considered duplicates by Mixpanel.Here's an example of how your event tracking might look: LBKS{ "event": "Your Event Name", "properties": { "time": 1618716477000, "distinct_id": "user123", "$insert_id": "unique_value_based_on_your_property", "your_property": "property_value", // other properties... } }LBKSIn this example, you would generate the $insert_id based on the property you want to use for deduplication. This way, if you send multiple events with the same $insert_id, Mixpanel will only count it once.It's important to note that: 1. The $insert_id must be ≤ 36 bytes and contain only alphanumeric characters or "-" Mixpanel Event Validation.2. Events with identical values for (event, time, distinct_id, $insert_id) are considered duplicates and only one of them will be surfaced in queries Mixpanel Event Anatomy.3. If you're using Mixpanel's SDKs, they automatically generate $insert_id for you, so you'll need to override this behavior to implement your custom deduplication logic.Remember, this approach will prevent duplicate events from being counted in your analysis, but it won't affect the raw data stored in Mixpanel. The deduplication happens at query time.

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

Let me check the knowledge base for you again. One moment! 📚

Yes, two events with the same $insert_id but different time or distinct_id will be considered unique and not duplicates in Mixpanel.According to the Mixpanel documentation, events are considered duplicates only when they have identical values for all four of these properties: event name, time, distinct_id, and $insert_id. This is clearly stated in the Mixpanel Event Anatomy documentation: "Events with identical values for (event, time, distinct_id, $insert_id) are considered duplicates and only one of them will be surfaced in queries."This means that if any of these four properties differ, including the time or distinct_id, the events will be treated as unique events in Mixpanel's system.It's important to note that the $insert_id alone is not sufficient for deduplication. It works in combination with the other three properties to ensure uniqueness. This design allows for flexibility in tracking events while still providing a mechanism to prevent accidental duplicates when retrying event submissions or handling network failures.

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.