DFP Destination Requirements

Standards for code placement, supported key-value formats, reports, and the type of segment data sent to DFP.

Requirements

This destination type requires the following:

DIL: Data Integration Library code should be deployed on your inventory. DIL helps eliminate the need to write special code for data collection, integration, reading cookie values, and recovering page data.

Note: If you're a customer of Audience Manager and Analytics, using Server-Side Forwarding, you don't need to place DIL code on your inventory. The Audience Manager module, deployed together with AppMeasurement, replace DIL and support the DFP functionality.
get_aamCookie Function: Code that captures the Audience Manager user ID and cookie data. Place this code on the top of the page or inside the <head> code block.
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.

Cookie Format and Key-Value Data

Audience Manager can send segment data to a browser cookie as follows:

Single keys (x=1&x=2).
Multiple keys (x=1&x=2&y=3&y=4).
Serialized values (x=1,2,3)
A standard value delimiter separates individual key-value pairs.

Only Qualified Segments are Sent to DFP

The amount data passed in to DFP 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 DFP (not all 100).