Update 2: Everflow has released our SKAdNetwork upgrades in beta, and screenshots of these updates in action are below.
Update: Apple officially made the decision to delay the requirement of IDFA requiring consent until the start of 2021 (right now we're expecting these changes to arrive in March 2021). This provides more time before these SKAdNetwork changes become essential.
SKAdNetwork, and the iOS 14 release, fundamentally changes how attribution is done in the mobile performance marketing space. Specifically, as it relates to the following:
For a quick explanation of what SKAdNetwork is, check out this highlght from our conversation with Roy Yanai of AppsFlyer:
If you’re an Ad Network, Agency or Publisher, you need to register as an Ad Network - [Register with Apple Here]
The Everflow platform already offers significant capabilities that address most of the changes and challenges imposed by iOS 14. These features have been proven at scale across our clients.
We already provide: Real-Time Reporting, Pixel-based or Server-Side Click and Impression Tracking, View-Through Attribution, and capture the critical device attributes (IP, User Agent, etc.) used for fingerprinting attribution. All of these features will help ease the transition for Ad Networks, Agencies, and Brands into this new world.
We're persistently working to determine the best ways for clients to handle the massive upcoming changes from SKADNetwork adoption - as more details come out and are able to be tested in the real world. To this end, we sat down with Sven Hezel, CEO and Founder of 24metrics, which is an Everflow integrated partner that provides anti-fraud detection and prevention. We discuss the basics of SKAdNetwork, how both our companies are preparing for it, and what fraud might look like under SKAdNetwork. Here is the full recording of our chat:
Expect more fireside chat conversations about SKADNetwork in the coming months. To see when our next SKAdNetwork chat (or all things performance marketing) is coming up - Follow us on LinkedIn.
With these new changes, the user must be sent directly from the ad placement to the Apple App Store. This makes re-brokering far less viable.
While sending the user directly to the App Store, Everflow simultaneously passes the critical impression and click data using pixels or a server-side implementation, as depicted in the flow below.
Understanding the New Attribution Flow
For passing data through Server-Side Clicks, two actions need to be set up to happen in parallel:
We recommend all clients promoting iOS offers to prepare their setup to be able to receive postback conversion directly from Apple and fingerprint conversions from the MMPs (for reasons explained further on).
The best way you can prepare for the upcoming changes is to enable Server-Side Clicks for all of your iOS offers in Everflow.
If you’re tracking Impressions, View-Through Attributions are also server-side, and will continue to track conversions successfully.
Setup Note: With Server-Side Clicks, the App/MMP won't be able to detect the user’s IP or User Agent. As these are critical details for fingerprinting attribution, make sure to append these parameters to your Server-Side Clicks:
With SKAdNetwork, the app is able to pass up to 64 event values. Clients will be able to receive this data directly to identify, track and analyze in-app events as they have always done.
The Event Report makes it easy to break down the event performance by offer, partner, or other comparative metric.
Here is Roy from AppsFlyer explaining how the postback conversion window will work under SKAdNetwork:
Everflow is used for managing all of the sources of performance driving traffic. By being closer to the traffic side, we’re able to collect the critical data from the source for real-time tracking of impressions and clicks. This data can be leveraged for analyzing traffic, while blocking fraud traffic sources and proxy traffic.
Our clients have always had the advantage of being able to automatically block traffic on the placement level. These features have become even more critical now that anti-fraud vendors are no longer able to monitor traffic in the redirect chain. Most fraudulent activity is stopped by setting clear rules that automatically block any partner’s traffic sources that deliver unnatural conversion rates, low event rates or other suspicious metrics.
Your Ad Network ID Needs To Be Detected In Every Placement
We’re still exploring the ramifications of this requirement and would not be surprised if there are additional announcements/changes associated with it.
Here is the requirement directly explained by Apple:
“The ad network ID is a unique identifier of the form “example123.skadnetwork”. Share your ad network ID with app developers who display your ads. Developers must include your ID in their app’s information property list to initiate the app install validation process. (Apple)”
Based on the linked instructions, in order to receive postbacks from Apple you will have your Ad Network ID included in the publisher apps info.plist. The major DSPs have already started requiring their app publishers to regularly update their apps with the DSP’s global list of required SKAdNetwork IDs.
There are clear issues with this from a feasibility and viability perspective for advertisers, networks and the Ad Networks. For example, this method shouldn’t work at all for mobile web as the info.plist doesn’t exist on that side.
We’re keeping in close contact with our clients and industry peers to better understand how this requirement will be handled.
Our recommendation: Make sure that you set up and enable Server-Side Clicks to pass all of the necessary details for the MMPs to be able to do fingerprinting attribution. This will be the best setup for transitioning, and gives you time to start getting your SKAdNetwork IDs into your partnered publisher apps.
Are you a mobile ad network? Check out how Roy explains how ad networks will work with AppsFlyer clients that are using the SKAdNetwork framework:
We've been busy working on updating the Everflow interface to reflect the new requirements posed by SKAdNetwork.
The screenshots below are mainly about achieving full SKAdNetwork functionality by allowing clients to set up and manage all of the required parameters for tracking and compliance. After we test this with more beta clients, we will refine and polish this section.
You can create a new iOS App Attribution setup with the necessary Ad Network parameters and API keys:
For managing your various app offers and partners, you can assign a Campaign ID to them, and then track their tied performance accordingly:
Finally, you'll be able to receive the postback data from Apple, and then pass on that data on to other partner and advertiser postback sources, including the MMP:
With our iOS App Attribution section, clients will be able to use Everflow to optimize and manage their traffic sources directly based on SKAdNetwork data and postbacks.
Being close to the traffic allows us to detect and pass the critical IP and User Agent data that the MMPs need for fingerprinting attribution. This gives us and our clients a significant advantage and benefit for their partners, especially in the early stages of this massive transition.
Our goal is to make it as easy as possible to adapt quickly despite the challenges posed by iOS 14 and SKAdNetwork, while continuing to empower our clients by arming them with the platform for optimizing data effectively.