This document explains how to install and use the Airbridge SDK.
SDK installation is a required step to fully utilize Airbridge’s core features, including performance tracking, deeplink configuration, and event collection.
Each section outlines the required setup steps and important considerations.
Please follow the steps in order to ensure a smooth SDK implementation.
First, refer to the developer guide below and install the Airbridge SDK that matches your development environment.
You can find the app name and SDK token required for installation in the Airbridge dashboard under:
Settings → Tokens
▶ Getting Started with the Airbridge SDK
Check supported development languages and install the appropriate SDK.
Learn how to locate your app name and SDK token in the Airbridge dashboard.
The Airbridge SDK automatically collects basic information such as:
Device information (e.g., device model, OS version)
App version information
For the full list of automatically collected data, refer to the guide below:
To collect IDFA from users who allow tracking via the App Tracking Transparency (ATT) prompt, additional configuration is required when sending Install events on iOS.
The collected IDFA is used for attribution through device ID matching, so please ensure this setup is completed if applicable.
However, if you are not collecting ADID (for example, when using a Restricted SDK), this step can be skipped.
▶ Tracking Authorization Prompt Configuration
Use AppTrackingTransparency.framework to display the ATT prompt and obtain user consent.
To allow users to land on specific in-app pages when clicking an Airbridge tracking link, implement deeplink navigation using the Airbridge.handleDeeplink function.
Airbridge tracking links first attempt to open the app via App Links or Universal Links
If that fails, the app is opened using a scheme deeplink
Regardless of how the app is opened, the Airbridge SDK delivers the scheme deeplink URL to the app through Airbridge.handleDeeplink
👉 Developers only need to implement in-app navigation logic based on the scheme deeplink URL received via Airbridge.handleDeeplink.
On iOS, enabling the Autofill feature (password storage) requires adding a Webcredentials domain for security reasons.
For details, refer to the guide below:
To measure in-app conversions and run retargeting campaigns, you must send relevant events from the app.
Please refer to the event taxonomy defined by the marketing team when implementing event names and properties.
No, setting a user identifier is not mandatory. However, it may be useful in the following cases.
For security reasons, we recommend hashing user identifiers before sending them.
Recommended use cases:
Internal analysis: Analyzing Airbridge events based on internal user IDs
Third-party integrations: Some third-party solutions require user IDs to associate events with logged-in users
Events that occur in the webView should be set to be recognized as app events in Airbridge. For this purpose, Airbridge provides a Bridge Function that can handle webView events through hybrid app settings.
To ensure that events occurring in the webView are properly sent as app events, please refer to the following setup methods for each development language.
▶ Android, iOS, Flutter, React Native, Unity: After installing Airbridge Web SDK on the webpage, send events with that SDK and apply hybrid app settings to the webView area.
Android: Hybrid App Setup
iOS: Hybrid App Setup
Flutter: Hybrid App Setup
React Native: Hybrid App Setup
Unity: Hybrid App Setup
Note that app events sent from the webView should be recorded in the 'App Real-time log', not the 'Web Real-time log' when performing QA.
It is recommended to collect properties written according to the event taxonomy set in advance by the marketer. However, we guide you on properties that must not be omitted for each event below, so please make sure to include these properties. If you do not collect the events below, you do not need to consider them.
Purchase Completion (Payment Completion) Event
Event name: airbridge.ecommerce.order.completed
Purchase amount: eventData.value
Used to check purchase amounts in reports.
Currency information (KRW, USD, etc.): eventData.goal.semanticAttributes.currency
When using ad mediation solutions, revenue earned from in-app ads is collected in US dollars (USD). To convert this to the app's base currency in the dashboard, currency information must be collected in the event.
If you are using Applovin Max, Google Admob, or Unity Levelplay Mediation, you can refer to the sample code in Integrating Mediation Platforms.
The base currency is 3 uppercase English letters (e.g., KRW, USD, etc.).
Please send to eventData.goal.semanticAttributes.currency. (Not eventData.goal.semanticAttributes.products.$0.currency.)
Order number: eventData.goal.semanticAttributes.transactionID
You can later remove duplicate events that come in with the same order number.
Purchase Cancellation Event
Event name: airbridge.ecommerce.order.canceled
Order number: eventData.goal.semanticAttributes.transactionID
Please send the order number from the purchase completion time, not from the cancellation.
Ad Impression Event
Event name: airbridge.adImpression
Currency information (KRW, USD, etc.): eventData.goal.semanticAttributes.currency
When using ad mediation solutions, revenue earned from in-app ads is collected in US dollars (USD). To convert this to the app's base currency in the dashboard, currency information must be collected in the event.
If you are using Applovin Max, Google Admob, or Unity Levelplay Mediation, you can refer to the sample code in Integrating Mediation Platforms.
The base currency is 3 uppercase English letters (e.g., KRW, USD, etc.).
Please send to eventData.goal.semanticAttributes.currency. (Not eventData.goal.semanticAttributes.products.$0.currency.)
Beyond basic ad performance tracking, Airbridge provides additional features such as app uninstall tracking.
Please complete any additional development tasks agreed upon with the marketing team in:
1. Preparing for Airbridge Implementation → Decide on Optional Feature Development
Once all SDK installation steps are complete, verify the following:
Deeplink configuration
Event collection
User identifier transmission (if implemented)
Any additional SDK feature setups
Refer to the guides below for detailed testing instructions:
After completing SDK testing, deploy the app version with the Airbridge SDK installed to the app store.
You can find all required information in the “Preparing for App Store Review” section of the Airbridge User Guide.
This completes the installation and configuration of the Airbridge SDK.
Once the SDK-enabled app version is live in the app store, proceed to the next step:
👉 3. Getting Started with the Airbridge Dashboard
도움이 되었나요?