Push notifications let you reach customers directly through their browser, even when they're not on your site.
This guide answers common questions about push subscribers, settings, and advanced use cases.
💬 Getting started? Read Get Started with Push Notification Channel first.
Subscription & Contact Counting
Do push subscribers count toward my contact limit?
Yes. Push subscribers are standalone contacts included in your billable contact count. If a contact is subscribed to multiple channels (email, SMS, push), they're counted as one contact.
Example: If you have 1,000 email subscribers and 500 push-only subscribers, your total billable contacts = 1,500 (not 1,000).
💡 Multi-channel subscribers (email + push, or SMS + push) count as one contact.
What happens if someone subscribes to push, then provides email or SMS at checkout?
Their email/SMS merges with the existing push contact automatically during checkout. This creates one unified contact profile.
However, if they subscribe to email/SMS via a signup form (not checkout), the cookie ID may be overridden, creating duplicate contacts.
Why do I have duplicate push contacts?
Duplicate push contacts occur in two scenarios:
Same person uses different browsers: If a customer subscribes using Chrome, then Firefox, they create two separate contacts (each browser = separate opt-in).
Push subscriber fills out email signup form: When a push subscriber later submits an email signup form (not checkout), the cookie ID may be overridden, creating a duplicate contact instead of merging.
To minimize duplicates:
Encourage email/SMS collection at checkout (merges automatically).
Regularly review your contact list for duplicates in Audience → filter by push subscription status + duplicate IP addresses.
Browser Compatibility & Technical Setup
Does push work on iPhone/iOS devices?
No. Web push notifications do not work on any browser on iPhone (iOS), including Chrome, Firefox, Safari, or Opera. This is an Apple platform restriction, not an Omnisend or browser limitation.
Push works on:
✅ Android mobile devices (Chrome, Firefox, Opera, Edge)
✅ Windows, macOS, Linux desktops (Chrome, Firefox, Opera, Edge)
Browser | Windows | Linux | macOS | Android | iPhone (iOS) |
Chrome | ✅ | ✅ | ✅ | ✅ | ❌ |
Firefox | ✅ | ✅ | ✅ | ✅ | ❌ |
Opera | ✅ | ✅ | ✅ | ✅ | ❌ |
Edge | ✅ | ❌ | ❌ | ✅ | ❌ |
Safari | ❌ | ❌ | ❌ | ❌ | ❌ |
Why is my push notification test not working?
Check these 5 things:
Your browser is open: Push notifications only appear when the browser is running.
You clicked "Allow": Verify you previously accepted push permissions on your website. Go to Audience → Segments → filter: Subscription Status = Subscribed to Browser Push Notifications to confirm.
You're using a supported device: Tests don't work on iPhone. Use Windows, macOS, or Android.
You didn't click "Block": If you previously blocked push notifications, clear browser permissions and revisit your site:
Chrome: Address bar → 🔒 icon → Site settings → Notifications → Allow
Firefox: Address bar → 🔒 icon → Permissions → Notifications → Allow
HTTPS is active: Your website must have a valid SSL certificate (https://).
Why is the browser push permission prompt not appearing?
Common causes:
You previously clicked "Block": Your browser remembers this. Check the address bar for a 🔔 or 🔒 icon → change to "Allow."
Wait 2–3 seconds: The prompt has a built-in delay after page load.
Test in incognito/private mode: Use a fresh browser session where you haven't blocked permissions.
No HTTPS: Your Store Settings URL must start with https://. Push requires an SSL certificate.
Browser compatibility: Push only works on Chrome, Firefox, Opera, and Edge (not Safari).
Push is disabled: Verify Store Settings → Push Notifications → Collect push channel subscribers is toggled on.
What HTTPS/SSL requirements are needed for push notifications?
Your website must have a valid SSL certificate (https://). Push notifications will not work on:
http://URLsSites without SSL certificates
Sites with expired or invalid certificates
To verify: Your store URL should start with https://yourstore.com.
How do customers subscribe to push notifications?
When a customer visits your website for the first time (after you enable push in Store Settings):
After 2–3 seconds, their browser shows a permission prompt asking: "[Your site] wants to show notifications"
If they click Allow, they're subscribed to push notifications.
If they click Block, their browser won't show the prompt again.
Important: The prompt is controlled by the browser (Chrome, Firefox, etc.), not Omnisend. You can't customize the message or timing beyond the default 2–3 second delay.
Automation
Why don't push subscribers receive welcome automations?
Push subscriptions do not trigger signup events. Welcome automations set to trigger on "Subscribed to Marketing" won't send messages to push-only subscribers.
To send welcome messages to push subscribers:
Go to Audience → Segments → Create Segment
Set filter: Subscription Status = Subscribed to Browser Push Notifications
Go to Automation → Create Workflow
Trigger: "Contact enters segment" → Select your push segment
Add a Push Notification message in the workflow
This way, contacts subscribing to push notifications will enter the segment and then the automation.
💡 Tip: Use Push Notifications to welcome subscribers who aren't subscribed to Email or SMS yet.
Have more questions? Contact us at [email protected] or via in-app chat.