Handling Duplicate Data
Segment guarantees that 99% of your data won’t have duplicates within an approximately 24 hour look-back window. Warehouses and Data Lakes also have their own secondary deduplication process to ensure you store clean data.
Segment has a special deduplication service that sits behind the
api.segment.com endpoint and attempts to drop 99% of duplicate data. Segment stores at least 24 hours’ worth of event
messageIds, which allows Segment to deduplicate any data that appears with the same
messageId within the stored values.
Segment deduplicates on the event’s
messageId, not on the contents of the event payload. Segment doesn’t have a built-in way to deduplicate data for events that don’t generate
messageIds. The message de-duplication is not scoped to a specific source or a workspace, and applies to all events being received by Segment.
Keep in mind that Segment’s libraries all generate
messageIds for each event payload, with the exception of the Segment HTTP API, which assigns each event a unique
messageId when the message is ingested. You can override these default generated IDs and manually assign a
messageId if necessary.
Duplicate events that are more than 24 hours apart from one another deduplicate in the Warehouse. Segment deduplicates messages going into a Warehouse (including Profiles Sync data) based on the
messageId, which is the
id column in a Segment Warehouse.
Data Lake deduplication
To ensure clean data in your Data Lake, Segment removes duplicate events at the time your Data Lake ingests data. The Data Lake deduplication process dedupes the data the Data Lake syncs within the last 7 days with Segment deduping the data based on the
This page was last modified: 26 Oct 2023
Questions? Problems? Need more info? Contact Segment Support for assistance!