Update your Kochava SDK integration for enhanced deep link attribution and dual-stack IP support
TL;DR Summary (click to expand)
New major SDK versions, iOS SDK v11.0.0 and Android SDK v7.0.0, are available now. If your app already has Enhanced Deep Linking integrated, this update automatically captures deep link URLs and click identifiers (e.g., Google’s GCLID/GBRAID, Meta’s campaign_ids, Snap identifiers) without any manual coding, improving attribution for reengagement campaigns and removing a step that could accidentally get dropped during app updates. The release also expands dual-stack IP support, enabling Kochava to collect both IPv6 and IPv4 when available, improving attribution when ad engagement and conversion provide different IP address families. This is particularly relevant for cross-device and household-level attribution, including CTV. We recommend looping in your app development team now to scope this upgrade into an upcoming dev sprint.
Android SDK v7.0.0 Documentation | iOS SDK v11.0.0 Documentation | Contact Kochava
New major version releases of the Kochava software development kit (SDK) are available now:
- iOS SDK v11.0.0
- Android SDK v7.0.0
If you run reengagement campaigns or regularly use cross-device attribution where dual-stack IP support is increasingly important, this upgrade is worth prioritizing with your app development team. For full technical release notes and upgrade guidance, see the Android SDK v7.0.0 documentation and iOS SDK v11.0.0 documentation.
Let’s unpack the key benefits of this major SDK release.
Enhanced Deep Link Attribution for Reengagement Campaigns
When a user clicks an ad across major publishers (e.g., Google, Meta, Snap) and your app opens via a deep link (Universal Link on iOS, App Link on Android), the click carries valuable attribution parameters with it. Identifiers such as Google’s GCLID and GBRAID, Meta’s campaign_ids, and Snap-specific identifiers tell you which campaign and click drive the reengagement. Kochava server-side infrastructure has always parsed and routed these parameters for attribution. However, getting them to Kochava in the first place has depended on app developers implementing additional manual coding during integration. The SDK update removes this dependency.
With this update, the SDK captures the full deep link URL the moment your app opens via a Universal Link or App Link, forwarding to Kochava servers without any additional custom event calls or manual instrumentation required. Our existing parsing infrastructure takes it from there, extracting and routing GCLID, GBRAID, campaign_ids, or other parameters.
Removing the manual dependency also solves a quieter, easy-to-miss problem. Since forwarding the deep link URL previously depended on a manual code call, that instrumentation could unintentionally get dropped during an app update, a refactor, or a minor SDK bump, often without anyone noticing until reengagement attribution results declined. With this behavior now built natively into the SDK, there’s no separate line of code to maintain. If Enhanced Deep Linking is integrated, the call fires automatically, making this a more foolproof approach than relying on a manual step your team needs to remember release after release.
The practical impact is most pronounced for reengagement campaigns. Automatically capturing the deep link URL and click identifiers it carries improves attribution coverage for users who already have your app installed, then return via a click on a paid ad. The result is more consistent, complete attribution across Google, Meta, Snap, and other major ad platforms that rely on Universal Link and App Link implementation.
Please note that during the SDK upgrade process, developers need to remove the code for any previous manual event instrumentation to avoid firing duplicate events. Be sure to provide your app development team with the following support documentation:
For questions or direct support during upgrade, please contact your Client Success Manager or email support@kochava.com.
Expanded Dual-Stack IP Support for More Complete Attribution
This major release also extends dual-stack IP capture across the Kochava SDK. As IPv6 adoption continues to grow across mobile operating systems and browsers, more devices can use either IPv4 or IPv6, and many now prefer IPv6 by default when it’s available. It’s a quiet shift, but one with real implications for how confidently you can attribute results. Updating your SDK integration ensures that your app is covered for dual-stack IP support.
Why Dual-Stack IP Support Matters
Some publisher ad-serving platforms still pass only a single IP address family in their tracking macros, often IPv4. If the same device later opens your app or fires a conversion over IPv6, the impression and conversion event carry different address families and can fail to attribute properly, even when the underlying user journey is genuine. This IP address dependency is especially relevant anywhere cross-device or household-level attribution comes into play, including CTV, where matching a living-room device to a mobile conversion often relies on IP-based signals.
With dual-stack IP support, you’ll see expanded attribution support across the full footprint of integrated ad networks, including premium platforms and publishers that leverage Atlas Performance as their supply performance system.
Dual-Stack IP Benefits
Dual-stack support improves Kochava’s ability to match attribution signals even when the app and media partner provide different IP address families. For example, if a publisher provides only IPv4 while the SDK primarily observes IPv6, Kochava can use the supplemental IPv4 collected by the SDK as an alternate matching signal.
Media partners supporting both IPv4 and IPv6 can provide both address families to Kochava, further improving the availability of matching signals across the attribution journey.
If you’re an integrated ad network or premium publisher leveraging Atlas Performance by Kochava, please contact integrations@kochava.com to discuss dual-stack IP support for your integration.
Getting Started
Since this release changes how deep link events are captured, it ships as a major SDK version. We recommend looping in your app development team now to scope the upgrade into an upcoming dev sprint cycle. Once the upgrade is complete, you can benefit from more complete reengagement attribution and broader dual-stack IP matching coverage.
Full technical release notes and upgrade guidance are available in the support documentation:
If you have questions about upgrade timing, dual-stack IP matching support for your account or partner mix, or how this update affects your specific integration, please reach out to your Client Success Manager or email support@kochava.com.
To stay up to date on the latest Kochava product updates and SDK releases, please subscribe to our newsletter.
