Sep 09, 2016

Released: SDK 4.10 for iOS, Android and more

Released: SDK 4.10 for iOS

This post has been updated on September 14th, 19th, 21st, October 4th, and December 5th, 2016 to reflect releases for additional platforms.

We’ve just released SDK 4.10, adding new features like custom session parameters, deep links in the attribution response, and some tweaks for iOS10.

The update is a minor version increment, meaning that you can just drop in the new source files without changing any of your own code.

SDK 4.10 is currently released for Android, iOS, Unity, Xamarin, Marmalade, Cocos2d-X, Cordova, React Native and Adobe Air. The Windows SDK will follow shortly.

Custom and partner parameters are now available on sessions

The Adjust SDK already allows you to add custom data to the in-app events you are tracking, and forward them either to your own BI systems or to partners like ad networks or analytics platforms.

With SDK 4.10, you’ll also be able to send these parameters when the SDK tracks a session or a new install.

Typically, this might be internal user IDs that you’d want to use in your database to sync up the in-app activity that adjust is tracking with your own data. In the past, you would often send this information on a specific event, but with 4.10, you can also attach the ID to every session.

Most of the data you might want about an install can already be received in your callbacks as it is, but in case we missed anything, the new custom parameters will come in handy.

Thanks to partner parameters, you typically don’t need to integrate additional SDKs to get full value from the ad networks or analytics tools you want to use. You can transmit all of the data they need via adjust. That’s why we keep upgrading them for more flexibility.

Updates for iOS 10

iOS 10 is released on September 13th, next week - and SDK 4.10 includes a few tweaks to ensure optimum performance on the new operating system. Specifically, there’s a fix to avoid an edge case that may result in organic install overcounting when users with Limit Ad Tracking activated reinstall your app.

We recommend an immediate update to SDK 4.10 to avoid exposure to the edge case. All the same, we expect the actual overcounting to be very rare.

This tweak does not apply to the Android SDK.

Check the deep links in the attribution response

You can already easily defer deep links with the Adjust SDK, by informing the adjust SDK whether or not to trigger a deep link after an install. With SDK 4.10, you can also access the specific deep link URL that the user had clicked on prior to install, even if you don’t want to defer the deep link.

For example, if you’re sending an email newsletter, you can already use an adjust tracker URL as links that automatically detect the user’s device and sends mobile users to specific locations in your app. If a user on a mobile device does not have your app installed, the trackers will send the user to the App Store to download the app.

After the install, you have been able to choose whether or not to open the same deep link. With SDK 4.10, you can decide not to, but still easily access the deep link URL. This data is in addition to the extensive source and user information available to your app in real time.

Ecommerce startup Vinted used this data to make users 77 % more likely to make a purchase.

Do I have to update?

We recommend an immediate update to SDK 4.10. If you’re already on an SDK version 4.0 or above, you don’t even need to change any of your code - just include the updated files in your project.

We use semantic versioning. This release is categorized as a minor update. As such, the new SDK is fully backwards-compatible, and does not introduce any changes that affect your current integration. This means that you can just drop in the new version of the SDK without having to change anything else in the app.

Typically, you don’t need to upgrade your SDK integration very often. The last time we released an SDK version with breaking changes, meaning that you had to change the integration to upgrade to the new SDK, was in December 2014. While you should use the latest SDK to ensure you have access to all functionality, we still officially support SDK 3.0, which was released in February 2014.