Install campaigns for Chrome, Microsoft Edge and Firefox
Each browser store has its own policies, counters, listing structure and review environment. The project begins with the exact extension URL or ID so that platform and category constraints can be checked before a test or campaign is proposed.
Chrome Web Store installs
Configure promotion for the verified Chrome Web Store listing, target GEO, pace and agreed counter.
Microsoft Edge Add-ons installs
Check availability and configure the campaign for the Microsoft Edge Add-ons listing and its own requirements.
Firefox add-on installs
Check Mozilla Add-ons requirements, project category, GEO and capacity before confirming the campaign.
How installs, active users and retention differ
Installs, active users, retention and store-displayed metrics describe different things. A responsible brief names the metric and does not imply outcomes beyond it.
| Metric | What it can indicate | Requires separate measurement |
|---|---|---|
| Install | An installation event within the agreed acquisition scope | Ongoing use, satisfaction and retention |
| Store counter | A store-displayed value under that platform’s rules and update timing | Real-time activity or identical counting across stores |
| Active users | Usage under a platform or product-specific definition | Long-term retention and monetization |
| Retained users | Users who return within a defined cohort window | Future activity and revenue |
Install volume, active users and retention are measured separately. The project brief states the checkpoint used for the campaign.
Campaign settings
- LISTING
Extension URL or ID
The exact store listing anchors platform review, category checks and measurement.
- AUDIENCE
Platform and GEO
Chrome, Microsoft Edge or Firefox plus the requested geography and any availability constraints.
- CAMPAIGN
Pace and period
Agree a small test window and a gradual campaign plan for paid work.
- VERIFICATION
Review point
Name the install signal or store counter and the time when it will be checked.
Free test process
- Submit the store listing. Include the browser, extension URL or ID, requested GEO and immediate goal.
- Confirm feasibility and scope. Extcorp checks the listing, browser, GEO and capacity, then agrees the period, pacing and install measure.
- Test, review and decide. If the project fits, begin with a short trial and review the named install checkpoint before planning paid work.
Product readiness
An extension should provide genuine utility, use clear permissions and comply with the relevant store rules. Acquisition is stronger when the listing communicates that value and the first-run experience helps a new user reach it. Extcorp may flag product or listing issues that should be addressed through browser extension growth or development before scaling.