Kochava-Certified Postbacks allow Kochava users to send a real-time feed of installs and in-app events to a Kochava-Certified partner. The endpoints and parameters included in these postbacks are defined within the integration, and managed by Kochava in conjunction with each specific partner. The Kochava-Certified Postback is the easiest way to establish a postback and should be used as the default method.
NOTE: Within Kochava, it is possible to create custom postbacks. For more information on creating a custom postback, refer to our Create a Custom Postback support document.
Create a New Postback Configuration
- Log in to Kochava.
- Select the desired Account and App.
- Select Apps & Assets > 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 Configuration.
- Select Media Partner.
- Click Save.
Edit Postback
- For an Install Event Postback, Click Install > Postback Tools > 🖉 (Edit).
- For Post-Install Active Events, locate the desired event and Click Edit Postback.
- Enter the Package Name (Android) or Bundle ID (iOS).
NOTE: The Package name is easily located in the URL of the app on the Google Play store. (id=com.packagename)
NOTE: The Bundle ID must be obtained from the app developer, the app manager or the Apple Store. For more information, refer to our Locating the Apple Bundle ID support document.
- Select a Delivery Delay.
NOTE: The Delivery Delay determines whether the postback is delivered in realtime or if there is an intentional delay before delivery. Delivery Delay can be set from 30 seconds to up to 10 minutes.
BEST PRACTICE: Selecting All will send all installs to the network, but will only include attribution information for installs attributed to that network. A common use case for delivering All is to enable the network to optimize targeting away from users who have already installed the app, even if that network did not drive the install.
- 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.
A. Click to edit Install Postback
B. Locate to desired Event and Click Edit Postback.
A. Realtime to 10 Minute Delay
B. Do Not Retry to 10 Attempts
C. All, Network Only, or Network + Agency
- Select the Delivery Method.
NOTE: The Delivery Method determines whether the partner will receive all events/installs or only those for which they have won attribution.
- Click Save.
NOTE: Updates to Kochava-Certified Postback will automatically take affect for the currently-configured postbacks.
Network Specific Fields
Network Specific fields contain data that is required for postbacks to be properly sent to network partners based on the desired delivery settings. It is very important that the network specific fields be properly set up. For example, Facebook requires a Facebook App ID and specific event names for proper attribution.
For more information about Network Specific Fields, contact your Kochava Client Success Managers.
Creating a Postback on a Standard SessionBegin SDK Event
The following details are associated with creating a SessionBegin Postback within Kochava:
- Attribution can occur on a single session per device per 24-hour period, starting 24 hours after the install.
- If the SessionBegin Postback is configured and set to Network Only, a single Postback will be sent per device per 24-hour period starting 24 hours after the initial install (or prior reengagement) if the install was attributed to that network or if the device converted on a Reengagement tracker for that network.
- If the SessionBegin Postback is configured and set to All, a single Postback will be sent per device per 24-hour period starting 24 hours after the initial install regardless of attribution source, and will include Unattributed data.
- For all Postback session data to be sent to an internal database or to an analytics platform, a custom App Open event must be used.