Your must-have Publisher’s Checklist to prepare for post-IDFA

We are moments away from the post-IDFA era. Apple’s AppTrackingTransparency (ATT) framework is already enforced on Beta users, and with the imminent privacy changes fast approaching, the mobile app ecosystem is gearing up to be as prepared as possible.

 

How can publishers best prepare? Follow this checklist of recommended actions to ensure a successful transition to a privacy-friendly ecosystem.

 

Start here:

✔ Update SKAdNetwork IDs on your info.plist today

Ensuring proper implementation of SKAdNetwork requirements will help you maximize revenue on IDFA-less inventory. Fyber released a SKAdNetwork Plist Generator (available in our development portal) to easily and effortlessly add the SKAdNetwork IDs to your info.plist files. This tool is available for any app developer – whether you’re a client of Fyber or not. The tool is built to simplify the process of creating the content for your info.plist file by pulling the relevant SKAdNetwork ID’s that you need to include in your project. So far, 52% of our publishers have adopted the full SKAdNetwork IDs for Fyber’s Marketplace in their info.plist – don’t wait until it’s too late.

 

Quick tip: Make sure you implement all network_ids from Fyber’s recommended list, available in JSON and XML format.

 
✔ Ensure all SKAdNetwork IDs are in lowercase on your plist

According to Apple’s specs, you must lowercase the ad network identifier string for installs to be tracked on your app. This is a critical step for all publishers, as any SKAdNetwork IDs with uppercase letters will fail. 

 
Update your SDKs

Double-check that you have updated to the latest version of your SDKs that support the SKAdNetwork API. Updating to the latest versions provides you access to the newest features, data, and improved stability – all contributing to helping you maximize revenue. Keep in mind that Marketplace SDK 7.7.1 is the minimum SDK version required for SKAdNetwork 2.0 and Xcode 12 to be supported. If you’ve been keeping up with our latest announcements, then you’ll know that we recently ramped up our contextual targeting parameters. We recommend updating to Marketplace SDK 7.8 for these additional contextual parameters capabilities and improved infrastructure. For the latest updates, check out our Marketplace Android and iOS changelogs. It’s not just critical to update now, but to continue to update in the post-IDFA era when users might choose to toggle their privacy settings or switch IDs. 

 
✔ Release your new app version as soon as possible

Don’t wait until the last minute – release your new app version with the newest SKAdNetwork IDs from Fyber on your plist to allow users to update to your latest app version. Implementing the info.plist in advance would enable you to work with your demand partners in order to test that postbacks are being fired appropriately from their app well ahead of the official enforcement by Apple.

 This will allow users to download the latest version of your app and ensure a smooth transition on all sides. 

 
✔ Talk to us, we’re here to help

At Fyber, we’re here to support you. Solutions such as contextual targeting parameters and Fyber’s DSP test app are available to help facilitate the transition to a post-IDFA era. Most importantly, testing is crucial to maximize preparations – work with your monetization partners to ensure demand partners and MMPs receive your postbacks. We will continue to update information about Fyber’s recommendations and solutions as new information becomes available.

 

Talk to your Fyber Account Manager

in case you have any further questions. 

 

Read these next

Contact Us










    By sharing your information you are agreeing to receive communications in regards to any questions or requests submitted on this form. Fyber will keep your information solely for internal tracking purposes and will not use this information for any other purpose. You may request to delete the information provided at any time.

    If you send us a message by clicking the "Send" button, we use a recaptcha service provided by Google LLC to check whether the message was sent by a natural person or a computer program ("bot") in order to ensure that only valid user requests are forwarded to us. Google LLC processes personal information from your browser, such as your browser settings and your click behavior on this screen. Please refer to the Privacy Policy for further information on data processing procedures of our third-party services.