Ad network and exchange
google.com
google.com is the domain Google's publisher platforms use in app-ads.txt: AdMob for apps, Google Ad Manager and AdSense. AdMob checks an app's app-ads.txt before it serves, so a missing or wrong google.com line limits ad serving.
532,703 apps across 123,597 app-ads.txt files declare google.com; 99% hold a DIRECT account and 34% list it as a RESELLER. 40% of the 746,232 lines checked name an account its sellers.json (956,084 sellers) does not list. 71% of its sellers are confidential, so buyers cannot see who they are.
- Apps declaring it
- 532,703
- Sellers in sellers.json
- 956,084
- Lines verified
- 10%
- Lines with errors
- 368,720
- Avg. supply path score
- 61.0 / 100
525,104 DIRECT · 180,207 RESELLER
71% confidential
80,367 of 780,067 checked lines
780,067 lines in total
566,482 apps scored
App counts, the sellers.json breakdown and the directory ranking are as of , recomputed daily (the same numbers as the directory). Line counts are recounted every 10 minutes. sellers.json last read 13 October 2026. The supply path score sums up how short and clean the declared paths are, 0 to 100 (how it is computed).
How to add Google to app-ads.txt
One line per account, in the app-ads.txt at the root of the domain your App Store and Google Play listings name as the developer website.
google.com, pub-0000000000000000, DIRECT, f08c47fec0942fa0
google.com, pub-0000000000000000, RESELLER, f08c47fec0942fa0
- Field 1:
google.com, the domain Google uses in app-ads.txt. - Field 2: your account ID with Google (format
pub-0000000000000000). It must equal theseller_idin Google's sellers.json. - Field 3: DIRECT if you hold the account, RESELLER if a partner holds it and sells your inventory. DIRECT vs RESELLER
- Field 4 (optional):
f08c47fec0942fa0, the certification authority ID on 82% of the lines naming google.com.
sellers.json at a glance
- Status
- Published
- Sellers listed
- 956,084
- Confidential
- 676,208 (71%)
- Passthrough
- 0
- Removed, last 30 days
- 26,838
- Last read
- Oct 13, 2026
- PUBLISHER955,500
- INTERMEDIARY0
- BOTH584
Cross-check of lines naming google.com
- Verified 80,367
- Seller ID not found 307,456
- DIRECT but intermediary 0
- RESELLER but publisher 61,264
- Seller type BOTH 249,919
- Confidential seller 81,061
- No sellers.json 0
- Unchecked 0
Every line naming google.com is looked up in its sellers.json. What each status means
Common errors with google.com lines
-
Seller ID not found
307,456 lines
Ask Google for the account ID it lists for you in its sellers.json, correct the line, or remove it if you no longer work with them. Buyers that check sellers.json drop these paths.
-
Seller type BOTH
249,919 lines
The account is listed as BOTH, so sellers.json alone cannot tell a buyer which relationship applies. Nothing to fix on your side; buyers usually look at the seller's domain.
-
Confidential seller
81,061 lines
The seller is confidential in sellers.json: its name and domain are hidden, so buyers cannot confirm who it is.
-
RESELLER but publisher
61,264 lines
If the account is yours, declare it DIRECT. If a partner holds it, ask Google why the account is listed as PUBLISHER.
Intermediaries most declared as RESELLER
Accounts on google.com that its sellers.json lists as INTERMEDIARY or BOTH, by the number of app-ads.txt files declaring them. Confidential sellers are left out.
| Seller domain | Type | Files |
|---|---|---|
| gannett.com | BOTH | 13,513 |
| aniview.com | BOTH | 13,029 |
| didna.io | BOTH | 12,992 |
| playwire.com | BOTH | 12,955 |
| voisetech.com | BOTH | 12,950 |
| gitberry.com | BOTH | 9,286 |
| adipolo.com | BOTH | 7,775 |
| empower.net | BOTH | 6,657 |
Apps that declare google.com
| App | Store | Relationship | Status |
|---|---|---|---|
| Android | DIRECT | Live | |
| Android | DIRECT | Live | |
| Android | DIRECT + RESELLER | Live | |
| Android | DIRECT | Live | |
| Android | DIRECT + RESELLER | Live | |
| iOS | DIRECT | Live | |
| Android | DIRECT + RESELLER | Live | |
| Android | DIRECT + RESELLER | Live | |
| Android | DIRECT | Live | |
| Android | DIRECT + RESELLER | Live | |
| Android | DIRECT | Live | |
| Android | DIRECT + RESELLER | Live | |
| Android | DIRECT + RESELLER | Live | |
| Android | DIRECT + RESELLER | Live | |
| Android | DIRECT + RESELLER | Live | |
| Android | DIRECT + RESELLER | Live | |
| Android | DIRECT | Live | |
| Android | DIRECT + RESELLER | Live | |
| Android | DIRECT + RESELLER | Live | |
| iOS | DIRECT | Live |
Questions about Google
Does Google publish a sellers.json?
Yes. Its file at https://storage.googleapis.com/adx-rtb-dictionaries/sellers.json listed 956,084 sellers when we last read it on 13 October 2026: 955,500 publishers, 0 intermediaries and 584 listed as both; 71% are confidential.
How many apps declare Google in app-ads.txt?
532,703 apps in Stoqlab's data (delisted apps included) declare google.com: 525,104 with at least one DIRECT line and 180,207 with at least one RESELLER line, across 123,597 app-ads.txt files, as of 13 October 2026 (recounted daily).
What is the certification authority ID for Google?
82% of the app-ads.txt lines naming google.com carry "f08c47fec0942fa0" in the fourth field. The field is optional; the IAB Tech Lab ads.txt 1.1 specification says identifiers in sellers.json supersede it, so a missing or different value does not make a line invalid.
Why do google.com lines fail verification?
Of 780,067 lines naming google.com, 368,720 contradict its sellers.json. The most common case is "Seller ID not found", on 307,456 lines. Ask Google for the account ID it lists for you in its sellers.json, correct the line, or remove it if you no longer work with them. Buyers that check sellers.json drop these paths.
Not sure whether your line should say DIRECT or RESELLER? DIRECT vs RESELLER in app-ads.txt
Sources: the public app-ads.txt files of tracked apps and the sellers.json of google.com. Something wrong? Tell us.