Install SDK
The Airbridge iOS SDK can be installed using the method below. After installation, you can verify whether the SDK has been properly installed through the iOS SDK Test.- SwiftPackageManager
- CocoaPods
- Tuist
- Manual install
- Navigate to [File]>[Add Packages…] in Xcode.
- Enter the following address into the search bar and click Add Package.
- Click Add Package again.
- The Airbridge iOS SDK will be added to Package Dependencies.
Install Restricted SDK
- SwiftPackageManager
- CocoaPods
- Tuist
- Manual install
- Navigate to [File]>[Add Packages…] in Xcode.
- Enter the following address into the search bar and click Add Package.
- Click Add Package again.
- The Airbridge iOS SDK will be added to Package Dependencies.
- Add the framework corresponding to the dependency of SDK to the project. Navigate to [Project File]>[General]>[Frameworks, Libraries, and Embedded Content] in Xcode and click +.
- Add all the frameworks below. Set the Embed of the added frameworks to “Do not Embed.” Then, navigate to [Project File]>[Build Phase]>[Link Binary With Libraries] in the Xcode and set the Status to “Optional.”
Initialize SDK
SDK initialization methods vary depending on the system architecture. For SceneDelegate Lifecycle or AppDelegate Lifecycle, refer to the method for AppDelegate. For SwiftUI Lifecycle, refer to the method for SwiftUI. The YOUR_APP_NAME and YOUR_APP_SDK_TOKEN can be found on the [Settings]>[Tokens] page in the Airbridge dashboard.- AppDelegate (Swift)
- AppDelegate (Objective-C)
- SwiftUI
Airbridge.initializeSDK function at the very top of AppDelegate’s application(_:didFinishLaunchingWithOptions:) function.Airbridge.initalizeSDK function is called within the application(_:didFinishLaunchingWithOptions:) of the AppDelegate for proper functionality.Configure ATT Prompt
- Prepare the text you will use in the ATT prompt.
-
Enter the prepared text in the
NSUserTrackingUsageDescriptionkey of theInfo.plistfile.
- Xcode
- Tuist
- Navigate to [YOUR_PROJECT]>[Info]>[Custom iOS Target Properties] in Xcode.
- Hover your mouse over the key items, click + that appears, and enter
Privacy - Tracking Usage Description. - Enter the text for the ATT prompt as value.
- Set the time for displaying the ATT prompt on the app.
Provide the ATT prompt at a desired time
Provide the ATT prompt at a desired time
ATTrackingManager.requestTrackingAuthorization function should be called at the desired time you want to display the ATT prompt.ATTrackingManager.requestTrackingAuthorization function does not provide the ATT prompt if the app that called it is not in an active state.Provide the ATT prompt at app launch
Provide the ATT prompt at app launch
- If the install event is not collected, the Airbridge iOS 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.
setAutoDetermineTrackingAuthorizationTimeout function can be used to set a sufficient delay before event collection. The default setting is 30 seconds and can be set to up to 3600 seconds (1 hour).
Opt-in setup
setAutoStartTrackingEnabled function 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
setAutoStartTrackingEnabled function to true, call the stopTracking function at the time when you can no longer collect events. When the stopTracking function is called, the SDK will stop collecting events.
SDK Signature
setSDKSignature function above the SDK initialization code.
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.How Airbridge Deep Links work
When a user clicks on the Airbridge tracking link, the scheme deep link embedded in the tracking link is converted into an Airbridge Deep Link, which can be either an HTTP deep link or a scheme deep link. This Airbridge Deep Link redirects the user to the desired app location. Then, the Airbridge SDK converts the Airbridge Deep Link back to the original scheme deep link embedded in the tracking link and passes it to the app.- Example scheme deep link embedded in the tracking link: YOUR_SCHEME://product/12345
-
Examples of Airbridge Deep Links
- 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=~~~

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
Enter the deep link information into the Airbridge dashboard
Enter the deep link information into the Airbridge dashboard
scheme://)iOS App ID- In the Apple Developer Dashboard, go to the [Identifier] of the app you want to set up the deep link and find the App ID Prefix and Bundle ID value.
-
Enter the iOS App ID in the format of
App ID Prefix+ .+ Bundle ID. (e.g.9JA89QQLNQ.com.apple.wwdc)
- App launch with Airbridge Deep Links
- User redirection with Airbridge Deep Links
Enable app launch with Airbridge Deep Links
Enable app launch with Airbridge Deep Links
- Navigate to [YOUR_PROJECT]>[Info]>[URL Types] in Xcode.
- Click + and enter the iOS URI scheme you submitted to the Airbridge dashboard into the URL Schemes field.
://.- Navigate to [YOUR_PROJECT]>[Signing & Capabilities] in Xcode.
- Click + Capability to add Associated Domains.
-
Add
applinks:YOUR_APP_NAME.airbridge.ioandapplinks:YOUR_APP_NAME.abr.geto Associated Domains. YOUR_APP_NAME is the App Name, which can be found on the [Settings]>[App Settings] page in the Airbridge dashboard.
Enable user redirection with Airbridge Deep Links
Enable user redirection with Airbridge Deep Links
trackDeeplink function to collect the Deeplink Open events through the SDK. Then call the handleDeeplink function to convert the Airbridge Deep Link into the original scheme deep link that was used to create the tracking link. Lastly, redirect the user to the intended in-app location.When the app is launched via an Airbridge Deep Link isAirbridgeDeeplink is true and the scheme deep link is sent to the callback uri. When the app is launched via other links isAirbridgeDeeplink is false and no callbacks are triggered. You can handle the Airbridge Deep Links separately by using this logic.trackDeeplink and handleDeeplink functions to track the Deep Link Open event and navigate the user to the intended in-app location.If both SceneDelegate and AppDelegate are present, set up the following callbacks in the SceneDelegate class. If only AppDelegate is used, set them up in the AppDelegate class. If neither is present and you are using SwiftUI, configure them in the App class.- SceneDelegate (Swift)
- AppDelegate (Swift)
- SwiftUI (Swift)
- SceneDelegate (Objective-C)
- AppDelegate (Objective-C)
- Implement a function to navigate the user when the app is opened via an Airbridge deep link.
- Set up the
scene:willConnectTo:options:callback. Call thetrackDeeplinkandhandleDeeplinkfunctions to collect Deeplink Open events, and call the function implemented above to navigate the user.
- Set up the
scene:openURLContexts:callback. Call thetrackDeeplinkandhandleDeeplinkfunctions to collect Deeplink Open events, and call the function implemented above to navigate the user.
- Set up the
scene:continue:callback. Call thetrackDeeplinkandhandleDeeplinkfunctions to collect Deeplink Open events, and call the function implemented above to navigate the user.
Set up deferred deep linking
When a user clicks on a tracking link with deferred deep linking capabilities and your app is not installed on the device, the Airbridge SDK collects the deep link as follows.How the Airbridge SDK collects deferred deep links
How the Airbridge SDK collects deferred deep links
- The
Airbridge.startTrackingfunction is called with the opt-in settings in place. Or, opt-in has not been set. - The ATT tracking response has been determined. Or, the event collection delay time set in the ATT prompt has expired.
Airbridge.handleDeferredDeeplink function to convert the saved Airbridge Deep Link into a scheme deep link after collection and pass it to the app. The converted scheme deep link should be used to send the user to the intended destination.
Airbridge.handleDeferredDeeplink function returns true if the app is installed and called for the first time, waits for the Airbridge Deep Link collection, and converts it to a scheme deep link to pass it to onSuccess. You can use this scheme deep link to send users to the intended destination.
If there is no stored Airbridge Deep Link, nil is passed to onSuccess. If the SDK is not initialized or if the Airbridge.handleDeferredDeeplink function has not been called for the first time, false will be returned.
The scheme deep link passed is generally in the format of YOUR_SCHEME://... URL. If you use services like Meta Deferred App Links, it may be passed in a different format.
Set up custom domain
- Enter the custom domain address into the Airbridge dashboard by referring to this article
- When initializing the Airbridge SDK, use the
setTrackingLinkCustomDomainsfunction to add the custom domain address. TheYOUR_APP_CUSTOM_DOMAINshould be the Fully Qualified Domain Name (FQDN).
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
Airbridge.trackEvent function to send events. Refer to the information below about the required Airbridge.trackEvent function components and their types.
Event Category
Event Category
Attributes
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.
Airbridge.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.Refer to the example below.- JSON types: String, Number, Boolean, Object<String, JSON>, Array<JSON>
- Types that cannot be used in semantic attributes and custom attributes: Struct, Class, etc.
Event Category of Standard Events provided by the SDK (AirbridgeCategory)
Event Category of Standard Events provided by the SDK (AirbridgeCategory)
Semantic Attributes provided by the SDK (AirbridgeAttribute)
Semantic Attributes provided by the SDK (AirbridgeAttribute)
Additional in-app event settings
Configure in-app event sessions
Configure in-app event sessions
setSessionTimeout function.Configure in-app event transmission frequency
Configure in-app event transmission frequency
setEventTransmitInterval function, you can modify it to a maximum of 86,400 seconds (1 day).Refer to the example below.Configure in-app event storage
Configure in-app event storage
setEventBufferCountLimit function, and to limit the storage size of the SDK, use the setEventBufferSizeLimit function.Refer to the example below.Clear unsent in-app events
Clear unsent in-app events
setClearEventBufferOnInitializeEnabled function to true to activate the event deletion option.Configure device IDs
Configure device IDs
| #{“width”: “140px”} Function | #{“width”: “240px”} Description |
|---|---|
Airbridge.setDeviceAlias | Adds additional device identifiers. Up to 10 can be entered. - key: Maximum 128 characters. It must satisfy the regular expression ^[a-zA-Z_][a-zA-Z0-9_]*$.- value: Maximum 128 characters. |
Airbridge.removeDeviceAlias | Deletes only specified device identifiers. |
Airbridge.clearDeviceAlias | Deletes all device identifiers. |
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 Screen, Product Catalog
Sign-up, Sign-in, Sign-out, Home Screen, Product Catalog
Sign up
Sign in
Sign out
Home screen view
Product list viewed
Search Results, Product View, Add Payment Info, Add to Wishlist, Add to Cart
Search Results, Product View, Add Payment Info, Add to Wishlist, Add to Cart
Search results view
Product detail page view
Payment method registration
Adding to wishlist
Adding to cart
Initiate Checkout, Order Complete, Order Cancel, Start Trial, Subscribe, Unsubscribe
Initiate Checkout, Order Complete, Order Cancel, Start Trial, Subscribe, Unsubscribe
Start payment
Purchase complete
Purchase cancellation
Start trial
Subscription
Unsubscribe
Ad Impression, Ad Click, Complete Tutorial, Achieve Level, Unlock Achievement
Ad Impression, Ad Click, Complete Tutorial, Achieve Level, Unlock Achievement
Ad exposure
Ad click
Tutorial completion
Level achievement
Task completion
User Data
Airbridge sends user data along with events. User data allows for a more accurate ad performance measurement.Set User IDs
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.| Function | Description |
|---|---|
Airbridge.setUserID | Inputs the user ID. |
Airbridge.clearUserID | Deletes the user ID. |
Airbridge.setUserAlias | Adds additional user identifiers. Up to 10 items can be added. - key: Up to 128 characters. Must follow the regular expression ^[a-zA-Z_][a-zA-Z0-9_]*$.- value: Up to 1024 characters. |
Airbridge.removeUserAlias | Deletes only specified identifiers. |
Airbridge.clearUserAlias | Deletes all additional user identifiers. |
Send additional user information
| Function | Description |
|---|---|
Airbridge.setUserEmail | Inputs the user email. It is hashed with SHA256. |
Airbridge.clearUserEmail | Deletes the user email. |
Airbridge.setUserPhone | Inputs user’s phone number. The data is hashed using SHA256. |
Airbridge.clearUserPhone | Deletes the user’s phone number. |
Airbridge.setUserAttribute | Adds additional user attributes. Up to 100 items can be added. - key: Up to 128 characters. Must satisfy the regular expression: ^[a-zA-Z_][a-zA-Z0-9_]*$.- value: Only supports string, number, and Boolean types. Up to 1024 characters. |
Airbridge.removeUserAttribute | Deletes only specified attributes from the additional attributes. |
Airbridge.clearUserAttributes | Deletes all additional user attributes. |
Airbridge.setHashUserInformationEnabled function is set to false, the user’s email and phone number are sent without hashing. The default setting is true.
Clear user data
You can reset user information with theAirbridge.clearUser function.
Include User Information in Install/Open Events
The SDK automatically sends install and open events immediately after initialization. Therefore, if you call user information functions right after initialization, 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. Follow these steps:Additional SDK Settings
Follow the instructions below for additional setup.Using Multiple Instance Apps
Airbridge object. However, in certain situations, you may need an independent SDK instance.
The SDK supports multi-tenant environments where multiple Airbridge projects can be operated simultaneously within a single app.
You can create a new instance using AirbridgeInterface.
Instance Creation and Initialization
Airbridge object and other instances, allowing you to use all SDK features, including initialization, independently.
Event Tracking Example
Set Up Deferred Deeplinks for Multiple Instance Apps
Airbridge.handleDeferredDeeplink(apps:onSuccess:onFailure) function.
When using the existing Airbridge.handleDeferredDeeplink(onSuccess:onFailure) function in a multi-app environment, each Airbridge instance may independently receive the deferred deeplink from the tracking link that was clicked, resulting in duplicate deliveries. This causes the onSuccess callback to be invoked multiple times, which can lead to unintended navigation behavior.
The Airbridge.handleDeferredDeeplink(apps:onSuccess:onFailure) function delivers via callback only the deferred deeplink from the most recently clicked tracking link, determined across all Airbridge instances passed through apps. The deferred deeplink is delivered only once per app install.
Airbridge.handleDeferredDeeplink(apps:onSuccess:onFailure) instead of Airbridge.handleDeferredDeeplink(onSuccess:onFailure).Calculating SKAdNetwork Conversion Value on the Server
calculateSKAdNetworkByServerEnabled option to true.
Restricting Identifier Tracking
You can prevent the SDK from collecting certain identifier data.Restricting Identifiers During SDK Initialization
Restricting Identifiers During SDK Initialization
setTrackingBlocklist method to specify which identifiers should be blocked. Events sent after this configuration will not include those identifiers.Restricting Identifiers During SDK runtime
Restricting Identifiers During SDK runtime
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.Identifier Restriction List
Identifier Restriction List
Integrate Google’s ICM attribution data
Create tracking links within the app
createTrackingLink function to create tracking links. Refer to the code examples and the parameter details below.
option parameter in the createTrackingLink function to configure tracking link options.
Configure tracking link options
Configure tracking link options
| Key | Type | Description |
|---|---|---|
| AirbridgeTrackingLinkOption.CAMPAIGN | String | The campaign credited with the winning touchpoint or conversion. |
| AirbridgeTrackingLinkOption.AD_GROUP | String | The ad group credited with the winning touchpoint or conversion. |
| AirbridgeTrackingLinkOption.AD_CREATIVE | String | The ad creative credited with the winning touchpoint or conversion. |
| AirbridgeTrackingLinkOption.CONTENT | String | The content credited with the winning touchpoint or conversion. |
| AirbridgeTrackingLinkOption.TERM | String | The search term credited with the winning touchpoint or conversion. |
| AirbridgeTrackingLinkOption.SUB_ID | String | The sub publisher that generated the touchpoint. Sub media values are usually provided by predefined “integrated” channels. |
| AirbridgeTrackingLinkOption.SUB_ID_1 | String | The 1st level sub-sub publisher that generated the touchpoint. Sub media values are usually provided by predefined “integrated” channels. |
| AirbridgeTrackingLinkOption.SUB_ID_2 | String | The 2nd level sub-sub publisher that generated the touchpoint. Sub media values are usually provided by predefined “integrated” channels. |
| AirbridgeTrackingLinkOption.SUB_ID_3 | String | The 3rd level sub-sub publisher that generated the touchpoint. Sub media values are usually provided by predefined “integrated” channels. |
| AirbridgeTrackingLinkOption.DEEPLINK_URL | (Custom Scheme URL String) | Configure the Deeplink URL for redirect. |
| AirbridgeTrackingLinkOption.DEEPLINK_STOPOVER | Boolean | Stopover Airpage feature of the Deep Linktrue: activatefalse: deactivate |
| AirbridgeTrackingLinkOption.FALLBACK_IOS | (“store” | Web URL String) | ios fallback when app is not installed |
| AirbridgeTrackingLinkOption.FALLBACK_ANDROID | (“store” | Web URL String) | android fallback when app is not installed |
| AirbridgeTrackingLinkOption.FALLBACK_DESKTOP | (Web URL String) | desktop fallback when app is not installed |
| AirbridgeTrackingLinkOption.FALLBACK_IOS_STORE_PPID | String | The ppid for the Custom Product Page in the Apple App Store. Enable the custom product page to be shown when landing in the App Store. |
| AirbridgeTrackingLinkOption.FALLBACK_ANDROID_STORE_LISTING | String | The Custom Store Listing listing value for the Google Play Store. Enables the display of your custom store listing when landing on the Google Play Store. |
| AirbridgeTrackingLinkOption.OGTAG_TITLE | String | og:title for tracking link |
| AirbridgeTrackingLinkOption.OGTAG_DESCRIPTION | String | og:description for tracking link |
| AirbridgeTrackingLinkOption.OGTAG_IMAGE_URL | (Web URL String) | og:image for tracking link |
| AirbridgeTrackingLinkOption.OGTAG_WEBSITE_CRAWL | (“desktop”) | When the tracking link is shared, the social media platform directly crawls the Open Graph of the desktop URL specified in fallbackPaths and uses it for the social share preview. Dynamic URLs are also supported, and any change to the Open Graph is reflected automatically from the next time the link is shared. The values set for title, description, and imageUrl will be ignored. |
| AirbridgeTrackingLinkOption.CUSTOM_SHORT_ID | String | Configure the short ID of tracking links depending on your campaign or contents. If not passed, a random short ID will be generate, and can not be changed once generated. |
| AirbridgeTrackingLinkOption.IS_REENGAGEMENT | (“off” | “on_true” | “on_false”) | Configure the Re-engagement parameter. The Re-engagement parameter has three options. off: OFF is the default setting. The touchpoint can be attributed to both install events and post-install events (in-app events). on_true: ON-TRUE is used for re-engagement campaigns for installed users. The touchpoint generated by the tracking link is attributed only to the deeplink open and the following in-app events, not to the install event. on_false: ON-FALSE is used for user acquisition campaigns targeting uninstalled users. The touchpoint generated by the tracking link is attributed only to the install event and the following in-app events, not to the ‘deeplink open’ event. |
onSuccess callback in the createTrackingLink function to pass the AirbridgeTrackingLink.
Create tracking links that launch the app or redirect users to the app store
Create tracking links that launch the app or redirect users to the app store
Create tracking links that launch the app or redirect users to a webpage
Create tracking links that launch the app or redirect users to a webpage
Create tracking links that redirects users to the app store only
Create tracking links that redirects users to the app store only
Create tracking links that redirects users to a webpage only
Create tracking links that redirects users to a webpage only
Use tracking links within the app
Depending on how links are opened, it may be challenging to properly use the tracking link within the app. By using theAirbridge.click function or the Airbridge.impression function, you can properly use the tracking link within the app without sending users to an external browser.
When the user clicks a tracking link within the app
When the user clicks a tracking link within the app
Airbridge.click function is called. Depending on the tracking link settings, the scheme deep link is passed, or the user is redirected to the app store or website.When the user engages with a tracking link within the app
When the user engages with a tracking link within the app
Airbridge.impression function is called, and the impression event data is collected.Get attribution results
setOnAttributionReceived function to get the attribution data of install events.
When the attribution result exists
When the attribution result exists
attributedChannel contains information about the ad channel to which the ad performance is attributed.The attribution result is passed to the callback within 1 minute after the install event is passed. If the app is closed before the attribution result is passed, the previous attribution result 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.When no attribution result exists (Organic)
When no attribution result exists (Organic)
Track Deeplink Opens from push notifications
When a user clicks a push notification, the deep link information in the payload should be passed to the Airbridge SDK to enable the collection of deep link events. Use theAirbridge.trackDeeplink function.
Track only Airbridge Deep Links
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. Set thesetTrackAirbridgeDeeplinkOnlyEnabled function to true to collect deep link events only if the app is opened through an Airbridge Deep Link and prevent unnecessary event collection.
Collect events using Action extension
- Add App Group.
- Navigate to [YOUR_PROJECT]>[Signing & Capabilities] in Xcode. Click + Capability and add App Groups. Enter a value in the following format in the App Groups field:
group.YOUR_DOMAIN.YOUR_DOMAIN.YOUR_PRODUCT.airbridge
- Add the SDK initialization code under the
viewDidLoadfunction.
setAppGroup settings. You need to delete all information related to the existing Airbridge SDK to remove or change the setAppGroup settings. This may cause unexpected results, such as previously collected install events being collected again.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.Collecting user consent data through consent management platforms
Collecting user consent data through consent management platforms
- When initializing the SDK, set the
setCollectTCFDataEnabledfunction totrueand thesetAutoStartTrackingEnabledfunction tofalse.
- After the user consent data is stored in the consent management platform, call the
startTrackingfunction.
Collecting user consent data using the Airbridge.setDeviceAlias function
Collecting user consent data using the Airbridge.setDeviceAlias function
- Check the location of the users who launched the app. If their location is within the EEA, check whether the user consent data has been previously collected. If not, user consent data collection is not required.
- If no user consent data has been collected previously, you may collect the data using a prompt or other means. The user consent data fields that need to be collected are
adPersonalization,adUserData.
eea) to the Airbridge SDK using the Airbridge.setDeviceAlias function.| Airbridge Field Name | Google Field Name | Description |
|---|---|---|
eea<string> | eea | Data indicating whether the user location is within the EEA or not - 0: Non-EEA. DMA not applicable.- 1: EEA. DMA applicable. |
adPersonalization<string> | ad_personalization | Data indicating whether the user allowed data tracking for ad personalization - 0: User didn’t allow tracking.- 1: User allowed tracking. |
adUserData<string> | ad_user_data | Data indicating whether the user allowed data sharing with Google - 0: User didn’t allow sharing.- 1: User allowed sharing. |
- After the user consent data and the user location data are sent to the Airbridge SDK, call the
startTrackingfunction.
Set up Meta deferred app links
fetchDeferredAppLink function should not be used.- Refer to the Meta ads document and install the Facebook SDK.
-
Set the
setTrackMetaDeferredAppLinkEnabledfunction in the Airbridge SDK totrue.
Initialize the Airbridge SDK with all functions disabled
setSDKEnabled function to false, the SDK can be initialized with all functions disabled.
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.Third-party platforms integrated with Airbridge
Third-party platforms integrated with Airbridge
SDK logs
The logs provided by the Airbridge SDK are categorized intoDebug, 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 value for setLogLevel function, the logs from that specified level up to the Fault level will be available.
Subsystem: co.ab180.airbridge into the filter at the bottom right in Xcode to view only Airbridge SDK logs.