Ad system

empower.net

Most of the 58,891 apps that declare empower.net reach it through a reseller: 93% have a RESELLER line, 27% a DIRECT one. Of 7,472 lines checked against its sellers.json (328 sellers), 17% match, 0.3% name an unlisted account and 82% declare the wrong seller type.

Apps declaring it
58,891

15,899 DIRECT · 54,682 RESELLER

Sellers in sellers.json
328

0% confidential

Lines verified
18%

1,325 of 7,551 checked lines

Lines with errors
6,226

7,551 lines in total

Avg. supply path score
49.3 / 100

61,118 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 13 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 empower.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.

empower.net, YOUR_ACCOUNT_ID, DIRECT
empower.net, YOUR_ACCOUNT_ID, RESELLER
  • Field 1: empower.net, the domain empower.net uses in app-ads.txt.
  • Field 2: your account ID with empower.net. It must equal the seller_id in empower.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): a certification authority ID. Most lines naming empower.net carry none, or different ones, so we do not suggest one.

sellers.json at a glance

Status
Published
Sellers listed
328
Confidential
0 (0%)
Passthrough
0
Removed, last 30 days
0
Last read
Oct 13, 2026
  • PUBLISHER328
  • INTERMEDIARY0
  • BOTH0

Cross-check of lines naming empower.net

  • Verified 1,325
  • Seller ID not found 24
  • DIRECT but intermediary 0
  • RESELLER but publisher 6,202
  • Seller type BOTH 0
  • Confidential seller 0
  • No sellers.json 0
  • Unchecked 0

Every line naming empower.net is looked up in its sellers.json. What each status means

Common errors with empower.net lines

  • RESELLER but publisher 6,202 lines

    If the account is yours, declare it DIRECT. If a partner holds it, ask empower.net why the account is listed as PUBLISHER.

  • Seller ID not found 24 lines

    Ask empower.net 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.

Common app-ads.txt errors and how to fix them

Apps that declare empower.net

AppStoreRelationshipStatus
Android RESELLER Live
Android RESELLER Live
Android RESELLER Live
Android RESELLER Live
Android RESELLER Live
Android RESELLER Live
iOS RESELLER Live
Android RESELLER Live
Android RESELLER Live
iOS RESELLER Live
iOS RESELLER Live
Android RESELLER Live
Android RESELLER Live
Android RESELLER Live
Android DIRECT + RESELLER Live
Android RESELLER Live
Android RESELLER Live
Android RESELLER Live
Android DIRECT + RESELLER Live
iOS RESELLER Live

Questions about empower.net

Does empower.net publish a sellers.json?

Yes. Its file at https://empower.net/sellers.json listed 328 sellers when we last read it on 13 October 2026: 328 publishers, 0 intermediaries and 0 listed as both; 0% are confidential.

How many apps declare empower.net in app-ads.txt?

58,891 apps in Stoqlab's data (delisted apps included) declare empower.net: 15,899 with at least one DIRECT line and 54,682 with at least one RESELLER line, across 6,639 app-ads.txt files, as of 13 October 2026 (recounted daily).

Why do empower.net lines fail verification?

Of 7,551 lines naming empower.net, 6,226 contradict its sellers.json. The most common case is "RESELLER but publisher", on 6,202 lines. If the account is yours, declare it DIRECT. If a partner holds it, ask empower.net why the account is listed as PUBLISHER.

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 empower.net. Something wrong? Tell us.