At WWDC 2020, Apple announced several changes to iOS 14 that aim to increase the level of control and transparency each user has over their own data. These changes impact the mobile ad-tech industry’s operating norms that have existed since iOS 6 unveiled the ID for Advertisers (IDFA). Get ready for the new normal with our SKAdNetwork Checklist.
In a nutshell, to comply with Apple’s new tracking guidelines, each actor needs to register with Apple as an ad network to provide, receive, and verify conversion information on IOS.
We at Smadex have been working alongside our partners and clients to be prepared for this new scenario. IOS 14 is around the corner, have you added our credentials yet?
How To Get Started
- For Publishers:
Include Smadex SKAdNetwork’s key in each of your apps’ info.plist file.
Smadex SKAdNetwork key is:
- For Exchanges:
Include the BidRequest.imp.ext.skadn object when SKAdNetwork is supported. In this object, include:
Skadnetids: to be present when the DSP receiving the request is in the p.list
Version: string that SKAdNetwork represents the version number
All in all, ensure that you can receive and process the following fields in the bid response. The DSP will send in the response the object BidResponse.seatbid.bid.ext.skadn when it expects the SSP to submit the click data and signature to the ProductView.
This object will contain the following attributes:
- Version: string representing the version of SKAdNetwork desired. Must be 2.0 or above.
- Network: Ad network identifier used in the signature. Will match one of the items in the skadnetids array in the request
- Campaign: the campaign ID, an integer from 1 to 100 expressed as a string
- Signature: SKAdNetwork signature as specified by Apple
What’s on your own SKAdNetwork checklist? Would love to chat with you on how to face this new challenge.
If you are a publisher or supply-side partner and have any comments or doubts, please contact Albert Puigbó at email@example.com 14SKadnetwork