Airbridge can collect various information while tracking events, such as ad clicks, app installs, and purchases, through tracking links and SDKs. Metrics are necessary to visualize the collected data for analyzing ad performance in the Airbridge reports. Airbridge supports metrics that visualize a single type of data or a combination of multiple data types.

For example, when tracking Order Complete events that occur on your app, Airbridge can aggregate the number of events occurred, the number of users who performed the event, or the sales revenue. You can use metrics such as “Order Complete Users (App)” or “Revenue (App)” to visualize a single type of aggregated data, or metrics such as “ARPU (App)” that uses multiple types of aggregated data to visualize the data you need for ad performance analysis.

To view the key metrics supported by Airbridge, go to this page. For comprehensive details on all metrics supported by Airbridge, refer to the Airbridge data specification sheet.

Airbridge supports various types of metrics, including those provided by default and those that can be customized for specific reporting needs.

The metrics that appear as event names aggregate the number of events. Such events are the events collected in line with your event taxonomy design. For example, when selecting Installs (App) as a metric in the Airbridge report, the number of Installs (App) events performed during the set date range will be shown.

Note that events appended with (App) refer to app events, and those with (Web) refer to web events. Events appended with (App+Web) refer to both app and web events.

The metrics that appear as event names appended with “Users” aggregate the number of users that performed the events. For example, when selecting Install Users (App) as a metric in the Airbridge report, the number of unique users who installed the app during the set date range will be shown.

This type of metric data is refreshed every hour. For example, the number of unique users who completed orders in the app between 12:00 PM and 1:00 PM can be visualized by selecting the “Order Complete (App)” metric after 1 PM.

Metrics like Revenue measure the event value collected. For example, when selecting Revenue (App) as a metric, the revenue amount collected when the Order Complete (App) event is performed within the set date range will be shown.

To use such metrics, the event value must be defined when setting up the event taxonomy.

Calculated metrics are defined by formulas using multiple metrics. For example, the CPI (Channel) metric, which is a default Airbridge metric, is a calculated metric that is defined as Cost (Channel) divided by Installs (App).

Airbridge users can define new calculated metrics using all metrics, including default Airbridge metrics and self-serve metrics defined by the Airbridge user. For more information about creating calculated metrics, refer to this article.

Cohort metrics can measure retention or revenue of targeted cohorts. For example, when selecting Day 1 Retention (#) as a metric, which is a sample cohort metric provided by default, the number of users who installed the app within the set date range and returned to the app on Day 1 will be shown.

Airbridge users can define new cohort metrics and use them across all apps within the organization in the Overview Dashboard, Actuals Report, and Trend Report. For more information about creating cohort metrics, refer to this article.

Self-serve metrics are metrics that Airbridge users can define and add to Airbridge by uploading their data to Airbridge for specific reporting needs.

For more information about how to define and use self-serve metrics, refer to this article.

Note

Starting February 4, 2025, the Overview Dashboard, Actuals Report, Trend Report, Retention Report, Revenue Report, Active Users Report, and Audience Manager will only display events and metrics measurable using the collected data.

The metric selector only shows metrics that are measurable using the data collected in Airbridge. This means that some metrics may not be available if the relevant data has not been collected yet or the SDK is not configured to collect certain data. Refer to the example below.