Verification Status | Action Required |
---|---|
X of X sellers are authorized. The app-ads.txt file is found and verified. InMobi crawled and verified your app-ads.txt file. |
No action needed |
X-Y of X sellers are authorized. Please include the missing seller entries in your app-ads.txt file to sell inventory with all of InMobi’s authorized sellers. |
Please include the missing seller entries in your app-ads.txt file to sell inventory with all of InMobi’s authorized sellers. Ads.txt helps prevent ad fraud by making it harder for malicious actors to sell fake ad inventory. Most buyers verify whether the reseller is legitimate and may reject the ad request if the reseller ID is missing in the app's ads.txt file. |
0 of X sellers are authorized. Please include the missing seller entries in your app-ads.txt file to avoid unintentional revenue loss. |
Please include the missing seller entries in your app-ads.txt file to avoid unintentional revenue loss. Ads.txt helps prevent ad fraud by making it harder for malicious actors to sell fake ad inventory. Most buyers verify whether the reseller is legitimate and may reject the ad request if the reseller ID is missing in the app's ads.txt file. |
File not found, Application ID/Bundle id provided under the inventory section doesn't match with the one given on app’s store listing. Please verify that the application ID (for android apps) and bundle ID (for iOS apps) provided on the publisher dashboard matches with the one given on the app’s listing page on Google Playstore / Apple App store. |
Please verify that the application ID (for android apps) and bundle ID (for iOS apps) provided on the publisher dashboard matches with the one given on the app’s listing page on Google Playstore / Apple App store.
|
The developer website could not be found in the app store listing. Please update the developer website in the app store listing. |
Add a developer website to your app’s listing in Google Play or the Apple App Store. App-ads.txt crawling will start at the root domain. The root domain needs to return from, or redirect to, the app-ads.txt file. If your app is published in multiple languages, verify that the correct developer website appears for each language variation. Note: If you’ve recently added a developer website or updated your app listing in Google Play, allow up to 24 hours for InMobi to detect these changes. |
The developer website in the app store listing is invalid. Please update the correct developer URL on the app store listing. |
The developer website URL on the app store listing or the redirection URL is either invalid or in the incorrect format. Check the URL of your developer website and its root domain and make sure it works correctly. Ensure there are no typos in the developer website URL in your app’s listing. If your app is published in multiple languages, verify that the correct developer website appears for each language variation. App-ads.txt crawling will start at the root domain. The root domain of the developer website URL needs to return from, or redirect to, the app-ads.txt file. |
The developer website on the app’s store listing or the redirection URL did not respond properly. Please ensure that the developer website on the app’s store listing or the redirection URL is working properly and the ads.txt file is reachable from root domain. Please ensure that the format of the headers in the response is correct and the response is sent within 1.5 sec. |
The developer website on the app store listing or the redirection URL did not respond properly. Ensure that the developer website on the app’s store listing or the redirection URL is working properly and the ads.txt file is reachable from root domain. Ensure that the format of the headers in the response is correct and the response is sent within 1.5 sec. |
File not found, The URL responded with invalid MIME type. The developer website on the app store listing responded with an unsupported MIME type in the header. Please verify that the ‘content-type’ key in header contains ‘text/plain’ as part of it's value. |
The URL responded with invalid MIME type. The developer website on the app’s store listing or the redirection URL responded with headers in incorrect format. This issue generally happens when the header (i.e., Content-Type) for any 200 OK response doesn’t contains text/plain As a resolution, please check the headers being returned in response to contain Content-Type one of a headers which returns text/plain as a value for this header. |
The app-ads.txt file was not found because it uses too many redirects. The IAB recommends no more than five redirects from the app-ads.txt page on a developer website. (Example: domain.com/app-ads.txt) Please move the app-ads.txt file to within five redirects from domain.com/app-ads.txt. |
InMobi crawler supports upto 5 redirections within the root domain and upto 1 redirection outside the root domain. Check the number of redirections happening from the developer website registered on App Store. Ensure that your web server hosts your app-ads.txt file or redirects to the correct location when you enter the app-ads.txt URL shown in your InMobi account. The app-ads.txt URL shown in your account is the URL InMobi uses to find your file. Update the developer website in your app’s store listing to the site’s subdomain or a different domain if you are unable to publish a file at the current location or want to use a different website. |
The app-ads.txt file was not found because it uses too many redirects away from the developer website. App-ads.txt files are typically hosted on the app developer’s website. (Example: domain.com/app-ads.txt) However, redirects can be common. IAB recommends no more than one redirect from the website’s app-ads.txt page. Please move the app-ads.txt file to within one redirect from domain.com/app-ads.txt. |
InMobi crawler supports upto 5 redirections within the root domain and upto 1 redirection outside the root domain. Check the number of redirections happening from the developer website registered on App Store. Ensure that your web server hosts your app-ads.txt file or redirects to the correct location when you enter the app-ads.txt URL shown in your InMobi account. The app-ads.txt URL shown in your account is the URL InMobi uses to find your file. Update the developer website in your app’s store listing to the site’s subdomain or a different domain if you are unable to publish a file at the current location or want to use a different website. |
An app-ads.txt file was not found on the developer website used in the app store listing. Please ensure the app-ads.txt file is hosted in the correct place on your app's website and setup as per InMobi’s guidelines. Example: https://yourwebsite.com/app-ads.txt |
Ensure that your app is registered with Google Play or the Apple App Store and that your developer website is included in the store listing for your app.
Note: If you’ve recently added a developer website or updated your app listing in Google Play, allow up to 24 hours for InMobi to detect these changes. |
Something went wrong. Please raise a ticket to InMobi support. The app-ads.txt file could not be crawled due to an unexpected error. |
Something unexpected happened and the file could not be crawled. Please raise a ticket for InMobi support |
Crawling is not supported for this platform. InMobi’s crawler only supports crawling of mobile websites, Android apps and iOS apps. |
Only iOS, android apps and mobile websites can be crawled by InMobi’s crawler. |
By installing this SDK update, you agree that your Children Privacy Compliance setting remains accurate or that you will update that setting, whenever there is a change in your app's audience. You may update the app's Children Privacy Compliance settings at https://publisher.inmobi.com/my-inventory/app-and-placements.