Support Home > Server-to-Server Integration > Post-Install Event Setup

Post-Install Event Setup

This feature is available only with paid Kochava accounts. Contact us to learn more.

Feature Summary: This document describes the recommended approach to integrate with the Kochava system to track post-install events. It is important to follow these API instructions in order to avoid data corruption and maximize the effectiveness of Kochava in your environment.


NOTE: For examples of post-install events, refer to our Post-Install Event Examples support documentation.


BEST PRACTICES: If strict authentication rules are being utilized, ensure that the procedures and policies within the Kochava Install Authentication Integration support documentation have been followed.

Install and Startup Tracking

To track the installation and startup of your application, please refer to the Server-to-Server Install Notification Integration Guide. Once Kochava has registered an install for a device, features can be tracked via server-to-server API according to the specifications provided here.

Post-Install Event API

To send a usage event from your application, call the following endpoint with a POST payload containing the desired JSON elements.


JSON Property Description Req.
kochava_app_id This is the unique application ID used to represent the app. Yes
app_version A string representation of the application version number. No
kochava_device_id kochava_device_id should be sent as a unique string that is consistent for each instance of the app on a single device. This will allow Kochava to associate data correctly when a device_id is not available. In the case that there will always be a device_id present and installs will always be sent before post-install events, kochava_device_id can be sent as an empty string.
device_ids This can be the IDFA, Android ID or a custom variant. You must submit at least one identifier within the device_id object, and may submit more than one. Yes
action Action associated to the API event. Yes
origination_ip The IP address of the device on install. Yes
device_ver Send the device_ver as an empty string, example “device_ver”: “”. Yes
device_ua A string representation of the device user agent as provided by the client. Please ensure that this is URL-encoded. This string is useful when campaigns require fingerprint attribution. Yes
usertime The time the event was completed by the user in Epoch format. No
data Each event is a JSON object – see examples.

event_name -> A string representation of an event that has happened.

event_data -> A corresponding value associated to the event_name. event_data is not required but useful for monetary tracking for correlated events (e.g. event_name -> “Level DLC Purchased” and event_value -> “20”).


WARNING: kochava_app_id, kochava_device_id, device_ids, action, origination_ip, device_ver, device_ua, and data keys MUST be included on post-install event payloads. Otherwise, the post-install events will not be properly associated to the install, which has several implications, such as lack of attribution associated to the event and minimum time to reengagement windows not being applied.


NOTE: kochava_device_id can be sent as an empty string, as long as a device id is being sent and vice versa. device_ver can also be sent as an empty string. The parameters themselves indicated in the above table however, must be included in the post-install event payload.


BEST PRACTICES: Send the event data as a JSON object per the example below.


Sample Event Calls:

Device Specific Instructions

The information below details how to send data from specific devices to Kochava through the server-to-server integration.

Device Sending a Usage Event Details
Roku Send GetDeviceUniqueId() as String within the UDID parameter of the S2S feed.


Last Modified: Aug 3, 2020 at 10:12 am