Working within Apple’s App Tracking Transparency (ATT) framework
Apple’s upcoming App Tracking Transparency (ATT) policy will require developers to ask for permission when they use certain information from other companies’ apps and websites for advertising purposes, even if they already have user consent. These changes will impact iOS App campaigns, so we’re sharing best practices with ATT in mind.
- Review Apple’s documentation and applicable laws and regulations. If the ATT framework is right for your app, you may decide to create and display a warm-up, or explainer, screen prior to asking for consent with the ATT consent prompt. The explainer screen allows you to give users more context on how your app uses information for advertising purposes. Implementing the custom explainer screen may improve performance for your iOS App campaigns. Learn more about creating and displaying an explainer screen by using the Firebase SDK
- Closely monitor the performance of all of your iOS App campaigns. If you ran iOS App campaigns for installs prior to the iOS 14 changes, you may see fluctuations or drops in performance as a result of the changes. For App campaigns for engagement, you will see a significant decrease in reach. Make applicable adjustments to budgets and bidding as needed to ensure that you get the most out of your App campaigns.
- Use the latest version of the Google Analytics for Firebase SDK. The SDK automatically integrates with SKAdNetwork, Apple’s framework for install conversion measurement that adheres to the new privacy measures. Using Google Analytics for Firebase automatically registers your apps for SKAdNetwork attribution so that you can measure “first open” conversions.
- Consolidate your iOS App campaigns for installs to run 8 or fewer campaigns. This will ensure optimal campaign performance while adhering to SKAdNetwork campaign limitations.
- Use target cost per install (tCPI) and target cost per acquisition (tCPA) instead of target return on ad spend (tROAS) bidding to ensure optimal performance.
- Once Apple’s ATT policies go into effect on April 26, 2021, you'll soon be able to view reporting data for SKAdNetwork (SKAN) by following the instructions below:
- Sign into your Google Ads account.
- Click Campaigns in the page menu.
- Click the Reports icon in the campaigns navigation menu.
- Click Other.
- Click SKAN conversions.
Note: There are several nuances in the way SKAdNetwork functions today that impact reporting for Google App campaigns on iOS. We’re working with the industry to give Apple feedback on how to further improve SKAdNetwork so advertisers can measure their campaign results accurately on iOS 14, including features like web-to-app attribution, video traffic, multi-touch attribution, custom conversion windows, and how to account for reinstalls.
Conversion reporting for your App campaigns will include modeled conversions for all channels to reflect conversions that may not be observed due to the ATT framework
- If you’re an ads publisher, visit the AdMob Help Center to learn ways you can minimize impact to ads revenue as a result of Apple’s new privacy measures.
General best practices
- Set up your iOS App campaigns around your advertising goals for optimal focus and performance.
- Take a focused approach to bidding based on your conversion goal, for example, app installs or in-app activity. Learn more about bidding for App campaigns
- Follow creative asset best practices.
- Track first opens, in-app purchases, or custom events by importing events from Firebase or by linking your Google Ads account with a third-party analytics tool.
- Use Universal Links for iOS to send mobile device users directly to relevant pages in your app. Learn more about deep links
- Adjust your bid and budget based on campaign performance. Learn more about evaluating performance based on your goal