This includes information on which products a customer views or purchases from you, how often they visit your website or mobile app, and even data that’s stored in your CRM system.įirst-party data is distinct from third-party data, which is facilitated by data brokers. If you link user or device data collected from your application with user or device data collected from other companies’ apps, websites, or offline properties for targeted advertising or measurement purposes, you will need to collect end-user permission through Apple’s AppTrackingTransparency framework.Īs a first-party data pipeline, Segment helps you collect data directly from end-users that have a direct relationship with your products or services. With iOS 14.5, Apple is enforcing their App Tracking Transparency privacy policy. On April 26, 2021, Apple released iOS 14.5 which includes the following updates that may impact your Segment implementation. If you discover an integration affected by Apple’s iOS 14 changes, but is not listed above or does not have updates, contact customer support. Segment integrations for both device- and cloud-mode now have the most recent changes from affected integration partners:Īdditional affected integration partners are in the process of making changes, and these will be included in future updates. Several integration partners made their own updates to support Apple’s iOS 14 platform changes. Segment’s integrations have been updated to support Apple’s iOS 14 changes. You should update all device-mode integrations and their bundled SDK packages accordingly. All device-mode destination SDKs require an update.ĭue to major changes to core Segment SDKs for version 4, all device-mode destination SDKs have been updated. The Segment example code, used along with Apple’s documentation, make it easy for developers to collect and pass the IDFA to the Segment SDK as a configuration item on app load. ![]() Remember, under iOS 14, applications can only collect the IDFA from a user if they consent to make it available. If you need to collect the user’s IDFA to pass it to specific destinations, or for other uses, you can follow the steps for Ad Tracking and IDFA in the iOS documentation to collect and pass IDFA as a configuration item to the Segment SDK. ( v4.1 at the time of this writing) You can manually pass the IDFA to the Segment SDK. (If your implementation requires the IDFA for compatibility with specific destinations, see the section below.)ĭue to this major change, you should upgrade to the latest stable version of analytics-ios. The Segment SDK no longer automatically collects the IDFA after version 4. Previously, the Segment SDK collected the IDFA as the value for each event if the user enabled ad-tracking. This major version release includes the following (API compatible) updates: Segment no longer automatically collects IDFA. The Segment iOS SDK ( analytics-ios) has been updated to version 4 with v4.1 released as stable. Segment updated the iOS Source SDK ( analytics-ios) and any affected destinations so they support Apple’s iOS platform changes. However, Segment’s iOS Source SDK ( analytics-ios) and any destinations that previously used IDFA require that you update them so they continue to work with iOS 14. ![]() Segment products, including Connections, Protocols, Engage, Unify (including Identity Resolution), and Privacy, Data Lakes, and Cloud Sources, do not rely on IDFA and so are not affected by these platform changes. Segment fundamentally agrees with Apple’s stance.Īpple released iOS 14 in the autumn of 2020, but delayed the IDFA changes until early 2021. These changes require developers to ask for user consent before collecting IDFA to track users across multiple applications. In June 2020, Apple made several privacy-related announcements at WWDC20 about its upcoming iOS 14 release, including changes to the collection and use of Identifier for Advertising (IDFA). For information about iOS 14.5, see What’s new in iOS 14.5 below.
0 Comments
Leave a Reply. |