Ad system
etarget.sk
Most of the 56 apps that declare etarget.sk reach it through a reseller: 98% have a RESELLER line, 1.8% a DIRECT one. 94% of the 16 lines checked name an account its sellers.json (8,788 sellers) does not list.
- Apps declaring it
- 56
- Sellers in sellers.json
- 8,788
- Lines verified
- 5.9%
- Lines with errors
- 16
- Avg. supply path score
- 46.9 / 100
1 DIRECT · 55 RESELLER
0% confidential
1 of 17 checked lines
17 lines in total
57 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 etarget.sk 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.
etarget.sk, YOUR_ACCOUNT_ID, DIRECT
etarget.sk, YOUR_ACCOUNT_ID, RESELLER- Field 1:
etarget.sk, the domain etarget.sk uses in app-ads.txt. - Field 2: your account ID with etarget.sk. It must equal the
seller_idin etarget.sk'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 etarget.sk carry none, or different ones, so we do not suggest one.
sellers.json at a glance
- Status
- Published
- Sellers listed
- 8,788
- Confidential
- 0 (0%)
- Passthrough
- 0
- Removed, last 30 days
- 0
- Last read
- Oct 11, 2026
- PUBLISHER8,788
- INTERMEDIARY0
- BOTH0
Cross-check of lines naming etarget.sk
- Verified 1
- Seller ID not found 16
- DIRECT but intermediary 0
- RESELLER but publisher 0
- Seller type BOTH 0
- Confidential seller 0
- No sellers.json 0
- Unchecked 0
Every line naming etarget.sk is looked up in its sellers.json. What each status means
Common errors with etarget.sk lines
-
Seller ID not found
16 lines
Ask etarget.sk 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.
Apps that declare etarget.sk
| App | Store | Relationship | Status |
|---|---|---|---|
| Android | RESELLER | Live | |
| iOS | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| iOS | RESELLER | Live | |
| iOS | RESELLER | Live | |
| iOS | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| iOS | RESELLER | Live | |
| iOS | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| Android | RESELLER | Live | |
| iOS | DIRECT | Live | |
| Android | RESELLER | Live |
Questions about etarget.sk
Does etarget.sk publish a sellers.json?
Yes. Its file at https://www.etarget.sk/sellers.json listed 8,788 sellers when we last read it on 11 October 2026: 8,788 publishers, 0 intermediaries and 0 listed as both; 0% are confidential.
How many apps declare etarget.sk in app-ads.txt?
56 apps in Stoqlab's data (delisted apps included) declare etarget.sk: 1 with at least one DIRECT line and 55 with at least one RESELLER line, across 16 app-ads.txt files, as of 11 October 2026 (recounted daily).
Why do etarget.sk lines fail verification?
Of 17 lines naming etarget.sk, 16 contradict its sellers.json. The most common case is "Seller ID not found", on 16 lines. Ask etarget.sk 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 etarget.sk. Something wrong? Tell us.