Creating a New Metric
With Airbridge, you can upload data to Airbridge and create your own custom metrics to monitor the health and performance of your service.
Attention
This feature is currently in beta. For any inquiries, contact your CSM.
Airbridge users can upload data that is not collected through the Airbridge SDK, such as the click-through rate of push messages or click rate of promotional emails. The uploaded data can be viewed in the Overview Dashboard, Actuals Report, and Trend Report by using self-serve metrics.
Self-serve metrics are metrics Airbridge users can add to Airbridge and use to create report views, similar to the metrics already available in Airbridge reports.
名称和定义的一致性
建议在组织内的所有 App 中，对于相同名称的事件或指标使用相同的定义，以助于提高多应用绩效分析的效率。
You can upload data as a CSV file to Airbridge using the following methods.
The data you upload is not integrated with the data collected through the Airbridge SDK. For example, if you upload data that contains an event with the same name as an Airbridge Standard Event, it will not affect the data collected through the Airbridge SDK in any way. Instead, it will be defined as a self-serve metric with the same name as the Standard Event. This self-serve metric will show the uploaded data, not the data collected through the Airbridge SDK.
Attention
This feature is currently in beta. For any inquiries, contact your CSM.
With Airbridge, you can create new metrics using formulas to define key indicators that meet your marketing needs. They can be used to create a report view on the Overview Dashboard, Actuals Report, and Trend Report.
Note
This feature is available across all Apps registered with the organization.
Calculated metrics are metrics Airbridge users can add to Airbridge by defining them using formulas, such as CPI (Cost Per Install), CPA (Cost Per Action), etc. They can be used to create report views similar to the metrics already available in Airbridge reports.
Calculated metrics are available across all Apps registered with the organization. However, some calculated metrics may be defined using components that only work as intended for specific apps. For more details, refer to this section of the article.
Components | Description | Example |
|---|---|---|
Metric | Standard/Custom Event metrics (Category), Self-serve metrics | Sign-up (App) |
Numbers | Real numbers | -10, 3.14, 1000 |
Operators | Arithmetic operators and parentheses | +, −, ÷, ×, (, ) |
Attention
Creating calculated metrics requires help from your CSM. For more information, contact your CSM.
Using calculated metrics, you can easily visualize indicators that are complex to calculate across the Overview Dashboard, Actuals Report, and Trend Report. Refer to the following use cases to understand how to use calculated metrics.
CTR (Click-through Rate) is the number of clicks that your ad receives divided by the number of times it is shown.
In general, CTR is the value obtained by dividing the number of times an ad has been clicked by the number of ad impressions and then multiplying by 100. For example, if the number of clicks is 10 and the number of impressions is 100, the CTR is 10(%).
CTR is not a preset metric in Airbridge. To monitor the CTR of your ads, you can create it as a calculated metric by defining it as shown below.
CTR = Clicks/Impressions * 100
You can define your own performance indicator using self-serve metrics and calculated metrics. For example, let's say you want to monitor a custom indicator in Airbridge calculated as follows.
Custom Indicator: The sum of the weighted values of the number of blog visitors (20%), the number of social media tags (30%), and the number of views on a video platform (50%)
First, you need to create self-serve metrics that define the number of blog visitors, the number of social media tags, and the number of views on video platforms, as these are not collected through the Airbridge SDK or other means. Let's say the self-serve metrics have been created as follows.
Number of blog visitors=Blog
Number of social media tags=Social
Number of views on video platforms=Video
Next, using these self-serve metrics, you can create a calculated metric named OwnedMedia by defining it as follows. The result value can be rounded to the third decimal place.
OwnedMedia = (
Blog× 20) ÷ 100 + (Social× 30) ÷ 100 + (Video× 50) ÷ 100.
You can monitor your custom indicator along with other ad performance data in your Airbridge report.
You can also create a new calculated metric by combining a calculated metric and a preset Airbridge metric. For example, you might want to monitor the revenue per OwenedMedia value. You could create a new calculated metric like the following.
OCO (Order Complete per OwnedMedia) = Sales amount (App) / OwnedMedia.
The calculated metrics are available in the Overview Dashboard, Actuals Report, and Trend Report across all Apps registered with your organization, and the individual formulas can be seen in the tooltips.
Day N metrics can be used to view the Day N retention or Day N revenue data in the Actuals and Trend Report. For example, you can create a Day N metric to measure the Day 7 retention rate of users or Day 30 revenue generated by users who installed the app and use it to visualize the data in your report.
A Day N metric measures retention or revenue-related indicators for the Nth day after the users' app entry date. You can use Day N metrics together with other metrics available in the report to create a comprehensive report view for your daily monitoring.
Note
Data of up to 62 days can be aggregated to visualize Day N metric data.
Note
This feature is available across all Apps registered with the organization.
1. In the [Reports]>[Actuals Report] or [Trend Report], click +Add next to [Metric] in the report config box.
2. Select the [Day N Metric] tab and click Create Day N metric.
3. Enter the metric name. The name must be unique. For clarity, use descriptive metric names like "Day 7 New User Retention (%)" and "Day 1 New User Ad Revenue."
4. Select a metric type. See below for the available metric types.
Day N Metric Type | Description |
|---|---|
Retention (%) | Retention rate |
Retention (#) | Number of retained users |
Revenue | Cumulative revenue |
ROAS (%) | Cumulative revenue on ad spend |
5. The Start Event is fixed to Install (App), which is the indicator of app entry. Data of users who didn't perform the Start Event will be excluded from the Day N metric reporting. When using GroupBys, the Start Event data will be grouped by the selected GroupBy option in the report.
6. Select the Return Event or Revenue Event depending on the metric type you selected. Up to 4 Return Events can be selected for retention-related metrics, and 4 Revenue Events can be selected for revenue-related metrics.
Return Event: The Return Event determines the retention of the user who performed the Start Event. If a user performs the Return Event, the user is determined to have returned to the service and is aggregated to measure the Day N metric.
Revenue Event: The Revenue Event is performed by users who performed the Start Event and is closely related to the revenue generated by the user. If a user performs the Revenue Event, the user is determined to have generated revenue, which is aggregated to measure the Day N metric.
For retention-related metrics, a measurement option must be selected. In General mode, the Return Events are aggregated based on all Start Events that occurred during the set date range to measure user retention. In Confined mode, user retention is measured with respect to a single Start Event. When a new Start Event occurs, the user journey that was initiated by the previous Start Event is no longer measured.
7. Select Day N. Day N is the Nth day after the users' app entry you want to measure the metric.
8. Click Create. The Day N metric is made available in the metric selector in the Actuals Report and Trend Report.
By creating Day N metrics, you can easily view the retention and revenue-related indicators of the Nth day after the users' app entry date on the Airbridge dashboard. Once created, the Day N metrics are available in the Actuals Report and Trend Report.
Refer to the following use cases to understand how to use Day N metrics.
In the Actuals Report, you can use report metrics and Day N metrics to plan marketing activities targeting users who have joined and been active for a certain period.
Let's say you have an e-commerce app. You can create an Actuals Report to track user retention and cumulative revenue 1 week after users install the app and consider pursuing marketing activities, such as offering coupons and promos to boost sales.
Create a report view using the following metrics.
Select Install Users (App) as a report metric.
Select Day 7 New User Retention (%), Day 7 Retained Users (#), Day 7 New User Revenue as Day N metrics.
When creating the Day N metrics, refer to the following.
Day 7 New User Retention (%): Configure the metric type as Retention (%), the Start Event as Install (App), the Return Event as Open (App), and Day N as Day 7.
Day 7 Retained Users (#): Configure the metric type as Retention (#), the Start Event as Install (App), the Return Event as Open (App), and Day N as Day 7.
Day 7 New User Revenue: Configure the metric type as Revenue, the Start Event as Install (App), the Revenue Event as Order Complete (App), and Day N as Day 7.
In the Trend Report, you can use Day N metrics to monitor the cumulative revenue trend generated by users over a certain period.
Let's say you want to track the daily cumulative ad revenue 1 month after users have installed your game app.
Create a report view using the following metrics.
Select Day 30 New User Ad Revenue as a Day N metric.
When creating the Day N metrics, refer to the following.
Day 30 New User Ad Revenue: Configure the metric type as Revenue, the Start Event as Install (App), the Return Event as Ad Impression (App), and Day N as Day 30.
Hover over or click a Day N metric to view the definition of the metric.
Attention
When a Day N metric is deleted, the metric data is deleted in all reports where it was supported.
Hover over or click a Day N metric and click the [trash] icon to delete the Day N metric. Any Airbridge user can delete the Day N metric regardless of their app roles.
Calculated metrics are defined at the organization level. However, pay attention if the formula defining the calculated metric includes a metric specific to an Airbridge App.
Take a look at the scenario below.
Let's say App A and App B are registered with your organization. As illustrated in the table below, custom events and self-serve metrics are created to measure App A and App B.
|
push_sent |
in_app_sent |
push_clicked |
|---|---|---|---|
Description | Custom event for tracking the number of push notifications sent | Custom event for tracking the number of in-app messages sent | Self-serve metric for tracking the number of push notification clicks |
App A | Defined | Defined | Defined |
App B | Defined | Defined | Not Defined |
Let's say the following 2 calculated metrics were also created, with the formulas including the custom events and self-serve metrics described in the table above. A calculated metric created for 1 App can be used for all Apps registered with the organization.
message_sent = push_sent + in_app_sent
push_click_rat
e= push_clicked / push_sent * 100
The calculated metrics will work differently for App A and App B as illustrated in the table below.
|
message_sent |
push_click_rate |
|---|---|---|
App A | The calculated metric data is displayed. | The calculated metric data is displayed. |
App B | The calculated metric data is displayed. | The calculated metric shows 0 because the “push_clicked” self-serve metric has not been defined for App B. |
Was this page helpful?