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’s audience filter tool enables you to define multiple filters and highly customize the targeting of your resource A/B tests, in-app messages, embedded, and push notification campaigns. You can use event recency filters and operators to target and track your audience based on the recency of custom events or purchases; for example, users who have Read More
Sites such as Facebook and Twitter provide URLs that make it very easy to post, tweet and share content from outside their platform. Swrve enables you to use these URLs in your in-app messages to create effective social campaigns that make app-referring and content-sharing directly from your app a seamless experience. Facebook To encourage users Read More
This article covers common questions about server-side implementations in Swrve. What is a server-side implementation? A server-side implementation is the use of Swrve without or in addition to the Swrve platform-specific SDKs. Typically this is done by using the Swrve Events API to send events and user properties in an automated way. Some common use cases for a Read More
To QA test your integration, A/B tests, and campaigns, you must first set up the QA devices you want to use for testing. Manage your QA devices and access device event logs with the QA Devices screen. Set up QA devices To access the QA Devices screen and set up a new QA device: On the Settings menu, 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
Swrve comes with three preset user roles—Company Admin, Full Access (previously called Default User), and Read Only. Our Roles Management and Assignment feature also lets you create custom user roles with any combination of permissions. You can assign roles to your users on a company-wide, app-level, or per user basis. For example, you may have Read More