SKAdNetwork 4.0 was introduced in March 2022, and it includes several new features and improvements for app user acquisition over previous versions of the framework making it particularly beneficial for subscription apps.
One of the key improvements is support for coarse-grain conversion values. This allows you to map events or revenue to low, medium, or high values while keeping user privacy. You will not know the exact conversion value, but it is better than "null". Postback may now contain either a fine-grain conversion value, coarse-grain conversion value, or "null" based on the privacy thresholds set by Apple. The developer must provide coarse and fine conversion values in a new method:
updatePostbackConversionValue(_: coarseValue: completionHandler: )
Another key improvement that is designed specifically for subscription apps is support for up to 3 postbacks. Here's how they work:
Developers can use the updatePostbackConversionValue(_:coarseValue:lockWindow:completionHandler:)
method to receive postbacks sooner. This method allows you to lock and confirm a conversion value before the end of the conversion window. You can select to lock the conversion value in any or all conversion windows. In the diagram below, you can see an example of an app that locks the conversion value during the second conversion window:
Once the system receives a locked conversion value, it immediately prepares the postback and disregards any subsequent updates to the conversion value within the same conversion window. The postbacks are then sent after a random delay, which is 24-48 hours for the first postback and 24-144 hours for the second and third postbacks, following the locked conversion. The system continues to ignore any further conversion value updates for the remaining time in the same conversion window. In SKAN 4.0, an app can finalize the conversion value by locking it, and the device will send the postback after a random delay of 24-48 hours.
The Hierarchical source ID, formerly referred to as the campaign ID field, enables advertisers to attribute installs to campaign ads and other attribution information. Advertisers can customize this four-digit value based on their objectives, such as campaign values, ad placement, or type of ad creative.
The postback always contains a minimum of two digits in this field, but up to four digits can be included depending on the number of installs and the privacy level achieved by the campaign ads. This feature gives advertisers more flexibility in their mobile app campaigns and provides them with additional attribution data when privacy thresholds are met. Most importantly, user privacy is safeguarded across apps.
The SKAdNetwork for Web Ads API empowers advertisers to evaluate the effectiveness of ad campaigns originating on the web, all while preserving user privacy. Beginning with iOS 16.1, ad networks can leverage this API to obtain SKAdNetwork attributions for web ad clicks in Safari that result in App Store app installations.
As mentioned previously, a developer can initiate up to three postbacks during three conversion windows. Use Apphud SDK in your subscription app to determine the current subscription status and update the conversion value depending on it. As an example, you may use status
, isInRetryBilling
and autorenewEnabled
properties of ApphudSubscription
object to update conversion value as follows:
autorenewEnabled
is true
), increase a conversion value by 1 point.regular
) increase a conversion value by 2 points.isInRetryBilling
is true
, increase a conversion value by 1 point.autorenewEnabled
is false
.status
is expired
or refunded
.At Apphud, we understand the importance of campaign performance analytics in driving app revenue growth. Therefore, we prioritize data accuracy. Our platform delivers the most precise app revenue data to enable you to formulate growth strategies. Get started with Apphud today!