Ad system
adingo.jp
Most of the 122,060 apps that declare adingo.jp reach it through a reseller: 97% have a RESELLER line, 12% a DIRECT one (17,255 files, 12,593 of them through taurusx.com's account). 22% of the 51,987 lines checked name an account its sellers.json (1,315 sellers) does not list. 41% of its sellers are confidential, so buyers cannot see who they are.
- Apps declaring it
- 122,060
- Sellers in sellers.json
- 1,315
- Lines verified
- 71%
- Lines with errors
- 15,524
- Avg. supply path score
- 50.6 / 100
14,620 DIRECT · 118,588 RESELLER
41% confidential
37,168 of 52,722 checked lines
52,722 lines in total
120,004 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 adingo.jp 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.
adingo.jp, YOUR_ACCOUNT_ID, DIRECT
adingo.jp, YOUR_ACCOUNT_ID, RESELLER- Field 1:
adingo.jp, the domain adingo.jp uses in app-ads.txt. - Field 2: your account ID with adingo.jp. It must equal the
seller_idin adingo.jp'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): a certification authority ID. Most lines naming adingo.jp carry none, or different ones, so we do not suggest one.
sellers.json at a glance
- Status
- Published
- Sellers listed
- 1,315
- Confidential
- 543 (41%)
- Passthrough
- 0
- Removed, last 30 days
- 0
- Last read
- Oct 13, 2026
- PUBLISHER1,259
- INTERMEDIARY44
- BOTH12
Cross-check of lines naming adingo.jp
- Verified 37,168
- Seller ID not found 11,775
- DIRECT but intermediary 2
- RESELLER but publisher 3,747
- Seller type BOTH 13
- Confidential seller 17
- No sellers.json 0
- Unchecked 0
Every line naming adingo.jp is looked up in its sellers.json. What each status means
Common errors with adingo.jp lines
-
Seller ID not found
11,775 lines
Ask adingo.jp 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
3,747 lines
If the account is yours, declare it DIRECT. If a partner holds it, ask adingo.jp why the account is listed as PUBLISHER.
-
Confidential seller
17 lines
The seller is confidential in sellers.json: its name and domain are hidden, so buyers cannot confirm who it is.
-
Seller type BOTH
13 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
2 lines
If a partner holds this account and resells your inventory, the line should say RESELLER. If the account is yours, ask adingo.jp to list it as PUBLISHER.
Intermediaries most declared as RESELLER
Accounts on adingo.jp 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 |
|---|---|---|
| taurusx.com | INTERMEDIARY | 12,593 |
| admixer.com | INTERMEDIARY | 9,174 |
| blueseasx.com | INTERMEDIARY | 7,703 |
| betweenx.com | INTERMEDIARY | 3,583 |
| waardex.com | INTERMEDIARY | 663 |
| bigo.sg | INTERMEDIARY | 622 |
| ignitemediagroup.co | INTERMEDIARY | 583 |
| iion.io | INTERMEDIARY | 457 |
Apps that declare adingo.jp
| App | Store | Relationship | Status |
|---|---|---|---|
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | 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 | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live |
Questions about adingo.jp
Does adingo.jp publish a sellers.json?
Yes. Its file at https://adingo.jp/sellers.json listed 1,315 sellers when we last read it on 13 October 2026: 1,259 publishers, 44 intermediaries and 12 listed as both; 41% are confidential.
How many apps declare adingo.jp in app-ads.txt?
122,060 apps in Stoqlab's data (delisted apps included) declare adingo.jp: 14,620 with at least one DIRECT line and 118,588 with at least one RESELLER line, across 17,255 app-ads.txt files, as of 14 October 2026 (recounted daily).
Why do adingo.jp lines fail verification?
Of 52,722 lines naming adingo.jp, 15,524 contradict its sellers.json. The most common case is "Seller ID not found", on 11,775 lines. Ask adingo.jp 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 adingo.jp. Something wrong? Tell us.