How to Promote a Browser Extension or Desktop App

How to promote a browser extension or desktop app

To promote a browser extension or desktop app, make the store listing or download page explain the value in one screenshot, make the first minute after install useful, and then send people from sources where they already have the problem you solve: search, communities, content, your own website, and paid traffic to a landing page. Measure each source by uninstalls and weekly active users, not by installs. And know the store rules first: the Chrome Web Store does not allow incentives for downloads, reviews, or ratings.

What the stores say about paid installs and reviews

The Chrome Web Store’s Spam and Abuse policy is the one most extension developers live under:

Google’s Spam FAQ removes any doubt. Asked whether you can provide incentives for users to download your extension, it answers “No”, gives the example that a game should not award in-game bonuses for installing an extension, and adds that rating or reviewing your own extension, or having affiliated people do it, may be treated as manipulation.

Other stores use broader words. Microsoft’s Edge Add-ons developer policies and the Microsoft Store Policies both state there is no place for any kind of fraud, including ratings and review manipulation. Safari extensions ship through the App Store, where Apple’s guidelines forbid paid or incentivized feedback, as covered in Can you pay for app reviews?. Firefox and Opera add-ons have their own review policies, so read them before any paid push.

The practical line: money can buy attention, never the install of a store extension and never a star. If you distribute a desktop app from your own website, no store placement is involved, and paying for real use of it is ordinary user acquisition.

Optimize the store listing or download page

People decide in seconds. Treat the listing like a landing page:

• Name the job, not the brand. “Tab Saver: close 50 tabs, restore them later” beats a clever one-word name nobody searches for.
• First screenshot shows the result. The before and after, the saved time, the finished export. Menus and settings pages can come later.
• Open the description with the problem, then three concrete things the tool does, then what it does not do.
• Explain every permission in plain words. Broad access with no reason given makes cautious users leave.
• For desktop apps, put supported OS versions, file size, and whether the installer is signed next to the download button.

Onboarding: the first minute decides retention

An install is only a chance. Many users leave in the first session because nothing visible happens.

1. Open a short welcome page on install (the runtime.onInstalled event in extensions) that shows one action to try right now.
2. Tell people how to pin the extension. New extensions often sit inside the browser’s extensions menu, where they are forgotten.
3. For desktop apps, skip the account wall if you can, and put the core feature on the first screen.
4. Ask for extra permissions at the moment they are needed, not all at once on day one.
5. Fire an event when the user completes the core action for the first time. That event is your real activation.

Track your uninstall rate

The Chrome Web Store developer dashboard reports daily installs and uninstalls. Extensions can also open a page on removal with runtime.setUninstallURL, a good place for a one-question survey (“What was missing?”). A desktop uninstaller can do the same.

Look at uninstalls within seven days of install, split by source. Many installs plus a high early uninstall rate means the source sends people who never wanted the tool.

Measure weekly active users yourself

The number on a Chrome Web Store listing is not an activity number. Google’s metrics documentation says it directly: the Users stats only capture installations and do not monitor whether users are active. So define activity yourself:

Count the core action, not a background heartbeat. An extension that pings your server every hour will show every idle install as “active”. Tag every campaign link with UTM parameters so each of these numbers can be split by source.

Where Sharklio fits, and where it does not

Sharklio campaigns reward users for what they do. Our team checks every campaign against the store rules above before it goes live.

• Chrome Web Store extensions: a click campaign to your own landing page. Users are credited for staying on the page for the view time you choose (5 to 60 seconds), and they decide for themselves whether to add the extension. The reward never depends on installing, and the page must not promise any bonus for installing either.
• Desktop apps you distribute yourself: a multi-step offer campaign. Each step is a real in-product goal, and your own server confirms it with a postback, for example “installed and opened” and then “used the core feature on a later day”.
• Never: any campaign that asks for a review or a rating, on any store. Those are rejected at review.

Targeting keeps the traffic relevant: choose desktop only as the device type, Windows as the operating system for a Windows app, and the browser that matches your extension (Chrome/Edge, Firefox, Safari, or Opera). There is no macOS option, so for a Mac-only app Safari plus desktop only is the closest filter. Set a frequency of once per user and daily caps while you test.

Run the same math on your own prices with the cost per result calculator.

Frequently asked questions