Table of Contents
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.
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
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.
Further Reading