I have recently received this email from branch , regarding the removal of install_referrer and instructions regrading the new googple api:
http://go2.branch.io/HF001080YlXgpTv0BqT00Aj
Are we ready for this ?
It is real soon...
This is the email from branch:
Hi Edan,
A couple of months ago, Google announced that they will stop broadcasting install_referrer intents on March 1, 2020. Branch uses this data to help power our deep linking and attribution services on Android devices.
Fortunately, Google has also introduced the Play Install Referrer API to provide the same data. This API provides better performance, and there is a good chance it is already configured in your app. However, Google has recently contacted several Branch customers about this, so we wanted to proactively reach out and help you confirm your configuration in advance of the cutoff date.
REQUIRED ACTIONS
Branch Android SDK: please do EITHER of the following for your Android app:
- Ensure you've linked the Play Install Referrer Library as a Gradle dependency. To do this, please add this directive to your build.gradle file (it is not necessary to implement any of the other steps on this page, as the Branch SDK will handle the rest for you).
OR
- Update to the most recent version of the SDK (v4.3.2), which bundles the Play Install Referrer Library automatically.
TUNE Android SDK: Please update to the most recent version of the SDK (v6.1.2, currently only available on JCenter). The TUNE Android SDK already bundles the Play Install Referrer Library, but older versions contain a rare bug that can cause a background thread to pause for up to 60 seconds while waiting for install_referrer data to be returned.
In addition, we recommend confirming that the following entry has been removed from your AndroidManifest.xml file:
Branch SDK
TUNE SDK
If you have any questions, please feel free to reach out to [email protected].
Sincerely,
The Branch Team
MORE DETAILS:
What are the two different pieces of tech here? Which one is deprecated, and which one is newer?
The install_referrer intent broadcast (docs) is the older technology. It is being replaced by the Play Install Referrer API (docs). On March 1, 2020, the former will stop operating entirely.
For most intents and purposes, these two technologies are equivalent. The newer Play Install Referrer API is more reliable (according to Google), and it contains some additional metadata about when users found and downloaded your app.
How can I tell whether my apps are impacted?
If you use the Branch Android SDK and have not linked the Play Install Referrer Library via Gradle dependency, then you will want to take one of the actions listed above.
If you use the TUNE Android SDK, you are already leveraging both the Play Install Referrer API (new) and install_referrer intent broadcast (deprecated). Most of the time, this should not be an issue. However, we still recommend updating your SDK.
If my app is impacted, what happens if I don’t update my SDK or link the InstallReferrer library by March 1, 2020?
Without Install Referrer data, the Branch Android SDK will fall back on other matching techniques. This will result in degraded attribution accuracy.
Older TUNE Android SDK versions will continue to receive Install Referrer data via the API, but in some rare cases, one of the background SDK threads may hang for up to 60 seconds while waiting for the install_referrer intent broadcast. After March 1, 2020, this intent will always be missing.
Besides updating the Android SDK, do I need to make any changes?
We recommend ensuring the deprecated InstallListener intent filter entry (shown above) has been removed from your AndroidManifest.xml file.
When I update my SDK, will any analytics or attribution change for my app?
If you are using the TUNE Android SDK, nothing will change.
If you are using the Branch Android SDK, it depends on whether you previously linked the Play Install Referrer Library via Gradle dependency. If you had, nothing will change. If you had not linked this library, you will now see some additional metadata (namely, install_begin_ts and clicked_referrer_ts).
What if I'm using a library, such as Cordova or React Native?
We are preparing updated versions of all of our modules, and anticipate these being ready prior to March 1, 2020. Please email us at [email protected] if you have any concerns.
Do I need to force my users to upgrade app versions?
No. There is no impact on your existing app users — only on measurement for new installs.
Can I talk to someone at Branch before making the changes?
Absolutely! We’re here to help. Please email us at [email protected], and we’ll go over any questions you may have.