Glossary
Must known terms related to the adoption of ads.txt and app-ads.txt
Certification Authority ID
An ID that uniquely identifies the advertising system within a certification authority (this ID maps to the entity listed in field #1). A current certification authority is the Trustworthy Accountability Group (aka TAG), and the TAGID would be included here [11]. Declaration of certification IDs are superseded by the identifiers object in sellers.json. Note: This field belongs to 1.1 version and may be deprecated in future releases.
Comments
Annotations included in an ads.txt file to provide additional context or information without affecting the file's functionality. Comments are denoted by the character "#". Any line containing "#" should inform the data consumer to ignore the data after the "#" character to the end of the line.
Publisher account ID
The identifier associated with the seller or reseller account within the advertising system in field #1. This must contain the same value used in transactions (i.e. OpenRTB bid requests) in the field specified by the SSP/exchange. Typically, in OpenRTB, this is publisher.id. For OpenDirect it is typically the publisher’s organization ID.
Records
The records enable publishers to designate which sellers are authorized to sell their digital advertising inventory. These records consist of a series of lines that outline fields in the following format: FIELD #1, FIELD #2, FIELD #3, FIELD #4. For instance, a sample line might look like this: placeholder.example.com, placeholder, DIRECT, placeholder.
Relationship type
An enumeration of the type of account. A value of ‘DIRECT’ indicates that the Publisher (content owner) directly controls the account indicated in field #2 on the system in field #1. This tends to mean a direct business contract between the Publisher and the advertising system. A value of ‘RESELLER’ indicates that the Publisher has authorized another entity to control the account indicated in field #2 and resell their ad space via the system in field #1. Other types may be added in the future. Note that this field should be treated as case insensitive when interpreting the data.
Seller domain name
The canonical domain name of the SSP, Exchange, Header Wrapper, etc system that bidders connect to. This may be the operational domain of the system, if that is different than the parent corporate domain, to facilitate WHOIS and reverse IP lookups to establish clear ownership of the delegate system. Ideally the SSP or Exchange publishes a document detailing what domain name to use.
SUBDOMAIN
A machine readable subdomain pointer to a subdomain within the root domain, on which an ads.txt can be found. The crawler should fetch and consume associate the data to the subdomain, not the current domain. This referral should be exempt from the public suffix truncation process. Only root domains should refer crawlers to subdomains. Subdomains should not refer to other subdomains.
Important Security Notice
Beware of scammers impersonating Tappx brand
We have identified fraudulent activities where malicious actors are imitating Tappx assets. These scams may compromise your security.
⚠️ Warning: The URL you came from has been flagged as potentially harmful.
To stay safe, only trust communications and services from the official Tappx domain: tappx.com
