Hi,
We are pulling data from the ADs API and were validating our results by checking against what’s on the dashboard - and it seems like we have unexplained discrepancies. I did see previous questions around the same topic, which were mostly a result of timezone differences. But the differences we’re seeing don’t look like they can be attributed to timezones.
For example, here’s the impressions and spend data that dashboard shows for one of our recent campaigns (date range used = 02/09/2018 - 02/16/2018):
And here’s what we get back from the API for the same campaign, with the same date range (notice that the request dates are in PST, which is the same as the account’s timezone):
{
"data_type": "stats",
"time_series_length": 7,
"data": [
{
"id": "abx6g",
"id_data": [
{
"segment": null,
"metrics": {
"impressions": [
0,
0,
0,
0,
2489,
40,
0
],
"tweets_send": null,
"billed_charge_local_micro": [
0,
0,
0,
0,
11367085,
0,
0
],
"qualified_impressions": null,
"follows": null,
"app_clicks": null,
"retweets": null,
"likes": [
0,
0,
0,
0,
1,
0,
0
],
"engagements": [
0,
0,
0,
0,
14,
1,
0
],
"clicks": [
0,
0,
0,
0,
14,
1,
0
],
"card_engagements": null,
"poll_card_vote": null,
"replies": null,
"url_clicks": [
0,
0,
0,
0,
4,
0,
0
],
"billed_engagements": [
0,
0,
0,
0,
3,
0,
0
],
"carousel_swipes": null
}
}
]
}
],
"request": {
"params": {
"start_time": "2018-02-09T08:00:00Z",
"segmentation_type": null,
"entity_ids": [
"abx6g"
],
"end_time": "2018-02-16T08:00:00Z",
"country": null,
"placement": "ALL_ON_TWITTER",
"granularity": "DAY",
"entity": "CAMPAIGN",
"platform": null,
"metric_groups": [
"ENGAGEMENT",
"BILLING"
]
}
}
}
Can someone please help us figure out what’s going on?
It’s difficult to get to the correct campaign on the dashboard with using just the names. Is there a way to use campaign IDs that come back in the API?
Thanks a bunch!
