Skip to main content
Maven metadata URL Install the Airbridge SDK and implement the necessary settings by following the steps below.

Install SDK

The Airbridge Unreal SDK supports the Unreal Engine v.4.23 and later.
The Airbridge Unreal SDK can be installed using the method below. After installation, you can confirm whether the SDK has been properly installed through the Unreal SDK Test.
  1. Download the latest version of the Airbridge Unreal SDK.
  2. Create the Plugins folder in the root directory of your Unreal Engine project.
  3. Locate the Airbridge Unreal SDK within the Plugins folder like in the following structure.
  1. Navigate to [Settings]>[Plugins] in the Unreal Engine toolbar and enable the Airbridge Unreal SDK.
unreal-sdk-01
  1. Add AirbridgeUnreal to the PublicDependencyModuleNames array within the app’s Build.cs file (<YOUR_UE_PROJECT>.Build.cs).

Install Restricted SDK

NoteInstall only one version of the SDK, either the general SDK or the restricted SDK.
Depending on policies and environments, restrictions on collecting device IDs like GAID and IDFA may be required. When installing the Restricted SDK version, the device IDs are not collected. Install the Restricted SDK using the method below.
  1. Download the latest version of the Airbridge Unreal SDK.
  2. Create a Plugins folder in the root directory of your Unreal Engine project.
  3. Locate the Airbridge Unreal SDK within the Plugins folder like in the following structure.
  1. Navigate to [Settings]>[Plugins] in the Unreal Engine toolbar and enable the Airbridge Unreal SDK.
unreal-sdk-01
  1. Add AirbridgeUnreal to the PublicDependencyModuleNames array within the app’s Build.cs file (<YOUR_UE_PROJECT>.Build.cs).

Initialize SDK

Enter the correct App Name and App Token values in the SDK Settings window. The App Name and App Token can be found on the [Settings]>[Tokens] page in the Airbridge dashboard.

Configure SDK settings

  1. Open the Project Settings window in the Unreal Engine.
  2. Under the [Plugins] section, click Airbridge Unreal SDK to open the SDK settings window. You may fill in the fields or click on the checkboxes that are necessary for your service.
  3. After filling in the required fields, click the Set as Default button.
See below for a guide to the settings.

Configure ATT Prompt

NoteThe functions necessary to ensure compliance with privacy policies should be reviewed with legal counsel.
In the iOS environment, the IDFA can only be collected when users consent to data tracking through the App Tracking Transparency (ATT) prompt. Event collection should be delayed until the user allows tracking. If the install event is collected before the user allows tracking through the ATT prompt, the install event data will lack an identifier, making performance measurement difficult. We recommend setting a sufficient delay time for event collection to collect identifiers.
  1. Prepare the text you will use in the ATT prompt.
  2. Provide the ATT prompt following this guide provided by Apple.
  3. If the install event is not collected, the Airbridge React Native SDK delays collecting install events for 30 seconds until the user allows tracking each time the app is launched. If the user exits the app before deciding whether to allow tracking, the SDK will not collect the install event and will try again at the next app launch.
In the SDK settings, configure the iOS Tracking Authorize Timeout Seconds to set a sufficient delay time for collecting install events. The default value is 30 seconds, and it can be set to up to 3600 seconds (1 hour).
AttentionSet a sufficient delay time to collect the app install event. If the SDK collects install events before users can allow tracking on the ATT prompt, the IDFA won’t be collected along with the install events.

Opt-in and opt-out setup

AttentionOptional settings. Configure only if necessary.
You can control when events are collected based on user consent. Set up either opt-in or opt-out according to the privacy policy of your service.
AttentionThis setting controls only when events are collected.
  • To limit advertising identifier collection, refer to Restricting Identifier Tracking or Install Restricted SDK.
  • User identifiers and user attributes set through functions such as SetUserID and SetUserEmail are sent as part of events, so they are not sent while event collection is stopped.

Opt-in setup

The opt-in policy collects events only after the user gives consent. After setting the Auto Start Tracking Enabled in the SDK settings to false, call the StartTracking function at the time when you can collect events. The SDK will start collecting events when the startTracking function is called.

Opt-out setup

The opt-out policy collects events until the user declines. After setting the Auto Start Tracking Enabled in the SDK settings to true, call the StopTracking function at the time when you can no longer collect events. The SDK will stop collecting events when the stopTracking function is called.

SDK Signature

AttentionOptional settings. Configure only if necessary.
With the SDK Signature, you can prevent SDK spoofing and use verified events to measure ad performance. The SDK Signature credentials, which are the Secret ID and the Secret, are required for the SDK Signature setup. They can be found on the [Management]>[Fraud Validation Rules]>[SDK Signature] page in the Airbridge dashboard. For more details on how to find the SDK Signature credentials, refer to this Airbridge guide. Once you have the credentials, go to the SDK settings and enter the Secret ID as sdkSignatureID and the Secret as sdkSignatureSecret.

Deep Linking

Deep linking allows you to redirect users from ads to specific locations within your app. The data collected from the tracking link enables you to monitor the performance of the deep link in Airbridge. Airbridge deep linking works in the following 3 steps.
  1. A scheme deep link is embedded in the tracking link.
  2. When the user opens the tracking link, the app opens through an Airbridge Deep Link.
  3. The Airbridge SDK converts the Airbridge Deep Link back to the scheme deep link and passes it to the app.
When the app is not installed, Steps 2 and 3 are deferred until the app is installed. This is called deferred deep linking.
Simple structure of Airbridge Deeplink
Step 1. A scheme deep link is embedded in the tracking link Embed in the tracking link the scheme deep link that takes the user to a specific screen in the app.
  • Example scheme deep link embedded in the tracking link: YOUR_SCHEME://product/12345
For deep linking to work, the app information must first be registered in [Tracking Link]>[Deep Links] of the Airbridge dashboard. Airbridge uses this information to convert deep links and to convert them back. If the registered information does not match the values set in the app, the app does not open or the user is taken to the wrong screen. Refer to Set up deep linking for more information. When creating the tracking link, also set the fallback destination (app market or website) for users who do not have the app installed. Step 2. When the user opens the tracking link, the app opens through an Airbridge Deep Link When the user opens the tracking link, Airbridge does not use the embedded scheme deep link as it is. Instead, Airbridge converts it into an Airbridge Deep Link, the format that opens the app most reliably in the user’s environment (OS, browser, and whether the app is installed), and opens the app with it.
  • HTTP deep link format 1: https://YOUR_APP_NAME.airbridge.io/~~~
  • HTTP deep link format 2: https://YOUR_APP_NAME.abr.ge/~~~
  • Scheme deep link format: YOUR_SCHEME://product/12345?airbridge_referrer=~~~
HTTP deep links work as App Links on Android and Universal Links on iOS, opening the app without an intermediate page. However, some environments such as in-app browsers do not support this method, and a scheme deep link is used in those environments. Airbridge automatically determines which format to use. The app code does not need to branch by format, but the deep linking setup must allow the app to open through all of the formats above. Refer to Set up deep linking for more information. When the app is not installed, Airbridge saves the Airbridge Deep Link. After the user installs and launches the app through the fallback destination, Airbridge passes the saved Airbridge Deep Link to the app. Refer to Set up deferred deep linking for more information. An Airbridge Deep Link contains information about which tracking link the user came through. Airbridge uses this information to measure the ad performance driven by the deep link. Because of this information, the format of an Airbridge Deep Link differs from the scheme deep link embedded in the tracking link. Step 3. The Airbridge SDK converts the Airbridge Deep Link back to the scheme deep link and passes it to the app When the app opens through an Airbridge Deep Link, the Airbridge SDK handles the following 3 tasks.
  1. It determines whether the given deep link is an Airbridge Deep Link.
  2. It collects the information contained in the deep link and sends a deep link event.
  3. It converts the Airbridge Deep Link back to the scheme deep link embedded in the tracking link (YOUR_SCHEME://product/12345) and passes it to the app.
As a result, regardless of which Airbridge Deep Link format opened the app, the app only needs to handle a single scheme deep link, the one embedded in the tracking link. For the SDK to receive the deep link and pass it to the app, deep linking must be set up in the app. Refer to Set up deep linking for more information.

Set up deep linking

For the deep linking setup, the following information is required.
  • Deep link information submitted in the Airbridge dashboard
  • In-app location address for user redirection
First, submit the deep link information to the Airbridge dashboard.
After entering the deep link information into the Airbridge dashboard, an additional setup is required to enable the following.
  • App launch with Airbridge Deep Links
  • Airbridge Deep Link event collection
  • User redirection with Airbridge Deep Links
For detailed instructions, refer to the information below.

Set up deferred deep linking

When a user clicks on a tracking link with deferred deep linking capabilities and the app is not installed on the device, the Airbridge SDK collects the deep link as follows.
Deferred deep links are automatically passed to onDeeplinkReceived callback, so no additional settings are required.

Set up custom domain

AttentionOptional settings. Configure only if necessary.
  1. Enter the custom domain address into the Airbridge dashboard by referring to this article
  2. In the SDK Settings, enter the custom domain address in the Custom Domain.
AttentionThe custom domain address you add to the SDK should be the same as the custom domain address entered into the Airbridge dashboard.

In-app events

The Airbridge SDK collects user actions from the app as per settings and sends them as in-app events.

Send in-app events

Setting up a Hybrid AppYou can set up the Unreal SDK to handle Airbridge-related work occurring on in-app websites in hybrid apps without changing the website code.
The Airbridge.TrackEvent function must be called to send events. Refer to the information below about the required Airbridge.TrackEvent function components and their types.
Refer to the component definition and available strings below.
The Standard Event Categories provided by the Airbridge SDK can be found in the AirbridgeCategory. You can also enter the Event Categories from the list of Standard Events.Custom events can be sent by entering the event name set in the event taxonomy.Refer to the example below.
AttentionThe Airbridge SDK v4 attributes differ from the previous version. The previous version’s attributes do not include action, label, and value.
Additional information about the event can be collected using attributes.
  • Action, Label: Collect information that can be used as GroupBys in the Airbridge reports
  • Value: Collect information that can be used for sales analysis. Airbridge can perform calculations using the collected data.
  • Semantic Attribute: Collect predefined attributes by Airbridge.
  • Custom Attributes: Collect attributes defined by Airbridge users.
In the FAirbridge::TrackEvent function, you can enter Action, Label, Value, and Semantic Attributes using the semanticAttributes parameter and Custom Attributes using the customAttributes parameter.The semantic attributes predefined by Airbridge can be found in the user guide below.
AttentionOnly actions, labels, values, and the semantic attributes defined in the List of semantic attributes can be passed in semanticAttributes.
  • An attribute that the SDK does not provide as a constant can still be passed as a string key, as long as it is on the list. For example, "totalQuantity".
  • A key that is not on the list is not processed correctly by Airbridge when passed in semanticAttributes. Pass your own attributes in customAttributes instead.
Please refer to the example below.
AttentionSemantic attributes and custom attributes only allow JSON as a data type.
  • JSON types: String, Number, Boolean, Object<String, JSON>, Array<JSON>
  • Types that cannot be used in semantic attributes and custom attributes: Struct, Class, etc.
The standard event categories and semantic attributes provided by the SDK are as follows.
Refer to the example codes for each type of data below.

Additional in-app event settings

AttentionThe default settings will apply if no additional settings are configured. Proceed after reviewing whether additional settings are necessary.
Configure additional settings for sending in-app events if necessary.
The Airbridge SDK includes session information when sending event data.When the app moves to the background or the process is terminated, the background entry time is recorded. When the app returns to the foreground or the process is restarted, the re-entry time is recorded. If the time difference between the last background entry and re-entry exceeds the session timeout, the previous session ends and a new session begins.The default session timeout is 300 seconds (5 minutes). In the SDK settings, you can configure Session Timeout Seconds up to 604,800 seconds (7 days).
AttentionThe Airbridge SDK collects Open events and Foreground events that initiate a new session. However, those events are not collected during a session.
The default transmission interval is set to 0 seconds. In the SDK settings, you can adjust Event Transmit Interval Seconds to modify it to a maximum of 86,400 seconds (1 day).
The following table shows the default and maximum values for the number of events and storage size.In the SDK settings, If you want to limit the number of events the SDK stores, use the Buffer Count Limit, and to limit the storage size of the SDK, use the Event Buffer Size Limit In Gibibyte.
When the event deletion option is activated, all in-app events that are not transmitted during the Airbridge SDK’s initialization process are deleted. By default, the event deletion option is inactive.In the SDK settings, set Clear Event Buffer On Initialize Enabled to true to activate the event deletion option.
The Airbridge SDK supports functions to include device identifiers in all events for transmission.Refer to the example below.

Example Codes

Airbridge collects in-app events that are classified as Standard Events and Custom Events. Standard Events are events predefined by Airbridge. Refer to the example codes below.
Sign Up
Sign In
Sign Out
Home viewed
Product list viewed
Search result viewed
Product viewed
Add payment info
Add to wishlist
Add to cart
Initiate checkout
Order completed
Order canceled
Start trial
Subscribe
Unsubscribe
Add impression
Ad click
Complete tutorial
Achieve level
Unlock achievement
Rate
Share
Schedule
Spend credits
Custom Events are events defined by Airbridge users to track user actions that are unique to their services. Refer to the example code below.

User Data

Airbridge sends user data along with events. User data allows for a more accurate ad performance measurement.

Set User ID

User IDs refer to the user identifier used in a service. User IDs should be unique IDs that can identify unique users across websites and apps. Refer to the example below.

Send additional user information

AttentionSensitive user information may be included. Send after a thorough review with a legal advisor.
Refer to the functions below to send additional user information. Refer to the example below.

Hash user information

When User Info Hash Enabled is set to false in the SDK settings, user emails and phone numbers are passed without being hashed. The default setting is true.

Reset User Information

You can initialize user information with the FAirbridge::ClearUser function.
AttentionOptional settings. Configure only if necessary.

Include User Information in Install/Open Events

The SDK automatically sends install and open events immediately after the app launches. Therefore, if you call user information functions right after the app launches, the user information may not be included in the install/open events depending on the event transmission timing. To ensure user information is included in install/open events, control the timing of event transmission through Opt-In setup. Implement in the following order:
  1. Set the Auto Start Tracking Enabled option to false when Configure SDK settings.
  2. Call user information functions to set user information.
  3. Call the startTracking() function to start event collection.

Additional SDK Settings

Follow the instructions below for additional setup.
AttentionOptional settings. Configure only if necessary.

Calculating SKAdNetwork Conversion Value on the Server

By default, the ConversionValue in SKAdNetwork is calculated using the values from the SDK. If you want to measure events collected server-side through SKAN instead of the SDK, set the calculateSKAdNetworkByServerEnabled option to true.
AttentionIf you are currently using conversion values calculated by the SDK via SKAdNetwork, please exercise caution when making changes. Altering the conversion value calculation method may cause inconsistencies between existing and new data.

Restricting Identifier Tracking

You can prevent the SDK from collecting certain identifier data.
NoteAirbridge Unreal SDK v.4.7.0 or later is required.
In SDK settings, set the Tracking Blocklist to specify which identifiers should be blocked. Events collected after this configuration will exclude the specified identifiers.Check the restricted data in the identifier restriction list.
AttentionAirbridge Unreal SDK v.4.9.0 or later is required.
While the SDK is running, you can use the AllowTrackingItem and BlockTrackingItem functions to set the data to be restricted. The specified identifier items will be excluded or included. This does not affect events that have already been stored.
Check the restricted data in the identifier restriction list.
An identifier restriction list is provided through AirbridgeTrackingBlocklist.

SDK settings by build settings

NoteAirbridge Unreal SDK 4.5.0 or later is required.
You can apply different SDK settings per build setting. Activate the Use Development Airbridge Settings or Use Production Airbridge Settings option, depending on your build setting to configure the SDK accordingly. If the Use Development Airbridge Settings or Use Production Airbridge Settings option is inactive, the SDK settings are set to the Default settings.
  • When the Use Development Airbridge Settings is activated and your app is on development Debug, Development, or Test setting, the SDK settings are set to the Development settings.
unreal-sdk-03
  • When the Use Production Airbridge Settings is activated and your app is on production Shipping setting, the SDK settings are set to the Production settings.

Integrate Google’s ICM attribution data

AttentionReact Native SDK v.4.4.0 or later is required.
Integrated Conversion Measurement (ICM) is Google’s privacy-driven solution for filling in conversion tracking gaps caused by stricter tracking limitations. Google provides the ICM attribution data, which is the non-deterministic attribution data provided by Google’s privacy-preserving conversion modeling. To integrate the ICM attribution data, the Google’s On-Device Conversion Measurement (ODM) SDK must be installed. For detailed information, refer to this article. or contact Google.
Airbridge Unreal SDK v.4.3.0 or later is required.
Tracking links are links that are embedded to ads for data collection. When users click on the ad, the tracking link is used to pass the touchpoint data to Airbridge, allowing for ad attribution. Also, users who click on the ad with a tracking link can be redirected to a specific destination. Use the CreateTrackingLink function to create tracking links. Refer to the code examples and the parameter details below.
c++
Use the Option parameter in the CreateTrackingLink function to configure tracking link options.
Use the OnSuccess callback in the CreateTrackingLink function to pass the FAirbridgeTrackingLink.
c++
Refer to the example codes below.
The deep links passed through the AFAirbridge::SetOnDeeplinkReceived method of the Airbridge Unreal SDK include not only Airbridge Deep Links but also deep links from other solutions.
ExampleGameModeBase.cpp
By setting Is Handle Airbridge Deeplink Only to true in the SDK settings, only Airbridge Deep Links will be passed to the onDeeplinkReceived callback. In this way, you can handle the deep links from other solutions separately from the Airbridge Deep Links. Depending on how the link is opened, it may be difficult to properly utilize the app’s tracking link in-app. The FAirbridge::Click function or FAirbridge::Impression function allows you to utilize tracking links normally, bypassing the external browser.
AttentionWhen you set up the Airbridge SDK to use tracking links within apps, every time a tracking link is used within the app, Deeplink Pageviews are aggregated as Target Events. The deep link performance may be affected when Deeplink Pageviews occur frequently right after Deeplink Opens.The attribution window for Deeplink Pageviews is set to 3 days by default. If you want to change the attribution window for Deeplink Pageviews, contact your Airbridge CSM. If you don’t have a designated CSM, contact the Airbridge Help Center.

Get attribution results

AttentionIt takes some time for the Airbridge SDK to collect attribution results. We do not recommend using attribution results for functionalities requiring real-time processing.
You can receive attribution results for installation events through the FAirbridge::SetOnAttributionReceivedfunction.
The value is delivered as follows, depending on the existence of attribution results.
If the attribution result exists, a dictionary including the values below will be passed to the callback. All keys provide the attribution data. For example, attributedChannel contains information about the ad channel to which the ad performance is attributed.The attribution results are passed to the callback within 1 minute after SDK initialization. If the app is closed before the attribution result is passed, the previous attribution results will be passed to the callback within 1 minute the next time the app is launched. Depending on network conditions and other factors, there may be a delay of up to 5 minutes.
If there is no attribution result, the following dictionary will be sent to the callback.
AttentionApply the code below using a custom iOS AppDelegate.
After the push notification is clicked, you need to pass the deep link information in the payload to the Airbridge SDK to collect the deep link event. Set up the FAirbridge::trackDeeplink function.

iOS

Add the code below to your custom AppDelegate.
The Airbridge SDK collects deep link events when the app is opened through a deep link, even if the deep link is not an Airbridge Deep Link. Configure Track Airbridge Link Only in the SDK settings to true to collect deep link events only if the app is opened through an Airbridge Deep Link and prevent unnecessary event collection.

Compliance with Google DMA

To comply with the Digital Markets Act (DMA), the user consent data must be sent to Airbridge. For more information about the DMA and whether it applies to your service, refer to the Airbridge user guide.
AttentionAdvertisers must collect user consent data from all existing and new users in the EEA at least once starting March 6, 2024.
If you are collecting user consent data using a consent management platform that complies with the Transparency and Consent Framework v2.2 protocol, refer to the following method to pass the user consent data to the Airbridge SDK.
For all other cases, refer to the following method.
Follow the steps below to use deferred deep linking in Meta ads. The Airbridge SDK collects the Meta deferred app links before the Airbridge deferred deep links. If there are no Meta deferred app links, the Airbridge deferred deep links are collected. Note that Meta does not support Meta deferred app links for SKAdNetwork campaigns.
  1. Install the Facebook SDK. Refer to the Meta Ads Guide (iOS).
  2. Configure the Facebook Deferred App Link Enabled in the SDK settings to true.

Enable and disable the Airbridge SDK

AttentionIf the SDK is not enabled immediately after the SDK initialization, the Install, Open, and Deeplink Open events may not be collected.
You can turn all functions of the Airbridge SDK on or off. While the SDK is disabled, everything it does stops, including collecting and sending events and handling deep links. Set the initial state Upon initialization, all functions of the SDK are enabled by default. By configuring SDK Enabled in the SDK settings to false, the SDK can be initialized with all functions disabled. Control the SDK at runtime While the app is running, use the functions below to check the activation status or change it.
AttentionEnabling and disabling the SDK controls everything the SDK does. To control only when events are collected, refer to Opt-in setup or Opt-out setup.

Set up Meta Install Referrer collection

To collect the Meta Install Referrer, enter the Meta App ID as the key value for Meta Install Referrer (Facebook App ID) in the SDK settings. Note that the decryption key must be submitted to the Airbridge dashboard to read the decrypted Meta Install Referrer. Refer to this user guide to learn how to enter the decryption key.

Set up uninstall tracking

Airbridge sends a silent push every day between 3:00 PM and 4:00 PM (UTC) to users who performed an app event at least once in the last 6 months to check if the app has been deleted. You can check the uninstall event in the Airbridge reports and raw data export files. Refer to the article below for the detailed setup instructions.

Integrate with third-party solutions

An additional SDK setup is required to integrate with some third-party solutions. It is recommended that you complete this setup before collecting data with the Airbridge SDK. Refer to the articles listed below for integrating with third-party solutions.

SDK logs

The logs provided by the Airbridge SDK are categorized into Debug, Info, Warning, Error, and Fault levels. The Debug level is the least critical log, while the Fault level is the most critical log. By default, the Airbridge SDK provides logs at Warning, Error, and Fault levels. By entering a specific log level as the Log Level value in the SDK settings, the logs from that specified level up to the Fault level will be available.