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
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
It is now possible to get the resource A/B test and variant IDs directly from the Resource Manager in the Swrve SDK in real-time for use in your third-party reporting systems. To have this feature enabled for your app, contact your CSM at support@swrve.com, and then use the following code to get the resource A/B test Read More
By default, Swrve stores customer resources and content in our US data center. Some customers may require that we store their data in our EU data center, therefore to accommodate these requirements, Swrve has separate .swrve.com endpoints for customers who require data separation (for example, eu-dashboard.swrve.com). This article explains how to update the SDK configuration to point to Read More
The Swrve Events API enables you to send Swrve information that you know about your users, from outside the app, via the User API call. Use the User API call to set the value of custom user properties by making an API call to <app_id>.api.swrve.com (or <app_id>.eu-api.swrve.com for EU-configured apps). This is useful if you Read More
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
Swrve treats an app session as a new session if the user returns to the app after having left it for 30 seconds, by default. However, you can configure the new session interval of 30 seconds using the newSessionInterval config property. You may want to extend it to several minutes to facilitate users taking longer Read More
This article provides examples of how to use deeplinks to send events. These examples show how to implement deeplinks both from within your app or by linking to your app from a partner app. Implementing the below examples in your code enables your Swrve users to send events via deeplinks from in-app messages of the form: swrve://?event=<event name> [SwrveSDK Read More