Try searching for
The exciting and much-anticipated release of SKAN 4.0 not only brings a lot of new features with it, it also brings a lot of options for both ad networks and app developers. With each version update, SKAN brings more and more value, but also becomes increasingly complex; user acquisition and SKAN strategy are the name of the game, and will set the savvy iOS developers apart from the rest.
Before we start talking about strategy, let’s first review what the SKAN 4.0 changes are all about. There are 4 categories for which SKAN 4.0 changes fall into:
In SKAN 4.0, Apple introduces up to 3 (!) postbacks per user that work in the following order:
When looking at the first postback with regards to LTV measurement, there are two main features:
The introduction of a second postback is great news: You can now measure user activity for day 3 to day 7. The three disclaimers to the second postbacks are:
The third postback is very much like the second postback, but measures user activity from day 8 to day 35. Similarly to the second postback, the third postback has three disclaimers
Apple is also introducing a new concept – ‘lockWindow’. This gives the app developer the option to stop measuring user activity in order to get the postback as soon as possible. Locking the measurement window can be done for each postback within its activity window. For example, you can lock the window of the second postback anywhere between day 3 and day 7 of the user’s activity.
One of the critical updates for SKAN 4.0 will be very useful for ad networks: better granularity in campaign dimension reporting. In previous SKAN versions, campaign IDs were limited to 2 digits, meaning ad networks could only assign an ad a number between 0-99. In SKAN 4.0, the campaign ID is reborn as “source identifier”, and can contain up to four digits (up to 10,000 values).
It’s extremely important to note that the ad network will only receive all four digits in a postback if the privacy thresholds are met. When privacy thresholds are not met, the ad network may receive three digits or two digits (two digits will be the minimum).
Over the past few months, we’ve held multiple discussions with ad networks on how they plan to utilize this new feature. As it stands, ad networks have two main approaches:
One of the main pain points previous SKAN versions presented was the lack of support for web-to-app attribution. As a result, some of marketers’ main acquisition channels (e.g. Google Ads) were not covered by SKAN.
Apple is now adding support for web-to-app attribution for Safari.
While this new solution supports Safari only, our data shows that Safari is the mobile browser of choice for 93.65% of iPhone users.
In previous versions of SKAdNetwork, if a cohort of users did not pass the privacy threshold, Apple would drop the conversion value and/or source app ID from the postback and both would be nulled.
In SKAN 4.0 this concept is broadened; there are four tiers of crowd anonymity: 0, 1, 2 and 3. Apple determines which crowd anonymity tier each install belongs to, and may drop one or more of the following fields based on the tier: fine grain conversion value, coarse-grain conversion value, source ID, or source app ID.
Now that we understand SKAN 4.0, let’s build a plan on how to tackle it.
While it will likely take a while for the industry to align with SKAN 4.0, you can already start thinking about how you would like to set up your LTV measurement to make the most of the additional capabilities.
What should you measure and when? Here are the factors to take into account:
A very important aspect of the ability to run campaigns effectively is taking decisions as fast as possible. With SKAN 4.0, unless the lockWindow function is used, the first postback will arrive 3-4 days after the install occurs.
When considering what you would like to measure, you will need to take into account that there’s a tradeoff between capturing user activity and data freshness.
A common misconception we’ve encountered is that the coarse-grain conversion value is a derivative of the fine-grain conversion value. This is not true at all. The coarse-grain conversion values are an entirely separate method of mapping events or revenue.
In AppsFlyer’s Conversion Studio, advertisers will be able to map a specific in-app event or revenue range as ‘low’, ‘medium’ or ‘high’ for each postback. For example, a developer could potentially map a purchase event as ‘medium’ on postback #2, and map a level_complete event as ‘medium’ on postback #3.
Depending on your app category, the coarse-grain conversion value can carry significant value and insight; a subscription-based app could map the subscription event to ‘high’ on the 2nd postback, for example. You can check out some category-specific examples for SKAN 4.0 measurement in the interactive SKAdventure simulator.
Reporting with SKAN 4.0 could get a bit tricky. Since the source ID can be either 2,3 or 4 digits, different dimensions may be returned on every postback.
Let’s look at an example: If an ad network is dedicating the 3rd digit to indicate the country, some of the postbacks received will include the country dimension, while others may not due to privacy thresholds. Moreover, the 2nd and 3rd postbacks only ever contain 2-digit source IDs by default, meaning the country data will only ever be available up to day 2 post-install.
App developers will need to prepare accordingly, understanding what the new capabilities—combined with the new restrictions—mean for their LTV data reports.
SKAN 4.0 brings a LOT of great new capabilities and many options for app developers to define how and what they want to measure. While this news is still fresh, we highly recommend getting yourself familiarized with it and getting a head start on planning.
It may take some time for the industry to fully adopt SKAN 4.0, as adoption depends on every stakeholder in this ecosystem: app developers, MMPs, ad networks, publishers and end users.
SKAN 4.0 introduces up to three postbacks for LTV measurement with varying measurement windows, a new “lockWindow” feature for faster data, ad network optimization with a new “source identifier” for detailed campaign reporting, support for web-to-app attribution via Safari, and a refined privacy threshold system with four tiers of crowd anonymity.
The update allows for up to 48 hours of user activity measurement in the first postback and introduces coarse-grain conversion values for a simpler privacy threshold. The second and third postbacks enable extended activity measurement from day 3 to day 7 and day 8 to day 35, respectively.
The “lockWindow” feature gives you the option to stop measuring user activity within a specified timeframe to receive postbacks sooner, optimizing the delivery of valuable user engagement data.
SKAN 4.0’s “source identifier” allows for more granular campaign dimension reporting, with the potential to use the two extra digits for internal optimization or finer reporting breakdowns, including country dimension or creative ID, depending on the advertiser’s needs.
Developers should consider the balance between capturing comprehensive user activity data and the need for data freshness. Also, think about how to optimize measurement for each type of postback, and account for reporting complexities due to varied levels of detail in source IDs caused by the new privacy thresholds.
