Interactive publication
Back to the catalogueAdvertising semanticsCase 19 of 22
Publisher-declared location
Location supplied by the publisher/app (e.g. a self-reported profile city or content geography) rather than device-observed, is far coarser and more gameable than GPS or IP-derived signals, but is often merged into the same location field without a source tag.
Class
Case to account for
Affects
1 conversion
01
Detection
Bidstream/segment record has a location field with no accompanying source/method attribute distinguishing declared from observed.
02
Mitigation
01
Require and preserve a location-source enum (declared vs. observed vs. inferred) on every record
02
Weight or exclude declared-location records separately in geo-targeting logic
03
Affected conversions
PointH3
OPENMore in Advertising semantics
Bidstream truncationCarrier NAT / multi-family IP poolingCorridor boundary oscillationCross-device location stitchingDeclared resolution exceeds input accuracyDestination 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 logsRecent presenceTreatment/control contaminationWork location inference