We scanned 105 Shopify stores for fake urgency. Here is what we found, and what we could not see

Between 20 and 24 October 2026 we pointed Provedly's scanner at 105 Shopify stores, 51 in the UK and 54 in Australia, and asked two questions of every product page it could load: is the "N people are viewing this" number real, and does the countdown timer restart when a new visitor arrives?

The short version: 15 of the 105 stores (14%) had an urgency or social proof app installed. We did not catch a single made-up viewer count, and the one ticking timer we could test was an honest same-day dispatch cut-off. That is a smaller story than the one we expected to write, and the reasons why matter more than the headline number.

What we scanned

The list was 109 well-known direct-to-consumer brands we picked by hand, kept only if their pages were served by Shopify. Of those, 105 loaded. Three failed with errors and one put up a bot challenge.

These are big, established stores, which is the first limit on what follows. Fake urgency is usually discussed as a small-store problem: a new shop with no sales history installs a "sales pop" app, sets a viewer range, and lets the app invent the rest. Large brands have real traffic to show, so they have less reason to fake it. Read every number below as describing this list, not Shopify as a whole.

How the scanner decides

Each store was loaded in headless Chromium the way a new shopper would see it: no cookies, no history, a fresh browser context for every load.

Viewer counters. When a page shows text like "23 people are viewing this" or "5 people have this in their cart", the scanner reads it five times over eight seconds, then reloads the page several more times in new contexts. It also records every network response the page received and searches them for that number. A real counter has to come from a server, so the number shows up in a response. If the number never arrived from any server and still changed between loads, the page generated it in the browser, and we flag it.

Countdown timers. The scanner reads the first ticking timer, waits up to two minutes, then opens the page again in a brand new context and reads it again. A timer counting down to a real deadline will have dropped by roughly the time that passed. A timer that restarts for every new visitor reads the same as before, or higher. Timers longer than a week, timers close to zero and anything that reads like a shipping cut-off are marked inconclusive rather than judged.

Apps. Separately, the scanner matches the page's script URLs against known urgency and social proof apps. This is context only. An installed app is not evidence of anything; plenty of them can be configured honestly.

What we found

The 15 stores with an app installed broke down like this (some stores had more than one):

Correction (29 October 2026): this post first said 17 stores (16%) had an app installed, and listed Secomapp on 2 of them. Our scanner matched any Secomapp script, and on both stores the script was Secomapp's BOGOS free gift and bundle app, which is not an urgency tool. Neither store had any other app we track, so the right count is 15 (14%).

Countdown timers were by far the most common urgency tool, installed on 9 of the 15. Yet only one store showed a ticking timer on the product pages we loaded, and it read "Order within 4h 17m 40s for same day dispatch". That kind of timer resets every day by design and is truthful about it, so we did not count it as fake urgency.

The gap between "installed" and "showing" is the interesting part. An app's script can load on every page while its timer appears only on a sale collection, only during a campaign, or only after a setting is switched on. Our scanner looked at the homepage and a few product pages per store, so a timer on a campaign landing page would have been missed.

What we could not see

We want to be as clear about the limits as about the results, because a scan that says "nothing found" is easy to over-read.

• Pages that did not load are not counted as clean, but they were not re-checked either. On this first run, some product pages hit the scanner's 30-second load timeout. Those pages were not tested, and this first version of the scanner did not record how many there were. So "0 flagged" means "0 found on the pages that loaded", not "0 across all 105 stores". The next run will record and retry every page it fails to test.
• Large brands only. The list skews heavily towards established stores with real traffic, exactly the stores least likely to need invented numbers.
• Product pages, not campaigns. Urgency often lives on sale and launch pages, which a product-page scan can miss.
• One moment in time. Each store was checked once. A timer switched on for a weekend sale would not show on a Tuesday.

None of this makes the result wrong. It makes it narrow. "We found no fake counters on the product pages of 105 big UK and Australian Shopify brands" is what the data supports, and it is all we are claiming.

What a fake counter actually looks like

We have read the code. In the public widget script of one social proof app we took apart, the "people viewing" number is this:

n = min === max ? min : Math.floor(min + Math.random() * (max - min + 1));
// re-rolled every 12 seconds, defaults min=15 max=50

The merchant picks a minimum and a maximum, and the script shows a random number between them. Nothing on the page ever asks a server how many people are there. Two people looking at the same product at the same moment see different numbers, and a reload gives a third.

Fake countdowns are simpler still: the timer is stored in the browser, so a visitor who opens the page in a private window gets a fresh one. You can test both yourself in under a minute. Open the product page in two private windows side by side, then reload one of them. A real viewer count and a real deadline will agree across both windows. Made-up ones will not.

Consumer regulators, including the UK's Competition and Markets Authority, have said that invented urgency and invented popularity can mislead shoppers. We are not lawyers, and nothing here is legal advice, but "would this number survive a reload in a private window?" is a fair test for any store to run on itself.

Check your own store

The scanner behind this post runs as a free tool at provedly.app/check. Paste a product page URL and it runs the same viewer and countdown tests on that page in about a minute, with screenshots of what it saw on each load.

If your current app shows a range instead of a count, Provedly's live counter only shows visitors our server has actually seen on that page in the last 90 seconds, and hides itself below a minimum you set instead of inflating. Countdown bars count to one real date, and evergreen timers are disclosed as per-visitor on the store's public verification page. How verification works explains the rest.

What we will do next

The next scan will fix the gaps above before it runs: a list weighted towards smaller and newer stores, every failed page recorded and retried, and campaign pages included alongside product pages. Update: the second scan is done. We scanned 200 small Shopify stores, tested every page, and found fake urgency on 12 of them: 7 of the 17 ticking countdowns restarted for every new visitor.

Frequently asked questions

Does an installed countdown timer app mean a store is faking urgency?

No. Most countdown apps can count down to a real deadline, and many stores use them that way. What matters is how the timer is configured. The only test that answers it is to load the page as a new visitor and see whether the timer starts over.

Why did you not name the stores?

The point of the scan was to measure how common fake urgency is, not to call out individual brands. None of the stores in this list was flagged, so there was nothing to name.

Can I see the evidence for my own store?

Yes. Run your product page through the free checker. It shows each reading it took, the network responses it searched and screenshots from each load.