Target and track your audience based on the date and time of custom user properties with date-typed user properties. For example, target users who have an upcoming event, such as a flight or concert, or ask customers to leave a review a few days after an event, such as checking out of a hotel or Read More
The Swrve SDK automatically collects the following device attributes on iOS, Android, and Unity. Each attribute is sent as a user property and updated each time they start a new session. User attribute name Description Example values swrve.device_width The width in pixels of the device screen. 1125 swrve.device_height The height in pixels of the device 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
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
At times, you may want to send different kinds of push notifications to your users depending on their in-app notification settings. You can often group notifications into specific categories, as the following examples show. A banking app may have different types of notifications: Statement-related notifications, such as informing users of a low balance or notifying Read More
Target your users based on their risk of churning with Swrve’s new churn propensity feature. What are churn propensity scores? Swrve generates a score for each user who has not already churned from your app on a scale of 0 to 100 indicating how likely they are to churn within the next 30 days—that is, 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
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
The Swrve SDK does not use the IDFA as of version 2.0.1. New submissions to the app store using older versions of the Swrve SDK may be rejected by Apple, so Swrve strongly recommends updating to the latest SDK. If you can’t upgrade to the latest Swrve SDK, follow the instructions below. If you upgrade Read More