iOS 17.4 Bug May Lead to Decreased ATT Opt-In Rates

Jeff Richardson — Fri, 12 Apr 2024 17:00:26 +0000

Bug fix included in iOS 17.5 beta

During recent testing, our team encountered a critical issue affecting app performance on iOS devices running versions 17.4.0 and 17.4.1. The issue is related to Apple’s App Tracking Transparency (ATT) framework and opt-in status reporting.

Here’s what you need to know:

Apple is aware of the bug and included a fix in iOS 17.5 beta

Apple is aware of the issue, and it appears they included a fix in iOS 17.5 beta, released on April 4. The full production release of iOS 17.5 is expected in late April or early May.

We will update this blog post once we receive any further confirmation from Apple.

What does the bug do?

The bug causes the ATT framework to prematurely return a “denied” status, irrespective of a user’s eventual response to the ATT prompt. This means that even if a user chooses Allow Tracking, the ATT status provided to the app and its SDKs may still be returned as though they selected Ask App Not to Track.

How does this bug impact you?

If your app is not prompting users for consent to track via the ATT framework, then this bug will not affect your iOS app.

If your app is prompting users for consent to track via the ATT framework, then the inaccurate reporting of ATT status may cause a drop in your ATT opt-in rates for users on iOS 17.4 and the corresponding collection of the identifier for advertisers (IDFA). In turn, this may reduce the volume of IDFA-attributable conversions as well as those matched via other consented attribution methods. We recommend monitoring your iOS attribution reports to gauge any impact of the bug on paid campaign performance and coordinating with your media partners on any contingency plans.

IMPORTANT
SKAdNetwork (SKAN) attribution and reporting are not impacted.

Quantifying the impact

How much has this bug affected ATT opt-in rates among apps that prompt?

Prior to version 17.4.0, we observed that the overall average ATT opt-in rate was around 45%. Isolating traffic running on iOS 17.4.0 and 17.4.1, we observe an average ATT opt-in rate of approximately 25%. These opt-in rates will vary depending on app category and region.

Stay tuned for updates

Be sure to subscribe to our newsletter to be the first to learn about new updates.

If you have specific questions or need help reviewing your ATT opt-in rates in analytics, please contact your client success manager or email Support@Kochava.com. Our team is here to support you and help minimize disruption to your app’s performance.

The post iOS 17.4 Bug May Lead to Decreased ATT Opt-In Rates appeared first on Kochava.

Apple Privacy Manifest Prep Checklist

Jeff Richardson — Mon, 08 Apr 2024 18:05:03 +0000

Steps to take with your next iOS app update after May 1, 2024

Per a February 29 post from Apple, beginning May 1, 2024, developers submitting an app update that leverages commonly used third-party software development kits (SDKs) identified by Apple will be required to update versions of these SDKs to include a privacy manifest and signature.

While the Kochava SDK has not been added to the list of SDKs requiring privacy manifests starting May 1, we recommend that our clients be aware of and start planning for what we believe will become a requirement for all mobile measurement partner (MMP) SDKs in the near future.

Please consult this helpful checklist:

#1 Understand the Impacts of Privacy Manifests

The upcoming change to Apple’s requirements is important for developers utilizing any SDKs, including Kochava iOS SDKs. The introduction of privacy manifests marks a significant shift in how developers manage third-party SDKs within their iOS apps. The core takeaway is the accountability placed on developers for all code within their apps, emphasizing the importance of understanding and managing data collection practices. Privacy manifests empower developers to retain SDK functionality while adhering to privacy standards—requiring user consent for data tracking via the App Tracking Transparency (ATT) framework.

Please find a prior blog post here that provides additional details around the launch of Apple’s privacy manifests.

#2 Pay Special Attention to Tracking Domains

A critical aspect of implementing privacy manifests involves declaring tracking domains. This process entails identifying and declaring any domains that track users through data collected by the app. When a domain is declared, any traffic from the app to the domain is blocked if the user has not been prompted and opted in through the ATT framework. As such, incorrect implementation could unintentionally restrict essential functionalities. For this reason, it’s crucial to work closely with Kochava, and any of your other SDK providers, to ensure correct implementation.

#3 Using a Kochava SDK? Here’s What You Need to Know

Our team has released iOS SDK version 8, which adds a specific tracking module to fully support privacy manifests and the required SDK signature. Tracking domains are automatically built into v8’s privacy manifest file, meaning that developers do not have to declare these domains manually.

Please consult this support documentation, which covers the process for migrating to iOS SDK version 8.

Do you need to upgrade to iOS SDK version 8?

Yes

If you’re prompting iOS users through the ATT framework to gather the IDFA and permission to track, you need to upgrade to iOS SDK version 8.

Apple requires that if you’re gathering the IDFA via an SDK, there must be a privacy manifest with at least one blocked domain, which is included in our optional tracking module’s privacy manifest.

No

If you’re not prompting iOS users through the ATT framework to gather the IDFA and permission to track, you do not need to upgrade to iOS SDK version 8.

You can continue using prior iOS SDKs and relying on first-party measurement for owned media, the AdServices framework for Apple Search Ads, and SKAN for attribution of paid media with other third-party ad networks.

What happens if you choose the wrong path?
If you choose the incorrect path, Apple will simply reject your app submission, and you will know you need a privacy manifest. Your app will not suddenly be removed from the App Store. Contact your client success manager or Support@Kochava.com for guidance along the way.

Important

The rollout of Apple’s privacy manifests continues to evolve, and their list of SDKs is likely to change over time. Be sure to subscribe to our newsletter and keep in close touch with our support team to stay up to date on new developments that may require action on your part.

The post Apple Privacy Manifest Prep Checklist appeared first on Kochava.

Industry