Skip to main content
GET /api/v2/buyer/targeting/geo-metros Compatibility shortcut for geo metro code-name pairs. New workflows should prefer List targeting dimension values with system=nielsen_dma, and Resolve targeting dimension text when the buyer provides a name such as “LA DMA”. The optional system query parameter defaults to nielsen_dma, which is the only supported geo metro system today.

​
Request

curl "https://api.interchange.io/api/v2/buyer/targeting/geo-metros?system=nielsen_dma" \
  -H "Authorization: Bearer $SCOPE3_API_KEY"

​
Parameters

FieldTypeRequiredNotes
systemenumNoOptional; defaults to nielsen_dma

​
Response

{
  "system": "nielsen_dma",
  "locale": "en-US",
  "entries": [
    { "code": "532", "name": "Albany-Schenectady-Troy" },
    { "code": "803", "name": "Los Angeles" }
  ]
}
Send only the numeric string codes in campaign constraints.geo_metros. To display labels for a campaign response, request fields=geo_metro_names on list_campaigns or get_campaign; included labels return in geo_metro_names, excluded labels return in geo_metro_names_exclude, and both are derived from the same local table.

Create campaign

Store metro targeting codes

Resolve targeting dimension text

Resolve names like LA DMA