We cover how Permutive collects DFP data on slots rendered and clicked
DFP Event Properties
Permutive can collect data from DFP on the impressions that have been rendered and clicked on the page. Each event contains default data and additional properties about the slot.
Each event contains the following properties:
|Advertiser ID||advertiser_id||Integer||Optional||Unique to campaign, found in DFP|
|Campaign ID||campaign_id||Integer||Optional||Unique to campaign, found in DFP|
|Creative ID||creative_id||Integer||Optional||Unique to the creative, found in DFP|
|Height||height||Integer||Optional||The height of the ad slot in pixels|
|Is empty||is_empty||Boolean||Optional||True of False, slot returned without the creative|
|Line Item ID||line_item_id||Integer||Optional||Unique to campaign, found in DFP|
|Service Name||service_name||String||Optional||Set to 'publisher_ads' if from DFP|
|Slot Ad Unit Path||slot.ad_unit_path||String||Optional||Unique to campaign, found in DFP|
|Slot Slot Element ID||slot.slot_element_id||String||Optional||Unique to campaign, found in DFP|
|Slot Targeting Keys||slot.targeting_keys||List of objects||Optional||Unique to campaign, found in DFP|
|Slot Targeting Keys K ey||slot.targeting_keys.key||String||Optional||Unique to campaign, found in DFP|
|Slot Targeting Key Value||slot.targeting_keys.value||List of Strings||Optional||Unique to campaign, found in DFP|
Slot Clicked (can be used for analytics, segmentation, and targeting)
Permutive collects this event from DFP when the slot has been clicked.
Slot Rendered (can be used for analytics)
Permutive collects this event from DFP when the slot has finished rendering on the page. You can see details on the event being fired from DFP here.
See an example of how to use these events for segmentation here.