Ad system
e-planning.net
Most of the 166,488 apps that declare e-planning.net reach it through a reseller: 100% have a RESELLER line, 16% a DIRECT one (25,549 files, 15,676 of them through thebrave.io's account). 33% of the 233,278 lines checked name an account its sellers.json (264 sellers) does not list. 4 sellers left its sellers.json in the last 30 days.
- Apps declaring it
- 166,488
- Sellers in sellers.json
- 264
- Lines verified
- 63%
- Lines with errors
- 88,799
- Avg. supply path score
- 51.2 / 100
26,150 DIRECT · 165,597 RESELLER
0% confidential
154,924 of 245,875 checked lines
245,875 lines in total
174,350 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 e-planning.net 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.
e-planning.net, YOUR_ACCOUNT_ID, DIRECT, c1ba615865ed87b2
e-planning.net, YOUR_ACCOUNT_ID, RESELLER, c1ba615865ed87b2- Field 1:
e-planning.net, the domain e-planning.net uses in app-ads.txt. - Field 2: your account ID with e-planning.net. It must equal the
seller_idin e-planning.net'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):
c1ba615865ed87b2, the certification authority ID on 97% of the lines naming e-planning.net.
sellers.json at a glance
- Status
- Published
- Sellers listed
- 264
- Confidential
- 0 (0%)
- Passthrough
- 0
- Removed, last 30 days
- 4
- Last read
- Oct 13, 2026
- PUBLISHER143
- INTERMEDIARY116
- BOTH5
Cross-check of lines naming e-planning.net
- Verified 154,924
- Seller ID not found 79,710
- DIRECT but intermediary 1,976
- RESELLER but publisher 7,113
- Seller type BOTH 2,152
- Confidential seller 0
- No sellers.json 0
- Unchecked 0
Every line naming e-planning.net is looked up in its sellers.json. What each status means
Common errors with e-planning.net lines
-
Seller ID not found
79,710 lines
Ask e-planning.net 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
7,113 lines
If the account is yours, declare it DIRECT. If a partner holds it, ask e-planning.net why the account is listed as PUBLISHER.
-
Seller type BOTH
2,152 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
1,976 lines
If a partner holds this account and resells your inventory, the line should say RESELLER. If the account is yours, ask e-planning.net to list it as PUBLISHER.
Intermediaries most declared as RESELLER
Accounts on e-planning.net 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 |
|---|---|---|
| thebrave.io | INTERMEDIARY | 15,676 |
| taurusx.com | INTERMEDIARY | 13,885 |
| admixer.com | INTERMEDIARY | 13,649 |
| bidmachine.io | INTERMEDIARY | 12,634 |
| loopme.com | INTERMEDIARY | 11,647 |
| conversantmedia.com | INTERMEDIARY | 11,510 |
| pubnative.net | INTERMEDIARY | 7,109 |
| unity.com | INTERMEDIARY | 6,032 |
Apps that declare e-planning.net
| App | Store | Relationship | Status |
|---|---|---|---|
| Android | DIRECT + RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | DIRECT + RESELLER | Live | |
| iOS | DIRECT + RESELLER | Live | |
| Android | DIRECT + RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| iOS | DIRECT + RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | DIRECT + RESELLER | Live | |
| Android | DIRECT + RESELLER | Live | |
| Android | DIRECT + RESELLER | Live | |
| Android | DIRECT + RESELLER | Live | |
| Android | DIRECT + RESELLER | Live |
Questions about e-planning.net
Does e-planning.net publish a sellers.json?
Yes. Its file at https://e-planning.net/sellers.json listed 264 sellers when we last read it on 13 October 2026: 143 publishers, 116 intermediaries and 5 listed as both; 0% are confidential.
How many apps declare e-planning.net in app-ads.txt?
166,488 apps in Stoqlab's data (delisted apps included) declare e-planning.net: 26,150 with at least one DIRECT line and 165,597 with at least one RESELLER line, across 25,549 app-ads.txt files, as of 13 October 2026 (recounted daily).
What is the certification authority ID for e-planning.net?
97% of the app-ads.txt lines naming e-planning.net carry "c1ba615865ed87b2" 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 e-planning.net lines fail verification?
Of 245,875 lines naming e-planning.net, 88,799 contradict its sellers.json. The most common case is "Seller ID not found", on 79,710 lines. Ask e-planning.net 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 e-planning.net. Something wrong? Tell us.