Creating passbacks

With a Passback tag, the 3rd-party server will send your request back to AdButler if there is no applicable ad in its service. 3rd Party Ad Servers with real time bidding often have pricing or geographic restrictions that can leave you with a blank ad when no ads are available. Passbacks ensure that you will always be able to serve a fallback.

To use Passbacks tags with AdButler, you'll want to create 2 zones: One to contain your 3rd Party ad tag, and another to contain your backup ads from AdButler and/or another 3rd Party ad server. You'll give this backup ad tag to your 3rd Party ad server to use in case no 3rd party ads are available. You can have multiple Passbacks in a chain.

The picture below is a breakdown of the process. Firstly the ad tag makes a request to AdButler and returns the initial 3rd party ad server (script/tag). The ad tag then makes a request to the 3rd party ad server for an ad. If no ad is available the 3rd party ad server returns the backup tag. The ad tag then makes a request to AdButler using that backup tag, and an ad is returned.

Passback Diagram

When AdButler chooses an 3rd party Ad Network as the ad item of choice, an impression is counted when AdButler delivers the 3rd party ad code to the page. Upon doing so, the ad serving process fully passes over to the Ad Network. If the Ad Network has no applicable ad item, and decides to use the AdButler Passback tag, the Ad Network will make a new request to AdButler. AdButler will respond to the request with an ad, and a new impression will be counted.

Can't find what you're looking for?

Send us an email

Visit the blog

For more ad serving tips, industry news and AdButler insights.