Kochava makes integration simple and easy whether you’re an advertiser, agency, network or publisher. For advertisers, the Kochava SDK (Software Development Kit) offers a lightweight yet powerful solution to everything from user acquisition to event tracking and LTV calculation. The Kochava SDK gives advertisers the peace of mind that Kochava is handling all of the heavy lifting from end-to-end testing protocols and SDK event queuing to 99.999% infrastructure uptime guarantee.
While Kochava supports S2S (server-to-server) integration the SDK method is the preferred option due to its reliability, versatility and configurability. The S2S option is designed for cases when tracking is desired during the SDK integration process or if an SDK integration is not possible due to issues like lack of source code access.
|Code lives in your app||API-based integration – no app update required|
|Communication and uptime managed by Kochava||Communication and uptime managed by your team|
|Codebase managed by Kochava||Codebase managed by your team|
As you can see from the table above, the total cost of ownership for SDK integration is significantly lower than S2S integration. If there’s still a question which integration type is the best fit, continue reading below to find out which features are exclusive to the SDK and which features are common to both integration types to further inform your decision.
The Kochava SDK is a turn-key solution which is the only SDK needed to manage over 3,800+ network integrations, attribute installs, and track all post-install activities including everything from location events to in-app purchases. The breadth of Kochava integrations with networks, publishers and 3rd-party services dramatically limits the number of 3rd party SDKs required to run a successful app. A single, stable SDK managed by Kochava simplifies update cycles, alleviates potential code conflicts, and provides peace of mind for the advertiser.
Implementing the Kochava SDK into an app is simple and flexible. Install tracking is the most basic level of implementation. Event tracking is simple and powerful and may be sent in a simple name/value fashion or in a JSON payload. Passing JSON objects within an event value allows advertisers to pass a SKU, discount amount, offer id, or any other meta data with the transaction. Here are some examples of JSON events. Of course all event metadata and values are available within reports and analytics for filtering, row-level reporting and visualization.
The SDK also offers automated session tracking, which is used to calculate loyalty and engagement metrics, Onboarding Links, deferred deep linking, Apple Watch integration, and iBeacon detection.
Reliability & Peace of Mind
Integrating the Kochava SDK means that you can focus on growing your business instead and let Kochava deal with the tracking.
- End-to-end testing methods
- Comprehensive troubleshooting protocols
- 99.999% tracking uptime guarantee
- Kochava-managed redundancy
- SDK install and event queueing (in cases of network connectivity issues or other activity interruption)
- Economies of scale for SDK innovation and maintenance
- Synchronized, globally-distributed and scalable infrastructure
- FIFO data flow from impression through post-install event
- Expeditious compliance with industry changes like iTunes IPV6 migration
Automated Session Tracking
The Kochava SDK tracks when an app becomes active or inactive. This allows you to understand session duration and frequency to inform your optimization efforts.
The Kochava SDK empowers advertisers to request the source of attribution from within the SDK. This attribution payload data is required for Deep Linking (sending a user directly to a specified in-app location), Deferred Deep Linking (sending a user directly to a specified in-app location after the user has downloaded the app) and Onboarding Links (serving a user an in-app experience contextual to the path of acquisition).
Toggles for Limit-Ad-Tracking & console logging
The Kochava SDK is highly configurable via server-side toggles, without an app update.These include defining which device IDs the SDK gathers, automated session tracking or even stopping tracking of specific events. This is useful for making mid-stream changes to your tracking, troubleshooting issues in the wild and ensuring that your app is always in compliance with your company’s security & privacy policies.
iBeacon detection (optional)
Kochava offers optional support to track real-world events with iBeacons and integrate those into your strategy.
Kochava supports all major platforms and frameworks including iOS, Android, Windows, Amazon, Cocos2d-x, Unity, Adobe AIR and Cordova (Phonegap). Kochava also has a web SDK to make tracking your sites and web apps simple, as well as first-class APIs for any custom integration you can think of.
SDK & S2S
Comprehensive Support (Including Super Publishers)
Kochava is integrated with every major network, including those which require SDK functionality. Because the Kochava SDK provides comprehensive integration with all integrated networks (Facebook, Twitter, Google, Snapchat, Amazon, IronSource, AdColony, Digital Turbine and many more) it is the only SDK you need. This single-SDK approach significantly minimizes potential complications in app update cycles and well as keep your app binary as lightweight as possible.
IdentityLink allows Kochava customers to associate an internal identifier with a Kochava device ID to manage their audience in unprecedented ways. By associating an internal customer identifier with a Kochava device ID, advertisers can correlate attribution and analytics information within Kochava to the customer’s behavior on different devices and platforms, as well as cross-compare data from internal or 3rd-party business intelligence tools in a meaningful way. IdentityLink gives advertisers actionable intelligence on all of their behavioral user data, regardless of where it exists, delivering a unified picture for more effective targeting, re-targeting, and optimization.
Flexible Event Methods
Tracking post-install events within Kochava provides a clear relationship between attribution source information and post-install behaviors. Kochava features a fully customizable event model with no pre-registration of events required. Events may be simple strings or rich JSON payloads full of event metadata. Here are some common event configurations. Any events the advertisers sends through the SDK are automatically provisioned within the Kochava dashboard. This model of event tracking offers a powerful window into user behavior including app launches, updates, purchases, etc., within a given timeframe. Within Kochava Analytics event data can be segmented by any available value including network, source, geo, and many others, in order to see which ad strategies are yielding the best ROAS. Here are some examples of the rich.
Setting up Kochava tracking on the Apple Watch is simple and straightforward. Attribution requires only a few lines of code, and any post-install events will be tracked via the existing dashboard. Kochava’s user dashboard will then let mobile app developers analyze key data points, providing actionable data on key performance indicators helping companies keep engagement and monetization high on the new platform. Access SDK integration documentation
An S2S integration utilizes an advertiser’s established server-side infrastructure to transmit install and event data to Kochava for attribution and analytics. Kochava processes this data in the same manner in which SDK traffic is processed, but it relies on the advertiser’s own infrastructure for all transmission, creating additional work and leaving the burden of maintenance on the advertiser.
S2S feeds also require round-the-clock monitoring by the advertiser’s team – Kochava tracking is only as good as advertiser IT performance. If the advertiser’s server stops sending data to Kochava, app intelligence and tracking capabilities are lost. With SDK integration, Kochava has architected several points of redundancy and data storage to ensure that even in cases of catastrophic hardware failure your data is always safe and always processed on a global FIFO (first-in-first-out) basis. In the case of S2S integration, any interruption of service or transmission will likely result in loss of data and can have a large potential impact on your ad campaigns and ultimately, revenue. The S2S method should be used in the following scenarios:
- Development team does not have access to edit the source code of the app(s).
- 3rd-party SDKs violate the company’s terms.
- Performance tracking is required before the next app update.
|End-to-end Testing Methods||X|
|Comprehensive Troubleshooting Protocols||X|
|99.999% Tracking Uptime Guarantee||X|
|SDK Install and Event Queueing||X|
|Expeditious Industry Compliance||X|
|Peace of Mind||X|
|Support for all connected devices||X||X|
|OTHER DATA ELEMENTS|
|Email Address Retrieval||X|
|Deferred Deep Linking||X|
|Custom Launch Experience||X|