Skip to content

Fix Appendix A Google Metro Codes link to point at the actual metro/DMA data - #185

Open
sujanchalla0510 wants to merge 1 commit into
InteractiveAdvertisingBureau:developfrom
sujanchalla0510:fix/geo-metro-codes-appendix-link
Open

sujanchalla0510 wants to merge 1 commit into
InteractiveAdvertisingBureau:developfrom
sujanchalla0510:fix/geo-metro-codes-appendix-link

Conversation

@sujanchalla0510

Copy link
Copy Markdown

Fixes #180.

Summary

Geo.metro (§3.2.19) is documented as a "Google metro code; similar to
but not exactly Nielsen DMAs," directing readers to Appendix A for the
codes. Appendix A's "Google Metro Codes" entry links to the Google Ads
geotargets reference
,
whose CSV has no metro or DMA concept at all — its Target Types are
Country, State, City, Postal Code, etc. (confirmed by the issue reporter
by downloading and inspecting the CSV directly).

Investigation

Google's own Authorized Buyers RTB guide
instead references a different file, geo-table.csv, for RTB geo
targeting. I downloaded and inspected that file directly (not just the
issue's excerpt) to verify before proposing a fix:

  • 210 rows have Target_Type = "DMA Region", with Criteria_IDs in
    the 200500–200881 range.
  • Their names are exactly Nielsen DMA codes offset by 200000:
    • 200501 → "New York, NY" (Nielsen DMA 501)
    • 200803 → "Los Angeles, CA" (Nielsen DMA 803)
    • 200602 → "Chicago, IL" (Nielsen DMA 602)
    • 200807 → "San Francisco-Oakland-San Jose, CA" (Nielsen DMA 807)

This matches the spec's own description — "similar to but not exactly
Nielsen DMAs" — exactly.

Fix

Updates the Appendix A link to geo-table.csv, notes which rows to use
(Target_Type = "DMA Region"), and cites the Google guide that
references it, so the link and the field description are finally
consistent.

Related to #153, the original dead-link fix that (unknowingly) swapped
in this still-incorrect replacement link.

…MA data

The `Geo.metro` field (section 3.2.19) is documented as a "Google metro
code; similar to but not exactly Nielsen DMAs," directing readers to
Appendix A for the codes. Appendix A's "Google Metro Codes" entry links
to the Google Ads geotargets reference
(developers.google.com/google-ads/api/reference/data/geotargets), whose
CSV has no metro or DMA concept at all - its Target Types are Country,
State, City, Postal Code, etc.

Google's own Authorized Buyers RTB guide
(developers.google.com/authorized-buyers/rtb/openrtb-guide) instead
references a different file, geo-table.csv, for RTB geo targeting.
Downloaded and inspected that file directly: it contains 210 rows with
Target_Type "DMA Region", Criteria_IDs in the 200500-200881 range, and
names that are exactly Nielsen DMA codes offset by 200000 (e.g. 200501 =
"New York, NY" = Nielsen DMA 501; 200803 = "Los Angeles, CA" = DMA 803;
200602 = "Chicago, IL" = DMA 602; 200807 =
"San Francisco-Oakland-San Jose, CA" = DMA 807) - matching the spec's own
"similar to but not exactly Nielsen DMAs" description precisely.

Updates the Appendix A link to the correct file, noting which rows to
use and citing the Google guide that references it.

Related to InteractiveAdvertisingBureau#180, InteractiveAdvertisingBureau#153 (the original dead link fix that swapped in this
still-incorrect replacement)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant