Creating Metrics through Data Uploads
You can upload data to Airbridge that is not collected through the Airbridge SDK or imported through channel integrations. Such data could include the click-through rate data of push messages or click rate data of promotional emails. You can create self-serve metrics to visualize such uploaded data in the Overview Dashboard, Actuals Report, and Trend Report.Self-serve metrics
Self-serve metrics are metrics you can add to Airbridge and use to create report views, similar to the metrics already available in Airbridge reports.
NoteIt is advised to use the same definition for events or metrics with the same name across all Apps in your organization. Using consistent names and definitions within the organization can enhance efficiency in analyzing ad performance reports across multiple Apps.
Data upload
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.Use cases
Refer to the following use cases to understand how to use self-serve metrics.App push messages
App push messages
App push messages are a powerful tools that can effectively increase a user’s lifetime value. Upload a CSV file that contains the number of app push messages sent daily to view the data alongside the ad performance data collected by Airbridge in Airbridge reports.
Measuring the click-through rate of push messages
Measuring the click-through rate of push messages
The performance of app push marketing can be measured by the click-through rate of push messages. You can create a self-serve metric and view the data in your Airbridge reports by uploading the click-through rate to Airbridge.Another way to view the click-through rate is to create a custom metric using the data you upload and the data collected by Airbridge. You upload the number of push messages sent to Airbridge and define a new custom metric as the number of push messages sent divided by the number of clicks, which is data collected by Airbridge.
Creating Metrics to Measure Revenue and Retention of a Targeted Cohort
NoteThis feature is available across all apps registered within the organization.

Cohort metrics
NoteData from up to 62 days can be aggregated to visualize the cohort metric data.
-
In the [Reports]>[Actuals Report] or [Trend Report], click +Add next to [Metric] in the report config box.

-
Select the [Cohort] tab and click Create cohort metric.

-
Enter the metric name. The name must be unique. For clarity, use descriptive metric names like “Day 7 Revenue” and “Day 3 User Retention (%).”

- Select Day N.
-
Select Revenue or Retention as metric type and the metric.
When the metric type is Revenue, you can select the view type. When the metric type is Retention, you can select the measurement option.
Metrics by metric type
Revenue MetricsRetention metricsAvailable view types and measurement options
View Types for Revenue metricsThe available view types vary depending on the Revenue Event.Measurement Options for Retention metrics - The Start Event is fixed to Install (App), which is the indicator of the user’s entry into your service. Data of users who didn’t perform the Start Event are not aggregated. Note that GroupBys are applied to the Start Event data.
-
Select the Return Event or Revenue Event, depending on the metric type you selected. You can select up to 5 events.
- Revenue Event: When a user performs the Revenue Event, the user is determined to have generated revenue, which is aggregated to measure the Day N metric.
- Return Event: When 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.
- Click Create. The cohort metric will appear in the [Cohort] tab of the metric selector in the Overview Dashboard, Actuals Report, and Trend Report for all apps within your organization.
Basic features
Find the definition of cohort metrics
Find the definition of cohort metrics
Hover over or click a metric to view the definition.

Delete cohort metrics
Delete cohort metrics
AttentionWhen a cohort metric is deleted, the metric data is deleted in all reports where it was supported.

Use cases
Refer to the following use cases to understand how to use cohort metrics.Actuals Report: Marketing activity planning
Actuals Report: Marketing activity planning
You can monitor the retention and revenue generated by users who have installed the app and been active for a specific period to plan targeted marketing activities.Let’s say you have an e-commerce app. In the Actuals Report, visualize the number of users who installed the app, the number of retained users up to the 7th day after install, and the cumulative revenue up to the 7th day after install. Based on the data, you might consider implementing marketing activities to boost sales, such as offering coupons and launching promotions.To do so, you need the following metrics:
Here is how you can create the cohort metrics:
- Basic metric: Install Users (App)
- Cohort metric: Day 7 New User Retention (%), Day 7 Retained Users (#), Day 7 New User Revenue

- Day 7 New User Retention (%): Configure Day N as Day 7, the metric type as Retention, data display as %, Start Event as Install (App), and Return Event as Open (App).
- Day 7 Retained Users (#): Configure Day N as Day 7, the metric type as Retention, data display as #, Start Event as Install (App), and Return Event as Open (App).
- Day 7 New User Revenue: Configure Day N as Day 7, the metric type and metric as Revenue, Start Event as Install (App), and Revenue Event as Order Complete (App).
Trend Report: Monitoring the trend of key metrics
Trend Report: Monitoring the trend of key metrics
You can monitor the health of your service by visualizing the cumulative revenue that users generate over a certain period.Let’s say you have a gaming app and want to track the cumulative ad revenue generated over 1 month after users have installed the app.To do so, you need the following metric:
Here is how you can create the cohort metric:
- Cohort metric: Day 30 New User Ad Revenue

- Day 30 New User Ad Revenue: Configure Day N as Day 30, the metric type and metric as Revenue, view type as Cumulative, Start Event as Install (App), and Return Event as Ad Impression (App).
Creating Metrics Using Formulas
You can create new metrics using formulas to define key indicators that meet your marketing needs and use them in the Overview Dashboard, Actuals Report, and Trend Report.
Custom metrics
NoteThis feature is available across all apps registered within the organization.
Use cases
Refer to the following use cases to understand how to use custom metrics.Example: CTR
Example: CTR
CTR (Click-Through Rate) measures the ratio of clicks to ad impressions. A high CTR for ads using a specific keyword or creative indicates strong performance. To track CTR, create a custom metric as follows:
- CTR = Clicks / Impressions * 100
Example: Custom performance metric
Example: Custom performance metric
If your team measures performance by the ratio of revenue to a key owned media metric, you can create a custom metric as follows:
- RpO(Revenue per OwnedMedia) = Revenue (App) / OwnedMedia
Attention
Example) When some apps in the organization do not collect a specific metric
Example) When some apps in the organization do not collect a specific metric
App A and App B are in the same organization. Both apps use the following custom events and self-serve metric.
Assume custom metrics are defined as follows.
- message_sent = push_sent + in_app_sent
- push_click_rate = (push_clicked / push_sent) * 100