The lifetime spend, lifetime minutes in app, and app version data on the User Attributes screen is calculated automatically for you by Swrve. The other attributes (level, age, gender and location) must be supplied by your development team to Swrve during your Swrve integration process. All default user attributes included in the user event must be 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
This is because KPIs are only calculated going forward in Swrve. The user state, however, is retroactive, so if you have a user who has spent money in the past, for example, they are displayed in your payers segment the next time they use your app.
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 Messaging KPI Charts screen Segments screen Data written every 2 seconds. Day 1/3/5/7 Retention KPIs KPI Charts screen KPI Read More
Review this article to identify causes for revenue disparity between Swrve and other services. You can identify many causes for revenue differences by comparing the details in the Swrve service with the revenue totals seen in your mobile app store. You can investigate many revenue differences by reviewing the data received for a specific device. Read More