Viewability
CESP underlines that this document is based on CESP trust in all information shared by each measurement company.
To navigate in a table :
– on computer : scroll vertically to compare various answers.
– on mobile : we recommand you switch to landscape format for a better display.
You can download the grid you want in Excel format while filtering measurement companies but also the global grid concerning viewability in PDF format, for web and app environments.
Measurement companies are splited in differents tabs according to whether their solution has been accredited by the MRC (Media Rating Council) or not.
Web environment
Accredited solution - Display
 Updated April 16th, 2021 |  |  |  |  |  |
|---|---|---|---|---|---|
| 1) Can you list the sensors/data points your solution uses to measure display viewability? | Adloox does not intend to share this information | JS tag, geometric method | IAS JS tag inserted into the page via an iframe. IAS uses different methods according to the placement type. | JS tag, geometric method, browser optimization method | Moat can measure wherever our JS tag is accepted for display measurement |
| 2) Is your solution compliant with OM SDK? | N/A | N/A | N/A | N/A | N/A |
| 3) Is your solution compliant with MRAID? | N/A | N/A | N/A | N/A | N/A |
| 4) Do you measure expandable formats? | Yes | Yes | Yes | Yes | Yes |
| a) If yes, is your measure based on the pixel count of the smaller initial format of the ad, when the smaller initial format is in place; or the pixel count of the larger expanded ad, for the duration when that larger expanded ad is in place; or do you use another method (specify which one)? | Viewability is not pixel count but percentage of ad unit in view and duration is ‘continuous 30%+ for 1+ sec’; size of unit is not relevant and Adloox recalibrates active sensor measurement as ad expands and contracts. This would include a duration that encompasses expand/contract events.Polling frequency is 100ms (MRC requirement) | The measurement is based on the pixel count of the initial format of the ad | IAS viewability measurement process identifies the size of the ad at each polling frequency (every 100ms for display and expandable rich media creatives). At each polling interval, the ad is determined to be viewable if the portion of the ad that is contained within the viewport exceeds the appropriate threshold for the size of the ad at the time of measurement. If the ad accumulates ten consecutive polling observations meeting the viewability requirements, the impression is reported as a viewable impression. | The measurement is based on the pixel count of the smaller initial format of the ad, when the smaller initial format is in place; or the pixel count of the larger expanded ad, for the duration when that larger expanded ad is in place. The duration measurement includes the time viewable in both states. | Moat is able to identify the non-expanded and expanded elements. Custom logic may be necessary to measure the unit. |
| 5) Do you measure Page Take-over ads? | Yes | Yes | Yes | Yes | Yes |
| a) If yes, do you measure each component of the page takeover separately? | Yes Adloox have a specific script for takeover taking into consideration the size of the page | Yes | Yes | Yes | Yes |
| b) If yes, how do you report page takeover viewability? | The takeover is treated as a unit in classic viewability report with a specific macro for segragation | DV measures and reports each ad independently for viewability in case of page takeover ads, if the ads have been setup with DV tags to measure independently. | As a display unit. | If the ads are measured independently, viewability will be determined for each component individually and each component will be reported separately in UI and reports. If the takeover is treated as a unit they will be reported as one single display ad. | Report a figure for each component measured |
| 6) Can you specify the method used to measure slide-in ads (a slide-in ad is an ad which appears by sliding on the screen after a launch event)? | Adloox JS monitors the DOM element (the DOM is the way Javascript sees its containing pages' data); Adloox treats this identically to below-the-fold going above-the-fold as the user scrolls the browser | DV identifies the ad creative on the page to be measured, and determines viewability based on the time spent in view as the ad slides onto the screen after launch event. | IAS viewability measurement process identifies the size of the ad at each polling frequency (every 100ms for display and expandable rich media creatives). At each polling interval, the ad is determined to be viewable if the portion of the ad that is contained within the viewport exceeds the appropriate threshold for the size of the ad at the time of measurement. If the ad accumulates ten consecutive polling observations meeting the viewability requirements, the impression is reported as a viewable impression. | There is no specific method for slide-in ads. Slide-in ads are treated as normal display ads | Upon request, Moat can write custom logic to enable measuring the unit |
| 7) Do you have limitation on Safari for cross-domain iframe? | Yes, Adloox isn't able to detect browser focus in cross-origin environment | No | Yes, Safari has a “Top Hits” feature which pre-loads websites in the background as a user types a URL into the navigation bar. (Example: while a user enters the URL in an address bar to a page 2, impression events load for ads related to page 1 prior to selecting "Enter".) IAS does not support this functionality as the impressions are not reported as viewable since we use PageVisibility API. Ongoing IAS research currently guides that cases like this represent 0.5% of our traffic and we are continuing to monitor this number as a resource for possible future changes to our systems. | No | No |
| 8) Do you have limitation on Chrome for cross-domain iframe? | Yes, Adloox isn't able to detect browser focus in cross-origin environment | No | No | No | No |
| 9) Do you have limitation on Android for cross-domain iframe? | Yes, Adloox isn't able to detect browser focus in cross-origin environment | No | No | No | No |
| 10) Do you have limitation on IOS environments for friendly iframe? | No | No | No | No | No |
| 11) Do you have limitation on IOS environments for non- iframe? | No | No | No | No | No |
| 12) Do you have any limitations on Android environments for friendly iframe? | No | No | No | No | No |
| 13) Do you have any limitations on Android environments for non- iframe? | No | No | No | No | No |
| 14) Does your solution have any other limitations? If yes, could you specify which ones? | Yes, JavaScript is required for Viewability measurement | Viewability measurement requires a JavaScript-enabled browser. Certain browsers and iFrame scenarios may have additional security limitations which prevent the use of geometric methodology. In these cases, viewability may be ascertained using IAB-standard APIs. | Yes, - JavaScript is required for all methods. -If IAS’s server domains are listed as ad servers in blocking software, the IAS servers will be blocked. -Ad integrated in deeply nested iframes can be hard to measure, especially in old IE versions. | JavaScript is required for measurement | Yes, Scroll rate is not measurable if the Moat tag loads inside a hostile iframe. If the user has disabled JavaScript, Moat will not measure the impression. |
| 15) Has your solution been accredited by MRC for display viewability measurement? | Yes | Yes | Yes | Yes | Yes |
| a) If yes, has your solution been continuously accredited since your first accreditation? | Yes | Yes | Yes | Yes | Yes |
| b) If no, are you in the process of being accredited by MRC? | N/A | N/A | N/A | N/A | N/A |
| 16) Do you provide custom viewability definitions? | Yes, Adloox can provide custom viewability definition on top of the MRC/IAB one | Yes, - the GroupM viewability definition - the PMX viewability definition - a user-set custom viewability definition | Yes | Yes | Yes |
| a) Are your custom viewability definitions compliant with the existing MRC standards? (if yes, specify which custom definitions are compliant) | Yes, All Adloox custom viewability definitions are set to never go under MRC minimum standards for viewability measurement | Yes All | Yes, These metrics are client specific and not available to all clients and falls under the data sharing agreements IAS has with the applicable clients. For further context, some examples of custom metrics include Time in View 100%, Time in View > 2seconds. | Yes Meetrics' custom definitions are flexible regarding the area and duration thresholds as well as audio criteria. All combinations can be implemented according to the client's needs. The calculation of all these metrics is compliant to the MRC guidelines. | Yes, List of all compliant display metrics: Fully On-Screen Measurable Impressions Fully On-Screen Impressions (No Time Minimum) Fully On-Screen Rate (No Time Minimum) 1 Sec Fully On-Screen Impressions 1 Sec Fully On-Screen Rate In-View Time > 5 Sec Rate In-View Time > 10 Sec Rate In-View Time > 15 Sec Rate In-View Time > 30 Sec Rate In-View Time > 1 Min Rate On-Screen Impressions On-Screen Rate On-Screen Measurable Impressions 80% On-Screen for 1 Sec Impressions 80% On-Screen for 1 Sec Rate Total Ad Dwell Time Total Active Page Dwell Time Active Page Dwell Time In-View Time > 5 Sec Impressions In-View Time > 10 Sec Impressions In-View Time > 15 Sec Impressions In-View Time > 30 Sec Impressions In-View Time > 1 Min Impressions |
| b) Have your custom definitions been accredited by MRC? (if yes, specify which custom definitions are accredited) | Yes o Various Time Exposure Metrics | Yes, (1) All user-set custom Display Viewable Impressions in Desktop and Mobile Web Environments (2) PMX viewability definition | No | No | Yes, List of all accredited display metrics: Fully On-Screen Measurable Impressions Fully On-Screen Impressions (No Time Minimum) Fully On-Screen Rate (No Time Minimum) 1 Sec Fully On-Screen Impressions 1 Sec Fully On-Screen Rate In-View Time > 5 Sec Rate In-View Time > 10 Sec Rate In-View Time > 15 Sec Rate In-View Time > 30 Sec Rate In-View Time > 1 Min Rate On-Screen Impressions On-Screen Rate On-Screen Measurable Impressions 80% On-Screen for 1 Sec Impressions 80% On-Screen for 1 Sec Rate Total Ad Dwell Time Total Active Page Dwell Time Active Page Dwell Time In-View Time > 5 Sec Impressions In-View Time > 10 Sec Impressions In-View Time > 15 Sec Impressions In-View Time > 30 Sec Impressions In-View Time > 1 Min Impressions |
| 17) Do you have a specific QA (Quality Assurance) procedure on tag / SDK implementation? | Yes | Yes | Yes | Yes | Yes |
| a) Do you have a certification program or way to vet signals from MRAID/SDK in mobile apps? | N/A | N/A | N/A | N/A | N/A |
Accredited solution - Video
Updated April 16th, 2021 | | | | | |
|---|---|---|---|---|---|
| 18) Is your solution compliant with all VAST version? | Yes | Yes | Yes | Yes | Yes |
| a) If no, can you specify which ones your solution supports? | N/A | N/A | N/A | N/A | N/A |
| b) Is your solution compliant with the VPAID wrappers included in VAST wrappers? | Yes | Yes | Yes | Yes | Yes |
| 19) Is your solution compliant with OM SDK? | N/A | N/A | N/A | Yes | N/A |
| 20) Is your solution compliant with MRAID? | N/A | N/A | N/A | N/A | N/A |
| 21) Can you list the sensors/data points your solution uses to measure video viewability? | Adloox does not intend to share this information | Industry-standard APIs such as intersection observer and VPAID, as well as geometric and resource-based data points | JavaScript-based technology that uses both geometric and browser optimization measurement approaches to determine viewability. VPAID or web video SDK implementation. | JavaScript measurement utilizing geometric and browser optimization approaches as well as VPAID, web video SDK implementation & OM SDK to determine viewability and video events | Moat VPAID tag |
| 22) Do you detect the presence of audio? | Yes | Yes | Yes | Yes | Yes |
| 23) Do you have any limitations on Safari for cross-domain iframe? | Yes, Adloox isn't able to detect browser focus in cross-origin environment | No | Yes, Deeply nested iframes may produce measurement limitations. | No | No |
| 24) Do you have any limitations on Chrome for cross-domain iframe? | Yes, Adloox isn't able to detect browser focus in cross-origin environment | No | No | No | No |
| 25) Do you have any limitations on Android for cross-domain iframe? | Yes, Adloox isn't able to detect browser focus in cross-origin environment | No | No | No | No |
| 26) Do you have any limitations on IOS environments for friendly iframe? | No | No | No | No | No |
| 27) Do you have any limitations on IOS environments for non- iframe? | No | No | No | No | No |
| 28) Do you have any limitations on Android environments for friendly iframe? | No | No | No | No | No |
| 29) Do you have any limitations on Android environments for non- iframe? | No | No | No | No | No |
| 30) Does your solution have any other limitations? If yes, could you specify which ones? | Yes, JavaScript is required for Viewability measurement | Yes Tagging - requires use of either DV Video Omnitag or DV integration with video platform (i.e. Innovid, Sizmek) Inventory - measurement capable on either VPAID or VAST inventory that is using OMID | Yes - JavaScript is required for all methods. - If IAS’s server domains are listed as ad servers in blocking software, the IAS servers will be blocked. - Ad integrated in deeply nested iframes can be hard to measure, especially in old IE versions. | JavaScript is required for measurement | Yes, Scroll rate is not measurable if the Moat tag loads inside a hostile iframe. If the user has disabled JavaScript, Moat will not measure the impression |
| 31) Has your solution been accredited by MRC for video viewability measurement? | Yes | Yes | Yes | Yes | Yes |
| a) If yes, has your solution been continuously accredited since your first accreditation? | No | Yes | Yes | Yes | Yes |
| b) If no, are you in the process of being accredited by MRC? | N/A | N/A | N/A | N/A | N/A |
| 32) Do you provide custom viewability definitions? | Yes, Adloox can provide custom viewability defnition on top of the MRC/IAB one | Yes, - the GroupM viewability definition - the PMX viewability definition - a user-set custom viewability definition | Yes | Yes | Yes |
| a) Are your custom viewability definitions compliant with the existing MRC standards? (if yes, specify which custom definitions are compliant) | Yes All | Yes All | Yes , These metrics are client specific and not available to all clients and falls under the data sharing agreements IAS has with the applicable clients. For further context, some examples of custom metrics include Time in View 100%, Time in View > 2seconds. | Yes Meetrics' custom definitions are flexible regarding the area and duration thresholds as well as audio criteria. All combinations can be implemented according to the client's needs. The calculation of all these metrics is compliant to the MRC guidelines. | Yes, List of all compliant video metrics: 2 Sec In-View Impressions 2 Sec Video In-View Rate Fully On-Screen Measurable Impressions Fully On-Screen Impressions (No Time Minimum) Fully On-Screen Rate (No Time Minimum) % of Video Played In-View Audible On 1st Quartile Rate Audible On 2nd Quartile Rate Audible On 3rd Quartile Rate Audible On Complete Rate Visible On 1st Quartile Rate Visible On 2nd Quartile Rate Visible On 3rd Quartile Rate Visible On Completion Rate Audible and Visible at 1st Quartile Rate Audible and Visible at 2nd Quartile Rate Audible and Visible at 3rd Quartile Rate Audible and Visible on Complete Rate Audible and Fully On-Screen for Half of Duration Impressions Audible and Fully On-Screen for Half of Duration Rate 3 Sec In-View Impressions 5 Sec In-View Impressions On-Screen Measurable Impressions On-Screen Impressions On-Screen Rate 3 Sec Video In-View Rate 5 Sec Video In-View Rate 1 Sec Fully On-Screen Impressions 1 Sec Fully On-Screen Rate 3 Sec Fully On-Screen Impressions 3 Sec Fully On-Screen Rate In-View Time 2 Sec In-View and Reached Completion Impressions 2 Sec In-View and Reached Completion Rate Audible On 1st Quartile Sum Audible On 2nd Quartile Sum Audible On 3rd Quartile Sum Audible On Complete Sum Visible On 1st Quartile Sum Visible On 2nd Quartile Sum Visible On 3rd Quartile Sum Visible On Completion Sum Audible and Visible on Start Sum Audible and Visible on Start Rate Audible and Visible at 1st Quartile Sum Audible and Visible at 2nd Quartile Sum Audible and Visible at 3rd Quartile Sum Audible and Visible on Complete Sum Audible and 80% On-Screen for Half of Duration (15 sec. cap) Impressions Audible and 80% On-Screen for Half of Duration (15 sec. cap) Rate Audible and Fully On-Screen for Half of Duration (15 sec. cap) Impressions Audible and Fully On-Screen for Half of Duration (15 sec. cap) Rate Audible and Fully On-Screen for Half of Duration (15 sec. cap) with Completion Impressions Audible and Fully On-Screen for Half of Duration (15 sec. cap) with Completion Rate |
| b) Have your custom definitions been accredited by MRC? (if yes, specify which custom definitions are accredited) | No | Yes, (1) Video Viewable Impressions in Desktop and Mobile Web Environments (2) PMX viewability definition | No | No | Yes, List of all accredited video metrics: 2 Sec In-View Impressions 2 Sec Video In-View Rate Fully On-Screen Measurable Impressions Fully On-Screen Impressions (No Time Minimum) Fully On-Screen Rate (No Time Minimum) % of Video Played In-View Audible On 1st Quartile Rate Audible On 2nd Quartile Rate Audible On 3rd Quartile Rate Audible On Complete Rate Visible On 1st Quartile Rate Visible On 2nd Quartile Rate Visible On 3rd Quartile Rate Visible On Completion Rate Audible and Visible at 1st Quartile Rate Audible and Visible at 2nd Quartile Rate Audible and Visible at 3rd Quartile Rate Audible and Visible on Complete Rate Audible and Fully On-Screen for Half of Duration Impressions Audible and Fully On-Screen for Half of Duration Rate 3 Sec In-View Impressions 5 Sec In-View Impressions On-Screen Measurable Impressions On-Screen Impressions On-Screen Rate 3 Sec Video In-View Rate 5 Sec Video In-View Rate 1 Sec Fully On-Screen Impressions 1 Sec Fully On-Screen Rate 3 Sec Fully On-Screen Impressions 3 Sec Fully On-Screen Rate In-View Time 2 Sec In-View and Reached Completion Impressions 2 Sec In-View and Reached Completion Rate Audible On 1st Quartile Sum Audible On 2nd Quartile Sum Audible On 3rd Quartile Sum Audible On Complete Sum Visible On 1st Quartile Sum Visible On 2nd Quartile Sum Visible On 3rd Quartile Sum Visible On Completion Sum Audible and Visible on Start Sum Audible and Visible on Start Rate Audible and Visible at 1st Quartile Sum Audible and Visible at 2nd Quartile Sum Audible and Visible at 3rd Quartile Sum Audible and Visible on Complete Sum Audible and 80% On-Screen for Half of Duration (15 sec. cap) Impressions Audible and 80% On-Screen for Half of Duration (15 sec. cap) Rate Audible and Fully On-Screen for Half of Duration (15 sec. cap) Impressions Audible and Fully On-Screen for Half of Duration (15 sec. cap) Rate Audible and Fully On-Screen for Half of Duration (15 sec. cap) with Completion Impressions Audible and Fully On-Screen for Half of Duration (15 sec. cap) with Completion Rate |
| 33) Do you have a specific QA (Quality Assurance) procedure on tag / implementation? | Yes | Yes | Yes | Yes | Yes |
| a) Do you have a certification program or way to vet signals from MRAID/SDK in mobile apps? | N/A | N/A | N/A | N/A | N/A |
In-app environment
Accredited solution - Display
Updated April 16th, 2021 | | | |
|---|---|---|---|
| 1) Can you list the sensors/data points your solution uses to measure display viewability? | OM SDK or MRAID | OM SDK, AVID SDK, or MRAID | JS tag, with OMSDK |
| 2) Is your solution compliant with OM SDK? | Yes | Yes | Yes |
| 3) Is your solution compliant with MRAID? | Yes | Yes | Yes However there are some limitations with MRAID format which depens on the app. developer choices. |
| 4) Do you measure expandable formats? | Yes | Yes | Yes |
| a) If yes, is your measure based on the pixel count of the smaller initial format of the ad, when the smaller initial format is in place; or the pixel count of the larger expanded ad, for the duration when that larger expanded ad is in place; or do you use another method (specify which one)? | The measurement is based on both the pixel count of the initial format of the ad for the duration and the pixel count of the expanded ad. | IAS viewability measurement process identifies the size of the ad at each polling frequency (every 100ms for display and expandable rich media creatives). At each polling interval, the ad is determined to be viewable if the portion of the ad that is contained within the viewport exceeds the appropriate threshold for the size of the ad at the time of measurement. If the ad accumulates ten consecutive polling observations meeting the viewability requirements, the impression is reported as a viewable impression. | Moat is able to identify the non-expanded and expanded elements. Custom logic may be necessary to measure the unit. |
| 5) Do you measure Page Take-over ads? | Yes | Yes | Yes |
| a) If yes, do you measure each component of the page takeover separately? | Yes | Yes | Yes |
| b) If yes, how do you report page takeover viewability? | DV measures and reports each ad independently for viewability in case of page takeover ads, if the ads have been setup with DV tags to measure independently. | As a display unit. | Report a figure for each component measured |
| 6) Can you specify the method used to measure slide-in ads (a slide-in ad is an ad which appears by sliding on the screen after a launch event)? | DV identifies the ad creative on the page to be measured, and determines viewability based on the time spent in view as the ad slides onto the screen after launch event. | IAS viewability measurement process identifies the size of the ad at each polling frequency (every 100ms for display and expandable rich media creatives). At each polling interval, the ad is determined to be viewable if the portion of the ad that is contained within the viewport exceeds the appropriate threshold for the size of the ad at the time of measurement. If the ad accumulates ten consecutive polling observations meeting the viewability requirements, the impression is reported as a viewable impression. | Upon request, Moat can write custom logic to enable measuring the unit |
| 7) Do you have limitation on Safari for cross-domain iframe? | N/A | N/A | N/A |
| 8) Do you have limitation on Chrome for cross-domain iframe? | N/A | N/A | N/A |
| 9) Do you have limitation on Android for cross-domain iframe? | N/A | N/A | N/A |
| 10) Do you have limitation on IOS environments for friendly iframe? | Yes, OM SDK or MRAID is required | Yes, OM SDK, proprietary SDK or MRAID is required | Yes, OM SDK required |
| 11) Do you have limitation on IOS environments for non- iframe? | Yes, OM SDK or MRAID is required | Yes, OM SDK, proprietary SDK or MRAID is required | Yes, OM SDK required |
| 12) Do you have any limitations on Android environments for friendly iframe? | Yes, OM SDK or MRAID is required | Yes, OM SDK, proprietary SDK or MRAID is required | Yes, OM SDK required |
| 13) Do you have any limitations on Android environments for non- iframe? | Yes, OM SDK or MRAID is required | Yes, OM SDK, proprietary SDK or MRAID is required | Yes, OM SDK required |
| 14) Does your solution have any other limitations? If yes, could you specify which ones? | No | No | Yes, Limitations depend on the partner or the environment being measured. Moat is partner agnostic and can measure wherever our tag is accepted. |
| 15) Has your solution been accredited by MRC for display viewability measurement? | Yes | Yes | Yes |
| a) If yes, has your solution been continuously accredited since your first accreditation? | Yes | Yes | Yes |
| b) If no, are you in the process of being accredited by MRC? | N/A | N/A | N/A |
| 16) Do you provide custom viewability definitions? | Yes, - the GroupM viewability definition - the PMX viewability definition - a user-set custom viewability definition | Yes | Yes |
| a) Are your custom viewability definitions compliant with the existing MRC standards? (if yes, specify which custom definitions are compliant) | Yes All | Yes, These metrics are client specific and not available to all clients and falls under the data sharing agreements IAS has with the applicable clients. For further context, some examples of custom metrics include Time in View 100%, Time in View > 2seconds. | Yes, List of all compliant display metrics: Fully On-Screen Measurable Impressions Fully On-Screen Impressions (No Time Minimum) Fully On-Screen Rate (No Time Minimum) 1 Sec Fully On-Screen Impressions 1 Sec Fully On-Screen Rate In-View Time > 5 Sec Rate In-View Time > 10 Sec Rate In-View Time > 15 Sec Rate In-View Time > 30 Sec Rate In-View Time > 1 Min Rate On-Screen Impressions On-Screen Rate On-Screen Measurable Impressions 80% On-Screen for 1 Sec Impressions 80% On-Screen for 1 Sec Rate Total Ad Dwell Time Total Active Page Dwell Time Active Page Dwell Time In-View Time > 5 Sec Impressions In-View Time > 10 Sec Impressions In-View Time > 15 Sec Impressions In-View Time > 30 Sec Impressions In-View Time > 1 Min Impressions |
| b) Have your custom definitions been accredited by MRC? (if yes, specify which custom definitions are accredited) | Yes | No | Yes, List of all accredited display metrics: Fully On-Screen Measurable Impressions Fully On-Screen Impressions (No Time Minimum) Fully On-Screen Rate (No Time Minimum) 1 Sec Fully On-Screen Impressions 1 Sec Fully On-Screen Rate In-View Time > 5 Sec Rate In-View Time > 10 Sec Rate In-View Time > 15 Sec Rate In-View Time > 30 Sec Rate In-View Time > 1 Min Rate On-Screen Impressions On-Screen Rate On-Screen Measurable Impressions 80% On-Screen for 1 Sec Impressions 80% On-Screen for 1 Sec Rate Total Ad Dwell Time Total Active Page Dwell Time Active Page Dwell Time In-View Time > 5 Sec Impressions In-View Time > 10 Sec Impressions In-View Time > 15 Sec Impressions In-View Time > 30 Sec Impressions In-View Time > 1 Min Impressions |
| 17) Do you have a specific QA (Quality Assurance) procedure on tag / SDK implementation? | Yes | Yes | Yes |
| a) Do you have a certification program or way to vet signals from MRAID/SDK in mobile apps? | Yes DV has certification processes in place for MRAID and OM SDK enabled partners. For SDK, DV integrates the partner's ad SDK in our testbed app to undergo a series of manual and automated tests that determine the accuracy of the implementation by comparing its results with the expected results. Furthermore, DV performs volume tests with our partners to ensure that the impression counts are aligned and critical benchmarks in measurement and viewability are met. In cases where DV sees a discrepancy, we recommend our partners to implement changes and validate them before confirming them as certified. | Yes | Yes, In addition to the certification performed by IAB Tech Lab for OM SDK implementations, Moat performs QA on OM SDK apps before considering these apps measurable. |
Not accredited solution - Display
Updated April 16th, 2021 | | |
|---|---|---|
| 1) Can you list the sensors/data points your solution uses to measure display viewability? | Adloox does not intend to share this information | OM SDK or MRAID |
| 2) Is your solution compliant with OM SDK? | Yes | Yes |
| 3) Is your solution compliant with MRAID? | Yes | Yes |
| 4) Do you measure expandable formats? | Yes | Yes |
| a) If yes, is your measure based on the pixel count of the smaller initial format of the ad, when the smaller initial format is in place; or the pixel count of the larger expanded ad, for the duration when that larger expanded ad is in place; or do you use another method (specify which one)? | Viewability is not pixel count but percentage of ad unit in view and duration is ‘continuous 30%+ for 1+ sec’; size of unit is not relevant and Adloox recalibrates active sensor measurement as ad expands and contracts. This would include a duration that encompasses expand/contract events. Polling frequency is 100ms (MRC requirement) | The measurement is based on event signals of the respective technology used, either MRAID or OM SDK. |
| 5) Do you measure Page Take-over ads? | Yes | Yes |
| a) If yes, do you measure each component of the page takeover separately? | Yes | Yes |
| b) If yes, how do you report page takeover viewability? | The takeover is treated as a unit in classic viewability report with a specific macro for segragation | If the ads are measured independently, viewability will be determined for each component individually and each component will be reported separately in UI and reports. If the takeover is treated as a unit they will be reported as one single display ad. |
| 6) Can you specify the method used to measure slide-in ads (a slide-in ad is an ad which appears by sliding on the screen after a launch event)? | Adloox JS monitors the DOM element (the DOM is the way Javascript sees its containing pages' data); Adloox treats this identically to below-the-fold going above-the-fold as the user scrolls the browser | There is no specific method for slide-in ads. Slide-in ads are treated as normal mobile display ads |
| 7) Do you have limitation on Safari for cross-domain iframe? | N/A | N/A |
| 8) Do you have limitation on Chrome for cross-domain iframe? | N/A | |
| 9) Do you have limitation on Android for cross-domain iframe? | N/A | |
| 10) Do you have limitation on IOS environments for friendly iframe? | Yes, OM SDK, proprietary SDK or MRAID is required | Yes, OM SDK or MRAID is required |
| 11) Do you have limitation on IOS environments for non- iframe? | Yes, OM SDK, proprietary SDK or MRAID is required | Yes, OM SDK or MRAID is required |
| 12) Do you have any limitations on Android environments for friendly iframe? | Yes, OM SDK, proprietary SDK or MRAID is required | Yes, OM SDK or MRAID is required |
| 13) Do you have any limitations on Android environments for non- iframe? | Yes, OM SDK, proprietary SDK or MRAID is required | Yes, OM SDK or MRAID is required |
| 14) Does your solution have any other limitations? If yes, could you specify which ones? | Yes, JavaScript is required for Viewability measurement | No |
| 15) Has your solution been accredited by MRC for display viewability measurement? | No | No |
| a) If yes, has your solution been continuously accredited since your first accreditation? | N/A | N/A |
| b) If no, are you in the process of being accredited by MRC? | Under review | No |
| 16) Do you provide custom viewability definitions? | Yes, Adloox can provide custom viewability definition on top of the MRC/IAB one | Yes |
| a) Are your custom viewability definitions compliant with the existing MRC standards? (if yes, specify which custom definitions are compliant) | Yes, All Adloox custom viewability definitions are set to never go under MRC minimum standards for viewability measurement | Yes Meetrics' custom definitions are flexible regarding the area and duration thresholds as well as audio criteria. All combinations can be implemented according to the client's needs. The calculation of all these metrics is compliant to the MRC guidelines. |
| b) Have your custom definitions been accredited by MRC? (if yes, specify which custom definitions are accredited) | Under review | No |
| 17) Do you have a specific QA (Quality Assurance) procedure on tag / SDK implementation? | Yes | Yes |
| a) Do you have a certification program or way to vet signals from MRAID/SDK in mobile apps? | Yes | Yes |
Accredited solution - Video
Updated April 16th, 2021 | | | |
|---|---|---|---|
| 18) Is your solution compliant with all VAST version? | Yes | Yes | Yes |
| a) If no, can you specify which ones your solution supports? | N/A | N/A | N/A |
| b) Is your solution compliant with the VPAID wrappers included in VAST wrappers? | Yes | No | Yes |
| 19) Is your solution compliant with OM SDK? | Yes | Yes | Yes |
| 20) Is your solution compliant with MRAID? | Yes | Yes | Yes However there are some limitations with MRAID format which depens on the app. developer choices. |
| 21) Can you list the sensors/data points your solution uses to measure video viewability? | Industry-standard APIs such as VPAID, MRAID and OM SDK OMID API. | AVID SDK, OM SDK | OM SDK |
| 22) Do you detect the presence of audio? | Yes | Yes | Yes |
| 23) Do you have any limitations on Safari for cross-domain iframe? | N/A | N/A | N/A |
| 24) Do you have any limitations on Chrome for cross-domain iframe? | N/A | N/A | N/A |
| 25) Do you have any limitations on Android for cross-domain iframe? | N/A | N/A | Yes, OM SDK required |
| 26) Do you have any limitations on IOS environments for friendly iframe? | Yes, OM SDK or MRAID is required | Yes, OM SDK, proprietary SDK or MRAID is required | Yes, OM SDK required |
| 27) Do you have any limitations on IOS environments for non- iframe? | Yes, OM SDK or MRAID is required | Yes, OM SDK, proprietary SDK or MRAID is required | Yes, OM SDK required |
| 28) Do you have any limitations on Android environments for friendly iframe? | Yes, OM SDK or MRAID is required | Yes, OM SDK, proprietary SDK or MRAID is required | Yes, OM SDK required |
| 29) Do you have any limitations on Android environments for non- iframe? | Yes, OM SDK or MRAID is required | Yes, OM SDK, proprietary SDK or MRAID is required | Yes, OM SDK required |
| 30) Does your solution have any other limitations? If yes, could you specify which ones? | No | No | Yes, Limitations depend on the partner or the environment being measured. Moat is partner agnostic and can measure wherever our tag is accepted. |
| 31) Has your solution been accredited by MRC for video viewability measurement? | Yes | Yes | Yes |
| a) If yes, has your solution been continuously accredited since your first accreditation? | Yes | Yes | Yes |
| b) If no, are you in the process of being accredited by MRC? | N/A | N/A | N/A |
| 32) Do you provide custom viewability definitions? | Yes, custom viewability definitions such as GroupM, PMX, or a client defined definition are possible when inventory supports OMID/OMSDK | Yes | Yes |
| a) Are your custom viewability definitions compliant with the existing MRC standards? (if yes, specify which custom definitions are compliant) | Yes All | Yes, These metrics are client specific and not available to all clients and falls under the data sharing agreements IAS has with the applicable clients. For further context, some examples of custom metrics include Time in View 100%, Time in View > 2seconds. | Yes, List of all compliant video metrics: 2 Sec In-View Impressions 2 Sec Video In-View Rate Fully On-Screen Measurable Impressions Fully On-Screen Impressions (No Time Minimum) Fully On-Screen Rate (No Time Minimum) % of Video Played In-View Audible On 1st Quartile Rate Audible On 2nd Quartile Rate Audible On 3rd Quartile Rate Audible On Complete Rate Visible On 1st Quartile Rate Visible On 2nd Quartile Rate Visible On 3rd Quartile Rate Visible On Completion Rate Audible and Visible at 1st Quartile Rate Audible and Visible at 2nd Quartile Rate Audible and Visible at 3rd Quartile Rate Audible and Visible on Complete Rate Audible and Fully On-Screen for Half of Duration Impressions Audible and Fully On-Screen for Half of Duration Rate 3 Sec In-View Impressions 5 Sec In-View Impressions On-Screen Measurable Impressions On-Screen Impressions On-Screen Rate 3 Sec Video In-View Rate 5 Sec Video In-View Rate 1 Sec Fully On-Screen Impressions 1 Sec Fully On-Screen Rate 3 Sec Fully On-Screen Impressions 3 Sec Fully On-Screen Rate In-View Time 2 Sec In-View and Reached Completion Impressions 2 Sec In-View and Reached Completion Rate Audible On 1st Quartile Sum Audible On 2nd Quartile Sum Audible On 3rd Quartile Sum Audible On Complete Sum Visible On 1st Quartile Sum Visible On 2nd Quartile Sum Visible On 3rd Quartile Sum Visible On Completion Sum Audible and Visible on Start Sum Audible and Visible on Start Rate Audible and Visible at 1st Quartile Sum Audible and Visible at 2nd Quartile Sum Audible and Visible at 3rd Quartile Sum Audible and Visible on Complete Sum Audible and 80% On-Screen for Half of Duration (15 sec. cap) Impressions Audible and 80% On-Screen for Half of Duration (15 sec. cap) Rate Audible and Fully On-Screen for Half of Duration (15 sec. cap) Impressions Audible and Fully On-Screen for Half of Duration (15 sec. cap) Rate Audible and Fully On-Screen for Half of Duration (15 sec. cap) with Completion Impressions Audible and Fully On-Screen for Half of Duration (15 sec. cap) with Completion Rate |
| b) Have your custom definitions been accredited by MRC? (if yes, specify which custom definitions are accredited) | Yes | No | Yes, List of all accredited video metrics: 2 Sec In-View Impressions 2 Sec Video In-View Rate Fully On-Screen Measurable Impressions Fully On-Screen Impressions (No Time Minimum) Fully On-Screen Rate (No Time Minimum) % of Video Played In-View Audible On 1st Quartile Rate Audible On 2nd Quartile Rate Audible On 3rd Quartile Rate Audible On Complete Rate Visible On 1st Quartile Rate Visible On 2nd Quartile Rate Visible On 3rd Quartile Rate Visible On Completion Rate Audible and Visible at 1st Quartile Rate Audible and Visible at 2nd Quartile Rate Audible and Visible at 3rd Quartile Rate Audible and Visible on Complete Rate Audible and Fully On-Screen for Half of Duration Impressions Audible and Fully On-Screen for Half of Duration Rate 3 Sec In-View Impressions 5 Sec In-View Impressions On-Screen Measurable Impressions On-Screen Impressions On-Screen Rate 3 Sec Video In-View Rate 5 Sec Video In-View Rate 1 Sec Fully On-Screen Impressions 1 Sec Fully On-Screen Rate 3 Sec Fully On-Screen Impressions 3 Sec Fully On-Screen Rate In-View Time 2 Sec In-View and Reached Completion Impressions 2 Sec In-View and Reached Completion Rate Audible On 1st Quartile Sum Audible On 2nd Quartile Sum Audible On 3rd Quartile Sum Audible On Complete Sum Visible On 1st Quartile Sum Visible On 2nd Quartile Sum Visible On 3rd Quartile Sum Visible On Completion Sum Audible and Visible on Start Sum Audible and Visible on Start Rate Audible and Visible at 1st Quartile Sum Audible and Visible at 2nd Quartile Sum Audible and Visible at 3rd Quartile Sum Audible and Visible on Complete Sum Audible and 80% On-Screen for Half of Duration (15 sec. cap) Impressions Audible and 80% On-Screen for Half of Duration (15 sec. cap) Rate Audible and Fully On-Screen for Half of Duration (15 sec. cap) Impressions Audible and Fully On-Screen for Half of Duration (15 sec. cap) Rate Audible and Fully On-Screen for Half of Duration (15 sec. cap) with Completion Impressions Audible and Fully On-Screen for Half of Duration (15 sec. cap) with Completion Rate |
| 33) Do you have a specific QA (Quality Assurance) procedure on tag / implementation? | Yes | Yes | Yes |
| a) Do you have a certification program or way to vet signals from MRAID/SDK in mobile apps? | Yes DV has certification processes in place for MRAID and OM SDK enabled partners. For SDK, DV integrates the partner's ad SDK in our testbed app to undergo a series of manual and automated tests that determine the accuracy of the implementation by comparing its results with the expected results. Furthermore, DV performs volume tests with our partners to ensure that the impression counts are aligned and critical benchmarks in measurement and viewability are met. In cases where DV sees a discrepancy, we recommend our partners to implement changes and validate them before confirming them as certified. | Yes | Yes, In addition to the certification performed by IAB Tech Lab for OM SDK implementations, Moat performs QA on OM SDK apps before considering these apps measurable. |
Not accredited solution - Video
Updated April 16th, 2021 | | |
|---|---|---|
| 18) Is your solution compliant with all VAST version? | Yes | Yes |
| a) If no, can you specify which ones your solution supports? | N/A | N/A |
| b) Is your solution compliant with the VPAID wrappers included in VAST wrappers? | Yes | Yes |
| 19) Is your solution compliant with OM SDK? | Yes | Yes |
| 20) Is your solution compliant with MRAID? | Yes | Yes |
| 21) Can you list the sensors/data points your solution uses to measure video viewability? | Adloox does not intend to share this information | OM SDK |
| 22) Do you detect the presence of audio? | Yes | Yes |
| 23) Do you have any limitations on Safari for cross-domain iframe? | N/A | |
| 24) Do you have any limitations on Chrome for cross-domain iframe? | N/A | |
| 25) Do you have any limitations on Android for cross-domain iframe? | N/A | No |
| 26) Do you have any limitations on IOS environments for friendly iframe? | Yes, OM SDK, proprietary SDK or MRAID is required | No |
| 27) Do you have any limitations on IOS environments for non- iframe? | Yes, OM SDK, proprietary SDK or MRAID is required | No |
| 28) Do you have any limitations on Android environments for friendly iframe? | Yes, OM SDK, proprietary SDK or MRAID is required | No |
| 29) Do you have any limitations on Android environments for non- iframe? | Yes, OM SDK, proprietary SDK or MRAID is required | No |
| 30) Does your solution have any other limitations? If yes, could you specify which ones? | Yes, JavaScript is required for Viewability measurement | No |
| 31) Has your solution been accredited by MRC for video viewability measurement? | No | No |
| a) If yes, has your solution been continuously accredited since your first accreditation? | Under review | No |
| b) If no, are you in the process of being accredited by MRC? | No | No |
| 32) Do you provide custom viewability definitions? | Yes, Adloox can provide custom viewability defnition on top of the MRC/IAB one | Yes |
| a) Are your custom viewability definitions compliant with the existing MRC standards? (if yes, specify which custom definitions are compliant) | Yes All | Yes Meetrics' custom definitions are flexible regarding the area and duration thresholds as well as audio criteria. All combinations can be implemented according to the client's needs. The calculation of all these metrics is compliant to the MRC guidelines. |
| b) Have your custom definitions been accredited by MRC? (if yes, specify which custom definitions are accredited) | No | No |
| 33) Do you have a specific QA (Quality Assurance) procedure on tag / implementation? | Yes | Yes |
| a) Do you have a certification program or way to vet signals from MRAID/SDK in mobile apps? | Yes | Yes |