Interactive publication
Back to the catalogueAdvertising semanticsCase 05 of 22
Declared resolution exceeds input accuracy
A platform declares support for a cell resolution finer than its location input can carry: IP geolocation's published best-case accuracy radius (~5 km) exceeds the equal-area radius of an R6 cell (~3.4 km), so an R6-or-finer declaration on IP-derived geography is a claim the input cannot honor. R5 (~9 km) is the finest defensible declaration from IP alone.
Class
Case to account for
Affects
2 conversions
01
Detection
Compare the declared minimum resolution's equal-area radius against the location source's published accuracy radius; declaration is unsupported when the cell radius is smaller.
02
Mitigation
01
Cap declared resolution by input provenance, not by platform capability — the ad server can accept an R6 list it cannot resolve
02
Carry a location-provenance field (physical, address_matched, platform_graph, ip_inferred) beside the declared resolution
03
Treat undocumented provenance as ip_inferred
03
Affected conversions
IP lookupH3 (probabilistic crosswalk)
OPENH3platform-native IDs
OPENChapter
IP Lookup To H3More in Advertising semantics
Bidstream truncationCarrier NAT / multi-family IP poolingCorridor boundary oscillationCross-device location stitchingDestination interestExcluded-area leakageFrequency 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