This feature is available only with paid Kochava accounts. Contact us to learn more.
Custom postbacks allow marketers to send a real-time feed of data captured by Kochava to a specific endpoint. This is particularly useful if your team has internal tools/endpoints that are built to analyze/store data for your apps.
NOTE: Within Kochava, it is possible to create Kochava-Certified Postbacks. For more information, refer to our Kochava-Certified Postbacks support document.
Use Cases for Custom Postbacks:
A Custom Postback enables Kochava users to perform tasks such as:
- Post a real-time feed of install and post-install events to an endpoint (e.g., data warehouse)
- Customize which parameters are sent on postback
- Create postbacks on demand
Create a Custom Postback
- Log in to Kochava.
- Select the desired Account and App.
- Select App Configurations > Partner Configuration.
Feature Note: To add this menu item to your Favorites Menu, select the “+” sign that appears when you hover over the menu. The Features Menu provides quick access to your most frequently visited areas of the Kochava UI.
- Click + Add a Custom Postback.
NOTE: In the next step, a custom event will be selected. If a custom event has not already been created, refer to our Post-Install Event Creation support documentation before preceding.
- Select the desired Event.
- Click Next.
- Set the event Status. (By default, this option is set to Active)
- Enter the Destination URL.
The destination URL is the endpoint that you wish to have data sent to, typically a clients own internal servers. After entering the desired endpoint, you can add data parameters into the query string of the URL (query string is everything that follows the “?” in the URL). Data parameters are key/value pairs in which data is delivered through. You can determine the naming conventions for your keys, and then the values can be established using the available dynamic macros that are seen below. Example: “event_name={event_name}“. Data parameters must be separated by “&“.
Available Macros
| Macro | Function |
Install |
Event |
|---|---|---|---|
| {} | Name set for registered event, will be “_install” for installs. | ✔ | ✔ |
| {} | Numerical data provided with event (if present). | ✔ | |
| {} | Numerical data provided with event (if present). | ✔ | |
| {} | Datetime of event. | ✔ | ✔ |
| {} | IP address of device on which event was performed. | ✔ | ✔ |
| {} | User Agent of the device on which the event was performed. | ✔ | ✔ |
| {} | IDFA of the device on which the event was performed. | ✔ | ✔ |
| {} | ADID of the device on which the event was performed. | ✔ | ✔ |
| {} | Android ID of the device on which the event was performed. | ✔ | ✔ |
| {} | Kochava Device ID of the device on which the event was performed. | ✔ | ✔ |
| {} | Name of the network responsible for the event conversion. | ✔ | ✔ |
| {} | ID of the campaign responsible for the event conversion. | ✔ | ✔ |
| {} | Name of the campaign responsible for the event conversion. | ✔ | ✔ |
| {} | Name of the Kochava tracker responsible for the event conversion. | ✔ | ✔ |
| {} | ID of the Kochava tracker responsible for the event conversion. | ✔ | ✔ |
| {} | Value received in site_id field, as received on the click. | ✔ | ✔ |
| {} | Value received in creative_id field, as received on the click. | ✔ | ✔ |
| {} | Time that the attribution occurred. | ✔ | ✔ |
| {} | The limit_tracking flag, as set by the developer within the app. | ✔ | ✔ |
| {} | The limit_tracking flag as set by the user within the OS of their device. | ✔ | ✔ |
| {} | Type of device identifier by which the event was attributed. | ✔ | ✔ |
| {} | ID of the click within Kochava. | ✔ | ✔ |
| {} | The city in which the event occurred. | ✔ | ✔ |
| {} | The ISO 3166-1 country code from which the event occurred. | ✔ | ✔ |
| {} | The version number of the device. | ✔ | ✔ |
| {} | The type of device that triggered the event. | ✔ | ✔ |
| {} | Optional event attribute key. | ✔ | |
| {} | Optional event attribute key. | ✔ | |
| {} | Optional event attribute key. | ✔ | |
| {} | Optional event attribute key. | ✔ | |
| {} | Optional event attribute key. | ✔ | |
| {} | Optional event attribute key. | ✔ | |
| {} | Optional event attribute key. | ✔ | |
| {} | Optional event attribute key. | ✔ | |
| {} | Optional event attribute key. | ✔ | |
| {} | Optional event attribute key. | ✔ | |
| {} | Optional event attribute key. | ✔ | |
| {} | Optional event attribute key. | ✔ | |
| {cp_0} | Optional attribute key. | ✔ | ✔ |
| {cp_1} | Optional attribute key. | ✔ | ✔ |
| {cp_2} | Optional attribute key. | ✔ | ✔ |
| {cp_3} | Optional attribute key. | ✔ | ✔ |
| {cp_4} | Optional attribute key. | ✔ | ✔ |
| {cp_5} | Optional attribute key. | ✔ | ✔ |
| {cp_6} | Optional attribute key. | ✔ | ✔ |
| {cp_7} | Optional attribute key. | ✔ | ✔ |
| {cp_8} | Optional attribute key. | ✔ | ✔ |
| {cp_9} | Optional attribute key. | ✔ | ✔ |
- Set Event Matching. (optional)
NOTE: The Event Matching field allows the event to be modified to another custom event. This field only needs to be modified if the event that was initially selected is no longer the event that is needed.
- Select a Delivery Delay.
NOTE: The Delivery Delay determines whether the postback is delivered in real time or if there is an intentional delay before delivery. The Delivery Delay can be set from real-time delivery up to a delay of 10 minutes.
- Set the Supply Network Data to Analytics Partner. (optional)
NOTE: Selecting “True” will send attribution-level data to the associated partner, while choosing “False” will not send the attribution-level data.
- Select Retry Attempts.
NOTE: The Retry Attempts determines the number of times Kochava will attempt to redeliver an event postback upon posting failure. Retry Attempts can be set from Do Not Retry to up to 10 attempts.
- Click Save.