> For the complete documentation index, see [llms.txt](https://docs.devtodev.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devtodev.com/metrics-and-glossary/sdk-metrics.md). # SDK Metrics ## **ARPU** **ARPU** (*Average Revenue Per User*) – the average revenue generated by any user within a defined timeframe. Every user is taken into account. Defined as the total gross revenue within a given period divided by the number of active users within the same period. ***ARPPU*** (*Average Revenue Per Paying User*) – the average gross revenue generated by a paying user. Non-paying users are not taken into account. Defined as the total gross revenue within a given period divided by the number of paying users within the same period. **1-day Cumulative ARPU** – cumulative average revenue per active user over the first 24 hours. The metric is calculated as total revenue over the first 24 hours divided by the number of active users over the selected report period. **3-day Cumulative ARPU** – cumulative average revenue per active user over the first 3 days. The metric is calculated as total revenue over the first 3 days divided by the number of active users over the selected report period. **7-day Cumulative ARPU** – cumulative average revenue per active user over the first 7 days. The metric is calculated as total revenue over the first 7 days divided by the number of active users over the selected report period. **14-day Cumulative ARPU** – cumulative average revenue per active user over the first 14 days. The metric is calculated as total revenue over the first 14 days divided by the number of active users over the selected report period. **30-day Cumulative ARPU** – cumulative average revenue per active user over the first 30 days. The metric is calculated as total revenue over the first 30 days divided by the number of active users over the selected report period. **60-day Cumulative ARPU** – cumulative average revenue per active user over the first 60 days. The metric is calculated as total revenue over the first 60 days divided by the number of active users over the selected report period. **90-day Cumulative ARPU** – cumulative average revenue per active user over the first 90 days. The metric is calculated as total revenue over the first 90 days divided by the number of active users over the selected report period. **180-day Cumulative ARPU** – cumulative average revenue per active user over the first 180 days. The metric is calculated as total revenue over the first 180 days divided by the number of active users over the selected report period. **270-day Cumulative ARPU** – cumulative average revenue per active user over the first 270 days. The metric is calculated as total revenue over the first 270 days divided by the number of active users over the selected report period. **360-day Cumulative ARPU** – cumulative average revenue per active user over the first 360 days. The metric is calculated as total revenue over the first 360 days divided by the number of active users over the selected report period. ## **Users and sessions** **Active users** – number of unique users that have visited your app during the given period. DAU is calculated by days, MAU is calculated by months, and "Active users" is calculated by any selected period of time. **Average session length** – average time spent in the app per user. Defined as the sum of the length of all sessions divided by the number of sessions within a given period. **Lifetime** – the average number of days between the first and last time the app was launched. The launch is considered to be the last if there has been no activity within the app during the last 7 days. **DAU** (*Daily Active Users*) – the number of unique users that have opened the app during a given day. The DAU for several days is calculated as the mathematical mean of all DAUs within the given period. **WAU** *(Weekly Active Users)* – a number of unique users that have opened the app for the past 7 days. The WAU for several months is calculated as the mathematical mean of all WAUs within the given period. **MAU** (*Monthly Active Users*) – a number of unique users that have opened the app for the past 30 days. The MAU for several months is calculated as the mathematical mean of all MAUs within the given period. **Sticky Factor** (DAU/MAU) – shows the average regularity of users’ logs. The more regular users log into app, the higher is Sticky Factor. If every user logs every day, the Sticky Factor is equal to 100%. **Loyal user** – a user who has opened app at least once after 24h from the first launch. **LDAU** (*Loyal Daily Active Users*) – a number of unique loyal users visiting the app during a given day. The LDAU for several days is calculated as the mathematical mean of all LDAUs within the given period. **LWAU** (*Loyal Weekly Active Users*) – a number of unique loyal users visiting the app for the past 7 days. The LWAU for several weeks is calculated as the mathematical mean of all LWAUs within the given period. **LMAU** (*Loyal Monthly Active Users*) – a number of unique loyal users visiting the app for the past 30 days. The LMAU for several months is calculated as the mathematical mean of all LMAUs within the given period. **Users online** – the average number of unique users, from whose devices any event was received in the given timeframe. Calculation is performed with the use of averaged data for the 5 minutes period, days, weeks etc. depending on the period and aggregation taken. **Max users online** – the peak number of users active on a particular day. **New users** – a total number of registrations within a given period. **Sessions** – the total number of sessions (opening or unfolding the application) for the given time period. **Sessions by user** – the average number of sessions made by one user during the period. **Tutorial conversion** – the share of new users who have successfully completed the tutorial. ## Monetary metrics **Average check** – an average gross revenue per payment. Defined as the total gross revenue divided by the number of payments. **Gross** – the total gross revenue (Sales Revenue) within a given period. Defined as the sum of all payments within a given period. **Paying users** – the number of users who have paid at least once within a given period. **New paying users** – the number of users who have made their first payment in the application within a given period. **Paying conversion** – the percentage of users registered in the given period and having afterwards made at least one payment, percentage taken of all users registered in the given period. **Paying share** – the share of users who have paid at least once per given period. Defined as the number of paying users within a given period divided by the number of unique users within the same period (DAU, WAU, MAU). **Revenue** – a total net revenue within a given period. This metric is calculated as the product of **Gross** and **Revenue rate**. "Revenue rate" (developer interest) is equal to 0.7 by default, but it can be changed in [project settings](/reports-and-functionality/project-related-reports-and-fuctionality/settings.md#payments-settings). **Transactions** – total number of transactions made by users within a given period. **Transactions by user** – an average number of transactions per user. Defined as the number of transactions (purchases) within a given period divided by the number of paying users within the same period. ## Retention and timespent **Day 1 retention (by hours)** – the percentage of users who have launched an app for the first time during the chosen period and then opened it on day 1 after the first launch ("day" here means 24 hours interval from the first launch). **Day 7 retention (by hours)** – the percentage of users who have launched an app for the first time during the chosen period and then opened it on day 7 after the first launch ("day" here means 24 hours interval from the first launch). **Day 28 retention (by hours)** – the percentage of users who have launched an app for the first time during the chosen period and then opened it on day 28 after the first launch ("day" here means 24 hours interval from the first launch). **Day 1 retention (calendar)** – the percentage of users who have launched an app for the first time during the chosen period and then opened it the next day after the first launch ("day" here means the date in the calendar). **Day 7 retention (calendar)** – the percentage of users who have launched an app for the first time during the chosen period and then opened it on day 7 after the first launch ("day" here means the date in the calendar). **Day 28 retention (calendar)** – the percentage of users who have launched an app for the first time during the chosen period and then opened it on day 28 after the first launch ("day" here means the date in the calendar). **Day 0 timespent** – the average amount of time spent on installation day for users who have launched an app for the first time during the selected timeframe. **Day 1 timespent** – the average amount of time spent on the 1st day after the installation for users who have launched an app for the first time during the selected timeframe. **Day 7 timespent** – the average amount of time spent on the 7th day after the installation for users who have launched an app for the first time during the selected timeframe. **Day 28 timespent** – the average amount of time spent on the 28th day after the installation for users who have launched an app for the first time during the selected timeframe. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.devtodev.com/metrics-and-glossary/sdk-metrics.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.