app-ads.txt is how app publishers to prove to advertisers that they own the app that originates an ad request.
Publishers host this file on the root domain of their website that is linked from the Google Play Store or Apple App Store. When an app makes an ad request, an advertiser can check the app marketplace page for the app, find the corresponding
app-ads.txt file, and verify that the publisher ID included in the ad request matches the corresponding ID in the
app-ads.txt file. This prevents a malicious actor from faking ad requests from an app, because the publisher ID in their ad request will not match the publisher ID included in the
You can read more about it here: https://iabtechlab.com/ads-txt
How do I implement
- Define your website on your Google Play Store and Apple App Store app pages.
- Work with all the ad networks implemented in your app and ask for the relevant lines you should add to your
app-ads.txtfile. Only add those lines you have been instructed to add by companies that you have a direct relationship with. You can find the relevant lines to add to your
app-ads.txtfile for AppLovin here.
- Add your
app-ads.txtfile to the root domain of the website that is defined in your app marketplace pages. For example, if the website from step 1 is “https://www.mywebsite.com/help/contact”, add this text file here: “https://www.mywebsite.com/app-ads.txt”.
Why should I implement
Currently, AppLovin does not require publishers to implement
app-ads.txt. However many bidding partners that AppLovin works with will start requiring it soon. If you don’t implement
app-ads.txt, this may hurt your eCPMs because there will be fewer advertisers who will be willing to pay you for ads.