> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adriel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Data reference

> Metrics, breakdowns, refresh cadence, and limits for the Airbridge data source in Adriel.

## Introduction

Airbridge is a mobile measurement partner (MMP) and deep-linking platform with strong adoption among Korean and global app marketers. It supports iOS, Android, and web through the Airbridge SDK and exposes attribution, ad performance, and engagement data through versioned Reports APIs.

This connector reads attribution and aggregated performance data for a single Airbridge app. Each data source maps to one app (identified by app name) and is locked to **one** of two mutually exclusive report types at creation: **Actuals** (ad performance and attribution events) or **Active Users** (engagement and revenue aggregates). Each report type uses its own API version, field-discovery strategy, and metric and breakdown catalog.

As a mobile attribution connector, attribution events, breakdowns, and currencies are standardized so widgets can aggregate across sources without additional configuration.

To connect this data source, see [How to connect Airbridge to Adriel](/data-sources/a-f/airbridge/how-to-connect).

## Data refresh strategy

### Architecture data

Architecture covers the Airbridge app identified by app name. For Actuals data sources, the metric and breakdown catalogs are discovered dynamically from the `actual-report/metrics` and `actual-report/fields` endpoints — new fields appear automatically once Airbridge exposes them for the app. Active Users data sources use a fixed catalog.

### Reports data

**On demand.** The data provided by this connector is fetched fresh when a dashboard is visited. Both Actuals (API v7) and Active Users (API v4) queries hit the Airbridge Reports API live; there is no report cache between visits.

The connection is not held open between calls, so every request carries the API key fresh. This is slightly slower under high throughput but ensures stale tokens never linger.

## Architecture levels

App → Channel → Campaign → Ad group → Ad → Creative

The active hierarchy depends on the chosen report type and the breakdowns selected on the data source.

## Metrics

<Note>
  **How to read the columns**
  **Data type** uses this vocabulary: Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean.
  **API Key** in code style like `airbridge:actuals_installs` is the literal field key Adriel sends to the Airbridge Reports API. *Italic text* describes how a value is produced when it doesn't map cleanly to a single source field.

  Each data source exposes only one report type. Metrics prefixed `airbridge:actuals_*` belong to **Actuals** data sources; metrics prefixed `airbridge:active_users_*` belong to **Active Users** data sources. Actuals metrics are discovered dynamically per app, so the picker reflects what the connected app exposes.
</Note>

### Clicks & impressions

*Available on Actuals data sources.*

| Metric      | Description             | Data type | API Key                         |
| ----------- | ----------------------- | --------- | ------------------------------- |
| Impressions | Tracked ad impressions. | Number    | `airbridge:actuals_impressions` |
| Clicks      | Tracked ad clicks.      | Number    | `airbridge:actuals_clicks`      |

### Installs & app events

*Available on Actuals data sources. The full set is discovered dynamically per app.*

| Metric        | Description                                                        | Data type | API Key                          |
| ------------- | ------------------------------------------------------------------ | --------- | -------------------------------- |
| Installs      | Attributed app installs.                                           | Number    | `airbridge:actuals_installs`     |
| App opens     | App-open events.                                                   | Number    | `airbridge:actuals_app_opens`    |
| Custom events | Each custom event defined in Airbridge surfaces as its own metric. | Number    | `airbridge:actuals_event_{name}` |

### Cost & ROAS

*Available on Actuals data sources.*

| Metric | Description                                         | Data type | API Key                  |
| ------ | --------------------------------------------------- | --------- | ------------------------ |
| Cost   | Reported network cost, in the app's local currency. | Currency  | `airbridge:actuals_cost` |

### Retention & engagement

*Available on Active Users data sources. App and web are tracked separately.*

| Metric             | Description                                    | Data type | API Key                         |
| ------------------ | ---------------------------------------------- | --------- | ------------------------------- |
| Active users (app) | SDK event generators during the period.        | Number    | `airbridge:active_users_app_au` |
| Paying users (app) | Users with purchase history during the period. | Number    | `airbridge:active_users_app_pu` |
| Active users (web) | Unique users with any web event.               | Number    | `airbridge:active_users_web_au` |
| Paying users (web) | Unique users with Order Complete web events.   | Number    | `airbridge:active_users_web_pu` |

### In-app revenue

*Available on Active Users data sources. Values are in the app's local currency.*

| Metric        | Description                                  | Data type | API Key                              |
| ------------- | -------------------------------------------- | --------- | ------------------------------------ |
| Revenue (app) | In-app purchase revenue.                     | Currency  | `airbridge:active_users_app_revenue` |
| ARPU (app)    | *Revenue divided by active users (app).*     | Currency  | `airbridge:active_users_app_arpu`    |
| ARPPU (app)   | *Revenue divided by paying users (app).*     | Currency  | `airbridge:active_users_app_arppu`   |
| Revenue (web) | Sum of value from Order Complete web events. | Currency  | `airbridge:active_users_web_revenue` |
| ARPU (web)    | *Revenue divided by active users (web).*     | Currency  | `airbridge:active_users_web_arpu`    |
| ARPPU (web)   | *Revenue divided by paying users (web).*     | Currency  | `airbridge:active_users_web_arppu`   |

## Breakdowns

### Active Users breakdowns

<Note>
  Active Users exposes a fixed set of breakdowns, each available at three granularities. Replace `{granularity}` with `daily`, `weekly`, or `monthly` — each granularity is a distinct breakdown under the hood, so a dashboard that mixes granularities for one conceptual field is using separate breakdowns.
</Note>

| Breakdown | Description                           | API Key                                         |
| --------- | ------------------------------------- | ----------------------------------------------- |
| Date      | Reporting date, week, or month.       | `airbridge:active_users_{granularity}_date`     |
| Country   | Country code.                         | `airbridge:active_users_{granularity}_country`  |
| OS        | Operating system (iOS, Android, web). | `airbridge:active_users_{granularity}_os`       |
| Channel   | Acquisition channel.                  | `airbridge:active_users_{granularity}_channel`  |
| Campaign  | Campaign name.                        | `airbridge:active_users_{granularity}_campaign` |
| Ad group  | Ad group or ad set.                   | `airbridge:active_users_{granularity}_ad_group` |

The full set spans 21 fixed fields across three granularities (63 breakdowns); the breakdown picker reflects all available combinations.

### Actuals breakdowns

<Note>
  Actuals breakdowns are discovered dynamically per app from the Airbridge fields endpoint, so the picker reflects what the connected app exposes.
</Note>

| Breakdown             | Description                                                                                                 | API Key                     |
| --------------------- | ----------------------------------------------------------------------------------------------------------- | --------------------------- |
| Attribution hierarchy | Grouping fields exposed by the app's Actuals report, such as channel, campaign, ad group, ad, and creative. | `airbridge:actuals_{field}` |

### Channel rollup

<Note>
  This is an Adriel-provided grouping. Selecting it returns a single aggregate sentinel row for cross-connector rollup rather than one row per channel; the connector does not query Airbridge for an all-channels breakdown.
</Note>

| Breakdown | Description                                          |
| --------- | ---------------------------------------------------- |
| Channel   | Return one aggregate row for cross-connector rollup. |

## Limitations

* **Report type is permanent** — a data source is locked to Actuals or Active Users at creation. Switching requires creating a new data source.
* **App and web are tracked separately** — Active Users splits metrics into app and web variants with distinct API keys; there is no automatic merge across platforms.
* **Per-report maximum date range** — Airbridge enforces a maximum period per report and returns an error for ranges that exceed it (surfaced as a "too much data requested" error) ([Airbridge Developers — Reports API](https://developers.airbridge.io/)). The cap varies by report, so no fixed value is imposed by Adriel.
* **Mixed report types not supported** — a single query cannot combine Actuals and Active Users breakdowns.
* **Attribution windows are app-configured** — attribution-window logic is set per app inside Airbridge, and the connector reports whatever windows the Reports API returns. SKAdNetwork attribution (iOS) follows Apple's postback timer.
* **Report generation is asynchronous** — each query creates a report and polls for completion (up to \~50 seconds); very large or slow reports can time out.
* **No connection caching** — the connection is not held open between calls; every request re-sends the API key.

## API references

* [Airbridge Developers](https://developers.airbridge.io/) — Reports API reference (Actuals and Active Users)
* [Airbridge Help Center](https://help.airbridge.io/) — API key generation and app configuration

## See also

* [How to connect Airbridge to Adriel](/data-sources/a-f/airbridge/how-to-connect) (paired how-to)
* [AppsFlyer data reference](/data-sources/a-f/appsflyer/data-reference) — alternative MMP with broader event coverage
* [Adjust data reference](/data-sources/a-f/adjust/data-reference) — alternative MMP