Microsoft Invest - Buyer Video Error report
The Buyer Video Error Report gives insight into video errors and their cause.
You can use this report to troubleshoot video settings and eliminate errors relating to buy-side video advertising. VAST 3 error codes provide further insight into the source of errors.
Time frame
All dates and times are given in UTC.
Time ranges
Time ranges define the time period of the data extracted for the report. The following is a complete list of time ranges available for reports.
However, all time ranges are not available for every report.
- Custom
- Current Hour
- Last Available Day
- Last Hour
- Today
- Last 24 Hours
- Last 48 Hours
- Yesterday
- Last 2 Days
- Last 7 Days
- Last 7 Available Days
- Last 14 Days
- Last 14 Available Days
- Last 30 Days
- Last 30 Available Days
- Last Month
- Last 100 Days
- Last 365 Days
- Quarter to Date
- Month to Date
- Month to Yesterday
- Lifetime
Intervals
Intervals determine how your data is grouped together into rows in the report response. The following is a complete list of intervals available for reports. However, all intervals are not available for every report.
- Hourly: Data is grouped into rows by the hour.
- Daily: Data is grouped into rows by the day.
- Monthly: Data is grouped into rows by the month.
- Cumulative: Data is grouped together in one figure, covering the entire selected time range.
This report's data is retained for 420 days.
Note
For impressions older than 100 days, the day will be returned rather than the hour.
Dimensions
Important
The Filter? column shows whether a dimension can be used as a filter as well as being used to group by.
For all revenue fields, the currency is defined by the Buying Currency field.
| Column | Filter? | Description |
|---|---|---|
| Only include results where a deal is present | N | Determines whether results are limited to deals only. |
| Insertion Order | Y | The insertion order associated with the impression. |
| Line Item | Y | The line item associated with the impression. |
| Campaign | Y | The campaign associated with the impression. (Does not apply to all advertisers.) |
| Deal | Y | The deal associated with the impression. |
| Creative | Y | The creative associated with the impression. |
| Publisher | Y | The publisher associated with the impression. |
| Ad Request Call Type | N | The type of handler that was used to send the impression to Microsoft Advertising (e.g., vmap, ut, mob, ptv, openrtb). |
| Site Domain | Y | The domain associated with the impression. |
| Application ID | N | The ID of the mobile app on the device where the impression occurred. |
| Impression Type | Y | The type of impression. An integer value which translates as follows: - 1 = Blank - 2 = PSA - 3 = Default Error - 4 = Default - 5 = Kept - 6 = Resold - 7 = RTB - 8 = PSA Error - 9 = External Impression - 10 = External Click |
| Device Type | Y | The device type on which the impression occurred. - Desktops & Laptops - Mobile Phones - Tablets - TV - Game Consoles - Media Players - Set Top Box - Other Devices |
| Video Context | Y | When and where an in-video ad plays – pre-roll, mid-roll, post-roll, or outstream. |
| Video Playback Method | Y | The playback method for the creative, for example ' Autoplay, Sound On'. |
| Video Player Size | Y | The size of the player based on width in pixels, e.g., 'small', 'medium', 'large'. |
| Creative Duration | N | The length of the video creative, in seconds. |
| Bidder Name | N | The name of the bidder associated with the impression. |
| Country | Y | The country in which the impression took place. |
| Seller | N | The name of the seller associated with the impression. |
| Supply Type | Y | The supply type for the impression - Web, Mobile Web, or Mobile App. |
Note
You can also filter on a particular number of impressions using the Minimum Impressions filter.
Metrics
Note
When values of a metric are displayed as percentages in the UI, they will be displayed as decimals when you export the report.
| Column | Description |
|---|---|
| Imps | The total number of impressions. Note that for a video, an impression occurs when the first frame of the creative plays. |
| Imps (default) | The number of impressions where a default creative served, because there were no valid bids. |
| Imps (kept) | The number of impressions for which a managed advertiser's creative served on the managed publisher's site. |
| Imps (resold) | The total number of resold impressions. |
| Imps (RTB) | The total number of RTB impressions. |
| Clicks | The total number of clicks. |
| CTR | The click-through rate of a creative, or the ratio of clicks to impressions, expressed as a percentage. |
| Cost Per Complete | The cost per video completion. |
| Total RPM | The total reported revenue for the placement. |
| Cost | The total cost of impressions. |
| Cost per Complete | The cost per video impression. |
| CPM | The cost per 1000 impressions. |
| VAST Error Rate | The rate of VAST errors for the video player, expressed as a percentage. |
| Ads Served | The total number of creative responses returned in response to a bid request. (Note that for a video, this does not equal an impression, because the first frame may or may not have been played.) |
| Total Error Count | The total number of VAST errors for the video player. |
| VAST 100 Error Count | The number of VAST 100 errors, indicating an XML parsing problem on the placement. Possible causes include: - The VAST supplied in adm was not a valid XML document. - The URL supplied in nurl did not resolve to a valid XML document. - Nurl only: The server did not respond with VAST, or at all when player called the nurl. - A CORS issue occurred. |
| VAST 101 Error Count | The number of VAST 101 errors, indicating a schema validation problem on the placement. A 101 error means that the VAST validated as XML, but did not validate per the VAST schema. In other words, mandatory elements or attributes were missing, or combinations of elements/attributes were not permissible. Possible causes include: - In-line and wrapper were both present. - AdTagURI was missing in wrapper element. - Duration was missing. - Ad node or MediaFile node was missing. - The offset attribute on a progress event was missing or invalid. |
| VAST 102 Error Count | The number errors indicating that the VAST version of the response was not supported. Possible causes include: - The bidder did not respect the VAST version(s) listed in the bid request. - The exchange sent the wrong VAST version(s) in the bid request. - VAST did not contain the version. (This could also be considered a schema validation issue.) |
| VAST 200 Error Count | The number of errors resulting in a trafficking problem. Possible causes include: - The player wanted Skippable Linear, but got back Linear. - The player wanted Linear, but got back Skippable Linear. - For Skippable Linear, the skipoffset didn't meet the publisher's expectations. - The bidder did not respect the skippability/skipoffset in the bid request. - The exchange was sending the wrong skippability/skipoffset in the bid request. - Potentially, any of the reasons in 201-203. |
| VAST 201 Error Count | The number of errors caused by the video player expecting different linearity. For more information see IAB's VAST documentation. |
| VAST 202 Error Count | The number of errors caused because the video player required a different video duration. For example, if a player is set up to play only 15-second video creatives and receives a 30-second creative from the buyer, the creative won't serve. In addition, creatives that are too short to fill the video duration may not serve unless the player allows ad podding and the total duration of videos in the ad pod fits the required duration. |
| VAST 203 Error Count | The number of errors that occurred because the video player was expecting a different size of creative. |
| VAST 300 Error Count | The number of errors caused by a general wrapper error. |
| VAST 301 Error Count | The number of errors caused by the timeout of the VAST URI provided in a current or subsequent wrapper element. This count includes request errors such as an invalid or unreachable URI, a request timeout for the URI, and security or other exceptions related to a VAST URI request. |
| VAST 302 Error Count | The number of errors caused because the wrapper limit was reached, as defined by the video player. Too many Wrapper responses have been received with no in-line response. |
| VAST 303 Error Count | The number of errors caused due to no VAST response after one or more wrappers. Also includes the number of empty VAST responses from fallback (waterfall handling). |
| VAST 400 Error Count | The number of general linear errors, typically caused when the video player is unable to display the linear ad. |
| VAST 401 Error Count | The number of errors caused because the file was not found when the player was unable to find Linear/MediaFile in the URI. |
| VAST 402 Error Count | The number of errors due to MediaFile URI timeouts. |
| VAST 403 Error Count | The number of errors caused because the video player can't find a media file whose attributes it supports. |
| VAST 405 Error Count | The number of errors caused due to a problem displaying the media file. |
| VAST 500 Error Count | The number of general NonLinearAds errors. |
| VAST 501 Error Count | The number of errors caused when the creative's dimensions were too large for the creative display area. |
| VAST 502 Error Count | The number of errors caused because the player could not fetch the NonLinearAds/NonLinear resource. |
| VAST 503 Error Count | The number of errors caused because the player could not find NonLinearresource with the supported type. |
| VAST 600 Error Count | The number of general companion ads errors. |
| VAST 601 Error Count | The number of errors caused because the creative's dimensions were too large for the companion ad display area. |
| VAST 602 Error Count | The number of errors caused because the required companion ad could not be displayed. |
| VAST 603 Error Count | The number of errors caused because the player was unable to fetch a companion ads/companion resource. |
| VAST 604 Error Count | The number of errors caused because the player could not find a companion resource with a supported type. |
| VAST 900 Error Count | The number of undefined errors. |
| VAST 901 Error Count | The number of general VPAID errors. |
Run your report
Follow these steps to run your report.
Select Reporting from the appropriate top menu (depending on how your account has been configured).
- Or, from the Publishers top menu, select Prebid Server Premium > Analytics > Prebid Server Analytics
Select the relevant report from the list. The Report screen shows the available filters, dimensions, and delivery options for the report. The selections you make here will determine what report data is delivered to you, and how.
Important
For an explanation of how grouping and filtering work, see Dimensions, Metrics, Filtering, and Grouping.
Select the relevant filters to limit the data displayed to just the information you want. For example, rather than running a report that shows impressions for all inventory sources, you may want to list results for just a select few. When you select a filter (by selecting Edit), a selection panel appears. Select items in the Available list (left), then select Add to include them in the Chosen list (right).
Group by Dimension. Grouping allows you to display rows of data in the order you prefer.
Warning
The more dimensions you group by, the larger the data set that is returned. Larger data sets can take substantially longer to process. Be sure to group using only the dimensions you need.
Choose a delivery option. Once you've selected your filters and grouped by your chosen dimensions, you need to choose a delivery method. Available delivery methods include:
Run now, show results in screen: For smaller amounts of data, you may want to view the report as soon as possible in your browser. You can download the report in XLSX, CSV, Excel/TSV and JSON format. However, there is a limit of 100,000 rows per report when downloading as XLSX and Excel file.
Run in background, notify me when results are ready to view: A popup notification will let you know when the report is ready to view or download.
Tip
The maximum size of the report that can be downloaded from the UI is 100 MB. Also, there is a limit of 100,000 rows per report when downloading as XLSX and Excel file. If the size of the report is more than that, you can try to download it using the API for that reporting service (The limit here is 10 million rows).
Export, send results via email: Run the report in the background and email the results to one or more email addresses.
Save as report template: Save your selected report settings so that you can run this report again in the future. You can name this template using the text entry field under Name this report (its checkbox is auto-selected when you choose this option). A saved report can be rerun from the Your Reports screen.
Add to scheduled reports: Run this report automatically at specified times and have it sent to one or more email addresses.
Name this report: Give this report with its current settings a name for future reference.
Select Run report to send your report request.