Ad system
adingo.jp
adingo.jp is the domain an ad system uses in app-ads.txt and ads.txt files. 95,051 apps in our data declare it. Its sellers.json lists 1,315 sellers.
- Apps declaring it
- 95,051
- Sellers in sellers.json
- 1,315
- Lines verified
- 70%
- Lines with errors
- 11,387
- Avg. supply path score
- 50.6 / 100
11,920 DIRECT · 92,501 RESELLER
41% confidential
26,450 of 37,856 checked lines
37,856 lines in total
93,734 apps scored
Apps and lines are recounted every 10 minutes. The sellers.json breakdown and the directory ranking are as of , recomputed daily. 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 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 9, 2026
- PUBLISHER1,259
- INTERMEDIARY44
- BOTH12
Cross-check of lines naming adingo.jp
- Verified 26,450
- Seller ID not found 8,569
- DIRECT but intermediary 2
- RESELLER but publisher 2,816
- Seller type BOTH 9
- Confidential seller 10
- 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
8,569 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
2,816 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
10 lines
The seller is confidential in sellers.json: its name and domain are hidden, so buyers cannot confirm who it is.
-
Seller type BOTH
9 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 | 8,716 |
| admixer.com | INTERMEDIARY | 6,320 |
| blueseasx.com | INTERMEDIARY | 5,303 |
| betweenx.com | INTERMEDIARY | 2,557 |
| ignitemediagroup.co | INTERMEDIARY | 479 |
| waardex.com | INTERMEDIARY | 458 |
| iion.io | INTERMEDIARY | 362 |
| bigo.sg | INTERMEDIARY | 282 |
Apps that declare adingo.jp
| App | Store | Relationship | Status |
|---|---|---|---|
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| 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 | DIRECT + RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live |
Questions about adingo.jp
How do I add adingo.jp to app-ads.txt?
Add one line for each account adingo.jp gives you: "adingo.jp, YOUR_ACCOUNT_ID, DIRECT". Use DIRECT when you hold the account yourself and RESELLER when a partner holds it and sells your inventory through adingo.jp. The account ID must be the seller_id adingo.jp lists for you in its sellers.json; adingo.jp will give it to you. Put the file at the root of the domain named as your developer website in the App Store and Google Play listings.
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 9 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?
95,051 apps in Stoqlab's data (delisted apps included) declare adingo.jp: 11,920 with at least one DIRECT line and 92,501 with at least one RESELLER line, across 12,263 app-ads.txt files. Counts are recomputed daily.
Why do adingo.jp lines fail verification?
Of 37,856 lines naming adingo.jp, 11,387 contradict its sellers.json. The most common case is "Seller ID not found" (8,569 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.
What is the difference between DIRECT and RESELLER?
DIRECT means the publisher owns the account; RESELLER means an intermediary sells the inventory on the publisher's behalf. DIRECT lines should match a PUBLISHER entry in the network's sellers.json, RESELLER lines an INTERMEDIARY entry.
Sources: the public app-ads.txt files of tracked apps and the sellers.json of adingo.jp. Something wrong? Tell us.