Blog The design do’s and don’ts for getting t...

The design do’s and don’ts for getting the user opt-in on iOS 14.5+

Since Apple’s announcement of App Tracking Transparency (ATT) in 2020 through to the eventual rollout of iOS 14.5 in April of 2021 and beyond, we’ve been working diligently with clients worldwide to create solutions that equip marketers and developers with the tools needed to navigate these changes. From understanding how to best embrace the ATT framework to aiding in user testing, we’ve worked together to chart the path forward and establish a new status quo. Throughout this process, we’ve learnt a lot about opt-in rates, how to improve them, and what to avoid.

In this post, we’re sharing our critical learnings from working with clients and partners to offer you a crash course into the do’s and don’ts of leveraging design to improve your opt-in rates. For the latest on working with SKAdNetwork, developing conversion value schemas, and succeeding on iOS post-IDFA holistically, check out our playbook created in partnership with TikTok: iOS 14.5+ Success made simple, out soon.

For now, let’s get into the UX side of things—and kick off with what not to do:

Beware of dark patterns

London-based UX Designer, Harry Brignull, coined the term dark patterns to define instances where designers use their understanding of human behavior to influence end-user decisions. More specifically, they use design psychology to subconsciously coerce these users into doing things that may not be in their best interest. Types of dark patterns to influence user behavior include:

dark patterns

It’s important to note that the utilization of dark patterns is not always intentional, and many companies are making a conscious effort to avoid them. When experimenting with your ATT implementation, you should do your best to identify and avoid the use of these patterns. If you would like to dive deeper into dark patterns, we encourage you to check out this research paper on the topic.

In some conversations we’ve had with app developers, a few have reported that their app was rejected from the App Store before they could begin testing their ATT implementation. Based on their feedback, we’ve collected three patterns that have resulted in App Store rejection thus far:


In the context of dark patterns, nagging is a repeated intrusion where the end-user is interrupted one or more times by another task not directly related to the one they are focusing on.

nagging marketing

One developer made use of a pre-permission prompt before triggering the ATT consent pop-up. If a user declined to consent to the ATT popup, the app would trigger a custom prompt again, either later in the same session or a subsequent session, with a deep link that leads into the end user’s privacy settings. Once there, users would be able to change their previous response to the IDFA pop-up. Another developer informed us that their app was similarly rejected for repeating the pop-up after the end user’s decision was made.

In response to their rejections, Apple viewed these implementations as “nagging” and responded:

"The permission request process on iOS is designed to give users control of their personal information. It is important to respect the user's decisions about how they want their data used. If they decide to not grant permission to your app, they should not be prompted to change their mind or be forced to reject the request multiple times."


Sneaking is defined as an attempt to hide, disguise, or delay divulging information relevant to the user. Sneaking often occurs in order to make the user perform an action they may have objected to if they knew of it.

sneaking marketing

Another app saw itself rejected after triggering the ATT pop-up right after the user agreed to the main consent GDPR banner. Within the context of this proximity and timing, Apple believed that this specific positioning would influence the user’s decision to opt-in to the ATT.

Interface interference

Interface interference is defined as any manipulation of the user interface that privileges specific actions over others, thereby confusing the user or limiting discoverability of important action possibilities.

interface interference

In this instance, the app developer triggered their pre-permission prompt and displayed visual queues alongside it that may subconsciously influence the end user. By positioning a thumbs up emoji near the ‘allow’ button, it was seen as interference when it came to the end-user making their own, unbiased, choice to consent to tracking.

Additionally, the pre-permission prompt should not act as a consent prompt on its own. While this was not the actual IDFA pop-up, Apple maintains that pre-prompts should serve only to educate the end user about their decision and not influence the action they take.

In the above instances, the app publishers with whom we were in contact were all able to correct the highlighted issues and get back into the store. Now that we know what steps to consciously avoid, let’s dive into the designs that have yielded more favorable results.

The view ahead

Whether you have already conducted multiple tests or are just getting started now, it’s never too late to devise a brand new opt-in strategy or A/B test and optimize an existing one. We encourage all app developers to perform tests to help benchmark their own user performance. However, if you don’t have the time or resources for this, you can still utilize the trends and learnings we’ve summarized here. Although there is no way to guarantee attaining a certain opt-in rate, we will continue to support you with our insights and best practices.

To stay updated with all of the latest news and learnings for all things iOS 14.5+, be sure to check our blog regularly. If you’re interested in having a 1:1 discussion with our UX experts or to request a demo for how we can support your business’ success on iOS with our next-generation solutions, take a look at our iOS and SKAN Solutions.

Be the first to know. Subscribe for monthly app insights.