Ad system
adview.com
Most of the 119,230 apps that declare adview.com reach it through a reseller: 100% have a RESELLER line, 6.9% a DIRECT one (15,790 files, 10,596 of them through Smaato's account). 45% of the 60,036 lines checked name an account its sellers.json (200 sellers) does not list. 97% of the lines carry the certification ID 1b2cc038a11ea319.
- Apps declaring it
- 119,230
- Sellers in sellers.json
- 200
- Lines verified
- 45%
- Lines with errors
- 32,789
- Avg. supply path score
- 49.4 / 100
8,184 DIRECT · 118,670 RESELLER
0.5% confidential
27,871 of 62,134 checked lines
62,134 lines in total
118,628 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 12 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 adview.com 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.
adview.com, YOUR_ACCOUNT_ID, DIRECT, 1b2cc038a11ea319
adview.com, YOUR_ACCOUNT_ID, RESELLER, 1b2cc038a11ea319- Field 1:
adview.com, the domain adview.com uses in app-ads.txt. - Field 2: your account ID with adview.com. It must equal the
seller_idin adview.com'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):
1b2cc038a11ea319, the certification authority ID on 97% of the lines naming adview.com.
sellers.json at a glance
- Status
- Published
- Sellers listed
- 200
- Confidential
- 1 (0.5%)
- Passthrough
- 0
- Removed, last 30 days
- 0
- Last read
- Oct 12, 2026
- PUBLISHER189
- INTERMEDIARY8
- BOTH3
Cross-check of lines naming adview.com
- Verified 27,871
- Seller ID not found 28,187
- DIRECT but intermediary 242
- RESELLER but publisher 4,360
- Seller type BOTH 1,473
- Confidential seller 1
- No sellers.json 0
- Unchecked 0
Every line naming adview.com is looked up in its sellers.json. What each status means
Common errors with adview.com lines
-
Seller ID not found
28,187 lines
Ask adview.com 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.
-
RESELLER but publisher
4,360 lines
If the account is yours, declare it DIRECT. If a partner holds it, ask adview.com why the account is listed as PUBLISHER.
-
Seller type BOTH
1,473 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.
-
DIRECT but intermediary
242 lines
If a partner holds this account and resells your inventory, the line should say RESELLER. If the account is yours, ask adview.com to list it as PUBLISHER.
-
Confidential seller
1 line
The seller is confidential in sellers.json: its name and domain are hidden, so buyers cannot confirm who it is.
Intermediaries most declared as RESELLER
Accounts on adview.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 |
|---|---|---|
| smaato.com | INTERMEDIARY | 10,596 |
| aceex.io | INTERMEDIARY | 4,422 |
| smartyads.com | INTERMEDIARY | 4,422 |
| blasto.ai | INTERMEDIARY | 3,529 |
| pubnative.net | INTERMEDIARY | 2,681 |
| screencore.io | BOTH | 1,434 |
| adapex.io | INTERMEDIARY | 812 |
Apps that declare adview.com
| App | Store | Relationship | Status |
|---|---|---|---|
| Android | RESELLER | Live | |
| Android | DIRECT + RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | DIRECT | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | DIRECT + RESELLER | Live | |
| Android | DIRECT + RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live |
Questions about adview.com
Does adview.com publish a sellers.json?
Yes. Its file at https://adview.com/sellers.json listed 200 sellers when we last read it on 12 October 2026: 189 publishers, 8 intermediaries and 3 listed as both; 0.5% are confidential.
How many apps declare adview.com in app-ads.txt?
119,230 apps in Stoqlab's data (delisted apps included) declare adview.com: 8,184 with at least one DIRECT line and 118,670 with at least one RESELLER line, across 15,790 app-ads.txt files, as of 13 October 2026 (recounted daily).
What is the certification authority ID for adview.com?
97% of the app-ads.txt lines naming adview.com carry "1b2cc038a11ea319" 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 adview.com lines fail verification?
Of 62,134 lines naming adview.com, 32,789 contradict its sellers.json. The most common case is "Seller ID not found", on 28,187 lines. Ask adview.com 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 adview.com. Something wrong? Tell us.