The ads.txt specification was developed in the spring of 2017, covering desktop and mobile web inventory.
So lets start with some basics before we proceed further with app-ads.txt
What Is Ads.txt ?
To provide the transparent inventory and Prevent Ad Fraud, IAB Tech lab rollout the ads.txt, Ads.txt is a text file which uploaded by the publisher/Site owner at root level which specifies all authenticated partner
You can read more about it
What Is Ads.cert ?
What is ads.cert ? It’s Working
ads.txt is not bulletproof against ad fraud. Human errors like misspelling supply-side platform names in ads.txt files have wrongly penalized exchanges from having their inventory being picked up. Plus, most ads.txt files don’t specify the type of inventory — display, video or native — a vendor is allowed to sell. That means display inventory can still be repackaged as video, for example, to boost CPM. If you want to go much deeper about the ads.txt and ads.cert. Please read it here.
Authorized Sellers for Apps (app-ads.txt)
The Authorized Sellers for Apps (app-ads.txt) specification details the following process:
● App developers provide a website URL in their app’s store metadata and publish an appads.txt file on that website that lists authorized sellers of their app’s ad inventory.
● Ad networks/sell-side platforms provide store listing URL on bid requests to facilitate
enforcement of authorized seller status.
● App stores publish app metadata in a standard HTML <meta> tag on the app store’s
listing page for the app so that it can be crawled and parsed as structured data.
● Authorized seller verifiers crawl app stores to find developer website information, crawl
developer websites to obtain and interpret app-ads.txt files, and enforce authorization
status on inventory
App developers must follow these steps to adopt app-ads.txt for their apps.
Provide developer website URL in app store listings
This specification relies on the presence of a developer website URL within the app’s store listing metadata in all app stores distributing the app. Many app stores currently collect the developer’s website URL to display as developer contact information within the store. Publishing a website and providing its URL is required for the app’s ad inventory to participate in the authorized seller scheme.
Publish an app-ads.txt file
Use the same guidelines as the ads.txt specification, with the exception that the “subdomain” directive is unused in appads.txt files and should be ignored if encountered
Changing the developer website URL for an app
Developers should anticipate that changes to the developer URL domain
may take some time to be recognized by interested authorized seller verifiers
Ad networks/sell-side platforms (aka “bid request issuers”)
Include the storeurl parameter within bid requests
App stores (Not For App developer)
app stores publish three HTML <meta>
tags with the store listing page for each individual app:
● The app developer’s website URL (often currently provided as a user-clickable link on the store listing page)
● The app’s bundle_id
● The app’s store_id
App stores must format the HTML meta tags as follows,
Inserting these tags into the <head>
HTML tag at the beginning of the HTML doc and including the appropriate value in the content
<meta name=”appstore:developer_url” content=”https://www.path.to/page” />
<meta name=”appstore:bundle_id” content=”com.example.myapp” />
<meta name=”appstore:store_id” content=”SKU12345″ />