Push notifications
Overview
Push notifications are brief messages or alerts delivered to a user's device through mobile applications or websites. They serve to engage users by delivering timely and relevant information even when the user is not actively using the application or website.
NOTE:
- Push notifications for web and for iOS/Android are available on selected Ortto plans.
- Push notifications are not currently supported for desktop applications.
Accessing push notifications
To access the push notifications page, go to Settings > Channels > Push notifications.
Managing push notifications
The push notifications page allows users to:
Key notes
Creating push notifications with Ortto involves three main steps:
- Configure Platforms: Go to Settings > Push Notifications to set up your push campaigns. Customize settings for each platform by entering your application IDs and completing any required authentication steps. For Android and iOS, make sure to install the Ortto SDK.
- Capture Permissions: For web push notifications, set up a push capture widget to obtain permission from your contacts to receive notifications. For Android and iOS, permission is obtained through your app.
- Create Push Campaigns: Design and launch your push campaigns to send messages directly to your subscribers.
Android and iOS push
Ortto enables mobile push notifications using Firebase Cloud Messaging (FCM) for Android and Apple Push Notification Service (APNs) for iOS.
Android Setup
- Create or use an existing Firebase project.
- Add the project's
.json
file to Ortto's Android setup.
iOS Setup
- Choose Firebase or APNs and provide the necessary
.json
file, keys, and IDs in Ortto.
Ortto SDKs
- Ortto provides SDKs for Android and iOS, including APIs, libraries, and code samples.
Key steps to enable push notifications
- Set up a Firebase project or APNs.
- Install Ortto's SDK for Android or iOS.
- Identify your contacts.
- Track activity events (to capture custom activities in Ortto).
- Complete setup in Ortto.
Once these steps are completed, you can start creating and sending push campaigns.
iOS notifications
Configuring iOS notifications with Ortto involves a few steps aimed at developers familiar with app development:
- Firebase Cloud Messaging (FCM) Setup (optional):
- Configure a Firebase project if needed.
- iOS SDK Installation:
- Install Ortto's iOS SDK as per our documentation.
- Identify Contacts and Track Events:
- Use Ortto's tools to manage contacts and track user interactions.
For detailed instructions on adding certificates, keys, or FCM data, visit Ortto’s Developer docs under Push Notifications for Android and iOS in Settings > Channels > Push notifications > iOS notifications > Setup.
Android notifications
Setting up Android notifications with Ortto involves a few steps aimed at developers familiar with app development:
- Firebase Cloud Messaging (FCM) Setup (required):
- Configure a Firebase project as per our documentation.
- Android SDK Installation:
- Install Ortto's Android SDK following our guidelines.
- Identify Contacts and Track Events:
- Utilize Ortto's tools to manage contacts and track user interactions.
For detailed instructions on adding the service account .json
file, refer to Ortto’s Developer docs under Push Notifications for Android and iOS in Settings > Channels > Push notifications > Android notifications > Setup.
Web notifications
Web push notifications are delivered to a person's browser after they grant permission through a capture widget.
When you create a push campaign, Ortto tries to send the notification when the subscribed customer is online, within the time to live (TTL) you set.
To Enable web notifications:
- You need a service worker (SW) installed on your website at the domain where notifications will originate.
IMPORTANT:
- Web notifications are supported on desktop and laptop browsers, as well as Android Chrome.
- Safari on iOS (MacBook) does not support web notifications if the Safari version is older than 16.0 or macOS version is older than 13.0.
- Web notifications are not currently supported on iPhone browsers.
Learn more about setting up web notifications.
Push notification limits
In Ortto, the Push notification limits section allows you to control when push notifications are sent. This helps manage how often customers receive notifications and when they are triggered from journeys.
Key features
- Limit how frequently customers receive Ortto-generated push notifications.
- Specify specific dates and hours for when push notifications are triggered from journeys.
These limits are designed to prevent customers from receiving too many notifications in a short period, which could lead to them unsubscribing.
EX: If a customer is part of multiple simultaneous campaigns, such as purchase feedback or sales notifications, these limits ensure they aren't overwhelmed.
How to set limits
- Activate the required push notification limit restriction by selecting checkboxes.
- Configure settings such as the minimum time between notifications a customer can receive.
- Prevent people receiving more than one push notification every X hours.
- Specify dates when no notifications should be sent, or set hours during which notifications should not be sent except for urgent cases.
- Do not send push notifications within Journeys on specific dates.
- Do not send mobile push notifications within Journeys outside of waking hours (8am - 9pm), except for notifications set to ignore limits.
- When enabled, Ortto sends push notifications during waking hours (8am to 9pm in the recipient's timezone), unless the notification is set to override these limits.
Push subscription preferences
Platforms and subscriptions
- Push campaigns or shapes within a journey can target multiple platforms depending on your setup.
- Subscribers receive notifications on all devices or browsers they've enabled.
Device and browser limits
- Each subscriber can receive notifications on up to 5 devices per platform.
EX: A subscriber might receive notifications on 5 iOS devices, 5 Android devices, and 5 web platforms (across different browsers).
Multiple subscriptions
- Subscribers with multiple subscriptions on a platform are indicated by a number next to that platform in their profile.
- This means they may receive notifications more than once, such as on both their web browser and iOS device.
Counting recipients
- When sending a push campaign to all platforms, recipients are counted once per platform they're subscribed to.
EX: A contact subscribed to both web and iOS notifications is counted in both the web and iOS recipient totals.
Automatic unsubscribe
If a push campaign fails due to the recipient not having push notification permission (resulting in an Invalid push activity), they will be automatically unsubscribed from receiving further notifications on that platform.
EX: If a contact initially agrees to receive notifications but later blocks them or changes their permission settings, any subsequent web push attempt will lead to an Invalid push activity and automatic unsubscription from web push notifications.
NOTE: Invalid push activities due to reasons like duplicate sends or exceeding set limits won’t trigger automatic unsubscription.