This is a collection of frequently asked questions found on each page of the Airbridge onboarding guide. Check the frequently asked questions during the onboarding process all in one place on this page.
Is it mandatory to install the Airbridge SDK?
Yes. The Airbridge SDK performs several critical functions:
Collects essential attribution data required for performance analysis
Enables deeplinking by routing users to specific in-app pages
Collects in-app conversion events generated by user actions
To fully utilize all Airbridge features, installing the SDK is required.
When can Airbridge be fully used after app deployment?
Once the app version containing the Airbridge SDK is deployed, Airbridge can collect:
App installs
Deeplink opens
App opens
Other conversion events
However, the point at which Airbridge can be used most effectively depends on the type of campaign being run.
Campaigns can be launched immediately after deploying the SDK-enabled app.
For rewarded install campaigns, it is recommended to allow sufficient time after deployment before launching campaigns.
▶ Why does Airbridge record more install events than internal data after deployment?
Stable retargeting requires a sufficiently high proportion of users to be on an app version that includes the Airbridge SDK.
Conversion events from users on older app versions without the SDK cannot be accurately tracked.
If rapid retargeting is required, consider encouraging app updates or enforcing a mandatory update.
How many events do other companies typically collect?
Companies typically collect only 5-15 key events that are essential for checking advertising performance. The more events you collect, the more management resources are required, so it's best to select and collect only the events that are essential for checking advertising performance.
Can I send events via server-to-server (API) instead of SDK?
If you collect events through the SDK, there is device information that is automatically collected. Airbridge automatically collects certain information such as Country Code and App Version, which is useful for setting up ad fraud verification rules. (▶ Data Automatically Collected by Airbridge SDK)
Events that do not fall under the above category can be sent through Airbridge's Server To Server Event API. When using the API, you must consider the following:
Server To Server Event API uses device ID (cookie ID in the case of web) or User ID as identifiers. You must obtain and store the Device ID from Airbridge SDK and then send it to the API, or set user identifiers in Airbridge SDK so that events sent via API and SDK events are matched by User ID.
The eventTimestamp must be within 24 hours of the event transmission time, and if the difference is more than 24 hours, the Airbridge server will not process the event. Please use an eventTimestamp within 24 hours of the transmission time.
For smooth postback, please send osName and osVersion under device together.
For detailed API requests and restrictions, please refer to the API guide below.
▶ Server To Server Event API Guide
What is the ad impression (adImpression) event? Do I need to collect it to check advertising performance?
The 'ad impression (adImpression)' event is an event that tracks whether users saw an ad on in-app ad placements. For example, a game company that generates revenue from ads in mobile apps may have ad placements that provide items to users when they view in-app ads. In this case, the ad impression event is collected when the user views the in-app ad. If you are using an ad mediation platform such as Google AdMob, AppLovin MAX, or Unity LevelPlay, please check the sample code in the guide below.
▶ Integrating Mediation Platforms
Ad impression and click data occurring on external placements outside your service are collected through tracking links or once ad channel integration is completed. This data can be viewed as 'Impressions' and 'Clicks' in the dashboard, and there is no need to additionally collect events within the app.
It's difficult to determine whether to distinguish user behavior as an event or as a sub-property.
The criterion for Airbridge to postback to media is 'events'. Please collect information that needs to be posted back to media as events. Examples:
You will postback when level 10 is achieved in a game.
Collect a custom event such as 'achieve_level_10'.
First purchase events are sent strictly according to internal criteria.
Please collect a custom event such as 'order_complete_first' separately from the purchase completion event.
Do I need to collect all semantic attributes in Airbridge?
Semantic attributes are optional and should only be collected if needed for advertising performance analysis. In other words, if they are not needed to check advertising performance, you do not need to collect them.
The recommended list of semantic attributes is as follows:
Product-related events (e.g., 'Add to Cart', 'Product View', etc.)
currency, product ID, product name, price, quantity
Purchase completion and purchase cancellation events
currency, transactionID, product ID, product name, price, quantity
Ad impression events
currency
What data does the Airbridge SDK collect automatically?
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:
Is setting user identifiers mandatory?
No, setting user identifiers is not mandatory. However, you may consider setting them in the following cases. Additionally, for security purposes, it is recommended to send user identifiers in hashed form.
Internal event analysis: When you want to analyze Airbridge events based on internal user IDs
Third-party integration: Some third-party solutions collect events based on user IDs, so you can set them if connection with member users is needed.
There is a webView inside the app. How should I send events that occur in the webView?
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.
Are there any required properties that must not be missing?
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.)
Where can I find the information needed for app review?
You can find all required information in the “Preparing for App Store Review” section of the Airbridge User Guide.
I want to create tracking links in bulk.
You can create tracking links in bulk through Google Sheets using Airbridge's tracking link generator. For information on how to create tracking links in bulk using the generator template, please refer to the user guide below.
▶ Creating Tracking Links in Bulk from Generator Template
I created a tracking link with the tracking link generator, but the performance of that link is not visible in the report.
If your Airbridge app role is agency, when using the tracking link generator, please verify that the 'Tracking Link API Token' is set to your own account or your agency's.
Airbridge distinguishes link creators through the tracking link API token. Agencies can only view data from tracking links created by users granted the same agency permissions, so tracking links created with an in-house marketer's tracking link API token will not appear in the report. Recreate the tracking link with the appropriate tracking link API token, or request channel data permissions from the advertiser for the campaigns you operate.
▶ Managing Agency App Access Permissions > Setting Channel Data Permissions
I want to dynamically change the user's landing page for catalog ad operations.
For the basic principle of dynamically changing a user's landing page, please refer to Airbridge's dynamic deep link guide. (▶ Setting Up Deep Links) Please refer to the content below on how to set up dynamic deep links.
Deep Link Address Example Let me explain using an example of a deep link address that lands users on a product detail page. The two deep link addresses below each navigate to different product detail pages:
ablog://detail?pid=1234 (detail page for product number 1234)
ablog://detail?pid=5678 (detail page for product number 5678)
Setting Deep Link Address Using Variables
Since the product number changes dynamically, set this part as a variable using curly braces ({}). For example, designate the pid value as a variable:
ablog://detail?pid={product_id}
Creating Tracking Link
Enter the deep link address set as above in the final destination and create a tracking link. The created tracking link will have a parameter added: product_id={product_id}. For example, the tracking link template could be as follows:
Inserting Dynamic Values Request the advertising channel to dynamically fill in the value for {product_id}. When an actual user clicks the tracking link, {product_id} is replaced with the ID of the clicked product. For example:
When clicking product 1234 ad: https://abr.ge/@airbridge_demo/channel_name?[...]&product_id=1234&[...]
When clicking product 5678 ad: https://abr.ge/@airbridge_demo/channel_name?[...]&product_id=5678&[...]
Deep Link Delivery
Airbridge passes the product_id value filled in the tracking link to the scheme deep link, enabling the user to land on the detail page of the clicked product:
Deep link address delivered to app when clicking product 5678 ad: ablog://detail?pid=5678
Deep link address delivered to app when clicking product 1234 ad: ablog://detail?pid=1234
Tracking links set up in this way can direct users to the detail page matching the product they clicked.
What is the Unattributed channel?
The Unattributed channel refers to cases where app installations or user inflows did not occur through a specific advertising campaign or marketing activity. This includes cases where users install or use the app naturally rather than being acquired through advertising. Other MMPs also call this Organic.
After publishing the app with the Airbridge SDK installed, more Install events are being counted in Airbridge than in internal data. What is the reason?
The Airbridge SDK counts it as an installation when the app is opened for the first time. Therefore, if an existing user who was already using the app updates to a new app version with the SDK installed, it will be counted as an app update internally, but Airbridge will detect that the user is using the app for the first time and count it as an Install event. Because of this, in the early stages of Airbridge adoption, more Install events than expected may be recorded. As time passes and most existing users update the app, this figure stabilizes.
Due to this, it can be difficult to distinguish between existing user updates and new user installations initially. Therefore, when operating install-rewarded ads, it is advisable to operate ads after most existing users have updated the app to reduce this noise.
If you are migrating from an MMP or have collected device IDs (GAID, IDFA, IDFV) of active users internally, you can mitigate this phenomenon by uploading (backfilling) device IDs to the Airbridge server. For details, please refer to the Checking First Event Status via ID Upload guide.
I want to find definitions of terms used in reports
You can check them in the report metrics and report group-by glossaries below.
▶ Report Metrics
I want to find frequently asked questions related to report interpretation.
You can check frequently asked questions related to Airbridge reports in the guide below.
▶ Frequently Asked Questions - Getting Started with Airbridge Reports
There are discrepancies between the number on advertising channel or app market report and Airbridge reports.
Numerical discrepancies can occur between advertising performance that can be checked in advertising channels and Airbridge reports. Representative causes of numerical discrepancies are as follows:
Attribution model
Data aggregation criteria
Validity verification rules
In addition, numerical discrepancies occur due to differences in metric definitions, duplicate event criteria, etc.
For detailed information, please refer to the user guide below.
▶ Reasons for Discrepancies Between Advertising Channels and Airbridge Dashboard
このページは役に立ちましたか？