Ad Verification

Third party ad verification including Google DFA

Third Party Ad Verification

Mixberry’s third party ad verification is based on IAB’s 2005 common guidelines for both US and International standards.

The implementation is based on what is referred to a “beacon” or “clear pixel” image. This image is served from the advertiser’s third party ad verification company, giving them the ability to count the number of ads served in addition to typically capturing certain information from the user’s environment and generating reports.

Advertiser Implementation for Mixberry Media

In order to utilize Mixberry’s third party ad verification feature, the advertiser must provide the clear pixel or beacon URL to Mixberry. This URL should be provided from the Advertiser’s third party verification company. The advertiser would typically specify certain parameters to define the ad being tracked and the ad verification company will then provide the advertiser with an HTML image tag based on the parameters that the advertiser entered.

In the Mixberry advertiser portal, the advertiser will include the HTML tag provided for the specific ad they set up. The formats that are generally provided could look like any of the following:
http://ad_verification_url/?a=b&c=d ...
https://ad_verification_url /?a=b&c=d ...
<img src="http://ad_verification_url/?a=b&c=d ..." height="1" width="1">

Within Mixberry’s portal, based on the examples above, the advertiser should enter: advertiser_url/?a=b&c=d… If the advertiser entered either “http://” or “https://”, Mixberry will automatically remove these. As ads are being heard on the publisher sites, Mixberry will add the “http://” or “https://” to match publishers’ site requirements.

According to IAB’s guidelines:

“Delivery of a “beacon”, which may be defined as any piece of content designated as a tracking asset. Beacons will commonly be in the form of a 1x1 pixel image, but the Guideline does not apply any restrictions to the actual media-type or content-type employed by a beacon response.”

Since audio ads do not contain HTML viewable code, Mixberry implements a separate clear pixel to be served with the audio ad content.

Mixberry’s implementation is based on generic standards and not any particular third party ad verification company.