Improve a popup · Store scanners · Free tool

What is this store using to capture email?

Last updated

One fetch of that address, server side, with no account and no install. Nothing is stored and the page we read never leaves our server.

Example scan — another store, not yoursdeathwishcoffee.com · 3 of 4Open this to see what the full report looks like before you hand over an address. It is a scan of deathwishcoffee.com. Enter your own store above and your result replaces it.Show the example

Everything below is a scan of deathwishcoffee.com, fetched from that store for this page. It is not a scan of your store.

Result for deathwishcoffee.com
3 of 4
Coverage, not a score

Of the 4 capture mechanisms this scan can check from public HTML, 3 are visible on deathwishcoffee.com. More is not better: four overlapping asks pointed at one shopper is a worse experience than two that work. This is a description of what is on the page, not a grade.

Read 611 KB of HTML from https://www.deathwishcoffee.com/ · HTTP 200 · 1 redirect followed

Detected on this page

Onsite popup or form app
klaviyo.com/onsite
Is anything on this page capable of rendering a popup or an overlay form?
Email marketing platform
klaviyo
Is there somewhere for a captured address to land?
SMS capture
postscript
Is a phone number being collected alongside the address, or instead of it?

Not detected on this page

Email field in the delivered HTML
no match
Can a shopper with JavaScript switched off still hand over an address?

Capture-adjacent apps on the page

Klaviyo
Email / Onsite forms
From the same app list the app detector uses.
Postscript
SMS
From the same app list the app detector uses.

What this scan cannot see

  • Whether a popup actually shows, and to whom. Triggers, timing, frequency caps and targeting rules all live in the app and never appear in the page HTML.
  • Exit intent, scroll depth, time on page and cart-value rules. None of these are visible in a static fetch of one page.
  • Anything injected after the page loads. A popup app that boots from a tag manager, or renders only on a second page view, leaves nothing here to find.
  • The offer, the copy or the design. This scan sees a vendor script, not what it puts on screen.
  • How any of it performs. No capture rate, no conversion rate, no revenue. This page makes no claim about your traffic and could not.

Same fetch, other questions

Which theme is it running →

Theme name and version, from the same page.

Which apps are on the page →

Common marketing and conversion apps, found on the same page.

The capture checks

A popup audit tells you which email capture mechanisms a storefront is running and which ones it is missing, so a store with an email platform and a signup form but no popup and no SMS comes back with two of four in place.

Every finding comes from the public page at the address you enter. No traffic estimate, ranking figure or third-party store database is used, and no claim is made about how any store performs. If you want to know whether a capture rate is any good, the email capture benchmark grades a rate you already have against published bands.

4 checks against one page. The interesting half of this tool is not the checks — it is the list underneath the result of what no page scan can answer, which is longer and is printed rather than implied.

The read
One request for the address you enter, from our server, following redirects the way a browser does. The request is abandoned after 9 seconds and follows at most 4 redirects.
Onsite popup or form app
Is anything on this page capable of rendering a popup or an overlay form?
Email marketing platform
Is there somewhere for a captured address to land?
Email field in the delivered HTML
Can a shopper with JavaScript switched off still hand over an address?
SMS capture
Is a phone number being collected alongside the address, or instead of it?
The denominator
4, because that is how many of these can be answered from one page as it arrives. It is a count of what this instrument can check, not a count of what matters. Most of what matters is in the list of things it cannot see.

Most shoppers leave without buying or leaving an email. Nudgesmart catches them before they go, and is available on the Shopify App Store. Browse the template library or see what it costs.

The capture checks on pages that answer differently

Sample pages, not customer data and not named stores. Every cell is produced by the same checks the scanner above runs. Read the counts as descriptions, not as rankings — the row at three is not doing better than the row at two.

Worked examples: sample storefront markup and what the scanner reports for it
Sample pageCoverageWhat was matchedVerdict
Stock Dawn, Klaviyo and an SMS app3 of 4Onsite popup or form app, Email marketing platform, SMS captureCoverage, not a score
Agency theme plus the built-in Shopify newsletter form1 of 4Email field in the delivered HTMLCoverage, not a score
A Theme Store theme that still carries its theme_store_id0 of 4none of the 4 checkable mechanisms visible in this pageCoverage, not a score
A popup vendor that is not in the signature table1 of 4Email field in the delivered HTMLCoverage, not a score
Headless storefront — Shopify assets, no theme object2 of 4Onsite popup or form app, Email marketing platformCoverage, not a score
Not a Shopify store at all0 of 4none of the 4 checkable mechanisms visible in this pageCoverage, not a score
The last two rows are the ones worth sitting with. A headless storefront can be running a full capture stack behind a script this scan never sees, and a page with no Shopify markers at all still produces a coverage count, because the four checks are about capture rather than about Shopify. Neither row is a verdict on the store.

What a page read cannot see

More mechanisms is not better

A store at four of four may be asking the same shopper for an address in a popup, in the footer, in a slide-in and by text message. A store at two may have one well-targeted popup and a platform that does something sensible with the addresses. The number has no opinion and neither does this page.

Everything that makes a popup work is invisible here

When it fires, how often, to whom, on which pages, after what behaviour, with what offer, and whether it is suppressed for people who already signed up. None of that is printed into a storefront page. A scan can tell you the machinery is present. It cannot tell you it is aimed anywhere.

Not detected is not missing

Anything injected after the page loads is invisible to a single read — a tag manager, a delayed script, a popup that only appears on a second page view. Every negative on this page means not visible in this page, and the wording never says otherwise.

One page, and usually the most cached one

This is a single read of a single address. Capture that only runs on a product page, a collection or a cart will not appear, and a heavily cached front page is the most likely of all to have been stripped.

No claim is made about the traffic of any store, yours included

There is no visitor estimate, no capture rate, no conversion figure and no revenue number anywhere in this tool, because it has no way to know any of them. Everything on the page came out of the one page it read.

Email capture audit questions

What does this audit actually check?

4 things, all of them visible in one read of one public page: whether an onsite popup or form app is loaded, whether an email marketing platform is loaded, whether an email field exists in the page, and whether anything is collecting a phone number. It reports which are present and which are not.

Is four out of four good?

It is not a score and there is no good. Four overlapping asks pointed at one shopper — a popup, a footer form, an SMS prompt and a platform running its own campaigns — is frequently a worse experience than two that are set up properly. The count describes what is on the page. What it should be is a judgement about the store, and this tool will not make it for you.

Why does it say a popup is not detected when I can see one?

Because one read of the page cannot see anything that arrives later. A popup injected by a tag manager, shown only on a second page view, or run by an app this tool does not recognise leaves nothing in the page to find. Not detected means not visible in this page, never missing.

Can it tell me when the popup fires or who sees it?

No, and nothing that reads a page can. Triggers, timing, frequency caps, exit intent, scroll depth and audience rules all live inside the app and never appear on the page. That list is on the page under what this scan cannot see, because it is longer and more interesting than the list of things it can.

Does it say anything about how well the capture is performing?

Nothing at all. No capture rate, no conversion rate, no revenue, no traffic. This tool knows one page. If you want to know whether a capture rate is any good, that is a different question and there is a separate tool on this site that answers it against published figures.

Get started

The scan found the popup. It cannot see who it opens for.

Firing at the wrong moment turns a signup ask into an interruption. Exit intent, scroll depth and time on page are conditions you set in Nudgesmart, which is the half of a capture stack no page scan can see.