The introduction of iOS 14.5 came with the rise of SKAdNetwork (SKAN) that had industry-wide impacts on the mobile measurement and attribution ecosystem. As such, Google will work differently from most non-self-attribution networks when it comes to SKAdNetwork campaigns.
Google will not be forwarding individual SKAdNetwork postbacks to Branch. However, aggregate SKAN data will be passed back via Google's Ads API. In this flow, Google collects individual SKAN postbacks, cryptographically validates them internally, and then provides only pre-generated results to Branch via an API endpoint. Additionally, data shared via API is may not include all data dimensions reflected in the SKAdNetwork postbacks.
Google Campaign Type
SKAdNetwork Support for Branch
通过 API 将汇总的 SKAN 数据提供给 Branch
SKAdNetwork Campaign ID
- Install vs. Reinstall
- Google does not share this via the API; therefore, all data is considered download/install in Branch systems.
Connecting Multiple Apps
If you have more than one app using the same Google Account ID, SKAdNetwork data may only appear in one of those apps. Do not connect the same Google Account ID in multiple apps to avoid visualization issues.
Because Google is utilizing the existing Google API to send SKAN data, the implementation is to activate Google Ads as a self-attribution ad network. Please follow the comprehensive guide on enabling Google Ads with Branch.
If you feel the data that you see in the Branch Dashboard is not correct, we recommend waiting 24-48 hours after implementation. It has a similar delay to cost data displayed on traditional SAN app install campaigns. Google’s conversion date is by ad interaction date (click), they have a system that matches an Apple postback to an ad interaction.
Updated 8 months ago