Mismatch of segmented stats and total stats


#1

Hey,

We noted there’s a slight difference between the stats of 17/12/2016 for campaign 6ni02 of account 18ce54dow44 when querying by platform and when querying in total.

The following request for the stats of the above campaign and date:

https://ads-api.twitter.com/1/stats/jobs/accounts/18ce54dow44/?with_deleted=true&placement=ALL_ON_TWITTER&end_time=2016-12-18T00%3A00%3A00%2B0900&metric_groups=ENGAGEMENT%2CBILLING%2CMOBILE_CONVERSION&granularity=DAY&entity_ids=6ni02&start_time=2016-12-17T00%3A00%3A00%2B0900&entity=CAMPAIGN

And this request for stats by platform for the same campaign and date:

https://ads-api.twitter.com/1/stats/jobs/accounts/18ce54dow44/?placement=ALL_ON_TWITTER&metric_groups=ENGAGEMENT%2CBILLING%2CMOBILE_CONVERSION&start_time=2016-12-17T00%3A00%3A00%2B0900&entity=CAMPAIGN&with_deleted=true&end_time=2016-12-18T00%3A00%3A00%2B0900&granularity=DAY&entity_ids=6ni02&segmentation_type=PLATFORMS

Returned a different total billed_charge_local_micro.

Can you please help? :slight_smile:
Thanks!
Noa


#2

Thanks for the question, @noa_hdr. Please note that

Segmented data is not expected to roll-up 100% to the non-segmented data, due to how this information is derived.

Source: Analytics Best Practices

Hope this helps!


Data mismatch between ads API analytic for organic and UI