Ad system
ad-generation.jp
Most of the 26,829 apps that declare ad-generation.jp reach it through a reseller: 89% have a RESELLER line, 36% a DIRECT one (3,036 files, 2,251 of them through amazon.com's account). Of 3,871 lines checked against its sellers.json (9,457 sellers), 86% match, 1.5% name an unlisted account and 0.6% declare the wrong seller type. 2 sellers left its sellers.json in the last 30 days.
- Apps declaring it
- 26,829
- Sellers in sellers.json
- 9,457
- Lines verified
- 86%
- Lines with errors
- 94
- Avg. supply path score
- 49.3 / 100
9,528 DIRECT · 23,943 RESELLER
8% confidential
3,909 of 4,551 checked lines
4,551 lines in total
29,571 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 11 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 ad-generation.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.
ad-generation.jp, YOUR_ACCOUNT_ID, DIRECT, 7f4ea9029ac04e53
ad-generation.jp, YOUR_ACCOUNT_ID, RESELLER, 7f4ea9029ac04e53- Field 1:
ad-generation.jp, the domain ad-generation.jp uses in app-ads.txt. - Field 2: your account ID with ad-generation.jp. It must equal the
seller_idin ad-generation.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):
7f4ea9029ac04e53, the certification authority ID on 91% of the lines naming ad-generation.jp.
sellers.json at a glance
- Status
- Published
- Sellers listed
- 9,457
- Confidential
- 752 (8%)
- Passthrough
- 0
- Removed, last 30 days
- 2
- Last read
- Oct 11, 2026
- PUBLISHER4,622
- INTERMEDIARY4,777
- BOTH58
Cross-check of lines naming ad-generation.jp
- Verified 3,909
- Seller ID not found 65
- DIRECT but intermediary 16
- RESELLER but publisher 13
- Seller type BOTH 277
- Confidential seller 271
- No sellers.json 0
- Unchecked 0
Every line naming ad-generation.jp is looked up in its sellers.json. What each status means
Common errors with ad-generation.jp lines
-
Seller type BOTH
277 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
271 lines
The seller is confidential in sellers.json: its name and domain are hidden, so buyers cannot confirm who it is.
-
Seller ID not found
65 lines
Ask ad-generation.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.
-
DIRECT but intermediary
16 lines
If a partner holds this account and resells your inventory, the line should say RESELLER. If the account is yours, ask ad-generation.jp to list it as PUBLISHER.
-
RESELLER but publisher
13 lines
If the account is yours, declare it DIRECT. If a partner holds it, ask ad-generation.jp why the account is listed as PUBLISHER.
Intermediaries most declared as RESELLER
Accounts on ad-generation.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 |
|---|---|---|
| amazon.com | INTERMEDIARY | 2,251 |
| adingo.jp | INTERMEDIARY | 145 |
| google.com | INTERMEDIARY | 22 |
| i-mobile.co.jp | BOTH | 15 |
| ninja.co.jp | INTERMEDIARY | 9 |
| flux-g.com | INTERMEDIARY | 8 |
| fourm.jp | BOTH | 7 |
Apps that declare ad-generation.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 | DIRECT | Live | |
| Android | DIRECT | 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 ad-generation.jp
Does ad-generation.jp publish a sellers.json?
Yes. Its file at https://ad-generation.jp/sellers.json listed 9,457 sellers when we last read it on 11 October 2026: 4,622 publishers, 4,777 intermediaries and 58 listed as both; 8% are confidential.
How many apps declare ad-generation.jp in app-ads.txt?
26,829 apps in Stoqlab's data (delisted apps included) declare ad-generation.jp: 9,528 with at least one DIRECT line and 23,943 with at least one RESELLER line, across 3,036 app-ads.txt files, as of 11 October 2026 (recounted daily).
What is the certification authority ID for ad-generation.jp?
91% of the app-ads.txt lines naming ad-generation.jp carry "7f4ea9029ac04e53" 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 ad-generation.jp lines fail verification?
Of 4,551 lines naming ad-generation.jp, 94 contradict its sellers.json. The most common case is "Seller ID not found", on 65 lines. Ask ad-generation.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 ad-generation.jp. Something wrong? Tell us.