Use passbacks to traffic remnant line items (legacy DFP)
For information on creating a passback using Google Publisher tags (GPT), see this help article.
If you are using legacy DART tags, you must re-tag using Google Publisher Tags (GPT) to ensure seamless ad serving on your site(s). Learn more
Passback line items are used with third-party advertisers for a number of reasons. Primarily, passback line items return a house ad or other remnant ad within DFP when the third party doesn't have an ad to serve or when this ad doesn't meet the minimum CPM agreed upon with the third party.
Before beginning this process, you should have generated a legacy passback ad tag in DFP to which remnant or house inventory is targeted. The third party should then take this ad tag and traffic it in their network as the lowest-priority ad, one that will serve if no eligible ads are found.
How to set up a passback with legacy DFP tags
You have two different options for setting up a passback:Set up passback line items using a unique ad unit
To use a unique ad unit solely for passback trafficking:
Create an ad unit to be used when a passback is served. (Learn how to create ad units)
Mark the ad unit as ‘special’ so that it must be explicitly targeted by line items. (Learn more about special ad units)
Marking the ad unit as 'special' ensures that no untargeted line items will serve to this ad unit.
Target all remnant line items to this ad unit. Ensure that none of these line items contain creatives with third-party redirect code, as this can result in an infinite loop of server calls.
Create a tag that will be passed back to DFP in case the third party doesn't have any remnant line items. Include the 'special' ad unit you just created in that tag. Give this tag to your third party to traffic as the lowest-priority eligible ad in their network.
When this tag is passed back to DFP, only the remnant line items you specifically targeted to the 'special' ad unit will be eligible to serve to it.
If you'd like to set up passback line items without using a dedicated ad unit, try the following approach, which uses key-value pairs:
Create a unique key with two different values to be used when a passback is served.
For example, you could create a 'Redirect' key with the values 'true' and 'false':
Target all of your remnant line items against both values using an
red=false OR red=true
This ensures that your remnant line items will be eligible to serve to both of the ad tags you'll be creating below. (Learn how to apply targeting criteria to a line item)
Target the line items that will redirect to the third-party ad network only to the key-value
Make sure the ad tag on your page contains the key-value
red=false. This will be the first ad request to DFP.
Both your remnant line items and the line items that will redirect to the third-party ad server will be eligible to serve to this ad tag.
Create an ad tag that includes only the key-value
red=trueand give it to your third party to traffic as the lowest-priority eligible ad in their network. This ad tag will be passed back to DFP if the third party doesn't have any remnant ads. This will be the second and final ad request to DFP.
Only your remnant line items will be eligible to serve to the ad tag passed back to DFP.
More informationHow passback ad serving works
Below is a diagram of how passbacks work in DFP, which is useful for understanding this process.
A page makes an ad request to DFP for an ad using the DFP ad tag on the page.
DFP returns a line item containing third-party code.
The page uses the third-party code to make a request to a third-party ad server.
Non-passback scenario: If a matching ad is available, an ad is served from the third-party ad server.
If no matching ad is available on the third-party ad server, the server returns (i.e. passes back) the DFP ad tag that you have provided your third party.
The page makes a second ad request to DFP using the passback tag contained in the third-party ad.
A house ad or other specifically targeted line item is returned from DFP.
To avoid looping, you must take the appropriate steps when using passbacks to make sure that the subsequent ad requests that are passed-back from the third-party ad server to DFP are unique and therefore do not call that same third party for an ad. Looping happens when steps 3-6 in the diagram above repeat indefinitely, which can cause your web page not to load properly.
We suggest using one of the following strategies to ensure that all ad requests used in the passback are unique:
- Use a unique ad unit just to handle passbacks.
- Use a unique key-value to handle passbacks.
We do not recommend using passbacks for the purposes of daisy chaining. In this process, you’ll call to DFP for an ad and DFP will return a third-party redirect; if the third party doesn’t have an ad, it will passback the ad call to DFP, which will then call to a different third party for an ad. This process continues until an ad, rather than a passback tag, is returned by a third party. Lining up several third-parties like this to try to fill inventory in order to get the highest CPM from competing networks is called a daisy chain of ad calls.
Daisy chaining is not recommended for several reasons. It can increase discrepancies between DFP and the third party; daily discrepancies of up to 20% are considered normal for each link in the daisy chain, and these discrepancies can quickly compound. This setup can also increase the probability of looping. Moreover, because you’re charged for each call to the DFP server, daisy chaining can increase your costs.
In addition to DFP, AdSense and Ad Exchange can provide your network with remnant ads that have greater value than ads served using passback method.
With AdSense and Ad Exchange, you can control delivery via a minimum CPM at a given priority range. For example, if you have Adsense/Ad Exchange competing at priority 12, and other ads at that priority have a .25 CPM value, DFP would only serve these ads if they can deliver a higher value impression.