Marfeel supports OneSignal as a third-party notification service for all Marfeel-produced native apps and PWAs for partners that want to continue using it as an alternative to MarfeelPush.
Marfeel's use of OneSignal enables Marfeel's partners to take advantage of the following capabilities to increase engagement and traffic to their Marfeel native apps and PWAs:
Publishers are able to schedule notifications, making this service ideal for sending notifications to users in different timezones all over the world.
Multiple CMS plugins
OneSignal also provides plugins for various CMS' (Content Management System) that enable publishers to, for example, configure push notifications to be sent automatically whenever a new article is published.
Automatic re-engagement notifications
Partners can configure push notifications to be automatically sent to users that haven't visited a publisher's site for a defined period of time.
Partners can send push notifications to a subset of users based on the segments a publisher creates. For example, publishers can create segments based on country, and send specific notifications to those users for precise user targeting.
With OneSignal, publishers can define a set of user devices to test delivery of their push notifications before sending them to their readers.
OneSignal also delivers a variety of complete reporting options to track and examine different metrics for a partner's push notifications.
For partners with Marfeel PWAs and native applications, Marfeel supports their One Signal integration. As soon as their One Signal account is configured, partners receive an automated invitation from One Signal to set their password and access their panels and dashboard to start creating and sending push notifications.
Send push notifications
For a step-by-step guide on how to send notifications, see the One Signal documentation here.
There are minor configurations that are required when partners want to send push notifications to only PWA users, only native app users, or all users as explained below.
Send push notifications to PWA users
To send notifications to only PWA users, only Google Chrome Web must be enabled as a platform during the Options stage of creating and sending a message. That is, Apple iOS and Google Android must be disabled.
Sending push notifications on the web is only compatible for publishers under HTTPS and can only be sent to Android users as this technology is only supported by Chrome.
Send push notifications to native app users
To send notifications to only native app users, Apple iOS and Google Android must be enabled as platforms during the Options stage of creating and sending a message. That is, Google Chrome Web must be disabled.
Send push notifications to both PWA and native applications users
To send notifications to both PWA and native app users, two separate messages must be created and sent.
The reason two notifications are required is because when adding deeplinks to the message, there is a different logic and behavior for native apps and PWAs.
Deeplinks for PWAs are added in the Launch URL field. For native apps, they are added in the Additional Data field. If both fields for the same message have deeplinks in them with their respective platforms enabled (iOS, Android, and Chrome) the Launch URL takes precedence. This means that if a native app user that taps the notification with a deeplink, the link will open in the installed browser of their device and not in their installed native app.