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 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
Simply integrating the Swrve SDK and enabling push notifications enables you to track important metrics and run several effective campaigns, while advanced integration provides more in-depth tracking and additional campaigns. This article takes you through the various levels of integration, and lists the metrics and campaigns made possible by each. For developer information on how to complete basic and advanced integration, Read More
Track important user metrics and run several effective campaigns simply by integrating the Swrve SDK and enabling push notifications. These tasks can be completed by a single engineer in less than a day, and allow your marketing team to do the rest. Launch a variety of effective campaigns Push notifications Nurturing – Remind new and evaluating users that 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
No. You should not use Advertising ID to identify your users in Swrve. Why should I not use the Google Advertising ID? You should not use Advertising ID because it is resettable by the user. When users reset their Advertising ID they look like a new users to the Swrve system. This makes our segmentation, Read More
When you send an IAP event to Swrve, you must send a valid ISO currency code in the local_currency parameter. Swrve uses this currency code to convert the cost from the local currency to USD which is reported in the KPI Metrics dashboard. On Android, this is tricky because the OS doesn’t reliably report the Read More
Payloads and user properties are sent to Swrve in a similar fashion, but are intended for much different purposes. There is a 500 key/value limit on payload data, since each payload is constantly being calculated and processed. Currently, there is no limit on user properties, although only some properties can be pulled out of Swrve Read More
In the Unity SDK, if Swrve is called before it has finished initializing, you may get a NullReferenceException. How to resolve the issue To address this issue, go to Edit > Project Settings > Script Execution Order and move SwrveComponent higher in the list.