Viewability Grid
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
[tabby title=”Accredited – Display” icon=”fa fa-check-circle-o”]
![]() Updated October 11th, 2019 | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
---|---|---|---|---|---|---|
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, browser optimization method, specific browser APIs | 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 | JS tag ,geometric method, browser optimization method |
2) Is your solution compliant with OM SDK? | ||||||
3) Is your solution compliant with MRAID? | ||||||
4) Do you measure expandable formats? | Yes | 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) | Expandable rich media ads are measured based on the placement of the vCE JavaScript tag. If the user places the vCE JavaScript with the unexpanded portion of the ad, Comscore measures the unexpanded ad. However, if the user places the JavaScript tag within expanded portion of the ad, the expanded portion is measured | 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 and the switch that enables the expansion, then needs to write a custom logic to measure the unit. |
5) Do you measure Page Take-over ads? | Yes | Yes | Yes | Yes | Yes | Yes |
a) If yes, do you measure each component of the page takeover separately? | Yes | Yes | 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 | A home page takeover involving several different creatives/payloads would also require individual tagging/measurement of the constituent ads. This is consistent with industry standards (MRC, JICWEBS, IAB Pan-European Viewability Guidelines). If the client wished to combine the results and/or transact on the basis of various combinations of different ads, they are free to do so but each creative unit would still have to be measured separately. | 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. | Viewability of this format is reported as all other formats within our UI and reports. If the ads are measured independently, viewability will be determined for each component individually. If the takeover is treated and sold as a unit, the components have to be jointly loaded and viewable (with at least the defined amount of area and defined amount of time) to be counted as a viewable impression. It is possible to measure them as one object, if requested. | 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 | Measurement for slide in ads is the same as any other banner ad. The ad is considered to be in view only when it slides into view (and meets the standard criteria). Viewability measurement tech is no different than non-slide-in ads. | 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, | Yes. | No | Yes, | Yes, | No |
8) Do you have limitation on Chrome for cross-domain iframe? | Yes, | No limitation on the desktop environment. | No | No | Yes, | No |
9) Do you have limitation on Android for cross-domain iframe? | Yes, | No limitation on the desktop environment. | No | No | No | No |
10) Do you have limitation on IOS environments for friendly iframe? | No | No | No | No | No | No |
11) Do you have limitation on IOS environments for non- iframe? | No | No | No | No | No | No |
12) Do you have any limitations on Android environments for friendly iframe? | No | No | No | No | No | No |
13) Do you have any limitations on Android environments for non- iframe? | No | No | No | No | No | No |
14) Does your solution have any other limitations? If yes, could you specify which ones? | Yes, | Yes. | 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, | Yes, | Yes, |
15) Has your solution been accredited by MRC for display viewability measurement? | Yes | Yes | Yes | Yes | Yes | Yes |
a) If yes, has your solution been continuously accredited since your first accreditation? | Yes | Yes | Yes | Yes | Yes | Yes |
b) If no, are you in the process of being accredited by MRC? | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
16) Do you provide custom viewability definitions? | Yes, | Yes, | Yes, | Yes | Yes | Yes |
a) Are your custom viewability definitions compliant with the existing MRC standards? (if yes, specify which custom definitions are compliant) | Yes, | Yes | Yes | Yes, | Yes | Yes, |
b) Have your custom definitions been accredited by MRC? (if yes, specify which custom definitions are accredited) | Yes | No | Yes, | No | No | Yes, |
17) Do you have a specific QA (Quality Assurance) procedure on tag / SDK implementation? | Yes | Yes | Yes | Yes | Yes | Yes |
a) Do you have a certification program or way to vet signals from MRAID/SDK in mobile apps? |
[tabby title=”Accredited – Video” icon=”fa fa-check-circle-o”]
![]() Updated October 11th, 2019 | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
---|---|---|---|---|---|---|
18) Is your solution compliant with all VAST version? | Yes | Yes | Yes | Yes | Yes | Yes |
a) If no, can you specify which ones your solution supports? | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
b) Is your solution compliant with the VPAID wrappers included in VAST wrappers? | Yes | Yes | Yes | Yes | Yes | Yes |
19) Is your solution compliant with OM SDK? | ||||||
20) Is your solution compliant with MRAID? | ||||||
21) Can you list the sensors/data points your solution uses to measure video viewability? | Adloox does not intend to share this information | Geometric method, browser optimization method, specific browser APIs, JS, Comscore Plug-In (AS3 and HTML5), VPAID Wrapper, Custom integrations. tag. | 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. | Geometric approach, rendering approach, browser optimization | Moat VPAID tag |
22) Do you detect the presence of audio? | No (planned for Q4 2019) | Yes | Yes | Yes | Yes | Yes |
23) Do you have any limitations on Safari for cross-domain iframe? | Yes, | Yes, | No | Yes, | Yes, | No |
24) Do you have any limitations on Chrome for cross-domain iframe? | Yes, | No limitation on the desktop environment. | No | No | Yes, | No |
25) Do you have any limitations on Android for cross-domain iframe? | Yes, | No limitation on the desktop environment For Mobile Browser viewability measurement, in older versions of Chrome (<51), the comScore UDM or another vCE Tag in a no-iFrame ad must be present to enable cross domain viewability measurement. For Chrome 51+, Comscore uses the IntersectionObserverAPI to measure viewability. | No | No | No | No |
26) Do you have any limitations on IOS environments for friendly iframe? | No | No | No | No | No | No |
27) Do you have any limitations on IOS environments for non- iframe? | No | No | No | No | No | No |
28) Do you have any limitations on Android environments for friendly iframe? | No | No | No | No | No | No |
29) Do you have any limitations on Android environments for non- iframe? | No | No | No | No | No | No |
30) Does your solution have any other limitations? If yes, could you specify which ones? | Yes, | Yes. | Yes, | Yes | Yes, | Yes, |
31) Has your solution been accredited by MRC for video viewability measurement? | Yes | Yes | Yes | Yes | Yes | Yes |
a) If yes, has your solution been continuously accredited since your first accreditation? | No | Yes | Yes | Yes | Yes | Yes |
b) If no, are you in the process of being accredited by MRC? | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable | Not applicable |
32) Do you provide custom viewability definitions? | Yes, | Yes, | Yes, | Yes | Yes | Yes |
a) Are your custom viewability definitions compliant with the existing MRC standards? (if yes, specify which custom definitions are compliant) | Yes | Yes | Yes | Yes , | Yes | Yes, |
b) Have your custom definitions been accredited by MRC? (if yes, specify which custom definitions are accredited) | No | No | Yes, | No | No | Yes, |
33) Do you have a specific QA (Quality Assurance) procedure on tag / implementation? | Yes | Yes | Yes | Yes | Yes | Yes |
a) Do you have a certification program or way to vet signals from MRAID/SDK in mobile apps? |
[tabby title=”Not accredited – Display” icon=”fa fa-circle-o”]
No measurement company have a not accredited solution.
[tabby title=”Not accredited – Video” icon=”fa fa-circle-o”]
No measurement company have a not accredited solution.
[tabbyending]
In-app environment
[tabby title=”Accredited – Display” icon=”fa fa-check-circle-o”]
![]() Updated October 11th, 2019 | ![]() | ![]() | ![]() | ![]() |
---|---|---|---|---|
1) Can you list the sensors/data points your solution uses to measure display viewability? | MRAID 2.0 or higher, geometric method and browser APIs, OM SDK, Comscore SDK | OM SDK or MRAID | OM SDK, AVID SDK, or MRAID | JS tag, with OM SDK or Moat SDK |
2) Is your solution compliant with OM SDK? | Yes | Yes | Yes | Yes |
3) Is your solution compliant with MRAID? | Yes | Yes | Yes | Yes (however MRAID can only be used for viewability in some circumstances, and once we have vetted the signal implementation individually, as it can be unreliable) |
4) Do you measure expandable formats? | 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)? | Expandables are atypical in-app but Comscore measures viewability of the creatives which are tagged in apps in the same manner as done when they are delivered in web environments. The key difference is that the Comscore SDK, MRAID or (since late February 19) OM SDK must be instrumented to support the measurement. | 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 and the switch that enables the expansion, then needs to write a custom logic to measure the unit. |
5) Do you measure Page Take-over ads? | Yes | Yes | Yes | Yes |
a) If yes, do you measure each component of the page takeover separately? | Yes | Yes | Yes | Yes |
b) If yes, how do you report page takeover viewability? | A home page takeover involving several different creatives/payloads would also require individual tagging/measurement of the constituent ads. This is consistent with industry standards (MRC, JICWEBS, IAB Pan-European Viewability Guidelines). If the client wished to combine the results and/or transact on the basis of various combinations of different ads, they are free to do so but each creative unit would still have to be measured separately. | 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)? | Measurement for slide in ads is the same as any other banner ad. The ad is considered to be in view only when it slides into view (and meets the standard criteria). Viewability measurement tech is no different than non-slide-in ads. | 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? | ||||
8) Do you have limitation on Chrome for cross-domain iframe? | ||||
9) Do you have limitation on Android for cross-domain iframe? | ||||
10) Do you have limitation on IOS environments for friendly iframe? | Yes, | Yes, | Yes, | Yes, |
11) Do you have limitation on IOS environments for non- iframe? | Yes, | Yes, | Yes, | Yes, |
12) Do you have any limitations on Android environments for friendly iframe? | Yes, | Yes, | Yes, | Yes,
|
13) Do you have any limitations on Android environments for non- iframe? | Yes, | Yes, | Yes, | Yes, |
14) Does your solution have any other limitations? If yes, could you specify which ones? | Yes. | No | No | No |
15) Has your solution been accredited by MRC for display viewability measurement? | Yes | Yes | Yes | Yes |
a) If yes, has your solution been continuously accredited since your first accreditation? | Yes | Yes | Yes | Yes |
b) If no, are you in the process of being accredited by MRC? | Not applicable | Not applicable | Not applicable | Not applicable |
16) Do you provide custom viewability definitions? | Yes, | Yes, | Yes | Yes |
a) Are your custom viewability definitions compliant with the existing MRC standards? (if yes, specify which custom definitions are compliant) | Yes | Yes | Yes, | Yes, |
b) Have your custom definitions been accredited by MRC? (if yes, specify which custom definitions are accredited) | No | No | No | Yes, |
17) Do you have a specific QA (Quality Assurance) procedure on tag / SDK implementation? | Yes | Yes | Yes | Yes |
a) Do you have a certification program or way to vet signals from MRAID/SDK in mobile apps? | Yes | Yes | Yes | Yes, |
[tabby title=”Accredited – Video” icon=”fa fa-check-circle-o”]
![]() Updated October 11th, 2019 | ![]() | ![]() | ![]() | ![]() |
---|---|---|---|---|
18) Is your solution compliant with all VAST version? | Yes | Yes | Yes | Yes |
a) If no, can you specify which ones your solution supports? | Not applicable | Not applicable | Not applicable | Not applicable |
b) Is your solution compliant with the VPAID wrappers included in VAST wrappers? | Yes | Yes | No | Yes |
19) Is your solution compliant with OM SDK? | Yes | Yes | Yes | Yes |
20) Is your solution compliant with MRAID? | Yes | Yes | Yes | Yes (however MRAID can only be used for viewability in some circumstances, and once we have vetted the signal implementation individually, as it can be unreliable). |
21) Can you list the sensors/data points your solution uses to measure video viewability? | MRAID, Comscore SDK, OM SDK | Industry-standard APIs such as VPAID, MRAID and OM SDK OMID API. | AVID SDK, OM SDK | Moat SDK, OM SDK |
22) Do you detect the presence of audio? | Yes | Yes | Yes | Yes |
23) Do you have any limitations on Safari for cross-domain iframe? | ||||
24) Do you have any limitations on Chrome for cross-domain iframe? | ||||
25) Do you have any limitations on Android for cross-domain iframe? | ||||
26) Do you have any limitations on IOS environments for friendly iframe? | Yes, | Yes, | Yes, | Yes, |
27) Do you have any limitations on IOS environments for non- iframe? | Yes, | Yes, | Yes, | Yes, |
28) Do you have any limitations on Android environments for friendly iframe? | Yes, | Yes, | Yes, | Yes, |
29) Do you have any limitations on Android environments for non- iframe? | Yes, | Yes, | Yes, | Yes, |
30) Does your solution have any other limitations? If yes, could you specify which ones? | Yes. | No | No | No |
31) Has your solution been accredited by MRC for video viewability measurement? | Yes | Yes | Yes | Yes |
a) If yes, has your solution been continuously accredited since your first accreditation? | Yes | Yes | Yes | Yes |
b) If no, are you in the process of being accredited by MRC? | Not applicable | Not applicable | Not applicable | Not applicable |
32) Do you provide custom viewability definitions? | Yes, | Yes, | Yes | Yes |
a) Are your custom viewability definitions compliant with the existing MRC standards? (if yes, specify which custom definitions are compliant) | Yes | Yes | Yes, | Yes, |
b) Have your custom definitions been accredited by MRC? (if yes, specify which custom definitions are accredited) | No | No | No | Yes, |
33) Do you have a specific QA (Quality Assurance) procedure on tag / implementation? | Yes | Yes | Yes | Yes |
a) Do you have a certification program or way to vet signals from MRAID/SDK in mobile apps? | Yes | Yes | Yes | Yes, |
[tabby title=”Not accredited – Display” icon=”fa fa-circle-o”]
![]() Updated October 11th, 2019 | ![]() | ![]() |
---|---|---|
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 | Viewability of this format is reported as all other formats within Meetrics UI and reports If the ads are measured independently, viewability will be determined for each component individually. If the takeover is treated as a unit, the components have to be jointly loaded and viewable (with at least the defined amount of area and defined amount of time) to be counted as a viewable impression. |
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? | ||
8) Do you have limitation on Chrome for cross-domain iframe? | ||
9) Do you have limitation on Android for cross-domain iframe? | ||
10) Do you have limitation on IOS environments for friendly iframe? | Yes, | Yes, |
11) Do you have limitation on IOS environments for non- iframe? | Yes, | Yes, |
12) Do you have any limitations on Android environments for friendly iframe? | Yes, | Yes, |
13) Do you have any limitations on Android environments for non- iframe? | Yes, | Yes, |
14) Does your solution have any other limitations? If yes, could you specify which ones? | Yes, | Yes, |
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? | Not applicable | Not applicable |
b) If no, are you in the process of being accredited by MRC? | No (planned 2020 when OM SDK is fully deployed) | No, planned in 2019 |
16) Do you provide custom viewability definitions? | Yes, | Yes |
a) Are your custom viewability definitions compliant with the existing MRC standards? (if yes, specify which custom definitions are compliant) | Yes, | Yes |
b) Have your custom definitions been accredited by MRC? (if yes, specify which custom definitions are accredited) | No | 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? | Adloox does not intend to share this information | Yes, |
[tabby title=”Not accredited – Video” icon=”fa fa-circle-o”]
![]() Updated October 11th, 2019 | ![]() | ![]() |
---|---|---|
18) Is your solution compliant with all VAST version? | Yes | Yes |
a) If no, can you specify which ones your solution supports? | Not applicable | Not applicable |
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? | No (planned for Q4 2019) | Yes |
23) Do you have any limitations on Safari for cross-domain iframe? | ||
24) Do you have any limitations on Chrome for cross-domain iframe? | ||
25) Do you have any limitations on Android for cross-domain iframe? | ||
26) Do you have any limitations on IOS environments for friendly iframe? | Yes, | Yes, |
27) Do you have any limitations on IOS environments for non- iframe? | Yes, | Yes, |
28) Do you have any limitations on Android environments for friendly iframe? | Yes, | Yes, |
29) Do you have any limitations on Android environments for non- iframe? | Yes, | Yes, |
30) Does your solution have any other limitations? If yes, could you specify which ones? | Yes, | Yes, |
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? | Not applicable | Not applicable |
b) If no, are you in the process of being accredited by MRC? | No | No, planned in 2019 |
32) Do you provide custom viewability definitions? | Yes, | Yes |
a) Are your custom viewability definitions compliant with the existing MRC standards? (if yes, specify which custom definitions are compliant) | Yes | Yes |
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? | Adloox does not intend to share this information | Yes, |
[tabbyending]