iOS App Attribution with SKAN When IDFA Isn't Collected
Airbridge measures supported app-to-app campaigns with SKAN without IDFA, and explains postback delays, reporting gaps and SDK requirements.

Key Takeaway
- Airbridge can measure app-to-app campaigns with SKAN when the ad channel supports SKAN, whether a user allows or denies data tracking.
- Expect SKAN 3.0 postbacks to take up to 48 hours after app installation to appear in your reports.
- Installing the Airbridge SDK is required to fully use core features like performance tracking and event collection.
Updated: November 16, 2026
Running paid acquisition on iOS without collecting the Identifier for Advertisers (IDFA) often feels like watching ad budgets vanish into a black box. You launch campaigns for your subscription app, test creatives, and then stare at dashboards trying to figure out which channel actually drove trials and subscribers. In Airbridge, you can measure app-to-app campaigns with SKAN as long as the ad channel supports SKAN, regardless of whether a user allows or denies data tracking. Before you wire up your stack, you need to know the reporting delays and SDK requirements that come with Apple's framework so you do not mistake normal system behavior for a broken integration.
SKAN 3.0 Reporting Behavior
When you check campaign performance the morning after launching a new iOS ad set, SKAN 3.0 postbacks are sent 24–48 hours after app installation, and the data can take up to 48 hours to appear in Airbridge. In SKAdNetwork version 3, the app finalizes a conversion value once a 24-hour timer expires after the last conversion-value update, and the device then sends the postback after a random 0–24-hour delay, making the earliest postback 24–48 hours after the final conversion value is set Receiving postbacks in multiple conversion windows. Once the measurement window closes, SKAN 3.0 starts a random postback timer of 0–24 hours and sends the postback at a random time during that window.
Daily install volume thresholds also affect what shows up in your dashboard. To maintain user privacy and ensure crowd anonymity, the device may limit the data that SKAdNetwork sends in postbacks. If your daily installs do not reach a certain threshold, you may see install counts that match your internal data while post-install event counts look lower than your internal figures.
| Reporting Aspect | SKAN 3.0 Behavior and Dashboard Impact |
|---|---|
| Channel Aggregation | Facebook and Google Ads SKAN data may be delayed because Facebook and Google Ads aggregate postbacks and pass them to Airbridge daily at a fixed time. |
| Low Daily Install Volume | When daily installs do not reach a certain threshold, SKAN sends postbacks with null conversion values. |
| Report Discrepancies | When SKAN postbacks contain null conversion values, SKAN install counts match internal-data install counts, but SKAN post-install event counts are lower than internal-data post-install event counts; this can create a discrepancy between first-party data and SKAN data in Airbridge reports. |
| SKAN 4.0 Fine Value Parity | For conversion-value settings in the Airbridge dashboard, SKAN 3.0 conversion values are the fine conversion values in SKAN 4.0, and configuring SKAN 4.0 fine conversion values is the same as configuring SKAN 3.0 conversion values. |
Measuring Without IDFA
If a user does not allow tracking on iOS, IDFA cannot be collected and device-level attribution is unavailable. That restriction does not leave you completely blind on paid social or search if you are running app-to-app campaigns on supported networks. Airbridge Core Plan includes ad network attribution for four major channels, along with reporting for subscription revenue and cohorts, plus up to two third-party integrations such as Amplitude or GA4:
- Ad network attribution for Google, Meta, Apple Ads, and TikTok
- Revenue, funnel, retention, and cohort reports
- Cost and ad spend aggregation, subscription revenue aggregation, and Predictive LTV
Getting SKAN attribution to work across your campaigns requires more than flipping a toggle in one dashboard. Full SKAN implementation for iOS app campaign measurement requires readiness across four places: the ad channels, the app or website where ads are displayed, the iOS app itself, and Airbridge. Specifically, SKAN integration between Airbridge and your ad channels must be complete.
Keep your campaign flow in mind when planning your acquisition funnel. If you run web-to-app campaigns, Airbridge cannot measure web-to-app campaigns using SKAN. You will need to factor this limitation into how you evaluate app-to-app campaigns versus web-first acquisition paths.
SDK and App Setup Requirements
Founders evaluating measurement tools often ask whether they can get full attribution and deep linking without putting another SDK into their app binary. Airbridge SDK installation is required to fully use core features, including performance tracking, deep link configuration, and event collection. Deferred deep links are also configured in the SDK.
For small teams shipping code without a dedicated data engineering department, the Airbridge Core Plan SDK is installed directly by developers on a self-serve basis to record predefined events and verify settings. GMAT channel integrations and 25 standard events are pre-configured, with subscription events limited to Start Trial, Subscribe, and Unsubscribe. Whether you build natively or use a cross-platform framework, documented SDK paths for Core include:
- iOS and Android
- React Native, Flutter, and Expo
- Unity
Once the SDK is in your codebase, preparing your iOS app for SKAN measurement involves a few concrete steps in the dashboard:
- Update the Airbridge SDK to the required version.
- Authenticate your iOS app in the Airbridge dashboard under Settings > App Settings > App Auth.
- Map your app events and event properties to conversion values and configure them in the Airbridge dashboard under Management > SKAN Conversion Value.
How your conversion value settings behave in the dashboard depends on when you registered your app. Airbridge Apps registered after November 18, 2024 have SKAN 4.0 conversion value settings applied by default, and those settings cannot be changed. Airbridge Apps that had SKAN 3.0 conversion value settings applied before November 18, 2024 retain those settings.
FAQS
FAQ
Our app does not collect IDFA on iOS and we want to know if we need an SDK. What does Airbridge require and measure in this setup?
To fully use core features such as performance tracking, deep link configuration, and event collection, installing the Airbridge SDK is required. When a user does not allow tracking on iOS, IDFA cannot be collected and device-level attribution is unavailable, but Airbridge can still measure app-to-app campaigns with SKAN when the ad channel supports SKAN.
Can we measure web-to-app campaigns on iOS through SKAN?
No, Airbridge cannot measure web-to-app campaigns using SKAN. SKAN measurement in Airbridge applies to app-to-app campaigns when the ad channel supports SKAN.
Why do our SKAN install numbers match internal data while post-install events look lower?
When daily installs do not reach a certain threshold, SKAN sends postbacks with null conversion values. When postbacks contain null conversion values, SKAN install counts match internal-data install counts, but SKAN post-install event counts are lower than internal-data post-install event counts, which can create a discrepancy between first-party data and SKAN data in Airbridge reports.
Related reading
Measure iOS ads Today
Install the SDK and map conversion values to measure SKAN campaigns.


