1. Preparing for Airbridge Implementation

In the previous document, we provided a general overview of the Airbridge onboarding process. In this document, we will explain in detail the basic tasks that marketers need to prepare for implementing Airbridge. We will guide you through the necessary requirements, including both essential and recommended items such as dashboard creation, advertising channel integration planning, event design, and review of additional development work. Please carefully review the contents below and proceed with the preparation work.

First, please create an Airbridge account and register your app. For detailed dashboard creation instructions, please refer to the user guide below.

▶ Registering a New App

▶ Go directly to the Airbridge Dashboard: Click the 'Dashboard' button.

The Airbridge app mode cannot be changed after creation, so please carefully select either Performance Measurement Mode or Development Mode. Generally, you should select Performance Measurement Mode for production apps where you will measure advertising performance, and Development Mode for staging or development apps that require testing during the development process. If you do not have a separate development app, it is fine to create only a Performance Measurement Mode app.

Managing Users (Optional)

If there are other users, invite them to the Airbridge app.

▶ Managing Users in Your Organization

Airbridge is fundamentally a Mobile Marketing Performance measurement tool (MMP). Please check the advertising channels you operate and verify whether they can be integrated with Airbridge. You can find a list of advertising channels integrated with Airbridge in the user guide below. If you cannot find an advertising channel you operate, please request that the advertising channel complete an advertising channel integration application form.

▶ List of Advertising Channels Integrated with Airbridge

▶ Advertising Channel Integration Application Form

Event taxonomy is the process of defining and structuring the events to be collected within an app or website. A well-designed event taxonomy effectively supports data analysis and campaign performance measurement. Please refer to the user guide below to organize the events and sub-properties needed to check advertising performance.

• ▶ Airbridge Events: You can reference various information about Airbridge events.

• ▶ Event Taxonomy: This is the official guide on how to design taxonomy.

• ▶ Follow Along with Event Taxonomy Design: If this is your first time designing taxonomy, check this onboarding guide.

• ▶ Example event taxonomies by industry can be found in the guides below.

  • Recommended Airbridge Events for the Gaming Industry

  • Recommended Airbridge Events for the Finance Industry

  • Recommended Airbridge Events for the Commerce Industry

• 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

Since Airbridge provides various features beyond app advertising performance tracking, you can proceed with additional work as described below if necessary. Marketers can determine whether each task is needed and can additionally request the development team to perform the corresponding work.

SDK Work Is Required

These are tasks that require additional SDK work to use features provided by Airbridge.

SDK Work Is Not Required

These are tasks that do not require additional SDK work when using features provided by Airbridge. However, you will need help from other administrators, so please check the task purpose.

This completes the integration preparation work. Please deliver the designed event taxonomy and additional development work list to your development team and proceed to the next step.

▶ 2. Performing Airbridge Development Task