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
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
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
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: swrve_event(swrve, @”Gameplay.Player.Death”, @”{ “Enemy” : “zombie” }”); Make sure you Read More
If you’re using one of the Swrve SDKs, you may be wondering how to ensure that batched events are received in the order they are sent. Below is a list of how events are processed for funnels. Use this as a guideline for ensuring event order in funnels: Swrve creates a timestamp for each event Read More
It takes 15 minutes for the Swrve service to update after you send an event. If you want to debug in real-time, use the QA User Logging screen. To access this screen, on the Settings menu, select QA devices. To view events for a specific device, select Logging . For more information about the QA User Logging screen, see How Read More
The Swrve SDK sends events in batch to save bandwidth and decrease the amount of requests needed to send details to Swrve. If you’re seeing errors in logs regarding these batch events, these batch events are being rejected by Swrve. Previously, the main cause of rejected batch events was virtual currencies either not set up Read More
Track item sales using IAP, purchase and custom events. IAP events — sales for real money Use the IAP event to track anything that can be bought for real world money in your app such as virtual currency bundles for a game, virtual items or unlocked functionality. Sending IAP events populates the Top Items report, Read More
This article highlights some common methods for using events and payloads to track users. Identify the level of users who make their first purchase Send an event (First.Purchase). Attach the payload of the current level of the user (“level”:3). Graph the event over all time or for the time period of your latest update. Locate the region Read More