- Technology
- Native SDK (OneSignal / FCM)
- Android 13+
- Runtime permission
- On tap
- Opens a URL in the app
- Frequency
- Transactional > marketing
Native push, not web push
Your website's browser notifications rely on the Push API, which Android WebViews don't support. A converter with push built in includes a native SDK; you send from the provider's dashboard or API, and messages arrive even when the app is closed.
Ask at the right moment
Android 13 and newer show a system permission prompt. If it appears on first launch, many users tap “Don't allow” — and rarely change it later. Better moments:
- After the first order: “Get delivery updates?”
- After following a topic or saving a search.
- From a settings screen on your site, triggered by the app.
Campaign types
| Type | Example | Frequency |
|---|---|---|
| Transactional | “Your order is out for delivery” | As it happens |
| Reminders | “Class starts in 1 hour” | As scheduled |
| Content | “New: autumn menu” | Weekly at most |
| Promotional | “20% off this weekend” | A few a month |
| Win-back | “Your cart is waiting” | Once, sometimes twice |
Deep links
Every push should open the exact page it talks about. Pass a URL in the notification data; the app loads it in the WebView. A push that opens the home page wastes the tap.
Measure
Track opens and the action after the open (purchase, booking) — tag push URLs with utm_source=push so your website analytics shows the result.
Frequently asked
Is push free?
Firebase Cloud Messaging is free; OneSignal has a free tier for mobile push. Check current limits.
Can I send push to iPhone users from an Android app?
No — push goes to installs of your app. iPhone users need an iOS app or web push on a home-screen PWA.