This article provides tips for troubleshooting common issues encountered with push notifications. Expected behavior When a user opens the app from a push notification, Swrve automatically sends a push engagement event. It is important that Swrve receives this engagement event to accurately track how many users have engaged with a particular notification. Swrve needs to receive the push engaged Read More
This depends on your target platform: If your target platform is iOS, you cannot receive a push notification on the iOS simulator. In this instance, you must test push notifications on a physical device. If your target platform is Android, you can test a push notification on an emulator if the emulator target uses a Read More
To enable an app to send push notifications to Google Play devices, you require a Firebase Cloud Messaging service account key. There are three main steps involved in creating a service account key for your app and entering it in Swrve: Create or import a project in Google’s Firebase Developer Console and collect the app’s Read More
At times, you may want to send different kinds of push notifications to your users depending on their in-app notification settings. You can often group notifications into specific categories, as the following examples show. A banking app may have different types of notifications: Statement-related notifications, such as informing users of a low balance or notifying Read More
Swrve supports the use of emojis in all push notification and in-app message campaigns. Emojis in push and in-app campaigns Push notification and in-app campaigns include an emoji picker directly in the notification content editor. To add an emoji to your message content, on the Content screen of the workflow, select the emoji icon and Read More
Learn how to configure the target audience of your daily recurring push campaigns using event recency criteria in our new campaign workflow for push notifications. We’ve redesigned our campaign workflow to be more consistent and streamlined across all channels. As we move each channel to the new flow, you might wonder what’s changed between the Read More
When creating push notifications in Swrve, the default action if a user engages with the push notification is to open the app. You can also configure the action to direct users to a specified URL or other location in the app—this is called deeplinking. For example, you might configure a push notification to direct the Read More
The current Swrve SDKs can request push device tokens as soon as the app loads or at a later time, such as after a tutorial. For more information about integrating push notifications in Swrve, see the platform-specific integration guides. Bulk push token upload If you have already collected a set of push device tokens for the Read More
Push notifications are sent to a device via the Apple Push Notification Service (APNS) using a device token that is unique to each app and user. These tokens can change over time, so Apple recommends requesting the latest device token each time the app opens. This device token is then sent to Swrve and used Read More