Ad system
planning.net
planning.net appears only as a RESELLER: 17 app-ads.txt files. We found no readable sellers.json for planning.net, so none of the 17 lines naming it can be checked. 100% of the lines carry the certification ID c1ba615865ed87b2.
- Apps declaring it
- 351
- Sellers in sellers.json
- 0
- Lines verified
- —
- Lines with errors
- 0
- Avg. supply path score
- 47.6 / 100
0 DIRECT · 351 RESELLER
Invalid
no line checked yet
17 lines in total
348 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 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.
planning.net, YOUR_ACCOUNT_ID, DIRECT, c1ba615865ed87b2
planning.net, YOUR_ACCOUNT_ID, RESELLER, c1ba615865ed87b2
- Field 1:
planning.net, the domain planning.net uses in app-ads.txt. - Field 2: your account ID with planning.net. It must equal the
seller_idin 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 100% of the lines naming planning.net.
sellers.json at a glance
- Status
- Invalid
- Sellers listed
- 0
- Confidential
- 0 (0%)
- Passthrough
- 0
- Removed, last 30 days
- 0
- Last read
- Oct 12, 2026
Cross-check of lines naming planning.net
- Verified 0
- Seller ID not found 0
- DIRECT but intermediary 0
- RESELLER but publisher 0
- Seller type BOTH 0
- Confidential seller 0
- No sellers.json 17
- Unchecked 0
Every line naming planning.net is looked up in its sellers.json. What each status means
Common errors with planning.net lines
-
No sellers.json
17 lines
planning.net has no sellers.json we can read, so these lines cannot be checked by anyone.
Apps that declare planning.net
| App | Store | Relationship | Status |
|---|---|---|---|
| iOS | RESELLER | Live | |
| iOS | RESELLER | Live | |
| iOS | RESELLER | Live | |
| iOS | RESELLER | Live | |
| iOS | RESELLER | Live | |
| Android | RESELLER | Live | |
| iOS | RESELLER | Live | |
| iOS | RESELLER | Live | |
| iOS | RESELLER | Live | |
| iOS | RESELLER | Live | |
| iOS | RESELLER | Live | |
| iOS | RESELLER | Live | |
| iOS | RESELLER | Live | |
| iOS | RESELLER | Live | |
| iOS | RESELLER | Live | |
| iOS | RESELLER | Live | |
| iOS | RESELLER | Live | |
| iOS | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live |
Questions about planning.net
Does planning.net publish a sellers.json?
There is a file, but it is not valid sellers.json (last read 12 October 2026), so lines naming planning.net cannot be checked against it.
How many apps declare planning.net in app-ads.txt?
351 apps in Stoqlab's data (delisted apps included) declare planning.net: 0 with at least one DIRECT line and 351 with at least one RESELLER line, across 17 app-ads.txt files, as of 14 October 2026 (recounted daily).
What is the certification authority ID for planning.net?
100% of the app-ads.txt lines naming 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.
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 planning.net. Something wrong? Tell us.