Push Notification Deliverability

How Push Notification work

Push Notification is one of the communication channels available in Engage for Campaigns and Automations. Sending Push Notifications requires two things:

1. A Push Notification Service. We currently support FCM, Expo, and OneSignal.

2. The user's device token. The device token is a unique identifier of the user's mobile device. This token makes it possible for the device to receive Push Notifications. The token is also generally referred to as registration token.

How to get a user's device token

• If you are using FCM as the push service, here is how to track the device token.

• If you are using Expo as the push service, here is how to track the device token.

• If you are using OneSignal as the push service, you do not need to track the device token on Engage. Here is how to use OneSignal with Engage.

• If you have connected services like Segment or PostHog to your Engage account and use their respective SDKs to track users' device tokens, the device tokens are automatically synced to Engage. No further action is required from you.

Improving deliverability

At every app launch, we recommend you get the device token and resend it to Engage. Device tokens expire or may be automatically unregistered. Refreshing the token ensures the user's device token stays up to date at every time. Engage can store up to 5 different device tokens per user.