Configuring ads.txt for geo and channel

Scope3 parses ads.txt files to determine which rows apply to which geos and channels.

Determining countries and channels for a property

As most properties do not have meaningful traffic for every channel and country, we use traffic data from various sources to determine the most common geo-channel combinations to model. Please contact us if you would like to see additional geo-channel breakouts for particular properties!

Using ads.txt comments for hints

As of the ads.txt specification (1.2), there is no standardized way to signal that a particular row applies only to a particular geography or channel. It is common practice for publishers to indicate this using a comment: a hash (#) followed by a hint in all capital letters. For instance, #US. Scope3 only interprets hints that are separated from each other by a space and consist of all capital letters.

Geo hints

Scope3 supports the following hints. Where a hint represents a region instead of a country, the countries we consider to be in the region are listed below.

Regions

Channel hints

We support a variety of channel hints. Note that we do not currently have a mechanism to distinguish an outstream placement from a standard banner placement. We plan to work with publishers and industry groups to support the Global Placement ID (GPID) in an upcoming release.