How to book interstitials in your web solution in Google Ad Manager

2024-10-13 17:43:21 UTC

This guide will go through the basics of booking image interstitials in Google Ad Manager in your ePaper solution for web.

If you are not familiar with booking ads in Google Ad Manager (e.g. on your website), we recommend you to book through the Visiolink Publishing Hub instead. Implementing Google Ads interstitials will disable the possibility to book from the Visiolink Publishing Hub.

 

1. Create Ad units   

You can place up to five fixed ad positions in your ePaper. In addition, you can create a frequency controlled position that is displayed dependent on the number of swipes the user makes. As a default this is set to 12 swipes. The number can be set in the Visiolink Publishing Hub. 

The fixed positions are placed after a page number in the publication. You can place them e.g. after page 1, after page 5 and after page 9. The page numbers must be odd numbers. The frequency position works fine with the fixed positions, as it will simply be shown X number of swipes after any ad has been displayed.

In addition, Vitec Visiolink supports several Key-values ("Customised targeting") for differentiating between titles if you have more titles in the same app and for targeting a specific issue of a publication. Please see "Key-value targeting" further below.

 

2. Book Creatives in your preferred size

As a default, we support all the most relevant standard sizes available in Google Ad Manager. Below, we have listed our recommendations. 

NB! On web, the "Visiolink Native Template" is not supported. Instead you can use the 1x1 size to book any ad size if you check the box "Allow creative size to differ from ad unit size". 

 

The following list is the full span of ad sizes supported in the web reader: 


1024x768: Recommended for best ratio between size and speed of execution. 
2048x1436
640x480
768x1024
1436x2048
580x400
480x320
400x300
336x280
320x480
300x600
300x250
250x250


If more than one ad is booked on the same placement, the ads will be rotated to display the ads evenly.

Empty Ad units will be ignored, so that the user swipes to the next page (there might be a short delay when swiping past an empty Ad unit, as we will need to ask the Ad unit if there are any ads booked). 

NOTE: As the web reader is seen as a single page system by Google, it is not possible to book the same ad on two different Ad units at the same time. Google will prevent the ad on one of the Ad units to be shown. If you wish to book an ad to be shown on more than one position, please use the frequency controlled position. 

3. Provide Visiolink with Account ID and Ad unit codes

Vitec Visiolink will need an overview of which Ad units should be placed after which pages Furthermore, we need the account ID of your Google Ad Manager account.

Both Account ID and Ad unit code can be found in your GAM account:

 

Account ID

You find the Account ID in the left panel at the top. The number written under the name of your account is your Account ID:

 

Ad unit code

Selecting "Ad units" under "Inventory" in the left panel will open an overview of all your Ad units. For each Ad unit you can see the Ad unit code:

 

Example:

Account ID 263413259
Placements Page 5 Page 11 Page 17 Frequency
Ad unit codes page5 page11 page17 freq

 

 

Key-value Targeting

We also have support for key-values. When creating your Line Item you can choose to target these key-values. Key-value are created under "Inventory" → "Key-values".

inventory_key_value.png

1. folderID: This gives you the opportunity to target a specific folder with the "folderID"
from the Visiolink Publishing Hub. When you target ("is any of") a specific "folderID", the ad will only be shown in the specific title.

NB: The key must be created precisely like this: "folderID" and with correct value.

2. pubdate: This gives you the opportunity to target a specific issue based on the date of the publication. When you target ("is any of") a specific "pubdate", the ad will only be shown in issues with this publication date.

NB: The key must be created precisely like this: "pubdate" and values must be written as dates in this format: YYYY-MM-DD (e.g. 2024-04-24)

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments