SKAdNetwork (SKAN) can be fully implemented for iOS app campaign measurement once everything is ready on the ad channels, on the app or web where the ads are displayed, on your iOS app, and on the MMP. Read on to learn how to get ready for iOS app campaign measurement with SKAN.
The following requirements must be met to measure iOS app campaigns with SKAN.
The iOS app has been authenticated on the [Settings]>[App Settings]>[App Auth] page in the Airbridge dashboard.
The Airbridge iOS SDK has been updated to the required version.
The app events and event properties have been mapped to the conversion values and configured on the [Management]>[SKAN Conversion Value] page in the Airbridge dashboard.
SKAN integration between Airbridge and ad channels is complete. SKAN integration between Airbridge and SANs (Self-attributing Networks) that require additional integration processes have been completed.
Attention
Even if all requirements are met, the SKAN version you want to implement may not be available for campaign measurement, depending on the SKAN version supported by the ad channel or the iOS versions of user devices.
For example, when the iOS version of the device is earlier than 16.1, SKAN versions earlier than 4.0 are automatically applied for campaign measurement. See below for the SKAN versions applied for measurement per iOS versions.
iOS 16.1 and later: SKAN 4.0
iOS 14.6 ~ 16.0: SKAN 3.0
iOS 14.5 and earlier: SKAN 2.2 and earlier
In order to measure your iOS app campaigns via SKAN, your iOS app must be authenticated upon being registered with Airbridge. For more details, refer to this article.
The following Airbridge iOS SDKs are required to be able to measure app campaigns with SKAN.
1.14.3 and later: Supports SKAN 1.0 to SKAN 3.0. Required to set up the fine SKAN conversion values.
1.33.1 and later: Supports SKAN 1.0 to SKAN 4.0. Required to set up the fine and coarse SKAN conversion values.
Conversion value configuration is essential to measure the in-app events that occur after app installs. Refer to the following articles to learn how to configure the conversion values.
Attention
For Airbridge Apps registered after November 18, 2024, the SKAN 4.0 conversion value settings will be applied by default and cannot be changed.
Airbridge Apps with the SKAN 3.0 conversion value settings applied before November 18, 2024, will retain those settings. If you wish to switch to SKAN 4.0, contact your Airbridge CSM. If you don't have a designated CSM, contact the Airbridge Help Center.
Once you switch from SKAN 3.0 to SKAN 4.0, switching back to SKAN 3.0 is not possible.
Apple sends the attribution data via postbacks to ad channels. The ad channels forward the postbacks to Airbridge when SKAN integration with the ad channels is complete.
The ad channels below are integrated with Airbridge and forward SKAN postbacks to Airbridge. If you want to request SKAN integration for ad channels other than the ones listed below, contact us at integration@ab180.co.
Meta ads and Google Ads
Meta ads and Google Ads require additional SKAN integration setup processes before running iOS app campaigns. For more details on the SKAN integration process, refer to the following articles.
Once Meta ads and Google Ads receive SKAN postbacks, they send the conversion values to Airbridge as aggregated numbers. Data discrepancies may arise between Airbridge and the ad channels due to the difference in when the SKAN data is aggregated.
Other ad channels
The following ad channels forward the SKAN postbacks to Airbridge as soon as they receive them. Airbridge performs the aggregation and decoding of the conversion values. The decoded SKAN data is made available in the Actuals and Trend Reports.
TikTok For Business (tiktok)
Moloco (moloco)
Unity Ads (unityads)
Mintegral (mintegral)
Appier (appier)
Inmobi (inmobi)
Refer to the table below for the SKAN postback parameters that ad channels support. Due to the privacy threshold and postback tier policy, the final conversion value may be sent as “null.”
The metrics and GroupBys you can use to view the relevant data are written in parentheses. Ad channels that don’t support SKAN 4.0 support SKAN 3.0 and earlier.
Supports SKAN 4.0 |
(SKAN Version) |
(SKAN Assisted Installs) |
(SKAN Re-installs) |
(Is View-through) |
(SKAN Postaback Sequence Index) |
(SKAN Source Identifier Digit) |
|
|
|
|
| |
---|---|---|---|---|---|---|---|---|---|---|---|---|
Meta ads | X | X | X | X | O | X | X | O | O | O | O | O |
Google Ads | O | X | O | O | O | O | X | O | O | O | O | O |
TikTok For Business | O | O | O | O | O | O | O | O | O | O | O | O |
Moloco | O | O | X | O | O | O | O | O | O | O | O | O |
Unity Ads | O | O | O | O | O | O | O | O | O | O | O | O |
Mintegral | O | O | X | O | O | O | O | O | O | O | O | O |
Appier | O | O | O | O | O | O | O | O | O | O | O | O |
Inmobi | X | O | X | O | O | X | X | O | O | O | O | O |
Refer to the table below for the additional parameters that ad channels support.
Only campaign-level and ad group-level data can be received. The GroupBys you can use to view the relevant data are written in parentheses.
|
(Campaign) |
(Campaign ID) |
(Ad Group) |
(Ad Group ID) |
---|---|---|---|---|
Meta ads | O | O | X | X |
Google Ads | O | O | X | X |
TikTok For Business | O | O | O | O |
Moloco | O | O | X | X |
Unity Ads | O | O | X | X |
Mintegral | O | O | X | X |
Appier | O | X | X | X |
Inmobi | O | O | X | X |
Was this page helpful?