Installed or active? The two coupon extension numbers your store needs
Install counts say an extension could reach your shoppers. Only your own sessions show if it acts. How to measure both, and which decision each one drives.
Jump to a section
In short
For store owners
You made the sale. A coupon extension took a cut.
Add Benson free to see what coupon extensions took from your orders over two weeks. Set rules to hide pop-ups and control which codes work in extension sessions.
We'll email you about getting started. Unsubscribe any time.
Someone in your team drops a link in the chat on a Monday morning. A coupon extension has millions of users and a fresh round of headlines. Underneath it: "Is this happening to us?"
By lunchtime you have two answers, and they disagree. Your paid-search agency says nobody under forty uses those any more. Your affiliate manager says half your customers probably have one. Both sound sure. Neither has looked at your store.
That's the trap. "How many people have it installed" is a number about the internet. "How often it acted in a session on my store, and what that did to the order" is a number about your business. You need both, and you need to know which is which before you change anything.
Why doesn't a big install count answer the question?#
The install counts are real, and they're large. The Chrome Web Store listing for PayPal Honey shows its user count on the page.
13M
Chrome users have PayPal Honey installed, according to its Chrome Web Store listing in October 2026.
It isn't alone. Capital One Shopping's listing on Microsoft's Edge Add-ons store shows more than five million users there, before you count Chrome. [Microsoft Edge Add-ons, Oct 2026] (opens the source) And the habit those extensions serve is common: in a September 2025 survey of 1,011 US adults for Savings.com, a coupon site, 54% of online shoppers said they search for discounts while browsing or at checkout. [Savings.com, Dec 2025] (opens the source)
None of that tells you what happens on your store. A national install count doesn't know your audience's age, device mix or country. It doesn't know whether an extension recognises your domain, holds any codes for you, or shows anything at all when your shoppers reach the cart.
So split the question in two:
- Installed (reach). Of the shoppers who visit you, how many carry the extension? That's a possibility. It says what could happen.
- Active (impact). In how many of your sessions did the extension actually do something: show a pop-up, try codes, offer cash back? That's behaviour. It says what did happen, and it's the only one you can tie to an order.
The gap between them is the interesting part. An extension can be installed and quiet: switched off for your site, waiting for a page it never reaches, or simply not holding an offer for you. Another can be installed by a small share of your shoppers and still turn up in most of the sessions that end in a discounted order.
Why can't you see either number today?#
Because both happen in the shopper's browser, not on your server.
An extension is software the shopper installed. Chrome's own documentation describes how extension scripts can read the pages a shopper visits and change them, while their code stays invisible to the page's own scripts. Chrome for Developers Your store didn't send that pop-up, so nothing in your stack logged it.
That leaves most merchants with blind spots in exactly the places they'd look:
- Google Analytics and Shopify analytics record pages, sources and orders. They have no field for "a coupon extension was running". An extension session looks like any other session that happened to use a code.
- Session recordings rebuild the page from what your own scripts can see. Extension panels are often drawn in a sealed-off part of the page or in their own frame, and replay tools can't record content inside frames they don't control. PostHog's troubleshooting guide says third-party embeds can't be recorded, for instance. PostHog The pop-up may show as an empty box, or not at all.
- Timing. Coupon extensions tend to wake up where there's a code field: the cart and the checkout. By then the shopper has chosen what to buy, so the extension's moment never shows up as a landing page or a traffic source.
So most merchants find out sideways. A customer mentions a pop-up. A code you gave one creator turns up on dozens of orders. A commission line arrives for a partner you didn't know was involved. In a 2024 Modern Retail report, the founder of the cookware brand Anyday said leaks usually showed up as a sudden spike in revenue on a code they then found on Honey or another coupon site. [Modern Retail, May 2024] (opens the source)
Sometimes it's pure chance:
Why does the gap matter beyond the discount?#
If you only have the install count, you tend to make one of two mistakes. You panic and switch everything off, including an extension partner that may be bringing you shoppers. Or you relax because "it's only a few per cent of browsers", while the few that are active sit on your cart page in exactly the sessions that were about to convert.
The cost also lands on people outside ecommerce:
- Finance sees discount depth creep up and commission rise, with no line in any report that explains why.
- Affiliate and creator partners lose credit, or get paid for sales they didn't drive, when their codes travel. That muddies every decision about which partners to grow.
- Networks are changing their terms. PPC Land reported in January 2026 that Awin had suspended Honey's payments and access to new advertiser programmes, after Rakuten Advertising and impact.com took their own action. [PPC Land, Jan 2026] (opens the source) When a partner's status changes, you want your own record of what it did on your store, not the headlines.
And the next visitor may not be a person. Agentic browsers run a full browser engine and fire your analytics tags, so GA4 counts their sessions as real visitors, as Seer Interactive points out. [Seer Interactive, Jul 2026] (opens the source) The same discipline applies: know which actor was in the session before you decide what it's worth.
What can you check yourself this week?#
You can get a long way without buying anything. Each check answers part of the question, and each has a catch.
Install the extensions and walk your own checkout. Add the big coupon and cashback extensions to a clean browser, then browse, add to cart and reach the code field. You'll see what a shopper sees. The catch: there are a lot of them, they behave differently by country and account, and some watch for testers. Benjamin Edelman reported in December 2025 that Honey looks for signs of a tester, such as a new account or a logged-in affiliate dashboard, and follows affiliate rules more strictly for those users. [Benjamin Edelman, Dec 2025] (opens the source) What you see may not be what your shoppers see.
Search your orders for codes you never published. Export a month of orders and sort by discount code. Look for creator or staff codes on far more orders than that person could drive, and for codes on orders with no matching campaign. Benson's free code check shows which of your codes some extensions and voucher sites hold. The catch: this finds leaked codes, not extension sessions. It misses extensions that apply cash back rather than codes, and it can't tell you how many shoppers had the extension at all.
Read your affiliate reports against checkout timing. Where your network shows click times, look for partner clicks seconds before purchase, from shoppers who arrived through search or email. The catch: it shows who got paid, not who changed the shopper's mind, and the report often arrives weeks after the order.
Watch session recordings of cart and checkout. Filter for sessions that applied a code and watch the last minute. The catch: the blind spots above. You may see the cart total drop with nothing on screen to explain it.
Put together, these checks tell you whether you have a problem. They won't give you a rate you can track week by week, and they can't separate installed from active.
How does Benson measure both?#
Benson runs a small script on your storefront and reports two separate signals. They are kept apart on purpose.
Session detection (active). When a known coupon or cashback extension does something Benson can recognise on your pages, such as injecting its button or pop-up, that session is tagged with the extension's name and the page it acted on. That's the extension share you see in your dashboard, and the cohort Benson compares with everyone else on conversion, order value and discount depth once your orders are connected. It's on every plan, including Free, alongside observe mode, which records what Benson would hide without hiding anything.
The limit: it only sees an extension that shows itself. A quiet extension leaves nothing to detect, and pages without the script, sampling and consent choices leave gaps.
The installed-extension check (reach). Many extensions make a few of their own files available to every website. Benson asks the browser for one such file for each extension on a short list of coupon, cashback and shopping-assistant extensions. If it loads, that extension is installed and switched on, even if it never shows itself. Chrome for Developers explains why those files are reachable. Our privacy policy lists every extension checked.
The limits are strict, and they matter for reading the number:
- It runs once per visit, only in desktop Chrome and Microsoft Edge, and never on checkout pages. Firefox and Safari give each install its own random address, so they can't be checked, and mobile Chrome has no extensions.
- In the EEA, the UK and Switzerland it runs only after the shopper gives analytics consent. Each store chooses whether the check is off, automatic, or only with consent. See Consent and storage.
- A found file proves the extension is installed. A missing one proves nothing.
- It keeps only the names of matched extensions, as part of the visit's events.
- If an extension's page in your dashboard has no Installed vs active card, the check isn't running on your store.
Where it runs, the extension's page shows three figures: the share of checked visits with it installed, how often it was active when installed, and the installed but quiet remainder. The share is always of checked visits, never all visits, because installed is unknowable everywhere else. Benson shows no figure until at least 100 visits have been checked, so a handful of visits can't pose as a market share.
Use each signal for the decision it can support:
- Is this worth my time? Start with installed share and how many visits were checked.
- Should I hide a pop-up? Use active sessions and the pages they act on. A rule can only change behaviour you can see.
- Is this partner worth what I pay? Compare the active cohort's orders with a fair control, then test. How to evaluate an extension partnership covers the questions to ask.
- Did my change work? Put it behind a holdout. Hiding pop-ups with a holdout is on Pro, and the holdout guide explains how to read it.
The honest answer after a fortnight is usually narrower than "extensions are everywhere" or "nobody uses those". It sounds more like: this one is installed on a slice of our desktop visits, shows itself on the cart for a smaller share, and those sessions carry deeper discounts than the rest. That's a sentence you can act on, and test.
Start with the first two weeks playbook, then install Benson from the Shopify App Store if you're on Shopify, or see Benson on your store on another platform.
Questions merchants ask
- If an extension is installed but quiet, is it costing me anything?
- Not in that session. Installed but quiet means it was present and did nothing Benson could see. It is still reach: a change on its side, or a new code it learns, could make it active, so keep an eye on the active share over time.
- Why does Benson only check desktop Chrome and Edge?
- The check asks the browser for a file the extension makes available to websites. Chrome and Edge give each extension a fixed address, so the file can be found. Firefox and Safari give every install its own random address, and mobile Chrome has no extensions.
- Can I see installed extensions in Google Analytics?
- Not by default. Analytics tools record pages, sources and orders, not what the shopper installed. Benson pushes a dataLayer event when it detects an extension in a session, which you can send to GA4 to compare cohorts yourself.
- Does the installed check run at checkout?
- No. It never runs on checkout pages, and runs at most once per visit. In the EEA, the UK and Switzerland it runs only after the shopper consents to analytics.
- Which number should I report to finance?
- Report both, labelled. Installed share says how many checked visits carried the extension. Active sessions and their orders say what it did. Only a holdout says what a change to it was worth.
Sources#
- Chrome Web Store: PayPal Honey listing and user count
- Microsoft Edge Add-ons: Capital One Shopping listing and user count
- Savings.com: America's savings shift, 2025 coupon and deal trends
- Modern Retail: How promo code leaks are impacting DTC brands' profit margins
- PPC Land: Awin confirms Honey violated affiliate policies, suspends payments
- Benjamin Edelman: Honey's Dieselgate, detecting and tricking testers
- Seer Interactive: The new analytics blind spot, AI traffic and AI agents that shop
- Chrome for Developers: Content scripts
- Chrome for Developers: Web accessible resources
- PostHog: Session replay troubleshooting
- r/shopify: Honey app shows discounts for "Shopify" when I have my own store
- r/shopify: Has anyone had issues with coupon codes leaking?
- r/ecommerce: Is there a way to find out if extensions like Honey are automatically giving discount codes?
- Benson privacy policy: Installed-extension check
- Benson docs: Consent and storage
- Benson docs: dataLayer and GA4 events
- Benson guide: Measure coupon extension impact
- Benson: How to evaluate a coupon extension partnership
- Benson: What the Capital One Shopping extension does on your Shopify store
- Benson: Holdout measurement for coupon controls
- Benson playbook: Your first two weeks



