Chrome Web Store conversion rate: how to measure impressions, page views and installs

"What's a good conversion rate (impressions to installs) for an extension in the Chrome Web Store?" is one of the most repeated questions in extension developer communities, and it rarely gets a useful answer. The honest one is that the number on its own means little. A listing that converts 2% of casual store browsers and 40% of visitors from your own website can look average in a blended chart while one of those channels is quietly broken.

This guide shows how to turn the Chrome Web Store dashboard into a proper funnel: what each metric counts, how to calculate conversion at every step, how to attribute installs to a source with UTM parameters and the store's Google Analytics 4 integration, and how to tell which part of the listing to fix when the numbers move.

Key takeaways

• The Chrome Web Store funnel has three steps you can see: store impressions, listing page views and installs. Calculate a rate for each step instead of one blended number.
• There is no official benchmark for extension conversion rates. Compare each traffic source against its own history, because intent varies far more between sources than between listings.
• Chrome breaks page views down by utm_source, utm_medium and utm_campaign. Tag every link you control, or that traffic lands in one unattributed bucket.
• The store's GA4 integration sends an install event only when the user accepts the permission prompt, so a new permission warning shows up directly as a lower install rate.
• When conversion drops, find the step that moved first. Impressions point to ranking and search, page views to how you look in results, installs to the listing page itself.

What the Chrome Web Store dashboard actually counts#

The Developer Dashboard splits listing analytics across three pages, introduced in the 2022 analytics revamp: Installs and Uninstalls, Impressions, and Weekly Users. For conversion, the first two matter.

The definitions come from Chrome's store listing metrics documentation and the revamp announcement. Every chart exports to CSV, which is what you will use for the calculations below.

Two details are easy to miss. First, page views are not a subset of impressions. Someone who clicks a link on your website goes straight to the listing and creates a page view without ever seeing the item in store search. Second, the units differ: impressions are described in terms of users, page views in terms of views, installs as install events. That is fine for tracking trends, but it means the ratios below are indexes you compare over time, not precise probabilities.

Edge and Firefox count differently#

If you publish on more than one store, do not paste the numbers into one sheet without adjusting.

• Microsoft Edge Add-ons reports an Impressions metric that "captures the total number of page views and user visits" to your product page, plus daily installs, both filterable by region, OS and language (Microsoft Learn). Edge impressions are therefore closer to Chrome page views than to Chrome impressions, and there is no documented UTM breakdown.
• Firefox Add-ons (AMO) breaks downloads down by utm_source, utm_medium, utm_content and utm_campaign, but only counts installs from the AMO listing page. Installs of an .xpi from your own site are not counted (Extension Workshop).

For a fuller comparison of what each store calls a user, see how to measure extension retention and uninstall rate, and for lining the stores up side by side, tracking one extension across Chrome, Edge and Firefox.

The three conversion rates to calculate#

A single "impressions to installs" ratio mixes two very different questions: do people click on you when they see you, and do they install when they read your page? Split them.

Calculate them weekly, not daily. Daily installs on a small extension swing too much for the ratio to mean anything, and a weekly window also smooths out the weekday pattern that most productivity extensions have.

A worked example#

Here is a hypothetical week for a small productivity extension, taken from the CSV exports:

Week of 2026-09-21
Impressions:                    18,400
Page views (all sources):        2,150
  of which utm_source=website      610
  of which utm_source=newsletter   140
  of which no UTM (store + other) 1,400
Installs:                          520

The blended overall conversion is 520 / 18,400, about 2.8%, and the listing conversion is 520 / 2,150, about 24%. Neither tells you much yet. The useful view comes from attributing installs to sources, which the dashboard alone cannot do: it breaks page views down by UTM but not installs. That gap is what the store's GA4 integration fills, covered next.

If you only have the dashboard, you can still estimate the store-driven part by subtracting tagged page views from the total. In the example, roughly 1,400 untagged page views against 18,400 impressions gives a listing visit rate of about 7.6% for store browsing. Treat it as an upper bound, because untagged traffic also includes links you did not tag and visitors who typed the URL.

Track where installs come from with UTM parameters#

The most common attribution question in the Chromium Extensions group and on Stack Overflow is some version of "is there a way to get referral or UTM codes when a Chrome extension is installed?" The extension itself cannot read the parameters of the store page that led to the install. The store, however, can, as long as you put them on the link.

Append UTM parameters to every link that points at your listing:

https://chromewebstore.google.com/detail/your-extension/abcdefghijklmnopabcdefghijklmnop?utm_source=website&utm_medium=hero_button&utm_campaign=evergreen

A naming convention keeps the reports readable months later:

Three rules make the data trustworthy:

1. Use lowercase and one spelling. Newsletter and newsletter show up as two sources.
2. Only use the three parameters Chrome forwards. The store passes utm_source, utm_medium and utm_campaign. Firefox also accepts utm_content, but Chrome will not report it, so do not rely on it for cross-store comparisons.
3. Never tag links that appear inside the store. UTM parameters are for traffic you send to the store, not for links between your own listings.

Measure installs by source with the store's GA4 integration#

The Chrome Web Store can send listing traffic to a Google Analytics 4 property it creates for you. Setup takes a minute, according to Chrome's Google Analytics guide:

1. Open your item in the Developer Dashboard and go to the Store listing page.
2. In the Additional metrics section, click Opt in to Google Analytics.
3. Open analytics.google.com. A new property named with your extension ID appears.
4. Mark the install event as a key event. Chrome's guide still calls these "conversions"; Google Analytics has since renamed conversions to key events, and the setting lives under Admin.

The store then sends page_view, session_start, first_visit and user_engagement events, plus a custom install event. UTM parameters on the incoming link populate Session source, Session medium and Session campaign, and the "first user" versions for new visitors.

In the Traffic acquisition report, add the install key event and the Session key event rate metric, then group by session source and medium. That table is the per-source listing conversion rate the dashboard cannot give you. For the hypothetical week above it might look like this:

Keep untagged traffic as one bucket. How GA4 labels visits that started inside the store is not documented in detail, so do not read too much into the source names it shows for them. The spread is the point. Visitors who clicked "Add to Chrome" on your own site already decided; store browsers are comparing you against five alternatives. Averaging them hides a drop in either.

Limits worth knowing before you rely on it#

The integration is useful but constrained, and several developer threads exist because people found out the hard way:

• The install event only fires after the permission prompt is accepted. Chrome's guide says it "is only sent if a user accepts the permission prompt." Every visitor who clicks Add and then cancels at the warning is a lost install you will not see as an event.
• You get the Marketer role, and it cannot be changed. Teammates can only be added by inviting them to your publisher, and they get the Viewer role.
• Data retention is set to two months, and data de-identification is on. Export or record what you want to keep longer.
• Google Ads linking is not supported. A thread titled "New GA4 integration for Webstore breaks Google Ads tracking" shows how much this hurt advertisers. The suggested alternative there was UTM parameters, which give you reporting but not automated bidding on installs.
• Data can take 24 to 48 hours to finalize. Do not judge yesterday's campaign this morning.

This property only sees the store page. To measure what people do after they install, you need a second, separate property fed from the extension itself; adding Google Analytics 4 to a Manifest V3 extension walks through that setup.

When conversion drops: find the step that moved first#

Threads such as "Install And Impressions Dropped Off A Cliff" and "Rankings plummeted with latest Chrome store update" follow the same pattern: installs fall and the developer does not know whether the store, the listing or the product is to blame. In the second thread, one developer described weekly impressions falling from a range of 85,000 to 90,000 to just 1,643 after the extension stopped appearing in search. Walking the funnel from the top tells you which kind of problem you have.

Impressions fell, rates held#

If impressions dropped but the visit rate and listing conversion held steady, people still like what they see; fewer of them see it. Likely causes:

• Ranking changes. Chrome's discovery documentation says items are ranked with "a heuristic that takes into account ratings from users as well as usage statistics, such as the number of downloads vs. uninstalls over time." A rising uninstall rate or a falling rating can therefore cost you impressions weeks later.
• Lost placements. Collections and editorial features end. With the Featured badge being retired in 2026, placements tied to it will change for many listings at once.
• Seasonality. Search demand for your category may simply be lower. One founder on Indie Hackers posted "Impressions Down, Installs Up" after seeing store impressions fall while installs from social traffic rose, and a reply pointed to seasonal keyword demand.
• A reporting gap. Days of zero impressions and installs across many listings at once have historically been reporting delays, not real drops. If the line goes to zero overnight, check whether other developers see the same before changing anything.

Visit rate fell#

Impressions are steady but fewer people open the listing. That is about how you look next to alternatives in results: icon, name, the summary (132 characters or less, per the listing guidelines), star rating and rating count. Two common triggers:

• Your rating slipped. The Chrome Web Store rating now leans on recent reviews, so one bad release moves it faster than it used to. See reading review and rating trends for how to read the stars next to the count behind them.
• A competitor improved. A rival with a fresh icon, a better summary or a burst of new reviews takes clicks from the same results page. You only notice if you are watching their listing too.

Listing conversion fell#

People open the page but install less. Check, in order:

1. Permission warnings. If a release added a permission that shows a new install warning, more visitors cancel at the prompt, and because the install event only fires after the prompt is accepted, the drop shows up directly in your install rate. Compare the date of the drop with the date of the release.
2. Screenshots and video. Chrome recommends at least one and preferably five screenshots at 1280x800 or 640x400. Outdated screenshots that do not match the current UI cost trust.
3. The first lines of the description. Most visitors never expand it. Lead with the problem you solve, not a feature list.
4. Recent reviews. A new one-star review that sits at the top of the list can do more damage than a tenth of a star.
5. Traffic mix. If a large, low-intent source such as a paid campaign or a viral post started in the same week, blended conversion falls even though nothing is wrong. Check the per-source table before touching the listing.

Improve one stage at a time#

Change one thing, wait a full week or two, and compare the rate for that stage. Store traffic is too noisy to read two changes made in the same week.

• To lift the visit rate: simplify the icon so it reads at small sizes, put the main keyword and the outcome in the summary, and work on the rating by fixing what recent low-star reviews complain about. Avoid keyword stuffing; Chrome warns that "repetitive or irrelevant use of keywords" can lead to suspension.
• To lift listing conversion: make the first screenshot show the result, not the settings page; explain any permission warning in plain words in the description before the visitor meets it in the prompt; and drop permissions you do not need.
• To lift installs from your own channels: link straight to the listing with UTM parameters, and put the install button where your visitors already decided, such as the end of a tutorial.

After each release, run through what to watch in the week after an extension release so a conversion drop caused by a new version is caught in days, not weeks.

Watch the public side of the funnel too#

Your dashboard shows your own funnel. It cannot show what changed around you: a competitor that started requesting fewer permissions, renamed its listing to target your keyword, or gained 300 ratings in a week. Those are often the real explanation for a falling visit rate.

Extenify tracks the public data of any listing, yours and your competitors', once a day on Chrome, Edge and Firefox, and its daily digest flags changes such as Requests more permissions, Listing name changed, Rating dropped, rank moves and Installs falling. Pair it with store change alerts routed to the right channel, and you see the outside events that line up with the dips in your own conversion chart.

Frequently asked questions#

What is a good conversion rate for a Chrome extension?#

Google does not publish a benchmark, and figures shared in forums use different formulas and traffic mixes. Calculate installs per page view for each traffic source and compare each source with its own history. Traffic from your own website should convert far better than store browsing; if it does not, the listing page is the problem.

What is the difference between impressions and page views in the Chrome Web Store?#

Impressions count users who discover your item while searching or browsing the store. Page views count views of your listing page from anywhere, including links from outside the store. Page views can therefore come from people who never saw an impression.

Does the Chrome Web Store track UTM parameters?#

Yes. The Impressions page breaks page views down by utm_source, utm_medium and utm_campaign, and the store's GA4 integration maps the same parameters to session source, medium and campaign. The dashboard does not break installs down by UTM; use the GA4 property for that.

Why are my Chrome Web Store impressions zero for a day?#

When many listings show zero impressions and installs on the same day, it has historically been a reporting delay that corrected itself later. Wait a day or two, check whether other developers report the same, and compare with your own extension telemetry before assuming a real drop.

Can I link the Chrome Web Store GA4 property to Google Ads?#

Not according to Chrome's current documentation, which lists Google Ads linking as not supported. You can still tag ad links with UTM parameters and report installs by campaign inside the GA4 property.

Summary#

"What's a good conversion rate?" is the wrong first question. Split the funnel into impressions, page views and installs, tag every link you control, turn on the store's GA4 property and mark install as a key event, then read the install rate per source every week. When the numbers move, find the step that moved first and fix that step only. Keep the outside view in sight as well, because a competitor's change or a ranking shift explains many drops that no listing tweak will fix.

Image credits#

• Cover photo: Close Up Photo of Black Digital Tablet on Brown Surface by weCare Media on Pexels, Pexels License.