Interactive publication
Back to the catalogueAdvertising semanticsCase 07 of 22
Excluded-area leakage
A requested exclusion zone (e.g. exclude a competitor's trade area or a control market) can still receive delivery if the platform's exclusion granularity is coarser than the requested boundary, or exclusion isn't supported and is silently dropped.
Class
Case to account for
Affects
2 conversions
01
Detection
Delivered impressions reported inside the geographic bounds of a declared exclusion zone.
02
Mitigation
01
Pre-subtract exclusions in cell space and submit only the net-positive target rather than rely on platform-side exclusion support
02
Reconcile delivery against the exclusion boundary every flight
03
Affected conversions
H3platform-native IDs
OPENPoint+radiusH3
OPENMore in Advertising semantics
Bidstream truncationCarrier NAT / multi-family IP poolingCorridor boundary oscillationCross-device location stitchingDeclared resolution exceeds input accuracyDestination interestFrequency across overlapping targetsGPS noise / boundary oscillationGPS-derived location accuracyHome location inferenceIP-derived locationLocation confidence scoringLocation interest versus presenceLookback window sensitivityMixed-provenance channel bundlePhysical presencePooled location sources in delivery logsPublisher-declared locationRecent presenceTreatment/control contaminationWork location inference