Lazy Loading

Last edited: 2024/12/05

Lazy loading pauses requesting and rendering ads until they approach the user's viewport.

Important notices before you start:

You must remove all existing scripts that handle lazy loading before using either GPT lazy loading or Yieldbird's lazy loading in Viewability Tools. If you do not, it may result in lazy loading not functioning properly or being activated twice.

When you use Viewability Tools’ lazy loading, you shall not use Ad units detection & targeting mode set to Detect ad units on page load and lazy load targeting

Within Viewability Tools, you can use one of the Lazy Loading technologies:

Yieldbird’s Lazy Loading (Recommended, can be enabled or disabled at the Ad Unit level)

Yieldbird’s Lazy Loading is a custom lazy loading technology that allows control at the Ad Unit level.

Google Publisher Tag’s Lazy Loading (Applies to the entire Domain)

This option lazy loads all Ad Units on the Domain and does not support Ad Unit-level customization, including automatic Lazy Loading control.

Google documentation on lazy loading: GPT documentation

Configuration

Regardless of whether you choose Yieldbird’s or Google’s lazy load you can configure the same parameters:

Auction Margin Percent (available only when using Yieldbird’s Prebid Stack) The distance between the user's current viewport and the ad slot at which the Prebid auction is triggered. e.g. 100 = call Prebid auction within 1 viewport, 200, within 2 viewports etc.

Fetch Margin Percent The distance between the user's current viewport and the ad slot at which the ad slot sends ad request to Google Ad Manager. e.g. 100 = fetch slots within 1 viewport, 200 = within 2 viewports etc.
Render Margin Percent The distance between the user's current viewport and the ad slot at which the ad is rendered. e.g. 100 = render slots within 1 viewport, 200 = within 2 viewports etc.

It is recommended to set render margin lower than fetch margin

Render Margin is available only when using Google Publisher Tag (GPT) Lazy Loading. Once the ad request reaches Google Ad Manager, the Yieldbird Platform loses control over it and cannot determine when the ad is rendered.

Mobile Scaling Multiplier for the three above parameters that apply to Mobile devices. e.g. 2.0 means that the three above parameters will be doubled for mobile devices (e.g. if you set render margin percent to 300, for Mobile it will be 600).

It is recommended to set Mobile Scaling higher than 1 (e.g. 2) because generally Mobile viewports are smaller and users are scrolling faster than on Desktop.

On this page:

Lazy Loading
Configuration