Ad system
sapo.pt
10 apps across 6 app-ads.txt files declare sapo.pt; 100% hold a DIRECT account and 80% list it as a RESELLER. Of 10 lines checked against its sellers.json (69 sellers), 60% match, 0% name an unlisted account and 0% declare the wrong seller type.
- Apps declaring it
- 10
- Sellers in sellers.json
- 69
- Lines verified
- 60%
- Lines with errors
- 0
- Avg. supply path score
- 52.9 / 100
10 DIRECT · 8 RESELLER
0% confidential
6 of 10 checked lines
10 lines in total
10 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 9 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 sapo.pt 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.
sapo.pt, YOUR_ACCOUNT_ID, DIRECT
sapo.pt, YOUR_ACCOUNT_ID, RESELLER- Field 1:
sapo.pt, the domain sapo.pt uses in app-ads.txt. - Field 2: your account ID with sapo.pt. It must equal the
seller_idin sapo.pt'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): a certification authority ID. Most lines naming sapo.pt carry none, or different ones, so we do not suggest one.
sellers.json at a glance
- Status
- Published
- Sellers listed
- 69
- Confidential
- 0 (0%)
- Passthrough
- 0
- Removed, last 30 days
- 0
- Last read
- Oct 9, 2026
- PUBLISHER68
- INTERMEDIARY0
- BOTH1
Cross-check of lines naming sapo.pt
- Verified 6
- Seller ID not found 0
- DIRECT but intermediary 0
- RESELLER but publisher 0
- Seller type BOTH 4
- Confidential seller 0
- No sellers.json 0
- Unchecked 0
Every line naming sapo.pt is looked up in its sellers.json. What each status means
Common errors with sapo.pt lines
-
Seller type BOTH
4 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.
Intermediaries most declared as RESELLER
Accounts on sapo.pt 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 |
|---|---|---|
| skoiy.xyz | BOTH | 4 |
Apps that declare sapo.pt
| App | Store | Relationship | Status |
|---|---|---|---|
| iOS | DIRECT + RESELLER | Live | |
| iOS | DIRECT + RESELLER | Live | |
| iOS | DIRECT + RESELLER | Live | |
| iOS | DIRECT + RESELLER | Live | |
| iOS | DIRECT + RESELLER | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT + RESELLER | Live | |
| iOS | DIRECT | Live | |
| iOS | DIRECT + RESELLER | Live | |
| iOS | DIRECT + RESELLER | Live |
Questions about sapo.pt
Does sapo.pt publish a sellers.json?
Yes. Its file at https://sellers.sapo.pt/sellers.json listed 69 sellers when we last read it on 9 October 2026: 68 publishers, 0 intermediaries and 1 listed as both; 0% are confidential.
How many apps declare sapo.pt in app-ads.txt?
10 apps in Stoqlab's data (delisted apps included) declare sapo.pt: 10 with at least one DIRECT line and 8 with at least one RESELLER line, across 6 app-ads.txt files, as of 12 October 2026 (recounted daily).
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 sapo.pt. Something wrong? Tell us.