Most visitors who leave your site will not come back on their own. You have two ways to reach them without paying for the same traffic twice: an email address they gave you, and a push subscription their browser granted.
They are not substitutes. Email is a durable, portable record of who someone is. Push is a thin, instant ping that lasts only as long as the permission does. The mistake is treating the choice as taste instead of a match between message and moment.
Here is what permission costs, when each channel wins, and which numbers settle the argument.
What does push permission actually cost you?
The browser prompt is a single use resource. Once a visitor blocks notifications, that browser will not ask again, and almost nobody reverses it in settings. On iOS, web push needs the visitor to add your site to their home screen first, so part of your mobile traffic cannot be reached this way.
The prompt is also a brand moment: an operating system dialog carrying your site name, shown at whichever moment you chose. On first load the answer is usually no, and permanently so. Email costs a form field, but you can ask again later. Push gives you one attempt.
When do push notifications beat email?
Push wins when the message is useful for hours rather than weeks and the visitor already knows your site.
- Back in stock on a watched item. Intent already exists.
- A price drop on a product they viewed. Same urgency.
- A cart reminder within the hour, while they are still shopping elsewhere, which pairs with a fuller cart abandonment sequence.
- Something starting now: a live session, a flash window, a time boxed offer, or a reason to click that is useless tomorrow.
When does email still win?
Email wins whenever the message has to be read rather than glanced at. A considered purchase needs options, photos and a price breakdown, which is a document, not a ping. Guides and newsletters are the same, and confirmations have to stay findable months later.
Email also outlives devices, while a push subscription is tied to one browser on one device, so a visitor who switches phone leaves your push audience silently. Push carries the nudge, email carries the argument, which is why the strongest welcome flow is still built there.
When and how should you ask for push permission?
Never on first load. Ask after an action that suggests a notification would be welcome: viewing the same product twice, using a size guide, or starting checkout.
Say what the notification will carry before the native dialog appears, and treat the ask as one interruption among everything else on the page, with the restraint described in popup timing and triggers. If a popup closed a moment ago, stay quiet.
Use two steps. Step one is your own element, a popup or inline card that explains the offer in your words, with a button labelled for what the visitor gets. Step two only happens if they press it, and that click triggers the real browser prompt on someone who has already agreed in principle.
On a decline, record it, stop asking for a long stretch, and never fire the native prompt anyway. You keep your one prompt, and the same restraint keeps email capture from feeling like a toll gate in collecting emails without annoying people.
How do you segment push, and how often should you send?
Segment on the last meaningful action, because it decides what a notification can usefully say.
| Segment | A notification that fits |
|---|---|
| Viewed a category, bought nothing | New arrivals in that category, sent rarely |
| Viewed one product twice | Price drop, restock or review count |
| Started checkout, did not finish | Cart reminder within the hour |
| Redeemed a first order discount | Shipping update, then a second purchase nudge later |
| Subscribed, never bought | One high value offer, then quiet |
Then set two budgets: a cap per channel and a ceiling on total touches per visitor per week, counting the permission ask as one. Push fatigue is nastier than email fatigue because muting notifications at the operating system level never shows up in your dashboard as an unsubscribe. Watch click rate at constant volume beside permission revoked rate, and apply the same thinking as popup frequency caps, one level up.
How do you measure push and email against each other?
Compare per recipient rather than per send.
| Metric | Push | |
|---|---|---|
| Opt in rate | Subscriptions divided by permission opportunities | Addresses captured divided by form sessions |
| Click rate | Clicks divided by delivered notifications | Clicks divided by delivered emails |
| Revenue per recipient | Attributed revenue divided by delivered | Attributed revenue divided by delivered |
| Cost of loss | Permission revoked, often invisible | Unsubscribe, visible and reversible |
Then choose per message rather than per habit.
| Message | Better channel | Why |
|---|---|---|
| Restock or price drop | Push | Useless tomorrow, no layout needed |
| Cart reminder within the hour | Push | Timing is the entire value |
| Order confirmation | Must be findable later | |
| Product comparison or guide | Needs length, images and links |
The two are additive: push is a fast lane for time sensitive nudges, email is a home for anything that has to be read. Capturing both, with the right ask at the right moment, is what heycustomer.byako.dev is for, since one visitor timeline drives the popup, the permission ask and the follow up.
FAQ
Q: Should I ask for push permission on the first page load? A: No. A first load ask gets answered before the visitor has a reason to say yes, and a block is permanent in that browser. Wait until they view a product or start checkout.
Q: Does push replace my email list? A: No. Push is tied to one browser on one device and vanishes when the permission is revoked or the visitor switches devices. Use it for time sensitive nudges and keep building the list.
Q: How do I know if push is annoying people? A: Watch click rate at constant volume beside permission revoked rate. Falling clicks at the same volume means fatigue, and operating system level mutes are worse than unsubscribes because reach drops with no signal.
Q: Can I use a popup to ask for push permission? A: Yes, and it is usually the best option. Let the popup explain the offer in your own words, then trigger the real browser prompt only when the visitor clicks the button inside it.