Geo Targeting - Mapping cities when postal codes is passed in the bid request about openrtb-doubleclick HOT 4 CLOSED

You are correct, the problem is that the canonical name provides the State as the immediate parent of postal codes, thee's no city in-between like one would expect. I supposed that postal codes might not always be exclusive to cities; but then, there's no problem in the sequence of parent geo_criteria_id's, in this case the first parent is 1015214 = Tampa. Unfortunately we don't use that sequence of IDs for building the child-parent relationships because, according to our documentation, "This field is included for legacy support, and the IDs may not be consistent across datasets. Canonical Names is the preferred method of constructing hierarchies." Let me investigate this.

from openrtb-doubleclick.

Upon some extra investigation... the easiest way to fix this is by supporting both parent chains; here's what I'm doing: link the GeoTarget objects by both the canonical names and parent IDs, with separate pointers; provide APIs that allow to lookup the "parent/ancestor by canonical name" or "parent/ancestor by parent ID". The OpenRTB mapper can then try both chains, with priority for the canonical chain because it's the supported/recommended/best-quality data, but if we don't find what you want there then a result based on the parent ID chain is certainly more useful than nothing.

from openrtb-doubleclick.

Implemented initially in this development fork:
opinali@b5eb2c4

from openrtb-doubleclick.

Done 53b9e63

from openrtb-doubleclick.