Ads.txt for Demand Partners

Last updated on August 7, 2017

Proposed by the Interactive Advertising Bureau (IAB), ads.txt is an initiative which aims to improve transparency for the world of programmatic advertising by enabling content owners to specify which advertising systems and resellers are authorized to sell their inventoryAd space available on a website or app. The basic unit of inventory for OpenX is an ad unit..

Adoption of ads.txt can help prevent domain spoofing and the sale of unauthorized inventory by providing a simple way for demand-side platforms (DSPs) to check if inventory from a particular source has been authorized for sale by the domain owner.

You can learn more by reading the following IAB topics:

Benefits

  • Increased transparency.

  • Decreased revenue for fraudsters.

  • Certainty that inventory you purchase from a given domain is being offered by authorized sellers.

Requirements

In order to ingest data from an ads.txt file, you must have a crawler that is capable of checking ads.txt files of the domains found in bid requests.

Ads.txt format

Each line is formatted as follows:

 Domain Name of the Advertising System, OpenX Account ID, TYPE OF ACCOUNT/RELATIONSHIP, (Optional) Certification Authority ID

In this live example, the publisherAn account type that represents a business with ad space to sell. has two OpenX accounts: https://docs.openx.com/ads.txt

Important: The OpenX Account ID in the ads.txt file should match the Publisher object's id attribute in the bid requestWhen OpenX Ad Exchange receives an ad request, it sends a communication containing details about the impression to selected real-time bidders to solicit bids for it..

  • The first line of the example illustrates that the publisher is using OpenX directly, with an OpenX Account ID of 123456789.

  • The second line of the example shows the publisher authorized another entity as a reseller of the ad space. That entity has an OpenX Account ID of 987654321.

Interacting with ads.txt

Below is a high level overview of the process of interacting with an ads.txt file. Please refer to the IAB Tech Lab Ads.txt Specification Version 1.0 and Partner Interaction Guide for ads.txt Specs for additional information.

  1. Via a crawler, check the ads.txt file of the domains found in the bid requests you receive.

    Tip: The IAB provides a reference implementation of an ads.txt data crawler in their GitHub repository.

  2. Download the ads.txt file and update your own internal database based on the information within ads.txt.

  3. Update your buying algorithm accordingly.

  4. Assess the bid requests you receive. If there is no match between the Publisher object's id attribute in the bid request and the authorized sellers listed in the ads.txt file, do not buy the inventory.

    The image below shows an example of where to find the Publisher object's id attribute in the bid request.

    Shows an example of where to find the Publisher object's "id" attribute in the bid request

Interpretation of server responses

When the ads.txt file is present, you need only read the content, parse it, and obey the declarations. When no ads.txt file is present, the IAB Tech Lab Ads.txt Specification Version 1.0 recommends the following:

Status Code Resource Status DSPDemand-side platform, a platform or provider that allows advertisers to manage multiple ad exchange and data exchange accounts through one interface, often in real time. Actions
HTTP 401 Restricted Seek direct contact with the content owner for authorization keys/clarification.
HTTP 404 Does not exist Assume no declarations exist and that all advertising systems are authorized to buy and sell ads for this particular website.

This topic applies to Ad Exchange.

Feedback form