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