States (Regions) are Returning as Metros in v2 Endpoints

[saraj345]

We are using the v2 endpoints for targeting and it appears that some states (regions) are returning from the API as cities (metros).

I’ve found the following classified as metros

Alaska
Delaware
Florida
Iowa
Indiana
Louisiana
Nevada
North Carolina
North Dakota
Ohio
Oklahoma
Oregon
Texas
Virginia
Washington
Wyoming

Has anyone else encountered this issue?

[juanshishido]

Hi, @saraj345. Could you please share an example request and response?

When requesting location_type=REGIONS, I get the expected results (example below), so I imagine you’re seeing the METROS results through a different request.

$ twurl -H ads-api.twitter.com "/2/targeting_criteria/locations?location_type=REGIONS&q=alaska"
{
  "data": [
    {
      "name": "Alaska, USA",
      "country_code": "US",
      "location_type": "REGIONS",
      "targeting_value": "07179f4fe0500a32",
      "targeting_type": "LOCATION"
    }
  ],
  "request": {
    "params": {
      "location_type": "REGIONS",
      "q": "alaska"
    }
  },
  "next_cursor": null
}

Thanks!

[saraj345]

Hey Juan,

Thank you for your response. I see what the issue is, one of them is on our side and the other I believe is on yours.

We loop over locations using the following
https://ads-api.twitter.com/2/targeting_criteria/locations

and we noticed that we get multiple locations with name “California, US”

First California Entry

{
“name”: “California, US”,
“country_code”: “US”,
“location_type”: “REGIONS”,
“targeting_value”: “fbd6d2f5a4e4a15e”,
“targeting_type”:“LOCATION”
}

Subsequent California Entry

{
“name”:“California, US”,
“country_code”: “US”,
“location_type”: “CITIES”,
“targeting_value”: “df2277a8b3eccb39”,
“targeting_type”: “LOCATION”
}

When I query the locations endpoint with q=California:
Full URL: https://ads-api.twitter.com/2/targeting_criteria/locations?q=California
We get back
{
“name”: “California, Columbia-Jefferson City MO, MO, USA”,
“country_code”: “US”,
“location_type”: “CITIES”,
“targeting_value”: “df2277a8b3eccb39”,
“targeting_type”: “LOCATION”
},

Is there a reason when getting all locations, California is named twice? Why doesn’t the second response have ‘Columbia-Jefferson City…’ attached to it?

Also, I don’t believe that is an actual location.

Thanks!

[juanshishido]

Thanks, @saraj345! We’ll sync up with the team to get more information as to what could be going on. It’ll likely take some time for us to circle back.

[juanshishido]

Hi, @saraj345. Sorry for the delay here. I’ll look into this this week. You also previously mentioned that we’re returning two values for Los Angeles at the city-level, which I want to post here for visibility:

    {
      "name": "Los Angeles, Los Angeles CA, CA, USA",
      "country_code": "US",
      "location_type": "CITIES",
      "targeting_value": "3b77caf94bfc81fe",
      "targeting_type": "LOCATION"
    },
    {
      "name": "Los Angeles, US",
      "country_code": "US",
      "location_type": "CITIES",
      "targeting_value": "019940ae78c7b3bc",
      "targeting_type": "LOCATION"
    }

Thanks again for bringing this to our attention.

[juanshishido]

Hi, @saraj345. We appreciate you raising this. We’ve resolved the issue. Nowr, “019940ae78c7b3bc” correctly show “Los Angeles, TX, US” as the name. Thanks!