iOS 15 Update Response Guide
iOS 15 Update Overview
iOS 15 was officially launched on September 21, 2021.
Compared to the significant changes in the iOS 14 update, the iOS 15 update has been made to further strengthen the privacy policies introduced in iOS 14.
Let's look into the major changes in iOS 15 and how to respond to them.
1. iCloud+ Private Relay
Function: Anonymous IP is applied to iCloud paying customers, and Device Fingerprint attribution is restricted.
Private Relay, first introduced in iOS 15, is a privacy feature that operates for iCloud paid subscribers when they use the Safari browser. This feature allows the user's IP in Safari to be replaced with an anonymous IP from the respective region.
For example, if the public IP of the actual access device is 223.39.220.170 as shown in the screenshot below, the Safari browser replaces it with an anonymous regional IP through a private relay.
[Actual public IP shown in Chrome (left) / Anonymous IP applied in Safari using private relay (right)]
In the case of the Safari browser with private relay applied, the user's IP is transmitted as an anonymous IP address, making it impossible to proceed with attribution through IP-based Device Fingerprint.
However, since the feature is open only to Safari browser users among paid subscribers of iCloud Private Relay, it seems unlikely that the performance of Device FingerPrint attribution will significantly decline through Private Relay. Since Private Relay cannot be used on browsers other than Safari, such as Google Chrome, Naver, and Whale, attribution through Device FingerPrint can still be conducted on these browsers.
Additionally, opening deep links and universal links through tracking links can be used regardless of the private relay function.
2. App Tracking Transparency Changes
Main change: The popup "ATTrackingManager.requestTrackingAuthorization" to obtain IDFA permission can only be called when the app is fully running.
There are also changes to the popup "ATTrackingManager.requestTrackingAuthorization" for obtaining IDFA, which began to be enforced from iOS 14.5 with App Tracking Transparency.
ATT popup example | Image source: Apple, PRESS RELEASE
In order to obtain the user's IDFA value as quickly as possible, it was common to call the popup for acquiring IDFA immediately after launching the app. (In developer terms, this is called invoking it in "didFinishLaunchingWithOption.") However, this method can no longer be used.
From iOS 15 onwards, the IDFA permission setting popup "ATTrackingManager.requestTrackingAuthorization" can no longer be called immediately after app launch and can only be used after the app is fully launched. If you are calling this popup immediately after app launch, you need to change the call timing to be from the ViewController instead of the 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 the use of IDFA will become difficult starting from iOS14, and the main device ID in use has been switched from IDFA to IDFV. Even if obtaining IDFA permission is delayed or cannot be obtained, user analysis and tracking through DFINERY are still possible as before.
3. New Framework AdBrixRM XC
In the case of the existing framework, 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 introducing the new framework, AdBrixRM XC, to solve this inconvenience.
Through the AdBrixRM XC framework, we will eliminate the inconvenience of having to update the AdBrixRM framework every time the 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 file
Open the pod file within the project, modify it as follows, and save it.
platform :ios, '8.0'
target "myXcodeProject" do
// pod 'AdBrixRemastered_XC' // Comment out or delete the previously set AdBrixRemastered, AdBrixRemastered_XC pod
pod 'AdBrixRmKit' // Apply "AdBrixRmKit"
end
After making changes, open the terminal and apply the AdBrixRmKit framework through pod install / pod update.
$ pod install
3.2. Modifications within the project
When the pod file is applied, you need to modify the import path within the project to match the AdBrixRmKit framework.
You can continue to use the existing API without any changes by simply changing the framework path.
Integration Support Inquiry
If you have any additional inquiries or need integration support related to iOS 15 and the AdBrixRmKit framework, please contact us at the email below, and we will actively support you.
support-tracker@adbrixsupport.zendesk.com