Finances

Product

The product title in the app or on the website, to which report financial indices are assigned.

Verification

Status of transaction verification. By default, system will not run verification procedure on payment transactions events, i.e. system will not verify if sum of transaction is correct and this transaction was really done by user.

User could send a packet with transaction information to the metrics system servers emulating application, so unverified transactions metrics could include fraud transactions.

myTracker could run verification on each mobile transaction by sending request to App Store and Google Play servers, however myTacker must have a key for payment verification — credentials.

If the key was added, myTracker will verify each mobile transaction and both verified and unverified data will be available in metrics.

Currency

Title of the currency used to display financial data in the report.

Subscription type

Subscription type at the event time:

  • Free
  • Trial
  • Paid

Revenue type

The way of generation app revenue to which transaction refers:

  • In-app payment (sale of game currency, app level, etc.)
  • Subscription (monthly subscription to a magazine, season broadcast, etc.)
  • Ad monetization (ads placement)
  • Custom revenue (any type of revenue, including offline purchases, payments via WeChat Pay, etc.)

Learn more

Revenue (d)

The total amount of revenue during the report period: revenue from ad placement, in-app payments, subscriptions and custom revenue. Learn more

Metric shows revenue, not profit, it does not consider taxes or app stores fee

RevenueFlow metric
Revenue CACurrent Attribution metric
Revenue LTLife Time metric
Revenue ATAttribution Time metric

Revenue (u)

The total amount of revenue during the report period: revenue from ad placement, in-app payments, subscriptions and custom revenue. Learn more

Metric shows revenue, not profit, it does not consider taxes or app stores fee

RevenueFlow metric
Revenue LTLife Time metric

Engaged audience (d)

The number of devices on which a user saw the in-app advertisement at least once for the selected period

Click stats are not available for all partners. Learn more

Engaged audienceFlow metric
Engaged audience CACurrent Attribution metric
Engaged audience LTLife Time metric
Engaged audience ATAttribution Time metric

Engaged audience (u)

The number of users who saw the in-app advertisement at least once for the selected period

Click stats are not available for all partners. Learn more

Engaged audienceFlow metric
Engaged audience LTLife Time metric

Engagement Rate (d)

Percentage of active devices on which a user saw the in-app ad.
Engagement Rate = number of engaged devices / number of active devices * 100%

Click stats are not available for all partners. Learn more

Engagement RateFlow metric

Engagement Rate (u)

Percentage of active users who saw the in-app ad.
Engagement Rate = number of engaged users / number of active users * 100%

Click stats are not available for all partners. Learn more

Engagement RateFlow metric

In-app impressions (d)

The number of in-app impressions for the selected report period

In-app impressionsFlow metric
In-app impressions CACurrent Attribution metric
In-app impressions LTLife Time metric
In-app impressions ATAttribution Time metric

In-app impressions (u)

The number of in-app impressions for the selected report period

In-app impressionsFlow metric
In-app impressions LTLife Time metric

CPM (d)

CPM (Cost per mille) — the average cost per thousand in-app impressions.
CPM = sum of payments for ad placement / number of in-app impressions *1000

CPMFlow metric
CPM CACurrent Attribution metric
CPM LTLife Time metric
CPM ATAttribution Time metric

CPM (u)

CPM (Cost per mille) — the average cost per thousand in-app impressions.
CPM = sum of payments for ad placement / number of in-app impressions *1000

CPMFlow metric
CPM LTLife Time metric

Transactions (d)

The total number of payment transactions during the report period. It's in-app payments, subscription and renewal payments (excluding trial), and custom payments passed to myTracker via the S2S API

TransactionsFlow metric
Transactions CACurrent Attribution metric
Transactions LTLife Time metric
Transactions ATAttribution Time metric

Transactions (u)

The total number of payment transactions during the report period. It's in-app payments, subscription and renewal payments (excluding trial), and custom payments passed to myTracker via the S2S API

TransactionsFlow metric
Transactions LTLife Time metric

Test transactions (d)

The total number of test payment transactions during the report period.

Test transactionsFlow metric

Test transactions (u)

The total number of test payment transactions during the report period.

Test transactionsFlow metric

Trial Subscriptions (d)

The number of trial subscriptions opened in the selected report period.

Trial SubscriptionsFlow metric
Trial Subscriptions CACurrent Attribution metric
Trial Subscriptions LTLife Time metric
Trial Subscriptions ATAttribution Time metric

Trial Subscriptions (u)

The number of trial subscriptions opened in the selected report period.

Trial SubscriptionsFlow metric
Trial Subscriptions LTLife Time metric

First Subscriptions (d)

The number of subscriptions that were paid up for the first time (excluding Renewals and Trial subscription)

First SubscriptionsFlow metric
First Subscriptions CACurrent Attribution metric
First Subscriptions LTLife Time metric
First Subscriptions ATAttribution Time metric

First Subscriptions (u)

The number of subscriptions that were paid up for the first time (excluding Renewals and Trial subscription)

First SubscriptionsFlow metric
First Subscriptions LTLife Time metric

Subscription Renewals (d)

The number of subscriptions renewed during the selected report period.

Subscription RenewalsFlow metric
Subscription Renewals CACurrent Attribution metric
Subscription Renewals LTLife Time metric
Subscription Renewals ATAttribution Time metric

Subscription Renewals (u)

The number of subscriptions renewed during the selected report period.

Subscription RenewalsFlow metric
Subscription Renewals LTLife Time metric

TPC (d)

Trial to Paid Conversion. The number of trials for the selected report period that converted to paid subscriptions over time.

TPCFlow metric

TPC (u)

Trial to Paid Conversion. The number of trials for the selected report period that converted to paid subscriptions over time.

TPCFlow metric

TPC Rate (d)

Trial to Paid Conversion Rate. Percentage of trials for the selected report period that converted to paid subscriptions over time.
TPC Rate = TPC / number of trial subscriptions

TPC RateFlow metric

TPC Rate (u)

Trial to Paid Conversion Rate. Percentage of trials for the selected report period that converted to paid subscriptions over time.
TPC Rate = TPC / number of trial subscriptions

TPC RateFlow metric

First Time Payers (d)

The total number of devices that first made payment. This can be an in-app payment, subscription, or custom payment (for example, an offline payment passed to myTracker via the S2S API).

It shows how many devices have converted from being "non-paying" to "paying" during the chosen report period.

First time payersFlow metric
First time payers CACurrent Attribution metric
First time payers LTLife Time metric
First time payers ATAttribution Time metric

First Time Payers (u)

The number of users who made the first payment. This can be an in-app payment, subscription, or custom payment (for example, an offline payment passed to myTracker via the S2S API).

In the project, a user can make payments from different devices but only one of them will be the first.

First time payersFlow metric
First time payers LTLife Time metric

DPU (d)

DPU — the number of paying devices per day.

On a daily basis, system computes the number of paying devices. Average of this metric for report period would be DPU value.

DPUFlow metric
DPU CACurrent Attribution metric

DPU (u)

DPU — the number of paying users per day.

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

DPUFlow metric

WPU (d)

WPU — the average number of paying devices per the past 7 days.
On a daily basis, system computes the number of devices that have made at least one payment in the past 7 days. Average of the present measure for report period would be WPU.

In other words, WPU is computed using moving 7 days window. For example, if the report is aggregated by days, than WPU for 2021-05-14 would show the number of devices that have made a payment between 2021-05-08 and 2021-05-14 inclusive.

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

WPUFlow metric
WPU CACurrent Attribution metric

WPU per week (d)

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

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

Report period WPU per week/ WPU
Mon 01/09 -
Sun 07/09
WPU per week: devices that have made at least one payment from 01/09 to 07/09
WPU: average value of the paying devices calculated from 26/08 to 07/09
Mon 01/09 -
Thu 04/09
WPU per week: devices that have made at least one payment from 01/09 to 04/09
WPU: average value of the paying devices calculated from 26/08 to 04/09
Thu 04/09 -
Wed 10/09
WPU per week: average value of WPU Thu-Sun and WPU Mon-Wed
WPU: average value of the paying devices calculated from 29/08 to 10/09
Mon 01/09 -
Sun 14/09
WPU per week: average value of WPU 01/09-07/09 and WPU 08/09-14/09
WPU: average value of the paying devices calculated from 26/08 to 14/09

WPU per weekFlow metric
WPU per week CACurrent Attribution metric

WPU per 7 days (d)

WPU per 7 days is the number of paying devices in 7 days.

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

Report period WPU per 7 days/ WPU
Mon 01/09 -
Sun 07/09
WPU per 7 days: devices that have made at least one payment from 01/09 to 07/09
WPU: average value of the paying devices calculated from 26/08 to 07/09
Mon 01/09 -
Thu 04/09
WPU per 7 days: devices that have made at least one payment from 01/09 to 04/09
WPU: average value of the paying devices calculated from 26/08 to 04/09
Thu 04/09 -
Wed 10/09
WPU per 7 days: devices that have made at least one payment from 04/09 to 10/09
WPU: average value of the paying devices calculated from 29/08 to 10/09
Mon 01/09 -
Sun 14/09
WPU per 7 days: average value of WPU 01/09-07/09 and WPU 08/09-14/09
WPU: average value of the paying devices calculated from 26/08 to 14/09

WPU per 7 daysFlow metric
WPU per 7 days CACurrent Attribution metric

WPU (u)

WPU — the average number of paying users per the past 7 days.
On a daily basis, system computes the number of users who have made at least one payment in the past 7 days. Average of the present measure for report period would be WPU.

In other words, WPU is computed using moving 7 days window. For example, if the report is aggregated by days, than WPU for 2021-05-14 would show the number of project users that have made a payment between 2021-05-08 and 2021-05-14 inclusive.

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

WPUFlow metric

WPU per week (u)

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

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

Report period WPU per week/ WPU
Mon 01/09 -
Sun 07/09
WPU per week: users who have made at least one payment from 01/09 to 07/09
WPU: average value of the paying users calculated from 26/08 to 07/09
Mon 01/09 -
Thu 04/09
WPU per week: users who have made at least one payment from 01/09 to 04/09
WPU: average value of the paying users calculated from 26/08 to 04/09
Thu 04/09 -
Wed 10/09
WPU per week: average value of WPU Thu-Sun and WPU Mon-Wed
WPU: average value of the paying users calculated from 29/08 to 10/09
Mon 01/09 -
Sun 14/09
WPU per week: average value of WPU 01/09-07/09 and WPU 08/09-14/09
WPU: average value of the paying users calculated from 26/08 to 14/09

WPU per weekFlow metric

WPU per 7 days (u)

WPU per 7 days is the number of paying users in 7 days.

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

Report period WPU per 7 days/ WPU
Mon 01/09 -
Sun 07/09
WPU per 7 days: users who have made at least one payment from 01/09 to 07/09
WPU: average value of the paying users calculated from 26/08 to 07/09
Mon 01/09 -
Thu 04/09
WPU per 7 days: users who have made at least one payment from 01/09 to 04/09
WPU: average value of the paying users calculated from 26/08 to 04/09
Thu 04/09 -
Wed 10/09
WPU per 7 days: users who have made at least one payment from 04/09 to 10/09
WPU: average value of the paying users calculated from 29/08 to 10/09
Mon 01/09 -
Sun 14/09
WPU per 7 days: average value of WPU 01/09-07/09 and WPU 08/09-14/09
WPU: average value of the paying users calculated from 26/08 to 14/09

WPU per 7 daysFlow metric

MPU (d)

MPU — the average number of paying devices per the past 30 days.
On a daily basis, system computes the number of devices that have made at least one payment in the past 30 days. Average of the present measure for report period would be MPU.

In other words, MPU is computed using moving 30 days window. For example, if the report is aggregated by days, than MPU for 2021-05-14 would show the number of devices that have made a payment between 2021-04-15 and 2021-05-14.

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

MPUFlow metric
MPU CACurrent Attribution metric

MPU per month (d)

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

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

Report period MPU per month/ MPU
01/10 - 31/10 MPU per month: devices that have made at least one payment from 01/10 to 31/10
MPU: average value of the paying devices calculated from 02/09 to 31/10
01/10 - 14/10 MPU per month: devices that have made at least one payment from 01/10 to 14/10
MPU: average value of the paying devices calculated from 02/09 to 14/10
14/09 - 15/10 MPU per month: average value of MPU 14/09-31/09 and MPU 01/09-15/10
MPU: average value of the paying devices calculated from 17/08 to 15/10
01/09 - 31/10 MPU per month: average value of MPU 01/09-30/09 and MPU 01/10-31/10
MPU: average value of the paying devices calculated from 03/08 to 31/10

MPU per monthFlow metric
MPU per month CACurrent Attribution metric

MPU per 30 days (d)

MPU per 30 days is the number of paying devices in 30 days.

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

Report period MPU per 30 days/ MPU
01/09 - 30/09 MPU per 30 days: devices that have made at least one payment from 01/09 to 30/09
MPU: average value of the paying devices calculated from 03/08 to 30/09
01/10 - 31/10 MPU per 30 days: average value of MPU 01/10-30/10 and MPU 31/10
MPU: average value of the paying devices calculated from 02/09 to 31/10
01/10 - 14/10 MPU per 30 days: devices that have made at least one payment from 01/10 to 14/10
MPU: average value of the paying devices calculated from 02/09 to 14/10
14/09 - 15/10 MPU per 30 days: devices that have made at least one payment from 14/09 to 15/10
MPU: average value of the paying devices calculated from 16/08 to 15/10
01/09 - 31/10 MPU per 30 days: average value of MPU 01/09-30/09, MPU 01/10-30/10 and MPU 31/10
MPU: average value of the paying devices calculated from 03/08 to 31/10

MPU per 30 daysFlow metric
MPU per 30 days CACurrent Attribution metric

MPU (u)

MPU — the average number of paying users per the past 30 days.
On a daily basis, system computes the number of users that have made at least one payment in the past 30 days. Average of the present measure for report period would be MPU.

In other words, MPU is computed using moving 30 days window. For example, if the report is aggregated by days, than MPU for 2021-05-14 would show the number of project users that have made a payment between 2021-04-15 and 2021-05-14.

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

MPUFlow metric

MPU per month (u)

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

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

Report period MPU per month/ MPU
01/10 - 31/10 MPU per month: users who have made at least one payment from 01/10 to 31/10
MPU: average value of the paying users calculated from 02/09 to 31/10
01/10 - 14/10 MPU per month: users who have made at least one payment from 01/10 to 14/10
MPU: average value of the paying users calculated from 02/09 to 14/10
14/09 - 15/10 MPU per month: average value of MPU 14/09-31/09 and MPU 01/09-15/10
MPU: average value of the paying users calculated from 17/08 to 15/10
01/09 - 31/10 MPU per month: average value of MPU 01/09-30/09 and MPU 01/10-31/10
MPU: average value of the paying users calculated from 03/08 to 31/10

MPU per monthFlow metric

MPU per 30 days (u)

MPU per 30 days is the number of paying users in 30 days.

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

Report period MPU per 30 days/ MPU
01/09 - 30/09 MPU per 30 days: users who have made at least one payment from 01/09 to 30/09
MPU: average value of the paying users calculated from 03/08 to 30/09
01/10 - 31/10 MPU per 30 days: average value of MPU 01/10-30/10 and MPU 31/10
MPU: average value of the paying users calculated from 02/09 to 31/10
01/10 - 14/10 MPU per 30 days: users who have made at least one payment from 01/10 to 14/10
MPU: average value of the paying users calculated from 02/09 to 14/10
14/09 - 15/10 MPU per 30 days: users who have made at least one payment from 14/09 to 15/10
MPU: average value of the paying users calculated from 16/08 to 15/10
01/09 - 31/10 MPU per 30 days: average value of MPU 01/09-30/09, MPU 01/10-30/10 and MPU 31/10
MPU: average value of the paying users calculated from 03/08 to 31/10

MPU per 30 daysFlow metric

ARPU (d)

ARPU — the average revenue from a single active device (revenue from ad placement, in-app payments, subscriptions, and custom revenue).

It's determined as ratio of sum for report period Revenue to Active devices (for ARPU & ARPU CA) or New devices (for ARPU LT & ARPU AT)

ARPU shows revenue, not profit, it does not consider taxes or app stores fee

ARPUFlow metric
ARPU CACurrent Attribution metric
ARPU LTLife Time metric
ARPU ATAttribution Time metric

ARPU (u)

ARPU — the average revenue from a single active user (revenue from ad placement, in-app payments, subscriptions and custom revenue).

It's determined as the ratio of sum for report period Revenue to Active users (for ARPU) or New users (for ARPU LT).

ARPU shows revenue, not profit, it does not consider taxes or app stores fee

ARPUFlow metric
ARPU LTLife Time metric

ARPPU (d)

ARPPU — the average revenue received from a single paying device (revenue from ad placement, in-app payments, subscriptions and custom revenue).

It's calculated as a ratio of sum for report period Revenue to Paying audience (for ARPPU & ARPPU CA) or First time payers (for ARPPU LT & ARPPU AT).

The present index helps analyze the source of the traffic. The greater the ARPPU of a particular source, the more efficient it is.

ARPPU shows revenue, not profit, it does not consider taxes or app stores fee

ARPPUFlow metric
ARPPU CACurrent Attribution metric
ARPPU LTLife Time metric
ARPPU ATAttribution Time metric

ARPPU (u)

ARPPU — the average revenue received from a single paying users (revenue from ad placement, in-app payments, subscriptions and custom revenue).

It's calculated as a ratio of sum for report period Revenue to Paying audience (for ARPPU) or First time payers (for ARPPU LT).

The present index helps analyze the source of the traffic. The greater the ARPPU of a particular source, the more efficient it's.

ARPPU shows revenue, not profit, it does not consider taxes or app stores fee

ARPPUFlow metric
ARPPU LTLife Time metric

Paying audience (d)

The number of devices that made payment during the selected report period.

Payment can be an in-app payment, paid subscription, or any custom payment passed to myTracker via the S2S API

Paying audienceFlow metric
Paying audience CACurrent Attribution metric

Paying audience (u)

The number of users who made payment during the selected report period.

Payment can be an in-app payment, paid subscription, or any custom payment passed to myTracker via the S2S API

Paying audienceFlow metric

Campaign cost

Campaign cost in selected currency.
Campaign costs can be logged using API, through the tracking link params and calculated by entered tariffs.

Learn more

ROI (d)

ROI — ad campaigns profit. It's determined as ratio of sum for report period Revenue, LT to Campaigns cost.

ROIFlow metric
ROI CACurrent Attribution metric

ROI (u)

ROI — ad campaigns profit. It's determined as ratio of sum for report period Revenue, LT to Campaigns cost.

ROIFlow metric