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. Setting up QA devices To access the QA Devices screen and set up a new QA device: Step 1: On the Read More
Swrve supports the use of emojis in all push notification and Conversations campaigns. Emojis in push notification campaigns Push notification campaigns include an emoji picker directly in the notification content editor. To add an emoji to your notification content, on the Add Content screen of the workflow, select the emoji icon and use the emoji dialog Read More
Swrve’s Currency Given KPI gives insight into the type and amount of in-app currency that has been given by the app to the user (without generating any revenue for the app). This KPI helps deal with situations where users are granted an initial amount of in-app currency for joining the app, for completing specific tasks Read More
This article provides an example of custom gameplay events. This example tracks the enemies that are killing game players. Send a custom event called Gameplay.Player.Death with an Enemy payload containing the class of enemy who killed the player. On iOS, this looks like the following:
|
1 |
swrve_event(swrve, @"Gameplay.Player.Death", @"{ "Enemy" : "zombie" }"); |
Make sure you don’t send the enemy’s name (for 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
In the Swrve SDKs, message display rules for an in-app message campaign work as expected under normal circumstances. However, there are some scenarios where a small number of users may see a campaign more than once. The SDK stores the in-app message display rules in a cache file on the user’s device. Some reasons why 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 Day 1/3/5/7 Retention KPIs Trend reports KPI Metrics Read More
Reengagement refers to the percentage of users that used the app yesterday and were also active today (regardless of their install date). Reengagement is based on a 24-hour rolling clock and users can contribute to this KPI only once per day. Day 1 reengagement, for example, is the percentage of users who started a session Read More
Swrve can keep track of the amount of revenue generated by each real-currency transaction visible to your app. The Revenue figure displayed on the KPI metrics dashboard is calculated by summing the amounts supplied for each ISO 4217 currency using a fixed exchange rate table (to USD) that is updated from time to time. For more 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