CONNECTIONS / Kochava
Kochava postbacks, delivered to every ad platform.
Kochava already resolves attribution and filters fraud on install, re-engagement, and in-app events. Signals reads the same postback and delivers it server-side to Meta, Snap, and TikTok's app conversions APIs, deduped against SDK traffic and ATT-aware on iOS.
- ● kochava :: postback received
- > Postback received event=install network=Apple Search Ads
- > Postback received event=purchase value=42.00 USD
- hash sha256(idfa,email) att=authorized
- route meta · snap · tiktok
- ✓ 3 destinations synced · postback delivered
The signal Kochava yields.
Every kind of signal that moves between Kochava and the platforms, through one hashed, deduplicated route.
- App conversions
- Every install or re-engagement Kochava attributes reaches Meta, Snap, and TikTok's app conversion APIs server-side, whether the attribution model is deterministic or SKAdNetwork.
Pick your platform. Every use case for it, in one place.
Every way Kochava data moves, grouped by platform and ranked by how many use cases Kochava supports.
Meta 1 
Snap 1 
TikTok 1 From authorization to delivered signal.
-
Point the postback
Kochava's postback URL for install, re-engagement, and in-app events is set to Signals' endpoint alongside whatever ad networks it already feeds.
-
Map attributed events
Each postback field maps to the matching event in Meta, Snap, and TikTok's app conversion schema in the visual mapper, including SKAdNetwork-only conversions.
-
Dedupe against the SDK
Postback events are deduped against the platform SDK on shared event IDs, so a purchase Kochava attributes and the SDK also logs posts once, not twice.
-
Deliver, ATT-aware
Server-side delivery to every mapped destination, with iOS routing that adapts to whether the user granted tracking, verified in the live debugger.
Kochava questions, answered.
Does Signals replace Kochava's own network integrations?
No. Kochava keeps sending attribution data to whatever ad networks it already integrates with; Signals reads the same postback and forwards the attributed event to each ad platform's app conversions API server-side. Kochava's attribution engine and fraud filtering stay exactly where they are. Signals only adds the delivery layer ATT broke.
What happens to installs Kochava attributes through SKAdNetwork instead of a device ID?
SKAdNetwork-attributed conversions still arrive as a Kochava postback, just with the fields Apple allows: a conversion value and campaign ID instead of a device identifier. Signals forwards what is present rather than requiring a device ID, so a privacy-attributed install reaches the ad platform's app conversions API alongside deterministic ones.
Does Signals see traffic Kochava's fraud filtering has already blocked?
No. Signals only reads the postback Kochava sends after its own fraud detection has resolved the event, so an install or click Kochava flags as invalid never generates a postback and never reaches an ad platform through Signals. Filtering stays entirely inside Kochava, upstream of anything Signals touches.
NEXT STEP
See your Kochava data working in every ad platform.
Ready to enable a use case, or still mapping what Kochava data could do? Our team helps you find the right place to start.
