iOS 14 对 Branch 数据集成的影响
| Branch 与该合作伙伴的集成是否需要更新 iOS 14？ | 客户需要采取行动吗？ | |
|---|---|---|
| Adjust | 是—需要收集 IDFV | |
| 土坯 | Integration is still valid without IDFA, because they would use MID/VID/AID user IDs. Still need to update postbacks to use IDFV, as device ID can be a fallback attribution parameter in lieu of a user ID (Adobe to first confirm if/how they can ingest IDFV). | 目前不可行。合作伙伴在进行任何更改之前，等待 Apple 的政策更新。 |
| Amplitude | 否 | 目前不可行。合作伙伴在进行任何更改之前，等待 Apple 的政策更新。 |
| AppsFlyer | 是—需要收集 IDFV | |
| Braze | 否—如果没有 IDFA，集成仍然有效，因为它们将使用内部用户 ID | |
| Firebase | 否—此集成完全由客户端处理 | |
| Google Analytics | 否—如果没有 IDFA，集成仍然有效，因为它们将使用内部用户 ID | |
| Heap | 否 | 目前不可行。合作伙伴在进行任何更改之前，等待 Apple 的政策更新。 |
| Kochava | 否—如果事件中缺少 IDFA，DI 会使用 IDFV | |
| Mixpanel | Integration is still valid without IDFA, because they would use Mixpanel's anonymous user IDs. Still need to update postbacks to use IDFV, as device ID can be a fallback attribution parameter in lieu of a user ID (Mixpanel to first confirm if/how they can ingest IDFV). | 目前不可行。合作伙伴在进行任何更改之前，等待 Apple 的政策更新。 |
| mParticle | 否—如果没有 IDFA，集成仍然有效，因为它们将使用内部用户 ID | Should upgrade to latest versions of all the relevant SDKs and kits to be safe. Customers who still want to collect IDFA and pass it to mParticle should implement Apple's frameworks for collecting it directly and pass it to mParticle on an Identify call. |
| Segment | 否—如果没有 IDFA，集成仍然有效，因为它们将使用内部用户 ID | Should upgrade to latest versions of all the relevant SDKs and kits to be safe. Customers who still want to collect IDFA and pass it to Segment should implement Apple's frameworks for collecting it directly and pass it to Segment on an Identify call. |
| Visual IQ | 否 | 目前不可行。合作伙伴在进行任何更改之前，等待 Apple 的政策更新。 |
Updated about 2 years ago