Log in

Device / User activity

Launches (d)

The number of launches for the selected report period.

For mobile apps, a launch is considered a new one if the app has been inactive on a device for 30 seconds (by default). For example, it happens when the app is launched 30 seconds after the phone was locked or the app went into the background mode.

For websites, a new launch is a view when more than 30 minutes have passed since the last view.

LaunchesFlow metric
Launches CACurrent Attribution metric
Launches LTLifeTime metric
Launches ATAttribution Time metric

Launches (u)

The number of launches for the selected report period.

For mobile apps, a launch is considered a new one if the app has been inactive on a device for 30 seconds (by default). For example, it happens when the app is launched 30 seconds after the phone was locked or the app went into the background mode.

For websites, a new launch is a view when more than 30 minutes have passed since the last view.

LaunchesFlow metric
Launches CACurrent Attribution metric
Launches LTLifeTime metric
Launches ATAttribution Time metric

Launches (p)

The number of app launches made on a platform for the selected report period.

A launch is considered a new one if the app has been inactive on a device for 30 seconds (by default). For example, it happens when the app is launched 30 seconds after the app went into the background mode.

LaunchesFlow metric
Launches CACurrent Attribution metric
Launches LTLifeTime metric
Launches ATAttribution Time metric

Authorisations (d)

The total number of authorisations on a device during the selected report period. It's a sum of Login events, tracked by MyTracker with device ID.

To log the Authorisation events, you need to configure SDK for iOS, Android, Unity, Flutter, Web platforms, or send events via S2S API.

AuthorisationsFlow metric
Authorisations CACurrent Attribution metric
Authorisations LTLifeTime metric
Authorisations ATAttribution Time metric

Authorisations (u)

The total number of authorisations during the selected report period. It's a sum of Login events, tracked by MyTracker with user ID.

To log the Authorisation events, you need to configure SDK for iOS, Android, Unity, Web platforms, or send events via S2S API.

AuthorisationsFlow metric
Authorisations CACurrent Attribution metric
Authorisations LTLifeTime metric
Authorisations ATAttribution Time metric

Authorisations (p)

The number of platform users who are authorized in the application during the report period.

AuthorisationsFlow metric
Authorisations CACurrent Attribution metric
Authorisations LTLifeTime metric
Authorisations ATAttribution Time metric

First authorisations (u)

The number of project users who are authorized in the application for the first time during the report period. In the project, a user can authorize from different devices, but only one of these authorizations will be counted as the first one.

To log the Authorisation events, you need to configure SDK for iOS, Android, Unity, Flutter, Web platforms, or send events via S2S API

First authorisationsFlow metric
First authorisations CACurrent Attribution metric
First authorisations LTLifeTime metric
First authorisations ATAttribution Time metric

First authorisations (p)

The number of platform users who are authorized in the application for the first time during the report period.

In the project, a user can authorize from different devices, but only one of these authorizations will be counted as the first one.

First authorisationsFlow metric
First authorisations CACurrent Attribution metric
First authorisations LTLifeTime metric
First authorisations ATAttribution Time metric

Sessions (d)

The total number of sessions over the selected time period.

The session is a time interval, during which a user continues to interact with a website or mobile app. MyTracker logs the session after the user ends the session and starts a new one.

For mobile apps, the session starts with the launch and stops when the application goes to the background for more than 30 seconds. You can change this interval by configuring the LaunchTimeout parameter of MyTracker SDK.

For websites, the session starts with a site visit and stops when more than 30 minutes have passed since the last activity. You can change this interval through the session timeout setting.

SessionsFlow metric
Sessions CACurrent Attribution metric
Sessions LTLifeTime metric
Sessions ATAttribution Time metric

Sessions (u)

The total number of sessions over the selected time period.

The session is a time interval, during which a user continues to interact with a website or mobile app. MyTracker logs the session after the user ends the session and starts a new one.

For mobile apps, the session starts with the launch and stops when the application goes to the background for more than 30 seconds. You can change this interval by configuring the LaunchTimeout parameter of MyTracker SDK.

For websites, the session starts with a site visit and stops when more than 30 minutes have passed since the last activity. You can change this interval through the session timeout setting.

SessionsFlow metric
Sessions CACurrent Attribution metric
Sessions LTLifeTime metric
Sessions ATAttribution Time metric

Broken sessions (d)

The total number of broken sessions over the selected report period.

Session is considered to be broken if we do not know it's stop time. For example, when an app crashes or the OS forces an app to stop.

The session is a time interval, during which a user continues to interact with a website or mobile app. MyTracker logs the session after the user ends the session and starts a new one.

For mobile apps, the session starts with the launch and stops when the application goes to the background for more than 30 seconds. You can change this interval by configuring the LaunchTimeout parameter of MyTracker SDK.

For websites, the session starts with a site visit and stops when more than 30 minutes have passed since the last activity. You can change this interval through the session timeout setting.

Broken sessionsFlow metric
Broken sessions CACurrent Attribution metric
Broken sessions LTLifeTime metric
Broken sessions ATAttribution Time metric

Broken sessions (u)

The total number of broken sessions over the selected report period.

Session is considered to be broken if we do not know it's completion time. For example, when an app crashes or the OS forces an app to stop.

The session is a time interval, during which a user continues to interact with a website or mobile app. MyTracker logs the session after the user ends the session and starts a new one.

For mobile apps, the session starts with the launch and stops when the application goes to the background for more than 30 seconds. You can change this interval by configuring the LaunchTimeout parameter of MyTracker SDK.

For websites, the session starts with a site visit and stops when more than 30 minutes have passed since the last activity. You can change this interval through the session timeout setting.

Broken sessionsFlow metric
Broken sessions CACurrent Attribution metric
Broken sessions LTLifeTime metric
Broken sessions ATAttribution Time metric

Unique sessions (d)

The number of sessions from different devices.

The session is a time interval, during which a user continues to interact with a website or mobile app. MyTracker logs the session after the user ends the session and starts a new one.

For mobile apps, the session starts with the launch and stops when the application goes to the background for more than 30 seconds. You can change this interval by configuring the LaunchTimeout parameter of MyTracker SDK.

For websites, the session starts with a site visit and stops when more than 30 minutes have passed since the last activity. You can change this interval through the session timeout setting.

Unique sessionsFlow metric
Unique sessions CACurrent Attribution metric
Unique sessions LTLifeTime metric
Unique sessions ATAttribution Time metric

Unique sessions (u)

The number of sessions made by different users.

The session is a time interval, during which a user continues to interact with a website or mobile app. MyTracker logs the session after the user ends the session and starts a new one.

For mobile apps, the session starts with the launch and stops when the application goes to the background for more than 30 seconds. You can change this interval by configuring the LaunchTimeout parameter of MyTracker SDK.

For websites, the session starts with a site visit and stops when more than 30 minutes have passed since the last activity. You can change this interval through the session timeout setting.

Unique sessionsFlow metric
Unique sessions CACurrent Attribution metric
Unique sessions LTLifeTime metric
Unique sessions ATAttribution Time metric

Average session duration (d)

The average session duration in seconds during the specified period.

Avg. session dur. = total duration of all sessions /  number of sessions (rounded down).

The session is a time interval, during which a user continues to interact with a website or mobile app. MyTracker logs the session after the user ends the session and starts a new one.

For mobile apps, the session starts with the launch and stops when the application goes to the background for more than 30 seconds. You can change this interval by configuring the LaunchTimeout parameter of MyTracker SDK.

For websites, the session starts with a site visit and stops when more than 30 minutes have passed since the last activity. You can change this interval through the session timeout setting.

Avg. session dur., secFlow metric
Avg. session dur., sec CACurrent Attribution metric
Avg. session dur., sec LTLifeTime metric
Avg. session dur., sec ATAttribution Time metric

Average session duration (u)

The average session duration in seconds during the specified period.

Avg. session dur. = total duration of all sessions /  number of sessions (rounded down).

The session is a time interval, during which a user continues to interact with a website or mobile app. MyTracker logs the session after the user ends the session and starts a new one.

For mobile apps, the session starts with the launch and stops when the application goes to the background for more than 30 seconds. You can change this interval by configuring the LaunchTimeout parameter of MyTracker SDK.

For websites, the session starts with a site visit and stops when more than 30 minutes have passed since the last activity. You can change this interval through the session timeout setting.

Avg. session dur., secFlow metric
Avg. session dur., sec CACurrent Attribution metric
Avg. session dur., sec LTLifeTime metric
Avg. session dur., sec ATAttribution Time metric

Median session duration (d)

The median session duration in seconds during the specified period.

Median session duration is defined by the number that divides a sorted ascending list of durations of all sessions in half (excluding broken sessions). For example, if durations are -1 (broken), 1 sec, 5 sec, 6 sec, then the median session duration is 5 sec.

The session is a time interval, during which a user continues to interact with a website or mobile app. MyTracker logs the session after the user ends the session and starts a new one.

For mobile apps, the session starts with the launch and stops when the application goes to the background for more than 30 seconds. You can change this interval by configuring the LaunchTimeout parameter of MyTracker SDK.

For websites, the session starts with a site visit and stops when more than 30 minutes have passed since the last activity. You can change this interval through the session timeout setting.

Median session dur., sec.Flow metric
Median session dur., sec. CACurrent Attribution metric
Median session dur., sec. LTLifeTime metric
Median session dur., sec. ATAttribution Time metric

Median session duration (u)

The median session duration in seconds during the specified period.

Median session duration is defined by the number that divides a sorted ascending list of durations of all sessions in half (excluding broken sessions). For example, if durations are -1 (broken), 1 sec, 5 sec, 6 sec, then the median session duration is 5 sec.

The session is a time interval, during which a user continues to interact with a website or mobile app. MyTracker logs the session after the user ends the session and starts a new one.

For mobile apps, the session starts with the launch and stops when the application goes to the background for more than 30 seconds. You can change this interval by configuring the LaunchTimeout parameter of MyTracker SDK.

For websites, the session starts with a site visit and stops when more than 30 minutes have passed since the last activity. You can change this interval through the session timeout setting.

Median session dur., sec.Flow metric
Median session dur., sec. CACurrent Attribution metric
Median session dur., sec. LTLifeTime metric
Median session dur., sec. ATAttribution Time metric

Average unique session duration (d)

The average session duration in seconds per device during the specified period.

Avg. session dur. per device = sum of average sessions durations of each device /  number of devices.

The session is a time interval, during which a user continues to interact with a website or mobile app. MyTracker logs the session after the user ends the session and starts a new one.

For mobile apps, the session starts with the launch and stops when the application goes to the background for more than 30 seconds. You can change this interval by configuring the LaunchTimeout parameter of MyTracker SDK.

For websites, the session starts with a site visit and stops when more than 30 minutes have passed since the last activity. You can change this interval through the session timeout setting.

Avg. unique session dur., sec.Flow metric
Avg. unique session dur., sec. CACurrent Attribution metric
Avg. unique session dur., sec. LTLifeTime metric
Avg. unique session dur., sec. ATAttribution Time metric

Average unique session duration (u)

The average session duration in seconds per user during the specified period.

Avg. session dur. per user = sum of average sessions durations of each user /  number of users.

The session is a time interval, during which a user continues to interact with a website or mobile app. MyTracker logs the session after the user ends the session and starts a new one.

For mobile apps, the session starts with the launch and stops when the application goes to the background for more than 30 seconds. You can change this interval by configuring the LaunchTimeout parameter of MyTracker SDK.

For websites, the session starts with a site visit and stops when more than 30 minutes have passed since the last activity. You can change this interval through the session timeout setting.

Avg. unique session dur., sec.Flow metric
Avg. unique session dur., sec. CACurrent Attribution metric
Avg. unique session dur., sec. LTLifeTime metric
Avg. unique session dur., sec. ATAttribution Time metric

Median unique session duration (d)

The median session duration in seconds per device during the specified period.

Median session duration per device is defined by the number that divides a sorted ascending list of median sessions durations of each device in half (excluding broken sessions).

The session is a time interval, during which a user continues to interact with a website or mobile app. MyTracker logs the session after the user ends the session and starts a new one.

For mobile apps, the session starts with the launch and stops when the application goes to the background for more than 30 seconds. You can change this interval by configuring the LaunchTimeout parameter of MyTracker SDK.

For websites, the session starts with a site visit and stops when more than 30 minutes have passed since the last activity. You can change this interval through the session timeout setting.

Median unique session dur., sec.Flow metric
Median unique session dur., sec. CACurrent Attribution metric
Median unique session dur., sec. LTLifeTime metric
Median unique session dur., sec. ATAttribution Time metric

Median unique session duration (u)

The median session duration in seconds per user during the specified period.

Median session duration per user is defined by the number that divides a sorted ascending list of median sessions durations of each user in half (excluding broken sessions).

The session is a time interval, during which a user continues to interact with a website or mobile app. MyTracker logs the session after the user ends the session and starts a new one.

For mobile apps, the session starts with the launch and stops when the application goes to the background for more than 30 seconds. You can change this interval by configuring the LaunchTimeout parameter of MyTracker SDK.

For websites, the session starts with a site visit and stops when more than 30 minutes have passed since the last activity. You can change this interval through the session timeout setting.

Median unique session dur., sec.Flow metric
Median unique session dur., sec. CACurrent Attribution metric
Median unique session dur., sec. LTLifeTime metric
Median unique session dur., sec. ATAttribution Time metric

Bounces (d)

Percentage of single-page sessions out of the total number over the selected report period.

A single-page session is considered as a session, in which interaction with a web app on a device was cancelled from the first page.

Bounces (u)

Percentage of single-page sessions out of the total number over the selected report period.

A single-page session is considered as a session, in which a user left a web app from the first page.

Page depth (d)

The average number of pages visited on a device.

Page depth (u)

The average number of pages visited by a user.

Pageviews (d)

The total number of pageviews during the selected report period (for Web only)

PageviewsFlow metric
Pageviews LTLifeTime metric

Pageviews (u)

The total number of pageviews during the selected report period (for Web only)

PageviewsFlow metric
Pageviews CACurrent Attribution metric
Pageviews LTLifeTime metric
Pageviews ATAttribution Time metric

App updates

The total number of application version updates occurred during the selected report period.

App updatesFlow metric
App updates CACurrent Attribution metric
App updates LTLifeTime metric
App updates ATAttribution Time metric

Activity days (d)

The average number of active days per device for the selected report period. An active day is a day for which at least one event on the device was logged: a registration, authorization, launch, pageview, in-app impression, or payments.

Payment includes a purchase, subscription, subscription renewal or custom revenue

Activity days FlowFlow metric
Activity days CACurrent Attribution metric
Activity days LTLifeTime metric
Activity days ATAttribution Time metric

Activity days (u)

The average number of active days per user for the selected report period. An active day is a day for which at least one user action was logged: a registration, authorization, launch, pageview, in-app impression, or payment.

Payment includes a purchase, subscription, subscription renewal, or custom revenue

Activity days FlowFlow metric
Activity days CACurrent Attribution metric
Activity days LTLifeTime metric
Activity days ATAttribution Time metric

Activity days (p)

The average number of active days per platform user for the selected report period. An active day is a day for which at least one user action was logged: a registration, launch, or payment.

Activity days FlowFlow metric
Activity days LTLifeTime metric

Active devices

The number of devices for which at least one event was logged during the selected period: a registration, authorization, launch, pageview, in-app impression, or payment.

Payment includes a purchase, subscription, subscription renewal, or custom revenue

Active devicesFlow metric
Active devices CACurrent Attribution metric
Active devices LTLifeTime metric
Active devices ATAttribution Time metric

Active users (u)

The number of users for whom at least one event was logged during the selected period: a registration, authorization, launch, pageview, in-app impression, or payment.

Payment includes a purchase, subscription, subscription renewal, or custom revenue

Active usersFlow metric
Active users CACurrent Attribution metric
Active users LTLifeTime metric
Active users ATAttribution Time metric

Active users (p)

The number of platform users for whom at least one event was logged during the selected period: a registration, app launch, or payment.

Active usersFlow metric
Active users LTLifeTime metric

DAU (d)

DAU — the number of active devices per day.

On a daily basis, system computes the number of active devices. Average value of this metric for aggregation period would be the DAU value.

DAUFlow metric
DAU CACurrent Attribution metric

DAU (u)

DAU — the number of active users per day.

On a daily basis, system computes the number active users. Average value of this metric for report period would be the DAU value.

DAUFlow metric
DAU CACurrent Attribution metric

DAU (p)

DAU — the number of active platform users per day.

On a daily basis, system computes the number active users. Average value of this metric for report period would be the DAU value.

DAUFlow metric

WAU (d)

WAU — the average number of active devices per the last 7 days.
On a daily basis, system computes the number of devices tah has been active for the last 7 days. Average of the present measure for report period would be WAU.

In other words, WAU is computed using moving 7 days window. For example, if the report is aggregated by days, than WAU for 2024-03-18 would show the number of devices has been active between 2024-03-12 and 2024-03-18 inclusive.

This metric is more complicated than WAU in the classic sense.
Note new metrics WAU per week and WAU per 7 days

WAUFlow metric
WAU CACurrent Attribution metric

WAU per week (d)

WAU per week is the number of active devices in one calendar week (Mon, Tue, etc.).

In contrast to the WAU metric, WAU per week shows the actual number of devices and processes data for the selected report period:

Report period WAU per week/ WAU
Mon 09/01 -
Sun 09/07
WAU per week: devices that were active from 09/01 to 09/07
WAU: average value of the active devices calculated from 08/26 to 09/07
Mon 09/01 -
Thu 09/04
WAU per week: devices that were active from 09/01 to 09/04
WAU: average value of the active devices calculated from 08/26 to 09/04
Thu 09/04 -
Wed 09/10
WAU per week: average value of WAU Thu-Sun and WAU Mon-Wed
WAU: average value of the active devices calculated from 08/29 to 09/10
Mon 09/01 -
Sun 09/14
WAU per week: average value of WAU 09/01-09/07 and WAU 09/08-09/14
WAU: average value of the active devices calculated from 08/26 to 09/14

WAU per weekFlow metric
WAU per week CACurrent Attribution metric

WAU per 7 days (d)

WAU per 7 days is the number of active devices in 7 days.

In contrast to the WAU metric, WAU per 7 days shows the actual number of devices and processes data for the selected report period:

Report period WAU per 7 days/ WAU
Mon 09/01 -
Sun 09/07
WAU per 7 days: devices that were active from 09/01 to 09/07
WAU: average value of the active devices calculated from 08/26 to 09/07
Mon 09/01 -
Thu 09/04
WAU per 7 days: devices that were active from 09/01 to 09/04
WAU: average value of the active devices calculated from 08/26 to 09/04
Thu 09/04 -
Wed 09/10
WAU per 7 days: devices that were active from 09/04 to 09/10
WAU: average value of the active devices calculated from 08/29 to 09/10
Mon 09/01 -
Sun 09/14
WAU per 7 days: average value of WAU 09/01-09/07 and WAU 09/08-09/14
WAU: average value of the active devices calculated from 08/26 to 09/14

WAU per 7 daysFlow metric
WAU per 7 days CACurrent Attribution metric

WAU (u)

WAU — the average number of active users per the last 7 days.
On a daily basis, system computes the number of users been active for the last 7 days. Average of the present measure for report period would be WAU.

In other words, WAU is computed using moving 7 days window. For example, if the report is aggregated by days, than WAU for 2024-03-18 would show the number of users has been active between 2024-03-12 and 2024-03-18 inclusive.

This metric is more complicated than WAU in the classic sense.
Note new metrics WAU per week and WAU per 7 days

WAUFlow metric
WAU CACurrent Attribution metric

WAU per week (u)

WAU per week is the number of active users in one calendar week (Mon, Tue, etc.).

In contrast to the WAU metric, WAU per week shows the actual number of users and processes data for the selected report period:

Report period WAU per week/ WAU
Mon 09/01 -
Sun 09/07
WAU per week: users who were active from 09/01 to 09/07
WAU: average value of the active users calculated from 08/26 to 09/07
Mon 09/01 -
Thu 09/04
WAU per week: users who were active from 09/01 to 09/04
WAU: average value of the active users calculated from 08/26 to 09/04
Thu 09/04 -
Wed 09/10
WAU per week: average value of WAU Thu-Sun and WAU Mon-Wed
WAU: average value of the active users calculated from 08/29 to 09/10
Mon 09/01 -
Sun 09/14
WAU per week: average value of WAU 09/01-09/07 and WAU 09/08-09/14
WAU: average value of the active users calculated from 08/26 to 09/14

WAU per weekFlow metric
WAU per week CACurrent Attribution metric

WAU per 7 days (u)

WAU per 7 days is the number of active users in 7 days.

In contrast to the WAU metric, WAU per 7 days shows the actual number of users and processes data for the selected report period:

Report period WAU per 7 days/ WAU
Mon 09/01 -
Sun 09/07
WAU per 7 days: users who were active from 09/01 to 09/07
WAU: average value of the active users calculated from 08/26 to 09/07
Mon 09/01 -
Thu 09/04
WAU per 7 days: users who were active from 09/01 to 09/04
WAU: average value of the active users calculated from 08/26 to 09/04
Thu 09/04 -
Wed 09/10
WAU per 7 days: users who were active from 09/04 to 09/10
WAU: average value of the active users calculated from 08/29 to 09/10
Mon 09/01 -
Sun 09/14
WAU per 7 days: average value of WAU 09/01-09/07 and WAU 09/08-09/14
WAU: average value of the active users calculated from 08/26 to 09/14

WAU per 7 daysFlow metric
WAU per 7 days CACurrent Attribution metric

WAU (p)

WAU — the average number of active platform users per the last 7 days.
On a daily basis, system computes the number of users been active for the last 7 days. Average of the present measure for report period would be WAU.

In other words, WAU is computed using moving 7 days window. For example, if the report is aggregated by days, than WAU for 2024-03-18 would show the number of users has been active between 2024-03-12 and 2024-03-18 inclusive.

This metric is more complicated than WAU in the classic sense.
Note new metrics WAU per week and WAU per 7 days

WAUFlow metric

WAU per week (p)

WAU per week is the number of active platform users in one calendar week (Mon, Tue, etc.).

In contrast to the WAU metric, WAU per week shows the actual number of users and processes data for the selected report period:

Report period WAU per week/ WAU
Mon 09/01 -
Sun 09/07
WAU per week: users who were active from 09/01 to 09/07
WAU: average value of the active users calculated from 08/26 to 09/07
Mon 09/01 -
Thu 09/04
WAU per week: users who were active from 09/01 to 09/04
WAU: average value of the active users calculated from 08/26 to 09/04
Thu 09/04 -
Wed 09/10
WAU per week: average value of WAU Thu-Sun and WAU Mon-Wed
WAU: average value of the active users calculated from 08/29 to 09/10
Mon 09/01 -
Sun 09/14
WAU per week: average value of WAU 09/01-09/07 and WAU 09/08-09/14
WAU: average value of the active users calculated from 08/26 to 09/14

WAU per weekFlow metric

WAU per 7 days (p)

WAU per 7 days is the number of active platform users in 7 days.

In contrast to the WAU metric, WAU per 7 days shows the actual number of users and processes data for the selected report period:

Report period WAU per 7 days/ WAU
Mon 09/01 -
Sun 09/07
WAU per 7 days: users who were active from 09/01 to 09/07
WAU: average value of the active users calculated from08/26 to 09/07
Mon 09/01 -
Thu 09/04
WAU per 7 days: users who were active from 09/01 to 09/04
WAU: average value of the active users calculated from 08/26 to 09/04
Thu 09/04 -
Wed 09/10
WAU per 7 days: users who were active from 09/04 to 09/10
WAU: average value of the active users calculated from 08/29 to 09/10
Mon 09/01 -
Sun 09/14
WAU per 7 days: average value of WAU 09/01-09/07 and WAU 09/08-09/14
WAU: average value of the active users calculated from 08/26 to 09/14

WAU per 7 daysFlow metric

MAU (d)

MAU — the average number of active devices per the last 30 days.
On a daily basis, system computes the number devices that has been active for the last 30 days. Average of the present measure for report period would be MAU.

In other words, MAU is computed using moving 30 days window. For example, if the report is aggregated by days, than MAU for 2024-03-18 would show the number of devices been active between 2024-02-18 and 2024-03-18.

This metric is more complicated than MAU in the classic sense.
Note new metrics MAU per month and MAU per 30 days

MAUFlow metric
MAU CACurrent Attribution metric

MAU per month (d)

MAU per month is the number of active devices in one calendar month (Jan, Feb, etc.).

In contrast to the MAU metric, MAU per month shows the actual number of devices and processes data for the selected report period:

Report period MAU per month/ MAU
10/01 - 10/31 MAU per month: devices that were active from 10/01 to 10/31
MAU: average value of the active devices calculated from 09/02 to 10/31
10/01 - 10/14 MAU per month: devices that were active from 10/01 to 10/14
MAU: average value of the active devices calculated from 09/02 to 10/14
09/14 - 10/15 MAU per month: average value of MAU 09/14-09/30 and MAU 10/01-10/15
MAU: average value of the active devices calculated from 08/16 to 10/15
09/01 - 10/31 MAU per month: average value of MAU 09/01-09/30 and MAU 10/01-10/31
MAU: average value of the active devices calculated from 08/03 to 10/31

MAU per monthFlow metric
MAU per month CACurrent Attribution metric

MAU per 30 days (d)

MAU per 30 days is the number of active devices in 30 days.

In contrast to the MAU metric, MAU per 30 days shows the actual number of devices and processes data for the selected report period:

Report period MAU per 30 days/ MAU
09/01 - 09/30 MAU per 30 days: devices that were active from 09/01 to 09/30
MAU: average value of the active devices calculated from 08/03 to 09/30
10/01 - 10/31 MAU per 30 days: average value of MAU 10/01-10/30 and MAU 10/31
MAU: average value of the active devices calculated from 09/02 to 10/31
10/01 - 10/14 MAU per 30 days: devices that were active from 10/01 to 10/14
MAU: average value of the active devices calculated from 09/02 to 10/14
09/14 - 10/15 MAU per 30 days: devices that were active from 09/14 to 10/15
MAU: average value of the active devices calculated from 08/16 to 10/15
09/01 - 10/31 MAU per 30 days: average value of MAU 09/01-09/30, MAU 10/01-10/30 and MAU 10/31
MAU: average value of the active devices calculated from 08/03 to 10/31

MAU per 30 daysFlow metric
MAU per 30 days CACurrent Attribution metric

MAU (u)

MAU — the average number of active users per the last 30 days.
On a daily basis, system computes the number of users been active for the last 30 days. Average of the present measure for report period would be MAU.

In other words, MAU is computed using moving 30 days window. For example, if the report is aggregated by days, than MAU for 2024-03-18 would show the number of users been active between 2024-02-18 and 2024-03-18.

This metric is more complicated than MAU in the classic sense.
Note new metrics MAU per month and MAU per 30 days

MAUFlow metric
MAU CACurrent Attribution metric

MAU per month (u)

MAU per month is the number of active users in one calendar month (Jan, Feb, etc.).

In contrast to the MAU metric, MAU per month shows the actual number of users and processes data for the selected report period:

Report period MAU per month/ MAU
10/01 - 10/31 MAU per month: users who were active from 10/01 to 10/31
MAU: average value of the active users calculated from 09/02 to 10/31
10/01 - 10/14 MAU per month: users who were active from 10/01 to 10/14
MAU: average value of the active users calculated from 09/02 to 10/14
09/14 - 10/15 MAU per month: average value of MAU 09/14-09/30 and MAU 10/01-10/15
MAU: average value of the active users calculated from 08/16 to 10/15
09/01 - 10/31 MAU per month: average value of MAU 09/01-09/30 and MAU 10/01-10/31
MAU: average value of the active users calculated from 08/03 to 31/10

MAU per monthFlow metric
MAU per month CACurrent Attribution metric

MAU per 30 days (u)

MAU per 30 days is the number of active users in 30 days.

In contrast to the MAU metric, MAU per 30 days shows the actual number of users and processes data for the selected report period:

Report period MAU per 30 days/ MAU
09/01 - 09/30 MAU per 30 days: users who were active from 09/01 to 09/30
MAU: average value of the active users calculated from 08/03 to 09/30
10/01 - 10/31 MAU per 30 days: average value of MAU 10/01-10/30 and MAU 10/31
MAU: average value of the active users calculated from 09/02 to 10/31
10/01 - 10/14 MAU per 30 days: users who were active from 10/01 to 10/14
MAU: average value of the active users calculated from 09/02 to 10/14
09/14 - 10/15 MAU per 30 days: users who were active from 09/14 to 10/15
MAU: average value of the active users calculated from 08/16 to 10/15
09/01 - 10/31 MAU per 30 days: average value of MAU 09/01-09/30, MAU 10/01-10/30 and MAU 10/31
MAU: average value of the active users calculated from 08/03 to 10/31

MAU per 30 daysFlow metric
MAU per 30 days CACurrent Attribution metric

MAU (p)

MAU — the average number of active platform users per the last 30 days.
On a daily basis, system computes the number of users been active for the last 30 days. Average of the present measure for report period would be MAU.

In other words, MAU is computed using moving 30 days window. For example, if the report is aggregated by days, than MAU for 2024-03-18 would show the number of users been active between 2024-02-18 and 2024-03-18.

This metric is more complicated than MAU in the classic sense.
Note new metrics MAU per month and MAU per 30 days

MAUFlow metric

MAU per month (p)

MAU per month is the number of active platform users in one calendar month (Jan, Feb, etc.).

In contrast to the MAU metric, MAU per month shows the actual number of users and processes data for the selected report period:

Report period MAU per month/ MAU
10/01 - 10/31 MAU per month: users who were active from 10/01 to 10/31
MAU: average value of the active users calculated from 09/02 to 10/31
10/01 - 10/14 MAU per month: users who were active from 10/01 to 10/14
MAU: average value of the active users calculated from 09/02 to 10/14
09/14 - 10/15 MAU per month: average value of MAU 09/14-09/30 and MAU 10/01-10/15
MAU: average value of the active users calculated from 08/16 to 10/15
09/01 - 10/31 MAU per month: average value of MAU 09/01-09/30 and MAU 10/01-10/31
MAU: average value of the active users calculated from 08/03 to 10/31

MAU per monthFlow metric

MAU per 30 days (p)

MAU per 30 days is the number of active platform users in 30 days.

In contrast to the MAU metric, MAU per 30 days shows the actual number of users and processes data for the selected report period:

Report period MAU per 30 days/ MAU
09/01 - 09/30 MAU per 30 days: users who were active from 09/01 to 09/30
MAU: average value of the active users calculated from 08/03 to 09/30
10/01 - 10/31 MAU per 30 days: average value of MAU 10/01-10/30 and MAU 10/31
MAU: average value of the active users calculated from 09/02 to 10/31
10/01 - 10/14 MAU per 30 days: users who were active from 10/01 to 10/14
MAU: average value of the active users calculated from 09/02 to 10/14
09/14 - 10/15 MAU per 30 days: users who were active from 09/14 to 10/15
MAU: average value of the active users calculated from 08/16 to 10/15
09/01 - 10/31 MAU per 30 days: average value of MAU 09/01-09/30, MAU 10/01-10/30 and MAU 10/31
MAU: average value of the active users calculated from 08/03 to 10/31

MAU per 30 daysFlow metric

Was this article helpful?