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
As of December 2015, it is now possible to log advertising and vendor identifiers. This article explains how to configure the iOS and Android SDKs to do so. To log IDFA (Identifier for Advertisers), add a constant called SWRVE_LOG_IDFA to the preprocessor macros under App Target > Build Settings > Preprocessing > Preprocessor Macros. This 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
Swrve is set up to handle a number of major world currencies. The following table lists the currencies supported by Swrve: Currency Code Description AED United Arab Emirates Dirham ANG Netherlands Antilles Guilder ARS Argentina Peso AUD Australia Dollar BRL Brazil Real BZD Belize Dollar CAD Canada Dollar CHF Switzerland Franc CLP Chile Peso CNY Read More
By default, all Swrve SDKs use HTTPS to communicate with Swrve servers. While this increases the security of your app’s connection with Swrve, you can configure the Swrve SDKs to communicate using HTTP if necessary. Follow the instructions below to do this: To deactivate the default setting, create a SwrveConfig object and configure as follows before initializing your shared 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
This article details the differences between the Swrve user ID and device ID and will help you determine which ID to use in your integration. What does the Swrve ID do? In Swrve, this ID is used to track a user for KPI reports, segmentation and dynamic content delivery. IDs are essential in delivering unique 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, 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 big issue, Read More