Ad system
adservice.io
16 apps across 2 app-ads.txt files declare adservice.io; 100% hold a DIRECT account and 100% list it as a RESELLER. We found no readable sellers.json for adservice.io, so none of the 4 lines naming it can be checked. 50% of the lines carry the certification ID g09h8i7j6k5l4m3n.
- Apps declaring it
- 16
- Sellers in sellers.json
- 0
- Lines verified
- —
- Lines with errors
- 0
- Avg. supply path score
- 52.0 / 100
16 DIRECT · 16 RESELLER
Not found
no line checked yet
4 lines in total
16 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 9 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 adservice.io 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.
adservice.io, YOUR_ACCOUNT_ID, DIRECT, g09h8i7j6k5l4m3n
adservice.io, YOUR_ACCOUNT_ID, RESELLER, g09h8i7j6k5l4m3n- Field 1:
adservice.io, the domain adservice.io uses in app-ads.txt. - Field 2: your account ID with adservice.io. It must equal the
seller_idin adservice.io'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):
g09h8i7j6k5l4m3n, the certification authority ID on 50% of the lines naming adservice.io.
sellers.json at a glance
- Status
- Not found
- Sellers listed
- 0
- Confidential
- 0 (0%)
- Passthrough
- 0
- Removed, last 30 days
- 0
- Last read
- Oct 9, 2026
Cross-check of lines naming adservice.io
- Verified 0
- Seller ID not found 0
- DIRECT but intermediary 0
- RESELLER but publisher 0
- Seller type BOTH 0
- Confidential seller 0
- No sellers.json 4
- Unchecked 0
Every line naming adservice.io is looked up in its sellers.json. What each status means
Common errors with adservice.io lines
-
No sellers.json
4 lines
adservice.io has no sellers.json we can read, so these lines cannot be checked by anyone.
Apps that declare adservice.io
| App | Store | Relationship | Status |
|---|---|---|---|
| iOS | DIRECT + RESELLER | Live | |
| iOS | DIRECT + RESELLER | Live | |
| iOS | DIRECT + RESELLER | Live | |
| iOS | DIRECT + RESELLER | Live | |
| iOS | DIRECT + RESELLER | Live | |
| iOS | DIRECT + RESELLER | Live | |
| iOS | DIRECT + RESELLER | Live | |
| iOS | DIRECT + RESELLER | Live | |
| iOS | DIRECT + RESELLER | Live | |
| iOS | DIRECT + RESELLER | Live | |
| iOS | DIRECT + RESELLER | Live | |
| iOS | DIRECT + RESELLER | Live | |
| iOS | DIRECT + RESELLER | Live | |
| iOS | DIRECT + RESELLER | Live | |
| iOS | DIRECT + RESELLER | Live | |
| iOS | DIRECT + RESELLER | Live |
Questions about adservice.io
Does adservice.io publish a sellers.json?
We found no sellers.json at https://adservice.io/sellers.json when we last looked on 9 October 2026. Lines naming adservice.io cannot be checked against it.
How many apps declare adservice.io in app-ads.txt?
16 apps in Stoqlab's data (delisted apps included) declare adservice.io: 16 with at least one DIRECT line and 16 with at least one RESELLER line, across 2 app-ads.txt files, as of 14 October 2026 (recounted daily).
What is the certification authority ID for adservice.io?
50% of the app-ads.txt lines naming adservice.io carry "g09h8i7j6k5l4m3n" 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.
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 adservice.io. Something wrong? Tell us.