HVR smartly reloads ad units on the page, creating new inventory on the website without the publisher having to add more ad units. This new inventory has a higher viewability than regular ad units resulting in higher eCPM.
Publishers generally see an additional revenue of 15-30%.
HVR works best when websites have users spending some time and interacting with the content of the page.
HVR refreshes a DFP (Google Admanager) or Adsense or Adx ad unit with an Affinity ad unit only when certain conditions are met:
- The Publisher's ad unit has already been viewed.
- 30 seconds have passed since the Publisher's ad unit has been viewed.
- Publisher's ad unit is being viewed on the page i.e.:
- In the user's viewport
- On an active tab
It is mutually agreed by the Publisher and Yield Solutions.
No. HVR only refreshes the publisher's ad unit after 30 seconds from the time it is visible on the page. Hence, the publisher's line items will not be affected in any way.
Yield Solutions will provide a simple javascript which has to be placed on the head section of the website. This code can be either hardcoded or called through one by one (1x1) pixel.
Hardcoding works much better than calling via DFP as it allows the HVR code to detect exactly when the viewability pixel is fired by DFP. The javascript should be placed before the
</head> html tag of the page:
Publishers can also use their adserver to call the tag by creating a 1x1 ad unit and placing the Invocation script in the creative for that 1x1 ad unit (Please disable safe frame for the creative). Example of a DFP 1x1 ad unit:
Note: Only one java script will be provided per website.
No. HVR works on regular IAB ad sizes (i.e. 300x250, 728x90, 970x250, 320x100, 320x50, etc). HVR will not work for non-standard ad sizes like 1x1.
In case the Publisher is using multi-size ad units, HVR can be configured to use a particular set of sizes.
For example:
Publishers ad unit calls for - 980x260, 970x250, 970x90, 728x90, 728x250.
HVR for this ad unit can be configured for - 970x250, 970x90, 728x90.
Yes. Publishers can provide a blacklist of ad units for HVR.
Yes, publishers will have control to enable and disable HVR via the publisher console. Publishers would generally like to deactivate HVR when they have a roadblock campaign.
Some publishers do not want to refresh a unit which serves a particular direct campaign. In this case, Yield Solutions can provide a creative template code which the publisher can use to pass a "Do Not Refresh" signal to the HVR code.
Place the html comment <!--NO_REFRESH--> within the creative.
Yes. We can call the following products via the same HVR code without the publisher changing the code.
Publishers will see a single line in their In-Pages stats within the Publisher Console, which will provide total impressions and revenue.
Visit our website
yieldsolutions.com, then click on the Sign Up section and share your credentials using the available form OR you can send us an email to
community@yielsolutions.comIf you didn’t find the answer to your question here or you have anything in specific, please send us an email to community@yielsolutions.com or share your details using contact us form and we’d be glad to assist you.
