app-ads.txt reference · Documentation

How to check your app-ads.txt.

Five steps to check your own file, then a card for each major mobile ad network with where to find your lines and what the standard certification ID looks like in practice. Everything here is a reference. The network’s own documentation is always the source of truth.

Five steps

  1. Find your developer website. It is the website field on your App Store and Google Play listings. The file has to live at the root of that exact domain, for example https://yourdomain.com/app-ads.txt. A file on another domain, or under a path, is not what crawlers check.
  2. Open the file. Load it in a browser and check that you see plain text, not a web page. In a terminal, the first command below should print 200 and a text content type.
  3. Check each line. Every record has an ad system domain, your account ID with that seller, DIRECT or RESELLER, and usually a certification authority ID, separated by commas.
  4. Compare with each network’s own instructions. For every ad network you use, get your lines from its dashboard or help centre (cards below). Those lines carry your own account IDs, so you cannot copy them from this reference.
  5. Re-check after any change. Whenever you add an app, a network or a mediation partner, or move your site. Networks and ad buyers crawl the file on their own schedule.

Two quick terminal checks

Status, content type and final address after redirects:

curl -sSL -o /dev/null -w '%{http_code} %{content_type} %{url_effective}\n' https://yourdomain.com/app-ads.txt

Search the file for a network’s lines:

curl -sSL https://yourdomain.com/app-ads.txt | grep -i 'applovin.com'

Common mistakes

The standard is the IAB Tech Lab’s Authorized Sellers for Apps (app-ads.txt) v1.0, an extension of ads.txt. Later ads.txt versions added variables such as OWNERDOMAIN and MANAGERDOMAIN, which some networks ask for.

Network by network

For each network: where to find your lines, the official page to follow, and what the leading publishers’ files show. “Certification ID” is the fourth field most often seen on that network’s lines in the files collected for this reference. Compare it with the network’s own documentation before relying on it.

Google (AdMob / Ad Manager)

google.com

Your AdMob publisher ID is in the AdMob console under Settings. Google asks you to publish the file at the root of the developer website, with the domain entered exactly as listed on Google Play. AdMob can take up to 24 hours to crawl and verify it.

ironSource (Unity LevelPlay)

ironsrc.com

Add the ironsrc.com DIRECT line with the publisher ID from your LevelPlay account page, plus ironSource’s authorised reseller list. ironSource’s documentation also covers the OWNERDOMAIN variable.

Unity Ads

unity3d.com

In the Unity Monetization dashboard, go to Setup › Organization Settings and copy the list of sellers into your file. Unity notes that banner demand is reduced without app-ads.txt.

Meta Audience Network

facebook.com

Meta’s documentation gives the line format with your Meta Business Manager ID: facebook.com, <Business ID>, RESELLER, followed by Meta’s certification ID.

Mintegral (Mobvista)

mintegral.com

Mintegral’s guidance points to Account › Account Info in the Mintegral dashboard for your Publisher ID, which you add to its DIRECT line. No official Mintegral link was verified for this page; use the dashboard.

  • Certification ID seen most often: 0aeed750c80d6423
  • 21 exact lines appear in 3+ companies’ files (see the reference file).

Pangle (TikTok for Business)

pangleglobal.com

Pangle’s documentation gives a DIRECT line using your Account ID, shown at the top right of the Pangle platform’s main page.

  • Pangle: app-ads.txt ↗
  • Certification ID seen most often: 7998eac5087f6110
  • 9 exact lines appear in 3+ companies’ files (see the reference file).

Liftoff / Vungle

vungle.com · liftoff.io

See the Liftoff Help Center article for the lines to add for Liftoff and Vungle.

Chartboost

chartboost.com

Chartboost provides an app-ads.txt verifier in its dashboard (Monetization › Tools › App-ads.txt) that scans your apps and shows missing lines. It also asks that the developer URL on each store listing is current.

InMobi

inmobi.com

InMobi’s dashboard provides personalised app-ads.txt entries for your account. Its documentation says its crawler follows up to five redirects within the root domain and one outside it.

Fyber (Digital Turbine)

fyber.com

Digital Turbine’s documentation gives a DIRECT line for fyber.com with your Digital Turbine publisher ID (found in your user profile credentials in the DT Console) and a list of authorised resellers.

AdColony (Digital Turbine)

adcolony.com

AdColony is part of Digital Turbine. See Digital Turbine’s guide for the lines to add.

BidMachine (Appodeal)

bidmachine.io

No official link was verified for this page. Check your BidMachine or Appodeal dashboard for your lines.

  • 66 exact lines appear in 3+ companies’ files (see the reference file).

Smaato

smaato.com

Smaato’s publisher documentation provides an app-ads.txt snippet for your publisher account; the line format is smaato.com, <publisher ID>, DIRECT, followed by Smaato’s certification ID.

Tapjoy

tapjoy.com

No official link was verified for this page. Check your Tapjoy dashboard for your lines.

  • Certification ID seen most often: 29e595b1aeb5904d
  • 5 exact lines appear in 3+ companies’ files (see the reference file).

Amazon Publisher Services

aps.amazon.com

No official link was verified for this page. Check your Amazon Publisher Services account for your lines.

  • Certification ID seen most often: 4582cc3fa09ce42f
  • 47 exact lines appear in 3+ companies’ files (see the reference file).

Not sure your file and your mediation setup agree? A Monetization Audit reviews your ad stack end to end, including the networks and lines behind it.

Start with a Monetization Audit →

Reference only, not advice. Network instructions change; follow the linked pages. Back to the reference library and downloads.

Calculator by The Game Scientist ↗