Region segmentation breakdown available in v1?

[emilyb]

Is region still available as a segmentation type in version 1? I’m receiving 400 errors. All other segmentation breakdowns are working for me.

This is a sample call I’m making:

https://ads-api.twitter.com/1/stats/jobs/accounts/1hhzhz?placement=ALL_ON_TWITTER&metric_groups=BILLING%2CENGAGEMENT%2CMEDIA&country=US&start_time=2016-10-01T07%3A00%3A00Z&entity=CAMPAIGN&end_time=2016-10-05T07%3A00%3A00Z&granularity=DAY&entity_ids=5wxdq%2C5vv1z%2C5p3bi%2C63731%2C63732%2C63733%2C63734%2C63735%2C63736%2C63737%2C63738%2C60p93%2C60p94%2C60p95%2C60p96%2C60p4n%2C60p42%2C60p3m%2C60p3f&segmentation_type=REGIONS

[juanshishido]

@emilyb: Yes, the segmentation_type=REGIONS is still supported. Please note that the country param is required for this segmentation type. While you’ve included it in your request, it must be specified as a GeoId. To find this ID, use the GET targeting_criteria/locations endpoint. For US, the value is 96683cc9126741d1.

Your params would be: segmentation_type=REGIONS&country=96683cc9126741d1.

Hope this helps!