Overview
Kochava is a mobile measurement platform (MMP) that attributes installs and in-app events using click trackers and server-to-server postbacks.
Click Trackers
Macro-based click attribution via click_id.
Postbacks
Install and in-app event callbacks via S2S.
Cost & Revenue
Cost API plus revenue and ROI reporting.
Make sure you have access to your Kochava network/publisher partner setup and Affclix Mobile Tracking settings.
Attribution Flow
User Clicks Tracker
Kochava captures the click and device identifiers; click_id travels in the tracker.
App Installation
Kochava attributes the install to the original click.
Postback Triggered
Install or in-app event is sent to Affclix via S2S callback.
Conversion Logged
Affclix verifies the signature, normalizes, deduplicates and records the conversion.
Click Tracker
Kochava click trackers carry campaign and network identifiers plus the click_id returned later through postbacks.
https://control.kochava.com/v1/cpi/click
?campaign_id={campaign}
&network_id={publisher}
&site_id={affiliate_id}
&creative_id={creative}
&click_id={click_id}Pass click_id on the tracker — it must be returned in every postback for attribution to succeed.
Postback Configuration
Kochava fires install and event postbacks to the Affclix receiver. The integration is identified by its unique slug; authenticity is verified by the per-platform HMAC signature header.
POST https://track.your-domain.com/postback/mmp/{slug}
?tid={click_id}
&event={event_name}
&revenue={event_data}
¤cy={currency}Copy Postback URL
Open Mobile Tracking → Kochava and copy the generated URL.
Configure Partner
Add the URL in Kochava partner setup and map click_id → tid, event_data → revenue.
Enable Events
Enable install and in-app event postbacks.
Event & Revenue Tracking
Kochava passes the event name and value on each postback:
event_name=purchase
event_data=9.99
currency=USDInstall Events
Automatically reported after attribution.
Custom Events
Signup, purchase and custom in-app actions.
Cost Reporting
Pull spend via the Kochava reporting API for ROI.
Fraud Prevention & Best Practices
- Verify HMAC signatures on every callback.
- Always pass click_id and return it as tid.
- Deduplicate conversions using click_id and event name.
- Include revenue and currency for purchase events.
- Use HTTPS endpoints only.