You have two filter options:
- By the installation version (first app version)
- By the current version (current app version)
When applying the filter, you select the users with a certain app version while ignoring information about returns/sessions. It means that you use the filter to build a cohort and then calculate retention rates regardless of the current app version.
Let’s say a user installed the 1.2 version of the application. If we apply the “first app version = 1.2” filter then the user will enter our cohort and we can calculate his retention rate. If the user updates the app to version 1.4 then he will still remain in the calculation because it is based on the first app version only. If after that we apply the “current app version = 1.4” filter then our user will enter the new cohort because the first app version is in this case irrelevant and the cohort is made of the users currently using the 1.4 version. Depending on the selected retention type, the retention rate of this user will be calculated from day 0 or 1 regardless of the app version he was using at that time.
Install date - filter users by the app installation date (the app installation date is the date and time of the first app launch). Event app version - filter users by the app version at the moment of the event execution (payment, session, etc. - based on the calculated metric). Current app version (App version) - filter users by the current app version (information is drawn from user cards). The ‘Filter by App versions’ is unavailable for the retention metrics. First app version - filter users by the original installation version (information is drawn from user cards). Channel type - if you use the filter by traffic type, you can filter traffic by paid and organic users. Channels - filter by traffic source. We receive channel information from the connected Attribution trackers. If we are talking about web SDK, then we receive information using the UTM parameter attached to the link that led the user to your website. Campaign - when applied to a campaign, it is used to select user sessions in specific campaigns. We receive campaign information from the connected Attribution trackers. In case of web SDK, we receive information using the UTM parameter attached to the link that led the user to your website. Country - filter users by country (defined by IP address), e.g. select Spanish users, etc. For most metrics, the user country is the country in which the person who performed the event resides. For some other metrics (e.g. retention rate), however, country information is pulled from the user card. In SDK 1 we get country information during the SDK initialization, in SDK 2 we receive it with every event. Language - filter users by locale, e.g. select users with English locale and compare them with British locale users. In SDK 1 we get country information during the SDK initialization, in SDK 2 we receive it with every event. Devices - filter users by the selected device model. In SDK 1 we get country information during the SDK initialization, in SDK 2 we receive it with every event. OS version - filter users by certain OS version. In SDK 1 we get country information during the SDK initialization, in SDK 2 we receive it with every event. Lifetime - number of days between the first and the last app launch. Information obtained from the SDK.
For most metrics, filters are applied to the data received at the time of the event. For some other metrics (e.g. retention rate, installs), however, information is pulled from the user card.
Paying capacity - all paying users are divided into 5 segments according to the sum paid: minnows, dolphins, grand dolphins, whales, and grand whales. Use this filter to find out the segment prevailing in your project or the most profitable segment. Open ‘Tuning - Paying capacity’ to change the sum that is required to enter each segment. Paying status - segment users into free and paying. Payment sum - filter users by the sum paid. Use it to select the users who paid $100 or more, etc. Payment count - filter users by the number of payments, e.g. find the users who made two payments or more and study their behavioral metrics. First payment date - filter users who made their first payment before or after the defined date. Last payment date - filter users who made their last payment before or after the defined date. Ad unit - filter data by ad unit. Information for filters by ads is based on data from ad networks (Ad revenue). Learn more about integration. Ad source - filter data by ad source. Ad placement - filter data by ad unit placement. Ad network - filter data by ad networks.
Subscription bundle - the name of the subscription active at the time of the event (you can compare the behavior of users who purchased a subscription to one part of the functionality with those who purchased a subscription to another part). Subscription state - the current state of the user's subscription, which can have the following values:
- None - the user does not have and never had a subscription
- Unsubscribed: - Expired - the user's active subscription has expired, and they didn’t renew it during the Grace period. - Refunded - the user has refunded their subscription.
- Trial - the user is using a trial period of any subscription Subscribed New - the user purchased a subscription for the first time.
- Renewed - the user renewed their subscription (using the auto-renew option or manually during the Grace period)
- Reactivated - the user purchased a subscription after being previously marked as Expired or Refunded.
- Upgraded - the user purchased a more expensive subscription.
- Downgraded - the user purchased a cheaper subscription.
Subscription filters are built on the basis of data received from SDK and app stores. Integration with stores allows you to receive information about subscription purchases even if the user hasn’t opened the app.
Ad impressions - filter users by the number of impressions over the selected period of time. Ad revenue - filter users by the amount of ad revenue earned through ad networks. Advertising ID - filter users by the device’s ad ID to analyze the metrics of individual users. Name, Email, Gender, Age - if you pass data for these fields, you can use them to filter. Android ID - filter users by the selected device IDs. Cheater - a user property used to filter cheaters out of the report. Tester - a user property used to separate sessions of testers and ordinary users. Read about adding devices. Crossplatform user ID - filter data by cross-platform usage and display only users with the specified ID. devtodev ID - a user ID specified by the app developer. Display diagonal - filter users by by the display diagonal. The information is retrieved from the SDK. First app version - filter users by the original installation version. Last seen - filter users by the date of last activity, e.g. select the users who opened the app last month. Main ID - filter users by an ID that you created. Payer - filter users by payment status - payers and non-payers. Push available - filter users by push notification opt-in status - those who provided the consent and who didn’t. Segment - select the users who are included in the specified segment. Timezone offset - filter users by their timezone. The information is retrieved from the SDK. User level - use this filter to select lists of users who leveled up to a specified level.
The information about traffic we retrieve from a UTM code or connected Attribution trackers. The information received through the Attribution tracker takes priority over the information received through devtodev SDK. The information we collect about the traffic source allows you to filter data by the following parameters.
Type - filter users by traffic type, e.g. you can use data from the tracker to select users coming from a paid source (External ad) or from External organic traffic source, or from Cross-promo ad. Source - filter data by the source of user data, e.g. data retrieved using the Custom postback API or a specific ad network (Tenjin, Branch.io, etc). Publisher - filter users by traffic source. The source is retrieved from the ‘utm_source’ parameter or an attribution tracker. Sub publisher, Sub placements - filer data by traffic type. The type that is retrieved from the ‘utm_medium’ parameter or an attribution tracker. Campaigns - filter data by campaigns. The data on campaigns is retrieved from the ‘utm_campaign’ parameter or an attribution tracker. Ad set - filter users by ads. Sub Ad groups - filter users by ad group. Sub sites - filter data by ad placement. Sub keywords - filer user data by keywords. The keywords are retrieved from the ‘utm_term’ UTM parameter.