The product title in the app or on the website, to which report financial indices are assigned. For example, bonus name in a game or subscription title
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 servers, however MyTracker 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.
Title of the currency used to display financial data in the report.
Subscription type at the event time:
The way of generation app revenue to which transaction refers:
Type of purchase to which transaction refers:
The total amount of revenue during the report period: revenue from ad placement, purchase, subscriptions, and custom revenue. Learn more
Metric shows revenue, not profit, it does not consider taxes or app stores fee
Revenue – Flow metric
Revenue CA – Current Attribution metric
Revenue LT – LifeTime metric
Revenue AT – Attribution Time metric
The total amount of revenue during the report period: revenue from ad placement, purchases, subscriptions, and custom revenue. Learn more
Metric shows revenue, not profit, it does not consider taxes or app stores fee
Revenue – Flow metric
Revenue CA – Current Attribution metric
Revenue LT – LifeTime metric
Revenue AT – Attribution Time metric
The amount of payments made by VK Play platform users during the report period.
Metric shows revenue, not profit, it does not consider taxes
Revenue – Flow metric
Revenue CA – Current Attribution metric
Revenue LT – LifeTime metric
Revenue AT – Attribution Time metric
The number of devices on which a user clicked or saw the in-app advertisement at least once for the selected period
Click stats are not available for all partners. Learn more
Engaged audience – Flow metric
Engaged audience CA – Current Attribution metric
Engaged audience LT – LifeTime metric
Engaged audience AT – Attribution Time metric
The number of users who clicked or saw the in-app advertisement at least once for the selected period
Click stats are not available for all partners. Learn more
Engaged audience – Flow metric
Engaged audience CA – Current Attribution metric
Engaged audience LT – LifeTime metric
Engaged audience AT – Attribution Time metric
Percentage of active devices on which a user clicked or 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 Rate – Flow metric
Percentage of active users who clicked or 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 Rate – Flow metric
The number of in-app impressions for the selected report period
In-app impressions – Flow metric
In-app impressions CA – Current Attribution metric
In-app impressions LT – LifeTime metric
In-app impressions AT – Attribution Time metric
The number of in-app impressions for the selected report period
In-app impressions – Flow metric
In-app impressions CA – Current Attribution metric
In-app impressions LT – LifeTime metric
In-app impressions AT – Attribution Time metric
The number of in-app clicks for the selected report period
Click stats are not available for all partners. Learn more
In-app clicks – Flow metric
In-app clicks CA – Current Attribution metric
In-app clicks LT – LifeTime metric
In-app clicks AT – Attribution Time metric
The number of in-app clicks for the selected report period
Click stats are not available for all partners. Learn more
In-app clicks – Flow metric
In-app clicks CA – Current Attribution metric
In-app clicks LT – LifeTime metric
In-app clicks AT – Attribution Time metric
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
CPM – Flow metric
CPM CA – Current Attribution metric
CPM LT – LifeTime metric
CPM AT – Attribution Time metric
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
CPM – Flow metric
CPM LT – LifeTime metric
The total number of payment transactions during the report period. It's purchases, subscription and renewal payments (excluding trial), and custom payments passed to MyTracker via the S2S API
Transactions – Flow metric
Transactions CA – Current Attribution metric
Transactions LT – LifeTime metric
Transactions AT – Attribution Time metric
The total number of payment transactions during the report period. It's purchases, subscription and renewal payments (excluding trial), and custom payments passed to MyTracker via the S2S API
Transactions – Flow metric
Transactions CA – Current Attribution metric
Transactions LT – LifeTime metric
Transactions AT – Attribution Time metric
The total number of payment transactions during the report period. It's the user payments made in the VK Play platform app.
Transactions – Flow metric
Transactions CA – Current Attribution metric
Transactions LT – LifeTime metric
Transactions AT – Attribution Time metric
The total number of test payment transactions during the report period.
Test transactions – Flow metric
The number of trial subscriptions opened in the selected report period.
Trial Subscriptions – Flow metric
Trial Subscriptions CA – Current Attribution metric
Trial Subscriptions LT – LifeTime metric
Trial Subscriptions AT – Attribution Time metric
The number of trial subscriptions opened in the selected report period.
Trial Subscriptions – Flow metric
Trial Subscriptions CA – Current Attribution metric
Trial Subscriptions LT – LifeTime metric
Trial Subscriptions AT – Attribution Time metric
The number of subscriptions that were paid up for the first time (excluding Renewals and Trial subscription)
First Subscriptions – Flow metric
First Subscriptions CA – Current Attribution metric
First Subscriptions LT – LifeTime metric
First Subscriptions AT – Attribution Time metric
The number of subscriptions that were paid up for the first time (excluding Renewals and Trial subscription)
First Subscriptions – Flow metric
First Subscriptions CA – Current Attribution metric
First Subscriptions LT – LifeTime metric
First Subscriptions AT – Attribution Time metric
The number of subscriptions renewed during the selected report period.
Subscription Renewals – Flow metric
Subscription Renewals CA – Current Attribution metric
Subscription Renewals LT – LifeTime metric
Subscription Renewals AT – Attribution Time metric
The number of subscriptions renewed during the selected report period.
Subscription Renewals – Flow metric
Subscription Renewals CA – Current Attribution metric
Subscription Renewals LT – LifeTime metric
Subscription Renewals AT – Attribution Time metric
Trial to Paid Conversion. The number of trials for the selected report period that converted to paid subscriptions over time.
TPC – Flow metric
Trial to Paid Conversion. The number of trials for the selected report period that converted to paid subscriptions over time.
TPC – Flow metric
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 Rate – Flow metric
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 Rate – Flow metric
The total number of devices that first made payment. This can be a purchase, 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 payers – Flow metric
First time payers CA – Current Attribution metric
First time payers LT – LifeTime metric
First time payers AT – Attribution Time metric
The number of users who made the first payment. This can be a purchase, 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 payers – Flow metric
First time payers CA – Current Attribution metric
First time payers LT – LifeTime metric
First time payers AT – Attribution Time metric
The number of VK Play platform users who made the first payment. A user can make payments from different devices but only one of them will be the first.
First time payers – Flow metric
First time payers CA – Current Attribution metric
First time payers LT – LifeTime metric
First time payers AT – Attribution Time metric
DPU — the number of paying devices per day.
On a daily basis, system computes the number of paying devices. Average value of this metric for report period would be the DPU value.
Payment includes a purchase, subscription, subscription renewal, or custom revenue
DPU – Flow metric
DPU CA – Current Attribution metric
DPU — the number of paying users per day.
On a daily basis, system computes the number of paying users. Average value of this metric for report period would be the DPU value.
Payment includes a purchase, subscription, subscription renewal, or custom revenue
DPU – Flow metric
DPU CA – Current Attribution metric
DPU — the number of paying users per day.
On a daily basis, system computes the number of paying users. Average value of this metric for report period would be the DPU value.
DPU – Flow metric
WPU —
the average number of paying devices per the last 7 days.
On a daily basis, system computes the number of devices that
have made at least one payment for the last 7 days. Average of the present measure for report period would be WPU.
Payment includes a purchase, subscription, subscription renewal, or custom revenue
In other words, WPU is computed using moving 7 days window. For example, if the report is aggregated by
days, than WPU for
This metric is more complicated than WPU in the classic sense.
Note new metrics
WPU per week and WPU per 7 days
WPU – Flow metric
WPU CA – Current Attribution metric
WPU per week is the number of paying devices in one calendar week (Mon, Tue, etc.).
Payment includes a purchase, subscription, subscription renewal, or custom revenue
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 week – Flow metric
WPU per week CA – Current Attribution metric
WPU per 7 days is the number of paying devices in 7 days.
Payment includes a purchase, subscription, subscription renewal, or custom revenue
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 days – Flow metric
WPU per 7 days CA – Current Attribution metric
WPU —
the average number of paying users per the last 7 days.
On a daily basis, system computes the number of users who
have made at least one payment for the last 7 days. Average of the present measure for report period would be WPU.
Payment includes a purchase, subscription, subscription renewal, or custom revenue
In other words, WPU is computed using moving 7 days window. For example, if the report is aggregated by
days, than WPU for
This metric is more complicated than WPU in the classic sense.
Note new metrics
WPU per week and WPU per 7 days
WPU – Flow metric
WPU CA – Current Attribution metric
WPU per week is the number of paying users in one calendar week (Mon, Tue, etc.).
Payment includes a purchase, subscription, subscription renewal, or custom revenue
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 week – Flow metric
WPU per week CA – Current Attribution metric
WPU per 7 days is the number of paying users in 7 days.
Payment includes a purchase, subscription, subscription renewal, or custom revenue
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 days – Flow metric
WPU per 7 days CA – Current Attribution metric
WPU —
the average number of paying users per the last 7 days.
On a daily basis, system computes the number of users who
have made at least one payment for the last 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
This metric is more complicated than WPU in the classic sense.
Note new metrics
WPU per week and WPU per 7 days
WPU – Flow metric
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 week – Flow metric
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 days – Flow metric
MPU —
the average number of paying devices per the last 30 days.
On a daily basis, system computes the number of devices
that have made at least one payment for the last 30 days.
Average of the present measure
for report period would be MPU.
Payment includes a purchase, subscription, subscription renewal, or custom revenue
In other words, MPU is computed using moving 30 days window.
For example, if the report is aggregated by days, than MPU for
This metric is more complicated than MPU in the classic sense.
Note new metrics
MPU per month and MPU per 30 days
MPU – Flow metric
MPU CA – Current Attribution metric
MPU per month is the number of paying devices in one calendar month (Jan, Feb, etc.).
Payment includes a purchase, subscription, subscription renewal, or custom revenue
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 month – Flow metric
MPU per month CA – Current Attribution metric
MPU per 30 days is the number of paying devices in 30 days.
Payment includes a purchase, subscription, subscription renewal, or custom revenue
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 days – Flow metric
MPU per 30 days CA – Current Attribution metric
MPU —
the average number of paying users per the last 30 days.
On a daily basis, system computes the number of users
that have made at least one payment for the last 30 days.
Average of the present measure
for report period would be MPU.
Payment includes a purchase, subscription, subscription renewal, or custom revenue
In other words, MPU is computed using moving 30 days window.
For example, if the report is aggregated by days, than MPU for
This metric is more complicated than MPU in the classic sense.
Note new metrics
MPU per month and MPU per 30 days
MPU – Flow metric
MPU CA – Current Attribution metric
MPU per month is the number of paying users in one calendar month (Jan, Feb, etc.).
Payment includes a purchase, subscription, subscription renewal, or custom revenue
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 month – Flow metric
MPU per month CA – Current Attribution metric
MPU per 30 days is the number of paying users in 30 days.
Payment includes a purchase, subscription, subscription renewal, or custom revenue
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 days – Flow metric
MPU per 30 days CA – Current Attribution metric
MPU —
the average number of paying users per the last 30 days.
On a daily basis, system computes the number of users
that have made at least one payment for the last 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
This metric is more complicated than MPU in the classic sense.
Note new metrics
MPU per month and MPU per 30 days
MPU – Flow metric
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 month – Flow metric
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 days – Flow metric
ARPU — the average revenue from a single active device (revenue from ad placement, purchases, 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
ARPU – Flow metric
ARPU CA – Current Attribution metric
ARPU LT – LifeTime metric
ARPU AT – Attribution Time metric
ARPU — the average revenue from a single active user (revenue from ad placement, purchases, 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
ARPU – Flow metric
ARPU CA – Current Attribution metric
ARPU LT – LifeTime metric
ARPU AT – Attribution Time metric
ARPU — the average revenue from a single active VK Play platform user. 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
ARPU – Flow metric
ARPU CA – Current Attribution metric
ARPU LT – LifeTime metric
ARPU AT – Attribution Time metric
ARPPU — the average revenue received from a single paying device (revenue from ad placement, purchases, 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
ARPPU – Flow metric
ARPPU CA – Current Attribution metric
ARPPU LT – LifeTime metric
ARPPU AT – Attribution Time metric
ARPPU — the average revenue received from a single paying users (revenue from ad placement, purchases, 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
ARPPU – Flow metric
ARPPU CA – Current Attribution metric
ARPPU LT – LifeTime metric
ARPPU AT – Attribution Time metric
ARPPU — the average revenue received from a single paying VK Play platform users. 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
ARPPU – Flow metric
ARPPU CA – Current Attribution metric
ARPPU LT – LifeTime metric
ARPPU AT – Attribution Time metric
The number of devices that made payment during the selected report period.
Payment can be a purchase, paid subscription, or any custom payment passed to MyTracker via the S2S API
Paying audience – Flow metric
Paying audience CA – Current Attribution metric
Paying audience LT – LifeTime metric
Paying audience AT – Attribution Time metric
The number of users who made payment during the selected report period.
Payment can be a purchase, paid subscription, or any custom payment passed to MyTracker via the S2S API
Paying audience – Flow metric
Paying audience CA – Current Attribution metric
Paying audience LT – LifeTime metric
Paying audience AT – Attribution Time metric
The number of VK Play platform users who made payment during the selected report period.
Paying audience – Flow metric
Paying audience CA – Current Attribution metric
Paying audience LT – LifeTime metric
Paying audience AT – Attribution Time metric
ROI (Return Of Investments) — ad campaigns profit.
ROI = (Revenue LT - Campaigns cost) / Campaigns cost * 100%,
ROI CA = (Revenue CA - Campaigns cost) / Campaigns cost * 100%,
where Revenue LT is total revenue for all time, Revenue CA is the revenue received from the ad campaign for the selected report period.
ROI – Flow metric
ROI CA – Current Attribution metric
ROI (Return Of Investments) — ad campaigns profit.
ROI = (Revenue LT - Campaigns cost) / Campaigns cost * 100%,
ROI AT = (Revenue AT - Campaigns cost) / Campaigns cost * 100%,
where Revenue LT is total revenue for all time, Revenue AT is the revenue earned over the attribution time.
ROI – Flow metric
ROI AT – Attribution Time metric
