Google Ad Manager

How the Google Ad Manager works in FanKit

Google Ad Manager is an ad exchange platform introduced by Google on June 27, 2018.[1] It combines the features of two former services from Google's DoubleClick subsidiary, DoubleClick for Publishers (DFP; formerly known as DART for Publishers) and DoubleClick Ad Exchange (AdX).

To find out more check out Google Ad Manager: Everything You Need To Know

How it works

Each ad is given a unique Google Publisher Tag with a unique Unit Ad Path whose design and display is controlled remotely by the Creator. Creators can control the geographic locations where their ads can be served, so can decide to serve ads in America, Asia, Europe or specific locations (eg London only).

Monterosa do not set geolocation boundaries for Google Ad Serving.

Google ads can be tested and served on any domain including localhost. The terminology used to reference ad slots and paths is as follows

• Unit path (unit code): generated from the ad tag published in the ad management tool by the Customer, example: /1234/TOP_CENTRAL_AD

• Ad unit slot size: example: 350 width, 250 height

• Ad position: where on the page, example: top, bottom or middle

Google Ad Manager in Studio

Creators can access the Google Ad Manager controls inside Projects that support Google Ad Manager integration within the Display Modes area of an Event. There are four "modes" on the tab where a Creator can set up and edit the Google Ad display ads: Card, Timeline, Tabs and Hub.

Containers for ads to display inside can be defined in Tab and Hub mode.

Card Mode: Optimised for Google Ad Manager, enter here the unit path which would be the unit code generated from the ad tag published in the Ad management tool (e.g. /1234/TOP_CENTRAL_AD), the ad unit slot size (e.g. 350 width, 250 height) and finally, the position of the ad on this page which can be at the top or bottom of the page in this mode

Timeline Mode: Optimised for Google Ad Manager, enter here the unit path which would be the unit code generated from the ad tag published in the Ad management tool (e.g. /1234/TOP_CENTRAL_AD), the ad unit slot size (e.g. 350 width, 250 height) and finally, the position of the ad on this page which can be at the top or bottom of the page

Configurable options

Within Studio you can configure the following:

• Unit Path: Unique name of the ad. Example: /87687331/RES_MAIN_FIXTURES

• Position: Where the advert sits on the page

• Display as Element: Publish specific Ad Unit Path within a feed as an Element (not yet available, roadmap)

• Default slot width: Input the default width of the ad position

• Default slot height: Input the default height of the ad position

• Size Mapping: Aad dimensions and type of ad displayed will change if configured within Studio to be appropriate to the window space

Unique ad unit path per position

Only the number of adverts assigned to a specific ad unit path will be displayed on the page. Google Published Tag library does not render random or repeated adverts if all existing adverts have been displayed.