Thanks for the question, @controledash.
Those links you provided don’t work, but we’ve looked at a specific campaign: 8t4m1. On ads.twitter.com, when the date range is [2017-10-25, 2017-10-31], we see 44,830 impressions. This matches what we get using the Ads API:
$ twurl -H ads-api.twitter.com "/2/stats/accounts/18ce548xann?entity=CAMPAIGN&entity_ids=8t4m1&start_time=2017-10-26&end_time=2017-10-27&metric_groups=ENGAGEMENT&placement=ALL_ON_TWITTER&granularity=TOTAL"
{
"data_type": "stats",
"time_series_length": 1,
"data": [
{
"id": "8t4m1",
"id_data": [
{
"segment": null,
"metrics": {
"impressions": [
44830
],
"tweets_send": [
1
],
"qualified_impressions": null,
"follows": null,
"app_clicks": null,
"retweets": null,
"likes": [
8
],
"engagements": [
389
],
"clicks": [
253
],
"card_engagements": null,
"poll_card_vote": null,
"replies": [
5
],
"url_clicks": [
3
],
"carousel_swipes": null
}
}
]
}
],
"request": {
"params": {
"start_time": "2017-10-26T02:00:00Z",
"segmentation_type": null,
"entity_ids": [
"8t4m1"
],
"end_time": "2017-10-27T02:00:00Z",
"country": null,
"placement": "ALL_ON_TWITTER",
"granularity": "TOTAL",
"entity": "CAMPAIGN",
"platform": null,
"metric_groups": [
"ENGAGEMENT"
]
}
}
}
However, when the specified date range is [2017-10-14, 2017-11-02]—on ads.twitter.com—we see 45,340 impressions.
For completeness, we used the asynchronous analytics endpoints to check the the impressions on the 26th, given the two date ranges specified. In both cases, we see 44,830 impressions.
Given that this is an ads.twitter.com issue, your best bet is to submit a request through that interface (the “Help?” link on the top right).
