SKAdNetwork and the iOS 14 release changed the process of mobile attribution in performance marketing.
Affise offers a solution, which allows you to work directly with SKAdNetworks as effectively as possible, taking into account all limitations and peculiarities.
There are four reasons why you can work with SKAd:
You want to promote your iOS application. You work directly on SKAdNetwork, and you want to accumulate the data on Affise. You need to register at Apple Developer.
You want to advertise something in your iOS application. You work directly on SKAdNetwork, and you want to accumulate the data on Affise. You need to register at Apple Developer.
You send traffic to the owner of an iOS application, which contains the advertisement. The owner uses SKAdNetwork, but not Affise. You get the data from an advertiser, and there's no need to register at Apple Developer.
You send traffic to the attribution platform (like Appsflyer) integrated with SKAdNetwork. You don't need to register at Apple Developer.
🔎 For this, follow our guide about Probabilistic Attribution.
Tracking with SKAdNetwork on Affise
To start working with SKAd, you need a SKAdNetwork profile.
To set up a profile on Affise:
1. You need to register at Apple Developer to get your Ad Network ID.
2. It's necessary to generate a Public Key. Learn more here.
You can find SKAdNetwrok profiles in Advertisers > SKAdNetworks.
⚠️ By default, only a General manager has access to the SKAdNetworks subsection.
You can create and edit your profiles.
Title: the name of the SKAdNetwork.
SKAdNetwork ID: an advertiser's SKAdNetwork ID.
⚠️ If you want to use several IDs, you need to create a separate SKAdNetwork.
Public key: a public key generated in SKAdNetwork.
Campaign ID list: Apple allows to create up to 100 traffic sources per campaign (offer, application).
Here you can determine your sources in several possible ways:
Up to 100 campaign IDs with 100 affiliates (pids).
Up to 50 campaign IDs with 50 affiliates and sub2 value combinations.
Up to 100 campaign IDs with one affiliate and 100 sub2 values.
⚠️ There should be no more than 100 sources or sub sources in total.
You can combine variants: 25 campaign IDs with affiliate + sub2 combo and 50 campaign IDs with affiliate IDs only, 10 campaign IDs with affiliate + sub2 combo, and 80 campaign IDs with sub2 values only, etc.
🔎 By this tool, you can define targeting according to agreements with your affiliates. For example, affiliate #123 has two sources: France (sub value #1) and Germany (sub value #2). Then you can create two Campaign IDs: pid 123 + 1 and pid 123 + 2.
When you prepare your SKAdNetwork profiles, you need to connect them to certain advertisers.
If you're a direct advertiser, you need to create a profile for yourself as an advertiser and connect the SKAdNetwork you created.
If you work with a direct advertiser and have your application in App Store, you need to create a profile for your advertiser.
If you work with an affiliate of the direct advertiser, you need to create a profile for your advertiser (not the direct one).
You can connect several SKAdNetworks for one advertiser. It's useful if your advertiser is a company, where developers have their Ad Network IDs in SKAdNetwork.
To get postbacks correctly, you need:
Ad Network ID (on the advertiser level)
Apple App ID (on the offer level)
Campaign ID (on the Advertiser level)
Check whether you have all the values before working with SKAdNetwork.
To receive postbacks from SKAdNetwork, you need to create a postback link. You can use the default or custom domain for the Admin panel.
The postback link should be set up in SKAdNetwork.
⚠️ You don't need additional parameters in the postback link. Affise receives the information from SKAdNetwork in the form it sends the data in the response.
The postback is sent by SKAdNetwork in JSON format by the POST method. It contains the following information:
Version: The version of the SKAdNetwork API.
Ad Network ID: your ID in SKAdNetwork if you're a direct advertiser or the ID of your advertiser, who uses SKAdNetwork.
Campaign ID: the campaign ID you set up on the SKAdNetwork edit page on Affise. This ID contains the affiliate ID and sub2 value.
Transaction ID: the ID of the conversion (unique for each conversion).
App ID: the ID of the application that should exist in the offer on Affise.
Attribution signature: your personal/your advertiser's Public key that should exist in the SKAdNetwork profile on Affise.
Redownload: an option that indicates the end-user redownloaded and reinstalled the application.
Source App ID: the ID of the application in the App Store, which contains an advertisement.
Conversion value: the goal value.
Fidelity type: indicates whether the install was generated with an impression or a click.
SKAdNetwork has a delay of up to 24 hours. It means you receive a postback after up to 24 hours since the conversion was made. A certain delay time is determined randomly. For example, the conversion was made at 14:30. A postback can be received at 14.35, at 20:03, at 05:57, etc. - at any time within 24 hours.
🔎 If you use the automation tools (CR, Click, KPI), select 24 hours only for your rules.
You can see all the parameters SKAdNetwork sent in Statistics > Server Postbacks.
You can also see the conversions in Statistics > Conversions.
There is a goal value passed as conversion value, and action ID passed as transaction-id. Each conversion from SKAdNetwork has a comment [SKAdNetwork Attribution].
You can set the affiliate postback for the SKAdNetwork integration. The system send only conversions received from SKAdNetwork via the link set up with the help of this option.
What to do next
📃 Related topics
Please contact the Affise Customer Support team regarding all raised questions via the e-mail: [email protected].