---
title: "Advanced Deduplication: Event ID"
description: "All events can now be deduplicated using the event ID parameter You can now prevent duplicate events by using the event ID parameter. This ID helps ensure that the same event isn’t tracked multiple times. <section class=\"warning box\" <strong Advanced Configuration</strong . This feature is intended for advanced users. If your tracking setup does not send custom EventIDs, Tracklution automatically generates them and manages deduplication on your behalf. Only configure custom E…"
slug: "advanced-deduplication-event-id"
category_slug: "tracking-guides"
category_name: "Tracking Guides"
order: 3000000046
published_at: "2025-11-07T11:41:09+00:00"
updated_at: "2026-04-14T12:00:04+00:00"
language_code: "en-US"
tags: []
---

## All events can now be deduplicated using the event ID parameter

You can now prevent duplicate events by using the **event ID** parameter. This ID helps ensure that the same event isn’t tracked multiple times.
<section class="warning-box"><strong>Advanced Configuration</strong>. This feature is intended for advanced users. If your tracking setup does not send custom EventIDs, Tracklution automatically generates them and manages deduplication on your behalf. Only configure custom EventIDs if you fully understand the implications and behavior of your tracking setup.</section>
### Requirements

Your event ID must be **at least 4 characters long**, but it’s best to make it longer and **truly unique**, such as using a generated value or order number. This reduces the chance of accidental deduplication between unrelated events.

### Deduplication Period: 30 Days

When checking for duplicates, the system looks back **30 days**. If another event with the same event ID is found within that time frame, it won’t be tracked again.

### Event-Specific Deduplication

Deduplication works **per event name**. In other words, the same event ID can exist across different event names without conflict. Because of this, you can in practice even use event ID similarly to a **session identifier**, it then limits each event name as a unique event per session.

### Event ID Takes Priority

The event ID is the **first thing the system checks** for duplicates. This means that even if other identifiers (like email, cookies, or fingerprints) differ, events with the same event ID will still be treated as duplicates.
<section class="warning-box"><strong>Important</strong>:&nbsp;If your event ID isn’t dynamic or accidentally stays the same for all events, the system will deduplicate everything, allowing&nbsp;only one event of the same type&nbsp;to be tracked within 30 days.</section>
### Code Example

    tlq('track', 'Purchase', {value: 25.5, currency: 'EUR', eventId: 'order_2239'});Supported case use: eventid, event_id, eventId;

### Webhook

Yes, event ID can be used for your webhooks as well. Include the event ID in your server’s URL*​*.

- Your specific URL is found under the Webhook tab in your Tracklution container.
- [Sending data to Tracklution with webhooks](https://support.tracklution.com/kb/article/15/send-events-from-any-platform-with-a-webhook)