iOS 15 update response information
iOS 15 Update Overview
iOS 15 was officially launched on September 21, 2021.
Compared to the iOS 14 update, which brought major changes, the iOS 15 update was updated to further strengthen the privacy policy introduced in iOS 14.
Let’s take a look at the major changes in iOS 15 and how to respond to them.
1. iCloud+ Private Relay
Function: Anonymous IP is applied to iCloud paid customers and Device Fingerprint attribution is limited.
Private Relay, first introduced in iOS 15, is a privacy protection feature that operates for paid iCloud subscribers when the user uses the Safari browser. Enabling this feature will replace the Safari browser users IP with your local anonymous IP.
For example, as shown in the screenshot below, if the public IP of the actual connected device is 223.39.220.170, the Safari browser replaces it with an anonymous local IP through private relay.
[Chrome with actual public IP (left) / Safari with anonymous IP applied using private relay (right)]
In the case of the Safari browser with private relay applied, the users IP is sent to an anonymous IP address, so attribution through IP-based Device FingerPrint cannot be performed.
However, since this feature is open to Safari browser users among paid iCloud subscribers, it is unlikely that the performance of Device FingerPrint attribution will significantly decrease through private relay. Since private relay cannot be used in browsers other than Safari, such as Google Chrome, Naver, and Whale, attribution via Device FringerPrint can still be performed in these browsers.
Additionally, deep linking and universal link open tracking through tracking links can be used regardless of the private relay function.
2. App Tracking Transparency changes
Major change: The pop-up "ATTrackingManager.requestTrackingAuthorization" that obtains IDFA permission can only be called when the app is fully launched.
There are also changes to "ATTrackingManager.requestTrackingAuthorization", a pop-up that obtains the IDFA of App Tracking Transparency, which was enforced starting from iOS 14.5.
ATT pop-up exampleㅣImage source: Apple, PRESS RELEASE
In order to obtain authorization and obtain the users IDFA value as quickly as possible, a method of calling a pop-up to obtain the IDFA immediately after running the app has been widely used. (In developer terms, this is called calling from "didFinishLaunchingWithOption".) However, this method is also no longer available.
Starting with iOS 15, the IDFA permission setting pop-up "ATTrackingManager.requestTrackingAuthorization" can no longer be called immediately after launching the app, and can only be used after the app is completely launched. If you call this pop-up right after running the app, you need to change the pop-up call point so that it can be called from ViewController, not AppDelegate. Please refer to the sample code in the iOS integration guide.
[iOS ATTrackingManager.requestTrackingAuthorization Sample code]
In the case of DFINERY, it is expected that using IDFA will become difficult starting from iOS14, and the main device ID used has been switched to IDFV rather than IDFA. Even if the acquisition of IDFA authority is delayed or cannot be obtained, user analysis and tracking through DFINERY is still possible as before.
3. New framework AdBrixRM XC
In the case of existing frameworks, there was the inconvenience of having to update the version of the AdBrixRM framework every time the Swift and Xcode versions were updated. We are releasing the AdBrixRM XC framework, a new framework to solve these inconveniences.
The AdBrixRM XC framework will eliminate the inconvenience of having to update the AdBrixRM framework every time the existing Xcode and Swift versions are updated.
To use the AdBrixRM XC framework, modify the current Xcode project as follows.
3.1. Modify and apply pod files
Open the pod file in the project, edit it as shown below, and save it.
platform :ios, '8.0' target "myXcodeProject" do // pod 'AdBrixRemastered_XC' // Comment out or delete the existing AdBrixRemastered and AdBrixRemastered_XC pods pod 'AdBrixRmKit' // Apply "AdBrixRmKit" end
After modifications, open a terminal and apply the AdBrixRmKit framework via pod install / pod update.
$ pod install
3.2. In-project modifications
Once the pod file is applied, the import path within the project must be modified to match the AdBrixRmKit framework.
Just change the framework path and you can use it without changing the existing API.
Inquiry for integration support
If you have any additional questions or need integration support regarding iOS 15 and the AdBrixRmKit framework, please contact us by email below and we will provide you with active support.
support-tracker@adbrixsupport.zendesk.com