Noticed that the values for the 6s_video_views in the Ad Groups Entity were not aligning with the values in the UI. If possible, do you know what API call is being made for the 6s_video_views in the UI?
The values that we’re receiving from the following API call look to pull some values from the 6s pre-roll views in the UI.
We’re currently using the sample API call:
https://ads-api.twitter.com/7/stats/jobs/accounts/######## with params: {‘placement’: ‘PUBLISHER_NETWORK’, ‘metric_groups’: ‘ENGAGEMENT,BILLING,VIDEO,MEDIA’, ‘start_time’: ‘2020-10-01’, ‘entity’: ‘LINE_ITEM’, ‘end_time’: ‘2020-10-31’, ‘granularity’: ‘DAY’, ‘entity_ids’: ‘####’}, headers: {‘Accept-encoding’: ‘gzip’}
Statistics differences between the API and UI are usually caused by a few different things:
- Your application will need to make requests for both placements,
ALL_ON_TWITTER and PUBLISHER_NETWORK , separately and sum up the results to match the UI,
- date ranges in the UI are inclusive while the
end_time is exclusive in the API, and
- the API will default to midnight in the accounts local timezone, if not specified
If these aren’t causing the discrepancy, please provide the Account ID, Entity IDs, and any campaign information in the UI (full URL is ideal) that isn’t matching and API request used to request this data.
Yes. We’re summing the values for both ALL_ON_TWITTER and PUBLISHER_NETWORK.
The times don’t seem to be an issue either when comparing additional dates.
Account ID: 18ce5530ihu
ID: i01wj
We’re looking at the sum total of 6s_video_views for the month of September 2020.
Using the API it looks like I’m getting a total of 876331.00 which matches the 6s pre-roll views in the UI rather than the 6s video views.
To add, we would be expecting to get the total views of 191960 that we’re seeing in the UI.
Extending the end_date to capture the entire served impressions of the line item (say Oct 3rd) returns:
"video_6s_views": [
876331
],
"video_total_views": [
1606578
]
This matches what is displayed in the UI for Results (as video_total_views) ‘The number of actions that fulfill your campaign objective, e.g. views in a promoted video views campaign’ and 6s pre-roll views as video_6s_views. I will need to investigate where the UI is getting the ‘6s video views’ value from because it is not clear whether the API is returning this.
Thank you for looking into this. That’s what we’re seeing in our response as well. Can you just let me know once you find out what the UI is pulling for the ‘6s video views’ value. Just trying to understand how to tie out these data points.
The 6s Video Views metric is not available via the API for pre-roll campaigns. For video view objective campaigns, the 6s video views value in the UI would be returned via the API as video_6s_views. For Pre-roll objectives, the 6s pre-roll views is mapped to video_6s_views.
Thank you for looking into this. Do you know why we’re seeing the 191,960 value in the UI then? 
Shouldn’t this be the 876331 value?
Sorry if I’m confused. If not, do you know what API call we’d have to make to get the 191,960 value?
Thank you again for looking into this. Just wondering if you’ve found the cause of the variation between the value that we’re seeing in the UI for 6s video views (191,960) and what is coming through in the video_6s_views in the API (876,331). If this is expected, do you know the API call we’d need to make to get the 191,960 value?
Hello, @zacharyriv. I’d like to try to help.
The API only has a single response attribute called video_6s_views. If the campaign you’re pulling analytics for is a regular video views objective, then the value it corresponds to in the UI is “6s video views.” If the campaign you’re pulling analytics for is a pre-roll objective, then the value it corresponds to in the UI is “6s pre-roll views.”
If you’re pulling analytics for a pre-roll campaign, you will not be able to get the “6s video views” number via the API. You’d only be able to get the “6s pre-roll views” number.
Please let us know if that helps clarify. Thank you.
Thanks @juanshishido! This helps clarify the values that we’re getting. Thank you for providing this insight.
1 Like