Meta App CAPI
Meta App CAPI, live end-to-end.
Datahash configures Meta App Events API using data from your MMP or SDK, verified against Meta Events Manager.
- ● meta.app_capi :: live
- > event fb_mobile_purchase value=899 THB
- hash sha256(em) madid=att_authorized
- dedupe vs sdk_event matched
- ✓ delivered · app event accepted
WHAT THIS ENABLES
Meta App CAPI
Meta App CAPI is the server-side delivery of in-app events from your MMP or SDK to Meta's App Conversions API, deduplicated against Meta SDK events and routed with each user's ATT opt-out status respected.
- iOS conversion signal rebuilt after ATT, without leaning on aggregated event measurement alone.
- App and web outcomes measured on one pipeline instead of two disconnected stacks.
- Post-install revenue events made available to Meta for value-based app campaign optimization.
Built for the teams that own the number.
Teams that want app and web conversion measurement on one pipeline.
From kickoff to verified events.
-
Ingest
MMP or direct SDK ingestion from AppsFlyer, Adjust, Branch, and others.
-
Configure
App CAPI destination with your Meta dataset.
-
Dedupe
Deduplication against SDK events so nothing double counts.
-
Route
ATT-aware routing that respects opt-out status.
WHAT FLOWS WHERE
One use case, every source.
An in-app purchase fires through your MMP or SDK, Signals hashes the identifiers and checks ATT status, then delivers the event to Meta's App Conversions API.
An in-app purchase fires through your MMP or SDK, Signals hashes the identifiers and checks ATT status, then delivers the event to Meta's App Conversions API.
What ships with this offering.
Server-side app events verified in Meta Events Manager.
Dedupe against your existing Meta SDK events.
Better optimization signal on iOS in the ATT world.
ON THE WIRE
What the platform actually receives.
Identifiers are hashed with SHA-256 at source. The payload the destination sees never contains raw PII.
- ● signals :: event payload
- > POST /{dataset}/events action_source=app
- event_name "fb_mobile_purchase" · event_time 1789002233
- em sha256 "a17c4e…" · madid "8f-2b…"
- advertiser_tracking_enabled 1 · value 899 · currency THB
- ✓ events_received 1 · dedupe matched
Adjacent moves on the same stack.
meta
Meta Web CAPI
Datahash is a Meta Business Partner. We set up Meta Conversions API on your website server-side, deduped with your existing Meta Pixel, hashed and privacy-safe.
Learn more
snap
Snap App CAPI
Server-side app conversion tracking into Snap, integrated with your MMP.
Learn moremeta
Meta Offline CAPI
Datahash ingests offline transactions from your POS, CRM, or warehouse and routes them to Meta with hashed identifiers, event dedupe, and closed-loop match reporting.
Learn moreBring it from where the data lives.
Every source that supports this use case. Pick a platform to see the exact setup.
Custom
Questions your team will ask.
Does this work with AppsFlyer, Adjust, and Branch?
Yes. Datahash ingests postbacks or exports from the major MMPs, including AppsFlyer, Adjust, Branch, Kochava, and Singular, and maps each event to Meta's App Conversions API schema. If you run your own SDK events instead of an MMP, we can ingest those directly. Either path arrives hashed and deduplicated against existing Meta SDK events before delivery.
Do we still need the Meta SDK?
Keeping the Meta SDK is recommended alongside App CAPI. The SDK still handles in-app signals CAPI cannot see on its own and gives Meta a second delivery path for the same events. Datahash dedupes the two streams using a shared event identifier, so Meta counts each purchase or install once instead of twice, and Events Manager shows the match rate for both paths.
How is dedupe handled between SDK and server events?
Both paths carry a shared event identifier that Meta uses to reconcile the two deliveries. When the same event arrives twice within Meta's dedupe window, once from the SDK and once from server-side App CAPI, Meta keeps a single copy instead of double counting the purchase or install. Datahash verifies the dedupe match rate in Events Manager before go-live and monitors it afterward.
NEXT STEP
Live in fifteen minutes. Measurable in a week.
Talk to our team of solutions engineers. We map your source data, propose an integration plan, and give you a live setup in the same call where possible.