V1 segmentation stats only through asynchronous analytic query

ling_amobee · 2016-04-07T17:06:10.649Z

According to the Twitter analytic documentation in
https://dev.twitter.com/ads/analytics/metrics-and-segmentation-in-analytics

Segmentation is available only through asynchronous analytics queries due to their significant added complexity.

However, I was able to query segmentation data via synchronous call.
Is there an error in the documentation? or
query segmentation data via synchronous call feature is to be removed?

Thanks

msbukkuri · 2016-04-07T17:39:32.029Z

@ling_amobee This change is only available via the v1 endpoints I believe. Can you provide a twurl here? Would be helpful if you can follow partner inbounds when raising issues.

ling_amobee · 2016-04-08T02:25:51.925Z

Thank you for the prompt response.

Here is synchronous query invoked with HTTP GET Method
/1/stats/accounts/some_account_id?start_time=2016-04-02&end_time=2016-04-03&granularity=DAY&entity=PROMOTED_TWEET&entity_ids=some_promoted_tweet_id&placement=ALL_ON_TWITTER&metric_groups=BILLING&segmentation_type=GENDER

This returns HTTP status 200 with JSON data containing segment information.

After carefully reading both asynchronous and synchronous analytic API call, I’ve realized that I have discovered an unintended parameter: “segmentation_type”. This is not a bug, actually.
We will stop using synchronous query for segment data and
use asynchronous query instead.