In June 2020, Apple announced an update requiring apps to ask users for permission to access Apple's identifier for advertisers (IDFA) through a prompt called App Tracking Transparency (ATT) framework. We are sharing our recommendations for how you can update your app and help protect your ad revenue.
Keep your Google Mobile Ads (GMA) SDK up to date
We encourage you to always keep your GMA SDK up to date in order to take advantage of the latest features and functionality. We regularly release new updates and features to improve performance. Install the latest Google Mobile Ads SDK for iOS (version 7.64 or later).
About SDK instance ID
With the latest versions of the GMA SDK, a rotating SDK instance ID is automatically generated for each app to ensure effective delivery, display and integrity of ads. SDK instance ID is unique for your apps and helps maximise your apps' ad performance.
Decide whether Apple's ATT prompt is right for your app
When employing the ATT framework, we recommend that you pay close attention to the wording in your content and run tests to find what works best for your app.
Some developers may choose to show an explainer message that appears to users immediately before the ATT prompt with details about how user data is used and how users can opt in to personalised ads. If you choose to show an explainer message, you can use Privacy & messaging to manage your ATT permission and create an explainer message and/or EU user consent message that your users see just beforehand. Learn more about IDFA messages in Privacy & messaging.
Please note that, for users in the European Economic Area along with the UK, Google's EU user consent policy continues to apply and should be taken into account in designing any message that precedes the ATT alert.
Set up mediation groups based on IDFA availability
For iOS apps, you can now create distinct mediation groups for ad requests with and without an Identifier for Advertisers (IDFA).
When you create a new mediation group or edit an existing mediation group, you can use the IDFA availability parameter to target ad requests based on the availability of the IDFA. Having separate waterfalls can help you test and optimise the performance of ad requests with and without IDFA.
Note: For all mediation groups, we recommend that you use ad network optimisation to dynamically adjust your waterfalls based on performance.
If you use bidding, you should continue using bidding. Bidding helps ensure that your impressions get the highest revenue for both segments of traffic (with and without IDFA) without having to manage separate waterfalls.
Use Google optimized floors
If you're using a third-party mediation platform, you can set your ad units to have a Google optimised eCPM floor. This means that Google dynamically sets your floors based on your users' geographic locations, ad unit's traffic and historical data.
With the changes around privacy on iOS, you may experience eCPM fluctuations. Having Google manage your eCPM floors can help limit the time spent manually adjusting eCPM floors.
Configure Apple's SKAdNetwork
Advertisers will be using Apple’s SKAdNetwork to measure the performance of their ad campaigns and the value that they get from advertising in your app. In order for advertisers to identify your app as a valuable source of their ads traffic, you will need to configure SKAdNetwork with Google’s network key. Learn more about configuring the SKAdNetwork.
Safeguard your iOS advertising campaigns
If you also advertise with Google App campaigns, you can learn more about how to prepare for ATT enforcement.