Web push vs. email: which alert channel actually delivers

If you build an alerting product, you'll eventually face the choice between web push and email as your primary channel. Both work. Neither is strictly better. But they fail differently, and the failure modes should decide the choice.

Web push delivers in seconds when it delivers. The service worker gets the payload, shows an OS-level notification, and the user either taps or dismisses. Median end-to-end latency on a well-tuned pipeline is under 10 seconds. That's the killer feature: for time-sensitive alerts, nothing else short of SMS is close. The tradeoff is fragility. Browsers throttle push aggressively on battery-saver modes, sandbox it in different ways per platform, and give users no way to see what they missed once a notification is dismissed. A push that arrives while your phone is face-down and gets swiped away is gone.

Email is the opposite. Slow but persistent. Median delivery is 30 to 120 seconds, sometimes longer if the provider quarantines your message for reputation checks. But once it lands, it stays. Users can search their inbox, forward the alert, and reread it a week later. For anything the user might act on hours after the fact — a research digest, a policy summary, a weekly brief — email wins.

The mistake we see most often is treating these channels as substitutes. They aren't. They serve different reader modes. Push is for 'do I care right now?' Email is for 'what happened while I wasn't looking?' A product that ships both with the same content is silently spamming its audience. A product that ships push for real-time triggers and email for daily or weekly digests respects both modes.

Cost matters less than most teams think. Both channels are effectively free at Northtape's scale — the marginal cost of a web push is a few milliseconds of CPU, and transactional email through modern providers is fractions of a cent per send. What isn't free is the trust budget. Every notification a user doesn't want costs future engagement disproportionately. A single false-positive push in the first week can end the relationship. A single spammy email can trigger a filter rule that catches your legitimate messages for months.

Our recommendation for a fintech or crypto alerting product: default new users to in-app only, with web push as an explicit opt-in for real-time triggers on a small number of tracked assets. Ship a weekly email digest with the top five items on their watchlist. Don't offer daily email until the user has been active for at least two weeks — the retention data shows daily digests to unengaged users mostly train them to filter you.

The technical work is comparable. Both channels need per-user subscription state, delivery logs, unsubscribe flows, and dead-subscription pruning. Web push adds a service worker and VAPID key management. Email adds SPF, DKIM, DMARC, and bounce handling. Neither should be underestimated — every alerting product we've seen has run into edge cases in the first month.

One thing both channels get wrong out of the box: they're too aggressive about retries. A web push that fails once will often get retried immediately, then again a minute later. An email that soft-bounces gets requeued four or five times. Both patterns burn user trust and provider reputation. Configure retries conservatively — one retry after five minutes, then let it drop. The information is stale by then anyway.

The last consideration is the failure surface. Web push failures are silent from the user's perspective — they never know a message was attempted. Email failures land in the sender's bounce reports and can accumulate against domain reputation. This means email needs more operational attention. Push needs more product attention: if your open rates drop below 30%, you're pushing too often, and no engineering fix will save you.

Ship both. Segment them by intent. Treat every notification like it costs you something because it does.

FAQs

Should I turn on both push and email alerts? Only if they serve different purposes. Push is for "do I care right now", email is for "what happened while I wasn't looking" — sending identical content on both channels reads as spam, not redundancy.

Why did I stop getting push notifications? Browsers throttle push aggressively on battery-saver modes and sandbox it differently per platform. A dismissed push leaves no record, so check your alert settings if delivery feels inconsistent.

What's the recommended default for a new account? In-app only to start, with push as an explicit opt-in for real-time triggers on a small number of tracked assets, and a weekly email digest once you've been active a couple of weeks.

Does email delivery cost more than push? Both are effectively free at this scale. The real cost is trust: an unwanted notification on either channel costs future engagement, not money.