Ad system
lbdp.us
383 apps across 18 app-ads.txt files declare lbdp.us; 71% hold a DIRECT account and 29% list it as a RESELLER. We found no readable sellers.json for lbdp.us, so none of the 20 lines naming it can be checked. 100% of the lines carry the certification ID b1d30350acaf0176.
- Apps declaring it
- 383
- Sellers in sellers.json
- 0
- Lines verified
- —
- Lines with errors
- 0
- Avg. supply path score
- 44.5 / 100
273 DIRECT · 110 RESELLER
Unreachable
no line checked yet
20 lines in total
383 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 8 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 lbdp.us 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.
lbdp.us, YOUR_ACCOUNT_ID, DIRECT, b1d30350acaf0176
lbdp.us, YOUR_ACCOUNT_ID, RESELLER, b1d30350acaf0176- Field 1:
lbdp.us, the domain lbdp.us uses in app-ads.txt. - Field 2: your account ID with lbdp.us. It must equal the
seller_idin lbdp.us'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):
b1d30350acaf0176, the certification authority ID on 100% of the lines naming lbdp.us.
sellers.json at a glance
- Status
- Unreachable
- Sellers listed
- 0
- Confidential
- 0 (0%)
- Passthrough
- 0
- Removed, last 30 days
- 0
- Last read
- Oct 8, 2026
Cross-check of lines naming lbdp.us
- 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 0
- Unchecked 20
Every line naming lbdp.us is looked up in its sellers.json. What each status means
Apps that declare lbdp.us
| App | Store | Relationship | Status |
|---|---|---|---|
| Android | RESELLER | Live | |
| iOS | RESELLER | Live | |
| iOS | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | DIRECT | Live | |
| iOS | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| iOS | DIRECT | Live | |
| Android | RESELLER | Live | |
| Android | DIRECT | Live | |
| iOS | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| iOS | RESELLER | Live | |
| iOS | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| iOS | RESELLER | Live |
Questions about lbdp.us
Does lbdp.us publish a sellers.json?
We could not reach it (last attempt 8 October 2026). Lines naming lbdp.us stay unchecked until it answers again.
How many apps declare lbdp.us in app-ads.txt?
383 apps in Stoqlab's data (delisted apps included) declare lbdp.us: 273 with at least one DIRECT line and 110 with at least one RESELLER line, across 18 app-ads.txt files, as of 11 October 2026 (recounted daily).
What is the certification authority ID for lbdp.us?
100% of the app-ads.txt lines naming lbdp.us carry "b1d30350acaf0176" 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 lbdp.us. Something wrong? Tell us.