You discovered a new feature🥳… This page is a work in progress.
Duplicated Events
Event duplication occurs when:- Page refreshes trigger multiple tracking calls
 - Back-button navigation re-fires events
 - Multiple tracking implementations overlap
 - Single-page applications double-track route changes
 
Idempotency-Key field. When you send the same event with the same , OneView automatically prevents duplicates from being processed, ensuring clean data across all downstream integrations.
How do I implement idempotency keys with OneView?
How do I implement idempotency keys with OneView?
Include an 
Idempotency-Key with each event request using a unique identifier like user_id + event_type + transaction_id to prevent duplicate processing.