iOS 14.5+: From day one until now

iOS & Apple

Apple first announced the release of iOS 14 at its Worldwide Developers Conference (WWDC) in June 2020, and it's been almost three and a half years since its release to the public on September 16, 2020 From the initial announcement until the rollout of iOS 14.5 in April 2021, the mobile marketing industry was sent into overdrive and pushed to reassess the way it handles user privacy and its approach to the mobile advertising ecosystem in general.

At Adjust, we’ve remained at the forefront of these changes, working closely with Apple, our partners, and clients to make the transition as seamless as possible and to provide guidelines and solutions that serve the needs of marketers, developers, and advertisers.In the increasingly post device-ID space, mobile measurement partners (MMPs) are still essential to app. As we delve into the next-generation of attribution and analytics, the definition of ‘measurement’ and how we deliver value has simply evolved. It’s no longer just about a strict focus on attribution and deterministic data but a broader, cohesive analysis of aggregated data.

With the official release of SKAdNetwork 4.0 (SKAN 4) and iOS 16 in October of 2022, further change was brought to the space. The way SKAN works was significantly altered, leading the industry to once again reassess its approach to mobile marketing and measurement on iOS—something many businesses had only recently figured out. At Adjust, we’ve continued to test, engineer, and solve for the updates and changes, which is why we were first to market with our SKAN 4-ready SDK.

As with all things iOS, we are constantly reiterating our commitment to investing in next-generation solutions that align with the privacy-centric evolution of the market—moving away from solutions that focus on individual data points and towards optimizing insights for aggregated data. As part of this, we also launched Conversion Hub in 2022, our all-in-one solution for smart, easy, and effective conversion value mapping. Conversion Hub is also completely set up for leveraging of SKAN 4’s new features, including coarse conversion values and lockWindow.

Pivoting now to 2023, Apple indirectly announced SKAN 5 at its WWDC conference in June, demonstrating their continued commitment to investing in and developing SKAN as the attribution solution for campaigns run on iOS.

From understanding SKAdNetwork (SKAN) up until and including SKAN 4 and AppTrackingTransparency (ATT) to best practices for getting the opt-in, building and mapping conversion value setups, working with Adjust’s Conversion Hub, and creating marketing strategies that perform best in the post-IDFA world, there are a lot of topics and themes to cover.

The industry is becoming increasingly privacy-centric, in fact, Apple has also recently made significant changes to adapt its iOS, Safari, and App Store business models in-line with EU requirements under the Digital Markets Act.

Adjust wholeheartedly embraces these measures to ensure user privacy and data protection. In this guide, we put a lens on the changes from iOS 14.5+ to iOS 17 and beyond, the significance for the industry, and how Adjust is adapting to deliver value to clients. We examine the ins and outs of working with SKAN and provide a holistic breakdown to ensure that marketers are up to speed with everything they need to know.

What is iOS 14?

iOS 14 and the initial release: What changed?

Up until the release of iOS 14.5, Apple had allowed each device to have a unique and resettable identifier, which was accessible to all apps downloaded on that device. The option to limit ad measurement was available in the settings of an Apple device, but most users didn’t know, or didn’t bother. This ID, the identifier for advertisers (IDFA) could be used by marketers to measure clicks and compare them to installs, which MMPs were then able to attribute. Iterations of this, starting with the Unique Device Identifier (UDID) had been in place since 2008—the switch to the IDFA took place in 2012.

The mobile ecosystem has since developed and evolved, however, along with user knowledge of it. Concerns about data privacy and how data is accessed and managed was and is a growing theme among users (and legislators). This has led to regulations like the EU’s General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA), the Children's Online Privacy Protection Act (COPPA), the EU's recent Digital Markets Act and Digital Services Act, and more, all of which have brought in new rules about how data must be respected and processed in those jurisdictions.

While the app industry continued to thrive alongside these changes, Apple’s announcement at WWDC 2020 that access to the IDFA would be contingent on gaining user consent via a pop-up garnered a much more severe reaction from the mobile marketing industry. The impact has not been as catastrophic as some early predictions indicated, and ATT opt-in rates are actually continuing to climb. Despite user privacy having already been top-of-mind in the industry for some time, iOS 14's announcement, and eventual rollout, did cause a seismic shift in how we’re fundamentally able to approach attribution and measurement.

Important: Although ATT was initially announced in 2020, it wasn’t until the release of iOS 14.5 in April 2021 that it was actually enforced.

app tracking transparency opt-in

This change meant that attribution as it was understood for apps and app marketers would be significantly impacted and that the way they had been measuring user acquisition could no longer be guaranteed. Essentially, there are two attribution and ad measurement approaches that can now be leveraged on iOS: The ATT framework that manages access to the IDFA with user consent, and SKAN (starting with iOS 14.5’s SKAN 2.2). If consent is acquired, those users can be measured and attributed in the same way as before the iOS 14.5 rollout, but for those who don’t, working with SKAN is crucial, and requires a completely different mindset and approach to how we gather and process information about acquisition and in-app events.

Data privacy changes

What do these privacy changes mean for app marketers?

From an industry perspective, the data privacy changes spearheaded by iOS 14.5 represent an ongoing shift toward an ecosystem centered around user privacy. Apple states that privacy is a fundamental human right, and they design their products based on this principle. Adjust wholeheartedly supports this framework and is working together with Apple, our clients, our partners, and the industry at large to ensure complete user privacy and respect for people’s decisions regarding their data.

What this means for marketers, however, is a potential lack of precision and accuracy in user acquisition (UA), attribution, and campaign performance. This is simply because advertisers have less visibility into user level data and campaign metrics. UA with the IDFA relies on precise campaign data that gives marketers visibility over performance, empowering decisions around which channels to invest their budget in, and how to optimize performance. There are usually specific KPIs like Day 0/Day 1 retention, user LTV, ROI, and ROAS. Marketers working with this model often operate within thin margins regarding where they invest budgets, and how to scale may come down to a matter of a few percentage points.

Before SKAN 4, this level of insight was prevented simply because the aforementioned KPIs weren’t supported. This makes understanding which channels to focus on complex in an ecosystem where mobile performance marketing had previously made it relatively automated and straightforward, and instead pivots attention onto how essential strategically-minded UA managers are post-IDFA. UA has always been a central pillar in mobile marketing, but the user-privacy driven shakeup has meant that old ways of doing things needed to be completely revisited, and that remaining agile and flexible is more essential than ever. We can no longer solely rely on automation to shift the percentage points in our favor.

Advertisers who get high opt-in rates are still able to have a good understanding of their KPIs per campaign and can optimize efficiently, as all tools and means of measurement they’re familiar with can be leveraged. Also, the better your opt-in rates, the more data you have to work with to more comprehensively understand and strategize regarding aggregated SKAN data. On that note, we’re happy to report that consent rates are consistently climbing as marketers are able to communicate the benefits of opting-in.

The rest of the inventory that is tracked via SKAN 2+ makes things more complicated to measure and manage. Let’s take a look at how it impacted the three most common monetization models: in-app advertising, in-app purchases, and subscriptions.

  • In-app advertising

    There are two main types of ads, contextual and targeted. Contextual, or non-targeted ads, are less specific, while targeted ads are served to specific users — based on their information gathered via the IDFA. They’re more expensive, but they offer higher conversion rates, making them the more popular choice generally speaking. Naturally, on iOS 14.5+, if a user hasn’t opted in, their IDFA is not available, and they can’t be served targeted ads. This is why some users have noted seeing more ads since opting out. Many publishers are serving an increased number of ads to make up for revenue lost from lack of ability to serve targeted advertising.

  • In-app purchases & subscriptions

    Users pay for in-app goods or services in a wide variety of apps, such as when buying gold or coins in a gaming app, unlocking premium features in a health and fitness or productivity app, or signing up for a subscription to a service. Here, iOS 14.5+ doesn’t have a direct impact on revenue, but the lack of attribution for opted-out users makes it difficult for advertisers to measure the success of campaigns, or to understand where high LTV and top-performing users are coming from.

Despite the panic, the industry has clearly demonstrated that advertising on iOS is not going to stop. There will always be users to acquire. This is why we have built comprehensive support for ATT and SKAN, and we are happy to offer solutions that focus on campaign optimization, actionable metrics, and empowering our clients to continue to focus on growth while upholding the highest privacy standards.

Privacy and data protection are central to the mobile advertising industry, and Adjust recommends that advertisers pursue a holistic approach to acquisition, attribution, and measurement on iOS, leveraging the ATT framework to obtain as much user-level, consent-based data as possible to use in conjunction with aggregated SKAN data.

Katie Madding


The opt-in

App Tracking Transparency, user consent, and the opt-in

As we covered above, it's the lack of access to the IDFA that causes the headache when it comes to attribution and campaign measurement on iOS. Apple’s ATT is the framework that allows ad targeting and measurement once a user has opted-in or granted consent to tracking. The more users you have consenting, the bigger your pool of efficiently measurable, granular data will be. Moreover, these users can receive targeted advertising and the data can be used to inform and continually improve strategies for conversion values, predictive analytics, and analysis of SKAN data sets.

The most accurate data in a post-iOS 14 world starts with a robust opt-in strategy—prioritizing user consent is not the only pillar of success, but it is key. It not only minimizes disruption, it delivers significant competitive advantages. While the more users you have consented the better, even a relatively low opt-in rate or percentage of opted-in users can prove pivotal to success.

Put simply, with a higher opt-in rate, marketers are able to receive more data points, and it’s these data points that then inform the broader strategy for both opted-in and non opted-in/aggregated data sets. At least some opted-in data is invaluable for teams wanting to work with predictive KPIs like pLTV, which helps anticipate growth opportunities within aggregated collections of SKAdNetwork and consented user data. The more deterministic data insights that can be gained, the more robust the pLTV results will be.

Note that SKAN data includes all users, meaning those that opted-in to ATT will be duplicated in your SKAN set.

When working with our clients to help develop top opt-in strategies and flows and to incorporate optimizing for the opt-in as part of an overall UX strategy, there are a few top themes we identified. These are the variables that have the biggest impact on influencing a user’s response to an ATT pop-up.

  • Location: Pinpointing the precise moment to serve the opt-in request is the top factor to define. We’ve identified that it is usually best to display the prompt during the onboarding flow.
  • Messaging: Pre-permission prompts that cue the ATT framework prompt mean the Apple pop-up will feel more natural. Use 2-3 short sentences to emphasize the benefits of opting-in. Also, although the first sentence in the ATT prompt itself can’t be customized, we highly recommend adapting the second string. This is another opportunity to address any concerns about data privacy, and to highlight the benefits of opting in.
  • Size: Users typically respond to pre-permission prompts that are full screen, as opposed to modals. This is because the former offers a more seamless user experience, while the latter can feel like an interruption.
  • Button placement: The placement of your call-to-action (CTA) button is an easy lift. Buttons with simple text, placed next to each other horizontally, with the positive acceptance on the right hand side, yield the best results.
att opt-in example

We’re also happy to continually demonstrate that opt-in rates are slowly but steadily increasing overall. Around the initial rollout of iOS 14.5 the global average sat at around 24%, as of Q2 2023, this number had increased to 34%.

In addition to building a fully optimized opt-in strategy, it’s also crucial to define an overall UX strategy that the opt-in is simply part of, and to continually test. Once a UX approach regarding when, where, and how you prompt users to give consent is designed and integrated, the work isn’t quite done. That’s why we advocate for continued, rigorous testing, including A/B testing and randomized controlled experiments.

Attribution with SKAN 3

iOS 14.5+ and working with SKAdNetwork 3

For users who don’t opt-in, Apple’s SKAdNetwork, a combination of SDK functions and API calls, is the solution that marketers can turn to for attribution of app installs and reinstalls. Free for advertisers to use, Apple’s goal with SKAN is to provide basic, privacy-focused attribution, and it doesn’t require user consent because Apple designed it within their privacy guidelines.

The attribution information from SKAN is relayed from the device, to Apple, and then to ad networks, developers, and mobile measurement partners like Adjust. Clients can implement SKAN on their own, or with Adjust’s help. It’s important to note that even when integrated with Adjust, it’s Apple that performs the attribution in this scenario, while Adjust takes care of aggregating the data.

skadnetwork install

Up until SKAN 3, in a single postback, SKAN provided space for 6-bits of downstream metrics, a number between 0 and 63 (or between 000000 and 111111 in binary), with an initial 24-hour timer. Otherwise known as a conversion value (and named the fine grain conversion value on SKAN 4) this can be assigned to any value that can be expressed in binary, and it’s up to apps to decide which events they want to include.

Every time the conversion value is updated to a fresh six-bit code defined within the app (up until SKAN 3), the timer is extended by an additional 24 hours. Once this conversion value-window expires, a second 24-hour window is triggered for attribution. The idea behind this is to obfuscate the time of install, making it impossible to link event triggers to individual users. This data is then shared via SKAN 3 in the aggregate, with no granular, user-level data accessible.

Put a little more simply, conversion values are a number between 0-63, used for measuring up to six events using the bit logic. Each conversion value is linked to specific conditions, which can then be unpacked into meaningful KPIs for reporting.

To make the most of this system, advertisers and marketers on SKAN 3 need(ed) to work thoroughly within the first 24 hours, leveraging all data possible to paint a clear picture of user behavior, from which projections and segments can be identified. It’s not just about acquisition, it’s about understanding what user behaviors in that first 24-hour window can tell us about what they might do later. For many apps, this meant a complete strategic rewriting regarding events tracking as they worked to identify and predict later-stage events. For example, a Day 7 subscription event could be tied to an earlier event by calculating the likelihood via predictive analysis.

conversion value skan 3

How a conversion value strategy is set up is key to success on SKAN. We’ll get into how Adjust supports clients in understanding, building, and mapping conversion values (both event-based and value-based) below, and how marketers and developers can identify which solution is suitable for their app. SKAN 4 introduced a lot of changes to conversion values and measurement potential in general, which we explore in detail below.

iOS 15 updates

A few more changes with iOS 15

The huge changes to attribution and tracking of post-install events on iOS came with the announcement of iOS 14 and the release of iOS 14.5 and ATT. And while it was not nearly as industry-defining as its predecessor, iOS 15 (released in September 2021) presented a few key changes and further developments in Apple’s steps toward further user privacy.

As of release, copies of “winning” SKAN postbacks (the attribution call when an app install occurs) can also now be sent to developers, not only to ad networks. This change was welcomed by the industry and understood to be providing developers with more transparency over their data, giving access from install to post-install.

Private Relay was one of the most interesting announcements from a mobile advertising perspective. Designed to prevent the tracking of iOS users on Safari, Private Relay in its current form redirects all network traffic through its servers and hides the user IP address, meaning they can’t be tracked and that user profiles can’t be built. Some rumors indicated that Apple would switch Private Relay on by default from iOS 16 onward, meaning that all SDK traffic will be routed through it, a move that would further complicate the process of gaining insight into users and campaign performance. So far, however, this hasn’t happened. Also, with SKAN 4, Apple now offers web-to-app attribution for Safari users.

Mail Privacy Protection was also rolled out, a feature that allows Apple Mail users to hide their IP address and location, and to anonymize the tracking of email opens. If these options are toggled on, access to information like email opens is no longer available to marketers. Hide My Email is another privacy-related feature that allows users to mask their email with a generated one when completing any online form.

Aimed at helping to improve UA strategies and campaign performance, another interesting iOS 15 feature is Custom Product Pages and Product Page Optimization. Marketers and developers create custom pages on the app store that can be targeted and optimized for up to 35 individual user segments and then linked to relevant UA campaigns.

Deep dive: Mastering Apple's Custom Product Pages to level-up your ASA and ASO performance.


SKAN 4, iOS 16, and how it works now

Released in October 2022, SKAN 4 introduced a bunch of new features and options that changed the iOS measurement and attribution space considerably throughout 2023 and will continue to make a big impact as adoption increases in 2024. These updates provide a significant opportunity to ad networks and app developers but also come with new complexity and mean that strategies and setups for conversion values and SKAN campaigns need to be reassessed.

Our article on how to fully leverage SKAN 4’s new features provides a detailed look at the status quo. We also have an in depth guide on how to make the switch from SKAN 3 to SKAN 4 and an all-in-one ebook created in partnership with TikTok that explains how to master SKAN 4.

In short, the key SKAN 4 feature updates are as follows:

  • Three postbacks instead of one: This is the huge one for mobile marketers. Instead of one postback with a 24-hour measurement window, there are now three. Postback 1 covers a 0-2 day post-install measurement window (with a 24-48 hour postback timer), Postback 2 covers day 3-7, and Postback 3 covers day 8-35, both of which have 24-144 hour postback timers.
skan 4 postbacks
  • Conversion value grains and coarse conversion values: There are now two types of conversion values: fine grain (the familiar 0-63 values from SKAN 3) and coarse grain conversion values, which assign a user as low, medium, or high. Fine grain values can only be received in Postback 1, while coarse grain values can be received in any of the postbacks.
  • Crowd anonymity tiers: Thanks to the new tiers, it’s now possible that campaigns with lower volume might receive some attribution information/a coarse grain value, potentially minimizing the number of “null” conversion values received (which has been a persistent problem on SKAN 3). Installs assigned to tier 1, 2, or 3 crowd anonymity will receive all three postbacks (with varying degrees of granularity), while tier 0 will only receive Postback 1 with a bare minimum of information.
crowd anonymity tiers
  • Source identifier: Referred to as campaign ID on SKAN 3 and only representing 2 digits, SKAN 4 allows up to 4 digits and has renamed this to source ID.
  • lockWindow: This allows you to apply a lock, the lockWindow at any point in each of the measurement windows to determine when the random timer for the postback will start, potentially reducing the waiting time to receive it. See below, where the lock is applied in the second measurement window at around day 5, meaning the random timer will start then instead of at day 7. This does mean, however, that no data following the lock, within the same window will be measured.
skan 4 postback lockwindow
  • Web-to-app attribution: It’s now possible to attribute from Safari advertising that directs to App Store product pages.

While SKAN 4 has already been out for some time, industry-adoption is taking place at a slow but steady pace. There’s no time like the present to design and plan your strategy to fully leverage the new capabilities and ensure you're always making the most of your measurement capacity on iOS. SKAN 5 may have been teased, but it’s a long way down the road. For now, we recommend thinking about how you will assign coarse grain conversion values and how you can use them to gain later-stage signals that will help you build predictions for LTV and early-stage insights.

Sandra Johansson

Product Manager Next Generation Measurement

While SKAN 4 has already been out for some time, industry-adoption is taking place at a slow but steady pace. There’s no time like the present to design and plan your strategy to fully leverage the new capabilities and ensure you're always making the most of your measurement capacity on iOS. SKAN 5 may have been teased, but it’s a long way down the road. For now, we recommend thinking about how you will assign coarse grain conversion values and how you can use them to gain later-stage signals that will help you build predictions for LTV and early-stage insights.

iOS 17 & new requirements

iOS 17 and the latest changes for app developers

As with every major iOS update, iOS 17 introduced some new privacy-related features and functionalities for mobile marketers and developers to pay close attention to. Released on September 18, 2023 and with some features set for enforcement in Spring of 2024, the primary goal of iOS 17 is to further improve user privacy and the ease with which app developers can provide clarity on what they are collecting and why. Every update’s goal is to further align the iOS landscape with Apple’s ATT framework and vision for privacy on their platform.

The iOS 17 features relevant to highlight here are privacy manifests and their corresponding required reason APIs and updates to Privacy Nutrition Labels.

  • Privacy manifests: Files aimed at providing app developers with complete transparency into the data practices of third-party SDKs they work with, enabling them to accurately complete their Privacy Nutrition Labels. Apple’s Xcode combines all privacy manifests provided by the third parties the app works with and sends them in one easy-to-use PDF called the Privacy Report.
  • Privacy Nutrition Labels: An original iOS 14 feature, Privacy Nutrition Labels are available on the App Store listings of any app, and detail to users exactly what data the app collects and how it’s used. The idea is that the information is standardized and easy to understand, like a nutrition label on packaged food.
  • Required-reason APIs: To be included in the privacy manifests, this category of APIs aims to further enforce Apple’s ban on fingerprinting. Apps referencing, or working with third-parties referencing, any of the APIs are required to state an allowed reason in their privacy manifest. From iOS 17 onward, any new app or update to an existing app will be required to include these required reasons when uploading to App Store Connect.
  • Other updates: Within the privacy manifest, app developers are also required to add a ‘dictionary’ that explains the usage of specific categories of data they, or their integrated third parties collect. Apple also requires transparency around the use of external domains, and requires all new versions of third-party SDKs to be signed and verified by Apple.

For more information on how Adjust can help you with iOS 17 and all privacy-related concerns and changes, including adjustments required following the implementation of the Digital Markets Act, get in touch with your contact person or request a demo.


Adjust’s solutions: How we’re supporting these changes

Adjust’s goal in working with clients on iOS 14.5+ though to iOS 17 and beyond is to empower data-driven decision-making and campaign optimization. We want our clients to comprehensively understand and have confidence in their marketing strategies on SKAN and working on iOS in general, while remaining confident that all data-privacy requirements are being upheld. We enable our clients and partners to continue leveraging powerful device-level data, to extra the maximum insights possible from aggregated SKAN data, and to always remain completely data-compliant.

Within the Apple context, we achieve this via our privacy-centric iOS and SKAN measurement framework.

  • SKAN Toolkit: Our set of SKAdNetwork tools empower clients to transform their iOS strategies with an easy set-up, measurement, and insights. The all-in-one toolkit includes Conversion Hub for conversion value mapping on SKAN 3 and SKAN 4, SKAN Analytics for real-time reporting, SKAN Partners complete with the most integrations in the industry, and SKAN Ad Spend for up-to-date spend data. New features in the toolkit include KPI modeling and predictions.
  • ATT opt-in best practices: A solid iOS and SKAN strategy starts by optimizing for the highest possible ATT opt-in rate. Consented, first-party, device-level data is an invaluable tool for gaining clarity into the early signals that indicate LTV later in the user journey, and for gathering the data needed to feed the predictive models used to perform more accurate transformations on aggregated SKAN data sets. We help clients supercharge their approach to the opt-in by building it into their UX strategy and creating a pre-prompt that converts. In short, any model used for forecasting or projection is only as powerful and precise as the data you feed it. In short, device-level data is great but it is not essential.

For full SKAN 4 support, make sure you have our latest SDK (SDK 4.33.0, available here.) in your app. Our SDK has always been open-source for ultimate transparency.

Next generation measurement

Adjust’s solutions: Conversion Hub, SKAN 4, and beyond

As we’ve covered extensively in this guide, conversion value strategies that make the most of SKAN are essential for success on iOS. This is why we launched Conversion Hub in September 2022, our smart, easy-to-use, conversion value solution that empowers clients, via machine learning, to map and configure app-specific conversion value setups.

By gathering insights and working closely with clients and partners, we’re able to continually offer robust updates in-line with our mission to bring next-generation solutions that reflect industry needs to the market..

Conversion Hub is an in-house SKAN expert for clients of all sizes and is now fully updated to support all SKAN 4 features, including coarse conversion values and lockWindow.

It’s super easy to use and get started with for both SKAN 3 and SKAN 4 campaigns. For SKAN 3 and SKAN 4’s postback 1 (i.e. for fine values), you can choose between two modes, 63CVs and 6-bit.

Let’s take a quick look at Conversion Hub’s features and functionality

1. Conversion Hub’s fine conversion value modes:

  • 63 CVs mode: Makes use of all 63 possible conversion values by mapping a revenue range to each value.
  • 6-bit mode: Provides maximum transparency on post-install engagements and empowers user journey optimization. Up to six events can be chosen and mapped to the six bits available.
conversion value mapping

2. Conversion Hub’s setup flows:

  • Smart setup: Designed for marketing teams seeking inspiration and guidance on the conversion value model that will work best for their app, vertical, and business model. Let Adjust's machine-learning algorithm suggest ready-to-go conversion value mapping based on your monetization efforts and vertical-based insights.
  • Advanced setup: Perfect for experienced teams who already have a fine conversion value model in mind. The most customizability and granularity is enabled by setting up the 63 CVs or 6 bit mode within the advanced setup flow.

3. Conversion Hub for coarse conversion values and SKAN 4’s measurement windows 2 and 3.

  • Postback 1: Conversion values can be mapped to low, medium, or high and may be received if the crowd anonymity requirements for a fine value aren’t met. If you’ve selected 63 CV mapping for your fine values, Conversion Hub will recommend mapping the low value to 0, the medium value to 1-31 and the high value to 32-63, i.e. splitting the values from your 63 CV fine mapping into two buckets. If you’ve selected 6-bit mapping, the recommendation will be to map purchase intent signals to the coarse values, with the low value being reserved for the session. Note the difference between the use cases below:
skan 4 postback conversion value
  • Postbacks 2 & 3: For the second and third SKAN 4 postbacks, Conversion Hub walks you through the most effective ways to map your coarse values according to either revenue buckets or purchase signal logic. Essentially, you’ll want to determine the most impactful data you can extract from the 3-7 day window and the 8-35 day window, and how your monetization model intricacies can impact the most effective way to utilize the low, medium, and high values. Need more info? Download our extensive report.

SKAN 4 in Datascape

It’s one thing to have your conversion values intricately mapped for the most strategic and comprehensive iOS campaign measurement and optimization possible. It’s another to be able to unpack and analyze what you receive with precision. This is where the SKAN 4 Datascape dashboard comes in. You can modify the whole dashboard for comparisons, apps, channels, and any relevant dimensions. Features you can use include:

  • SKAN totals: The volume of installs, reinstalls, and postback windows reported that day.
  • Fine and coarse activity distribution: Of all values received in a certain time and across windows, which shares were fine and coarse?
  • User quality analysis: See funnel progression of coarse values side-by-side.
  • SKAN metrics trends: Compare channels, apps, campaigns, and ad groups.
  • SKAN performance analysis: Overall performance insights.


The changes brought about by Apple’s privacy updates and rollout of iOS 14.5+ have been industry defining, but they have not been as severe for user acquisition or attribution as many people expected. As an industry leader, we understand that iOS and Apple (as well as our entire ecosystem) are constantly evolving. We work hard to stay well-connected with our partners and clients so we can remain at the forefront of changes and developments.

From day one, our approach has been to ensure that we serve our clients with robust iOS and SKAdNetwork solutions, that we empower marketers to make data-driven decisions with confidence, and that we uphold the principles of user privacy and data transparency. This philosophy focuses on leveraging powerful aggregated data to enable campaign optimization at scale.

The future of measurement on iOS and beyond—Privacy Sandbox on Android is right around the corner—will have its basis in aggregated data. Solutions driven by machine learning, just as Conversion Hub is already demonstrating, are critical to strategic marketers that want to confidently drive growth on iOS.

We understand that privacy underpins our industry, and as innovation progresses and evolves, so too will the specifics and technical requirements of user privacy. We place the best interests of our users and our customers at the center of the products and solutions that we develop, and will continue to do so as we optimize for SKAN 4, iOS 17+, and to SKAN 5 and beyond.

Now is the time to be fully diving into SKAN 4, strategically mapping coarse conversion values, and taking the first steps to determine how you'll maximize insights to predict LTV. Work with us as we leverage SKAN 4’s capabilities and tackle all privacy changes with cutting edge next-generation technologies and solutions. As adoption picks up pace, now is the perfect time to test. Learn more about what we’re calling the 4.0 milestones of SKAN 4.0 here.

To find out more about meausurement and attribution on iOS, to keep up-to-date with the latest information and developments, or to receive advice tailored to your specific app or business needs, you can request a demo, see our iOS & SKAN Solutions, or check out all the latest content.

Want to get the latest from Adjust?

Trusted by over 165,000 apps worldwide