The Swrve SDK automatically collects the following device attributes on iOS, Android, and Unity. Each attribute is sent as a user property and updated each time they start a new session. User attribute name Description Example values swrve.device_width The width in pixels of the device screen. 1125 swrve.device_height The height in pixels of the device 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 is a multi-channel customer engagement platform that provides hyper-targeting and hyper-personalization in real-time to automate relevant moments of interaction that acquire, retain and monetize customers. The Swrve native Roku SDK enables your app to use all of these features on the Roku OTT platform. This guide contains all the information you need to integrate Read More
By default, the Swrve SDK performs native device logging on iOS (Console Logs), Android (Logcat) and Unity. If required, you can disable these logs. On Android and iOS, you can also change the default logging level. Additionally, the Swrve Unity SDK creates a small delay of approximately 14 milliseconds (ms) when logging. This is a not a 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
Add customized, channel-specific content with Swrve’s new campaign workflow. Swrve’s streamlined campaign workflow gives you several options to set up, customize, and manage your campaigns. The new campaign workflow is now available for all campaign types except Conversations and geo-triggered notifications. This article covers adding content to an email or SMS campaign. For information about adding Read More
Marketers can employ the A/B test Resources tool to split their user group in half (or thirds, quarters, and so forth), and use those segments in different campaigns. These steps will allow you to A/B test separate campaigns while ensuring that users are not being exposed to more than one. There are three main steps involved in splitting Read More
Latency in Swrve depends on the type of data in question. The table below lists the approximate latency for different reporting data in Swrve. Data type Relevancy Total latency in realtime mode Segment membership A/B tests Campaign audiences Trend reports Segments screen Data written every 2 seconds All KPIs Trend reports KPI Metrics dashboard A/B Read More
After splitting up your user base with Swrve’s A/B Resources tool, you can use those segments in different campaigns to determine where your in-app message is most effective. Create an in-app message to target A/B test variants Step 1: In the Campaigns center, select Create campaign. Step 2: On the Choose your marketing channel screen, select In-app message as your campaign channel, Read More
To enable an app to send push notifications to Google Play devices, you require a Firebase Cloud Messaging server key. There are three main steps involved in creating a server key for your app and entering it in Swrve: Create or import a project in Google’s Firebase Developer Console and collect the Server key and Sender ID. Enter the Read More