Opt-in
Opt-in is a user's explicit consent to receive push notifications — clicking Allow on the browser's system prompt. Without opt-in, no subscription is created and the user never enters the base for future campaigns; it's the first, mandatory step before any web push.
Why opt-in rate is a key metric
Opt-in rate — the share of people who allow push out of everyone shown the prompt — directly determines the size of the base you build: even with heavy incoming traffic, a low opt-in rate leaves you with few subscribers for future campaigns. It's shaped by when the prompt appears, whether there's a soft pre-prompt explaining the benefit, and how much the page or PWA is trusted overall.
How PWAs raise opt-in rates
A standard tactic is not firing the browser's system prompt the moment the user lands, but showing a custom screen first — allow notifications so you don't miss the bonus — and only triggering the real system prompt after the user agrees on that screen. APEX's push engine works with the opt-in base you've already built, segmenting it and running triggered and scheduled campaigns, so the size and quality of that base sets the ceiling for the whole push channel.
FAQ
- What happens if a user clicks Block instead of opting in?
- No subscription is created, and the browser typically won't show that system prompt to them again — getting that user into the push base after that requires a different channel.
- Can you ask a user again after they decline?
- Not directly through the browser API, but you can prompt them to reinstall the PWA or reach them through another channel (email, retargeting) where they'll see the subscribe offer again.
Cloaking, anti-bot, push, split tests and your own domains — in one service.
Get started free