Duplicate traffic can consume QPS, create repeated results and make partner reconciliation difficult. The correct response depends on request identity and the commercial agreement.
Define a duplicate
A duplicate rule needs a time window and a stable request signature. Overly broad matching can suppress legitimate repeat intent; overly narrow matching protects nothing.
- Source context
- Query or intent
- IP and user agent
- Time window
Layer the controls
Global duplicate policy can be combined with IP request ceilings, member QPS and maximum-request boundaries.
Keep the outcome explainable
Operators need to distinguish filtered duplicates from upstream errors, empty demand and capacity rejection.
This guide describes Nexus product architecture and general AdTech operating concepts. Exact enforcement and integration behavior depends on the enabled revenue engine and agreed deployment configuration.