CONNECTIONS / App Events / App Events to Meta App CAPI
Your app conversion events, wired to Meta's App Conversions API.
Connect App Events and point Signals at your app conversion 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.
- ● app events → meta.capi :: live
- > read app_events rows=62,122
- hash sha256(email,phone) consent=filtered
- route meta deliver
- ✓ delivered · 51,561 matched
WHAT THIS ENABLES
App Events to Meta App Conversions
App Events to Meta App Conversions: your app conversion events, hashed and consent-checked, feed Meta as Signals sends in-app purchases and installs to Meta so app campaigns optimize on revenue as in-app events fire.
- In-app purchase and install events from your app conversion 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 app conversion events by app teams sending conversion events.
WHAT FLOWS WHERE
App Events to App CAPI, mapped.
Signals receives the in-app purchase and install events from your app conversion events; Signals hashes and consent-screens each record before Meta's App Conversions API accepts the app conversions for MAID and hashed-email matching.
Signals receives the in-app purchase and install events from your app conversion events; Signals hashes and consent-screens each record before Meta's App Conversions API accepts the app conversions for MAID and hashed-email matching.
Built for the teams that own the number.
App teams sending conversion events activating Meta's App Conversions API straight from app conversion events.
From kickoff to verified events.
-
Connect
Your app event stream pointed at Signals to feed Meta's App Conversions API, sized for MAID and hashed-email matching.
-
Map
Signals receives your app conversion 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 app conversion 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 app conversion events and forwards each app event as it arrives.
In-app revenue Meta can optimize on from your app conversion 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 app conversion events.
What App CAPI actually receives.
- ● signals :: event payload
- > POST /{dataset}/events action_source=app source=app-events.app_events
- event_name "fb_mobile_purchase" · event_time 1784206532
- em sha256 "a17c4e…" · madid "8f2b…"
- advertiser_tracking_enabled 1 · value 3086 · currency AED
- ✓ events_received 1 · dedupe matched
Adjacent moves on the same stack.
from App Events
App Events to TikTok App eAPI
App Events to TikTok App Events API: your app conversion events, hashed and…
Learn more
from App Events
App Events to Snap App CAPI
App Events to Snap App Conversions: your app conversion events, hashed and consent-checked,…
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 App Events Meta App CAPI sync run?
The pace follows your app conversion events: Signals sends changes from App Events 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 teams sending conversion events keep MAID and hashed-email matching in view. Delivery needs no export and no manual upload.
What match rate should a App Events-sourced Meta App CAPI batch expect?
Coverage of hashed identifiers across your app conversion events decides it, and app teams sending conversion events own that inside App Events. A live email or phone matches into Meta; neither, and it will not. First-run feedback flags MAID and hashed-email matching, which app teams sending conversion events then raise inside your app conversion events.
NEXT STEP