What is app-ads.txt?
App-ads.txt is a way for app publishers to prove to advertisers that they own the app where an ad request is originating from. 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 ad request with an app is sent out, 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 app-ads.txt file.
You can read more about it here:
How do I implement app-ads.txt?
- Make sure you define your website on your Google Play Store and Apple App Store app pages
- Work will all the ad networks implemented in your app and ask for the relevant lines you should add to your app-ads.txt file. Only add the lines as instructed by companies that you have a direct relationship with. You can find the relevant lines to add to your app-ads.txt file for AppLovin here
- Add your app-ads.txt file to the root domain of the website defined in your app marketplace pages. For example, if the website from #1 is "https://www.mywebsite.com/help/contact", add this text file here: "https://www.mywebsite.com/app-ads.txt"
Why should I implement app-ads.txt?
Currently, AppLovin does not require publishers to implement app-ads.txt. That being said, many of the bidding partners we work with will start enforcing it soon. If you don't implement app-ads.txt, it may hurt your eCPMs because there will be less advertisers willing to pay you for ads.