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 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 theactual-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
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.Clicks & impressions
Available on Actuals data sources.Installs & app events
Available on Actuals data sources. The full set is discovered dynamically per app.Cost & ROAS
Available on Actuals data sources.Retention & engagement
Available on Active Users data sources. App and web are tracked separately.In-app revenue
Available on Active Users data sources. Values are in the app’s local currency.Breakdowns
Active Users breakdowns
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.
The full set spans 21 fixed fields across three granularities (63 breakdowns); the breakdown picker reflects all available combinations.
Actuals breakdowns
Actuals breakdowns are discovered dynamically per app from the Airbridge fields endpoint, so the picker reflects what the connected app exposes.
Channel rollup
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.
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). 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 — Reports API reference (Actuals and Active Users)
- Airbridge Help Center — API key generation and app configuration
See also
- How to connect Airbridge to Adriel (paired how-to)
- AppsFlyer data reference — alternative MMP with broader event coverage
- Adjust data reference — alternative MMP