On this page

Kochava (Post-install)

Beta

This feature is in Beta. The feature may continue to evolve, and this documentation may not yet reflect the latest updates.

This integration is in closed beta. Contact your Amplitude Client Success Manager for support.

Kochava provides advertisers and publishers with a platform that helps growth marketers establish customer identity and segment and activate audiences in a privacy-first world.

Choose the correct integration

This page covers events that occur after users install your app, often called "custom events": user interactions, purchases, and other in-app activities. It guides you through setting up post-install events and connecting user identities to their actions.

There are two integrations, documented separately: "Kochava (Post-Installs) Event streaming" and "Kochava (Installs) events streaming." Kochava's IdentityLink feature requires that identity data arrive with or after the related event data. "Kochava (Post-Installs)" covers events after app installation and includes the "Send User" feature to link identities to actions. "Kochava (Installs) events streaming" covers initial app installations and omits "Send User" because install data must arrive first.

Use cases

Sending events from Amplitude to Kochava improves communication strategies and drives higher-value conversions through targeted messaging:

  • Campaign ROI insights: Correlate user actions tracked by Amplitude with marketing campaigns in Kochava for accurate attribution and optimized budget allocation.
  • Personalized ad targeting: Combine Amplitude's user behavior data with Kochava's audience segmentation to deliver tailored ads based on user interactions.
  • LTV analysis and retention: Analyze user behavior from Amplitude in Kochava to identify high lifetime value users for targeted retention strategies.

Considerations

  • You must enable this integration in each Amplitude project that uses it.
  • You need a Kochava account to enable this integration.
  • Amplitude has two destinations: Kochava (Install) and Kochava (Post Install).
    • Amplitude supports identity (user-attributes) forwarding to Kochava only in Kochava (Post Install).
  • Amplitude uses Kochava's IdentityLink API to send user attributes, which links user-level data with the device ID. The user attributes Amplitude sends don't link if Kochava doesn't receive the Install event with the same device ID first.
  • Send User feature: Available in the Post Install Events destination, this feature sends IdentityLink data along with other event data so Kochava can connect actions to the right user.
  • Relevant limits for Kochava events:
    • Kochava doesn't impose hard limits on quantity or velocity. Requests sent too quickly return 429 responses, which Amplitude handles automatically.
    • Requests must be smaller than 2MB.

Set up the integration

Prerequisites

To configure an Event Streaming integration from Amplitude to Kochava, you must meet the following Kochava prerequisites:

  • A Kochava account: You must have a Kochava account. Contact Kochava for more details.
  • Kochava App GUID: You must create an App and have the GUID assigned to it.
  • (Optional) Kochava API Key: To enable authentication with the integration, add your API Key in the Account Option.
  • (Optional) Kochava secret authentication key: To enable authentication with the integration, request a secret authentication key through the Kochava Client Success Team.

Kochava setup

  1. Log into your Kochava dashboard and copy your Account ID and Account Passcode.
  2. Go to the All Apps section and copy the GUID of the App you created.
  3. (Optional) Go to Account Options and select API Keys to locate or create your API key.
  4. (Optional) Contact your Kochava Client Success Manager to obtain your Kochava secret authentication key.

Amplitude setup

  1. In Amplitude, go to Data Destinations, then find Kochava (Post Install).
  2. Enter a sync name, then click Create Sync.
  3. Toggle Status from Disabled to Enabled.
  4. Paste your App GUID.
  5. (Optional) Click the single box Enable Authentication to authenticate your sync.
  6. (Optional) Paste your API Key (taken from the Kochava account).
  7. (Optional) Paste your secret key to API secret (provided by Kochava's CS team).
  8. Under Send Events, make sure the toggle is enabled ("Events are sent to Kochava") to stream events to Kochava. When enabled, events forward to Kochava automatically when Amplitude ingests them. This integration doesn't send events on a schedule or on demand.
  9. In Select and Filter events, choose which events to send. Choose only the events you need in Kochava. Transformed events aren't supported.
  10. Click Mappings to specify the identity mapping between Amplitude and Kochava. Kochava Device ID and IP Address (the IP address of the device on install) are required to save your sync configuration. Choose at least one of the following identifiers: Apple Advertising ID (idfa), Apple Vendor ID (idfv), Google Advertising ID (adid), or Android ID (android_id).
  11. (optional) In Select additional properties, select any more user properties to send to Kochava. If you don't select any properties here, Amplitude doesn't send any. Transformed event properties and transformed user properties aren't supported.
  12. (optional) Under Send Users, make sure the toggle is enabled to send users and their properties in real time whenever a user is created or a user property is updated in Amplitude.
  13. (optional) In Select additional properties, select any more user properties to send to Kochava. If you don't select any properties here, Amplitude doesn't send any. Transformed user properties aren't supported.
  14. When finished, enable the destination and Save.

Kochava Device ID compared to other identifiers

Send the Kochava Device ID as a unique string that is consistent for each instance of the app on a single device. Other identifiers (for example, Apple Advertising ID and Google Advertising ID) are mobile advertising IDs. A Kochava device can have multiple device IDs, but the Kochava Device ID must be unique. The Kochava Device ID can be technically the same string as the other identifiers, but it's a different concept.

Was this helpful?