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
This article provides tips for troubleshooting common issues encountered with in-app messages. Expected behavior In-app messages are triggered by events. The in-app message workflow enables you to create an audience filter so that the message is only shown to a subset of users who trigger that event. For iOS and Android, in-app messaging is automatically integrated after you Read More
To make it easy to test your customers’ end-to-end experience, Swrve allows QA devices to bypass certain rules that apply to app users when the campaign is live. Audience filters When previewing an in-app message, a QA device does not need to fulfill audience filter requirements. This saves you time trying to create the specific user behavior and history required to Read More