GPT Destination Requirements

Requirements and related information about setting up Google Publisher Tags (GPT) as an Audience Manager destination.

Consider the following points when you want to set up GPT as an Audience Management destination:
  • Add DIL: Deploy Data Integration Library (DIL) code on all the pages you want to target. DIL writes Audience Manager segment data and user IDs to cookies that get used by GPT for targeting.
  • Create a Cookie Destination: GPT must be set up as a cookie-based destination in Audience Management.
  • Implement Cookie Checking Code: Wrap the GPT .setTargeting API method in our recommended cookie checking code. This code helps prevent errors by looking for valid AAM cookies before the .setTargeting method gets invoked.
  • Add the AamGpt Function: The AamGpt code captures data from Audience Manager cookies and sends it to GPT. Place the Audience Manager Code for Google Publisher Tags (AamGpt) at the top of the page or inside the <head> codeblock.
    Note: The AamGpt function is not required if you use your own code to read Audience Manager cookie data.
  • Send Delivery Logs to Audience Manager: If you want a segment delivery report (optional), provide Audience Manager with a daily log that contains impression-level delivery data. The data can be in a raw format, but each record must contain the Audience Manager UUID. Audience Manager can pick up or receive these via FTP.

Only Qualified Segments are Sent to GPT

The amount of data passed in to GPT depends on how many segments a particular user qualifies for. For example, say you set up 100 Audience Management segments. If a site visitor qualifies for five of them, then only those five segments get sent to GPT (not all 100).

Note: There are no limits to the number of key-values you can send, but the Google request URL does have limits to the number of characters it can accept. See Setting targeting and sizes with GPT.