What is this store using to capture email?
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 exampleHide 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.
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 698 KB of HTML from https://www.deathwishcoffee.com/ · HTTP 200 · 1 redirect followed
Detected on this page
- Onsite popup or form app
- klaviyo.com/onsiteIs anything on this page capable of rendering a popup or an overlay form?
- Email marketing platform
- klaviyoIs there somewhere for a captured address to land?
- SMS capture
- postscriptIs a phone number being collected alongside the address, or instead of it?
Not detected on this page
- Email field in the delivered HTML
- no matchCan a shopper with JavaScript switched off still hand over an address?
Capture-adjacent apps on the page
- Klaviyo
- Email / Onsite formsFrom the same signature table the app detector uses.
- Postscript
- SMSFrom the same signature table 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
Theme name and version, read out of the same page.
A curated signature table matched against the same HTML.
You found the machinery. Nothing here says when it fires.
The list above is the machinery. What decides whether any of it works is when the popup fires and who sees it, and none of that is in the page. That is the half Nudgesmart does: targeting on real on-site behaviour, with per-campaign reporting on what it captured.
How it's calculated
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 HTML of 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.
Four checks against one page. The interesting half of this tool is not the four — it is the list underneath the result of what no page scan can answer, which is longer and is printed rather than implied.
- The fetch
- One request for the address you enter, from our server, following redirects and sending a normal user agent. The redirect is the part that matters: the bare domain answers with a redirect and an empty body. 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 of static HTML. 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.
Nudgesmart 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.
| Sample page | Coverage | What was matched | Verdict |
|---|---|---|---|
| Stock Dawn, Klaviyo and an SMS app | 3 of 4 | Onsite popup or form app, Email marketing platform, SMS capture | Coverage, not a score |
| Agency theme plus the built-in Shopify newsletter form | 1 of 4 | Email field in the delivered HTML | Coverage, not a score |
| A Theme Store theme that still carries its theme_store_id | 0 of 4 | none of the 4 checkable mechanisms visible in this page | Coverage, not a score |
| A popup vendor that is not in the signature table | 1 of 4 | Email field in the delivered HTML | Coverage, not a score |
| Headless storefront — Shopify assets, no theme object | 2 of 4 | Onsite popup or form app, Email marketing platform | Coverage, not a score |
| Not a Shopify store at all | 0 of 4 | none of the 4 checkable mechanisms visible in this page | Coverage, 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 this number doesn't tell you
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 static fetch — 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 fetch 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 your traffic or anyone elses
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 markup it fetched.
Questions
What does this audit actually check?
Four things, all of them visible in one fetch 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 delivered HTML, and whether anything is collecting a phone number. It reports which of the four 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 a scan of the delivered HTML cannot see anything that arrives later. A popup injected by a tag manager, rendered only on a second page view, or loaded by a script that this table 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 are never printed into the markup. 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 of HTML. 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.
Finding the popup is easy. Firing it at the right moment is not.
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.
