User expectations for privacy continue to grow, and new policies have been introduced which change how consumer data is collected and used for advertising. To effectively adapt to these new platform standards, it’s important that you understand the iOS measurement solutions that are available to you.
On this page
Key measurement frameworks for iOS App campaigns
|

|
1. Understand key Google-supported iOS measurement frameworks

Multiple forms of measurement have emerged for iOS app install campaigns.
Note: iOS measurement in Google Ads will change in the future to align closer with ICM measurement in App Attribution Partners for apps with ICM and on-device measurement event data implemented.
- Google’s conversion modeling: Modeled conversions, which we report in your Google Ads interface, use Google AI to help you assess the event-level performance of your campaigns when a subset of conversions can’t be directly linked to ad interactions. Learn more About modeled online conversions.
- Apple’s SKAdNetwork: SKAdNetwork, also known as SKAN, helps app advertisers measure their ad activity, such as impressions, clicks, and app installs, on an aggregated level. SKAdNetwork has become increasingly important to some app advertisers in assessing their iOS campaign performance across multiple ad networks.
Note: At WWDC in 2024, Apple introduced AdAttributionKit (AAK), a measurement framework that builds upon the core principles of SKAdNetwork. Google does not currently support AAK for attribution at this time.
|
|

|
2. Get started with SKAdNetwork for install and in-app event measurement

Many app advertisers have adopted a SKAdNetwork-oriented approach for both installs and in-app event measurement.
Install measurement
If you’re measuring installs with SKAdNetwork, you'll be able to view reporting data by following the instructions below:
- Go to Campaigns within the Campaigns menu
.
- Select the Reports icon
at the top of the page.
- Select Other.
- Select SKAN conversions.
|
|

|
3. Implement best practices for iOS App campaign measurement and optimization

For better app measurement:
- Implement on-device measurement: Implement on-device conversion measurement using event data to boost observable conversions available for enhanced iOS campaign optimization and reporting. It works without any user-identifying information ever leaving a user’s device or being disclosed to external parties, including Google. If your app has significant user sign-in and collects email and phone number data, we recommend you additionally implement our second variant of this solution which uses first-party data. Learn more about Google’s on-device measurement solutions.
- Activate integrated conversion measurement to get more real-time, comprehensive, and accurate cross-channel attribution in your third-party App Attribution Partner interfaces. Enable this solution by implementing on-device conversion measurement using event data and updating to the latest version of your third-party App Attribution Partner SDK.
- Evaluate if it makes sense to set up your app within the SKAdNetwork framework.
- For install measurement, integrate your app with SKAdNetwork for installs. Our Google Analytics solution helps you integrate and register your app for SKAdNetwork attribution so that you can measure “first open” conversions. You can also configure SKAdNetwork install measurement with another measurement SDK, like an App Attribution Partner, or manually.
- For post-install event measurement, set up your conversion value schema. You can do this through Google Analytics, a third-party App Attribution Partner, or the Google Ads API directly. When setting up your schema, ensure that it’s inclusive of the biddable events you plan on optimizing your App campaigns for.
- Consolidate your iOS App campaigns for install to run 8 or fewer campaigns. This will ensure optimal performance and support accurate SKAdNetwork campaign reporting, as more campaigns may obscure measurement within SKAdNetwork. Note that this limitation will be removed in the future for apps with on-device measurement event data.
- App Tracking Transparency: Review Apple’s documentation and evaluate if implementing the ATT consent prompt is right for your app. You may also decide to create and display a warm-up, or explainer, screen before asking for consent with the ATT prompt. The explainer screen allows you to give users more context on how your app uses information for advertising purposes. Users who accept the prompt will increase your observed conversions, improving conversion modeling and campaign optimization. Learn more about creating and displaying an explainer screen by using the Google Analytics for Firebase SDK.
Best practices
Review the table below for an overview out iOS best practices.
| Best practice for iOS App campaigns |
Best practice / Requirements |
Resources to learn more |
|
Campaign consolidation
|
Consolidate to 8 or fewer iOS App campaigns.
Note: This limitation will be removed in the future for apps with on-device measurement event data.
|
Best practices for iOS |
| App Tracking Transparency |
Consider implementing the AppTrackingTransparency (ATT) prompt and AdSupport Framework to collect consent and IDFA. |
|
| ODM first party data |
If app has a sign-in flow:
- Implement on-device measurement first party to provide deterministic ground truth.
|
Firebase: tutorial |
| ODM event data |
Include on-device measurement event data to provide deterministic ground truth. |
Using Firebase: Target capabilities with ODM Event Data
or
Using ODM Standalone SDK
Be aware of the compatible SDK versions.
|
| ICM implementation |
If using App Attribution Partners for iOS measurement:
- Implement Integrated Conversion Measurement (ICM) to integrate with AAPs for more accurate attribution.
|
|
| Firebase SDK |
If using Firebase iOS SDK, upgrade to v12.12.1+ to maximize performance benefits |
Firebase: iOS SDK release notes |
| On-device measurement considerations |
- For ODM benefits, events must be imported from a GA4F primary (Standard) property, not a sub-property.
- Avoid custom event names starting with reserved prefixes: "firebase_", "google_", or "ga_".
- ODM isn’t compatible with Firebase audience triggered events.
|
Google Ads: About ODM |
|
|

|
4. Apply general App campaign best practices

|
Note: This article will be updated to keep you informed on the latest iOS best practices. This article was last updated on August 19, 2026.
Related link