Search

Claravine + Kochava Integration

Julia Randall
Julia Randall
  • Updated

Kochava is a mobile measurement partner that enables advertisers with mobile apps to track conversions from marketing channels to their apps. Claravine offers a Kochava outbound connector; use this article to integrate and use it. Refer also to Kochava's documentation.

Integrate Claravine's Kochava outbound conector to:

  • Create a SmartLink with Universal Link support by including the correct subdomain.
  • Use a consistent taxonomy for campaign name, SmartLink name, and tracker name.
  • Create a SmartLink with custom parameters on the in-app destination based on Claravine Templates.
  • Create a SmartLink with a catch-all tracker destination that includes custom parameters defined in Claravine Templates.
  • Create a SmartLink with Custom Parameters.

There are no rate limits on SmartLink creation. Refer to Kochava's documentation for SmartLinks. 

Connect Claravine and Kochava

The only required field to set up your Claravine account with a Kochava outbound connector is the API Key, which you can find in the Kochava dashboard. 

  1. In Kochava, navigate to Dashboard → Account Options → Members and click on the icon next to the three dots.
  2. Follow the instructions in Configure a Platform Connector in Claravine to create the Kochava connector.
  3. You can also configure custom field mappings. These include remote field IDs and field labels for each third-party system. 
  4. When you save the integration, Claravine will validate the provided API Key, and will show an error if it is not valid. 
  5. Note that if you later update your integration (for instance, to add more mappings or change its name or description), you must provide the Kochava API key again when you save your changes. 

Kochava Fields Available for Integration

Field Label Req'd Inbound Outbound Notes
App Group Campaign ID Y ✔ ✔
Catch-All App Y   ✔
Channel Type Y   ✔
SmartLink Name Y   ✔
Network ID Y ✔ ✔
App Group Campaign Name Y ✔ ✔
Catch-All Destination Y   ✔
Subdomain N   ✔
Remote_field_1 N   ✔
Android Tracker Name Mostly   ✔ While not required, typical Kochava integrations have both an iOS and an Android integration
Android, if app is not installed, Destination Mostly   ✔ While not required, typical Kochava integrations have both an iOS and an Android integration
Android, if app is installed, Destination Mostly   ✔ While not required, typical Kochava integrations have both an iOS and an Android integration
iOS Tracker Name Mostly   ✔ While not required, typical Kochava integrations have both an iOS and an Android integration
iOS, if app is not installed  Destination Mostly   ✔ While not required, typical Kochava integrations have both an iOS and an Android integration
iOS, if app is installed, Destination Mostly   ✔ While not required, typical Kochava integrations have both an iOS and an Android integration
Path Mostly   ✔ Set the in-app destination when the app is installed
Agency ID N   ✔
Ad Pricing Model N   ✔
Ad Price N   ✔
Conversion App N   ✔
Conversion Events Mostly   ✔ Should be selected per Kochava (specific options available)
Roku, if app is not installed, Tracker Name N   ✔
Roku Destination N   ✔
Roku, if app is installed, Destination N   ✔
Kindle Tracker Name N   ✔
Kindle, if app is not installed, Destination N   ✔
Kindle, if app is installed, Destination N   ✔

Comments

0 comments

Article is closed for comments.