CONNECTIONS / Kochava / Kochava to Meta App CAPI
From Kochava events to Meta's App Conversions API.
Connect Kochava and point Signals at your Kochava events; it sends in-app purchases and installs to Meta so app campaigns optimize on revenue as in-app events fire, hashed and consent-checked for Meta.
- ● kochava → meta.capi :: live
- > read app_events rows=60,273
- hash sha256(email,phone) consent=filtered
- route meta deliver
- ✓ delivered · 43,999 matched
WHAT THIS ENABLES
Kochava to Meta App Conversions
Kochava to Meta App Conversions: Signals reads your Kochava events and sends in-app purchases and installs to Meta so app campaigns optimize on revenue, hashed and consent-checked as in-app events fire.
- In-app purchase and install events from your Kochava events activated for Meta, as Signals sends in-app purchases and installs to Meta so app campaigns optimize on revenue.
- App revenue events Meta can bid on beyond the MMP's last-click view, drawn from your Kochava events by app marketers running Kochava.
WHAT FLOWS WHERE
Kochava to App CAPI, mapped.
Signals reads the in-app purchase and install events from your Kochava events as in-app events fire, hashes and screens each record, and posts the app conversions to Meta's App Conversions API, keeping MAID and hashed-email matching in view.
Signals reads the in-app purchase and install events from your Kochava events as in-app events fire, hashes and screens each record, and posts the app conversions to Meta's App Conversions API, keeping MAID and hashed-email matching in view.
Built for the teams that own the number.
App marketers running Kochava activating Meta's App Conversions API straight from Kochava events.
From kickoff to verified events.
-
Connect
A Kochava postback to Signals to feed Meta's App Conversions API, sized for MAID and hashed-email matching.
-
Map
Signals receives your Kochava events, and its columns map to Meta's App Conversions API in the visual mapper, hashed and checked for MAID and hashed-email matching.
-
Deliver
On each run, Signals pulls your Kochava events, sends in-app purchases and installs to Meta so app campaigns optimize on revenue, and forwards each app event as it arrives, with MAID and hashed-email matching in the debugger.
What ships with this use case.
App revenue events Meta can bid on beyond the MMP's last-click view on every run, as Signals reads your Kochava events and forwards each app event as it arrives.
In-app revenue Meta can optimize on from your Kochava events, with event volume steady because Signals forwards each app event as it arrives.
A per-run match report from Meta's App Conversions API on MAID and hashed-email matching, straight out of your Kochava events.
What App CAPI actually receives.
- ● signals :: event payload
- > POST /{dataset}/events action_source=app source=kochava.app_events
- event_name "fb_mobile_purchase" · event_time 1783964620
- em sha256 "a17c4e…" · madid "8f2b…"
- advertiser_tracking_enabled 1 · value 1805 · currency AED
- ✓ events_received 1 · dedupe matched
Adjacent moves on the same stack.
from Kochava
Kochava to TikTok App eAPI
Kochava to TikTok App Events API: Signals reads your Kochava events and reports in-app…
Learn more
from Kochava
Kochava to Snap App CAPI
Kochava to Snap App Conversions: Signals reads your Kochava events and posts in-app…
Learn more
same use case
Adjust to Meta App CAPI
Adjust to Meta App Conversions: Signals reads your Adjust postbacks and sends in-app…
Learn moregeneric
Meta App CAPI
Datahash configures Meta App Events API using data from your MMP or SDK, verified against…
Learn moreAsked on almost every call.
How often does the Kochava Meta App CAPI sync run?
The pace follows your Kochava events: Signals sends changes from Kochava to Meta as in-app events fire. Because it forwards each app event as it arrives, app revenue events Meta can bid on beyond the MMP's last-click view stays current while app marketers running Kochava keep MAID and hashed-email matching in view. Delivery needs no export and no manual upload.
What match rate should a Kochava-sourced Meta App CAPI batch expect?
Coverage of hashed identifiers across your Kochava events decides it, and app marketers running Kochava own that inside Kochava. A live email or phone matches into Meta; neither, and it will not. First-run feedback flags MAID and hashed-email matching, which app marketers running Kochava then raise inside your Kochava events.
NEXT STEP