Information about the article or collection is passed in the ad request. This enables targeting via taxonomy using key value pairs, which you set up in your Google's Ad Manager. For example, the section, author, edition can all be passed as targeting information to GAM, allowing you granular control over which ads are served where without having to set up many specific ad units in the CMS. This requires no additional set up on the Pugpig side.

For slot-level and page-level targeting the key-values are combined and only ads satisfying all criteria will be eligible to serve to a given slot. If the same key is used in slot-level and page-level targeting the slot-level value will take precedence.

Article Page

Page-Level

platform: This is always set to app

site: This is always set to mobile

collection_tag: This is a list of all collection tags taxonomies (not the collection it is displayed in) on the article. The values are slugs

sections: This is a list of all sections on the article. The key is plural. The values are slugs

contributors: This is a list of all contributors on the article. The values are slugs

Custom taxonomies will be sent if they exist on the article. 

Additional custom tags can be sent if necessary. Please speak to support if required. 

Slot-Level

position: This can be Top Banner or In Article. Top banner is used for the lead top banner advert that appears at the very top of the page. In Article is used for all other inline adverts.

pos: This is the position of the ad on the page. First ad will be 1, second will be 2 etc. This can be used to target different MPU placements in-article. 

refresh_count: This is the number of times the ad has been refreshed and will increment provided that the ad refresh setting has been configured.

Additional custom tags can be sent if necessary. Please speak to support if required. 

Timeline

Page-Level

None. Currently each page-level target is defined at slot-level.

Slot-Level

platform: This is always set to app

site: This is always set to mobile

position: This is always set to timeline

collections: This is the timeline the ad appears on. The key is plural. The value is a slug i.e a timeline named `TV and Film` would become tv-and-film

os: This is set as one of android, ios or web

Custom taxonomies will be sent if they exist on the Google Ad card.

Additional custom tags can be sent if necessary. Please speak to support if required. 

Interstitial

Page-Level

content_type: This is always set to fullpage

platform: This is always set to app

site: This is always set to mobile

os: This is set as one of android, ios or web

page: This is the page number where the interstitial is injected (e.g. if the interstitial placement setting is configured to be injected after page 10 then the value sent will 11)
 

Slot-Level

position: This is always set to fullscreen

Further Reading

Key-Value Targeting