Jump to a popular page, or start typing.
    Talk to our team

    CONNECTIONS / Mobile SDK / Mobile SDK to Meta App CAPI

    Your Mobile SDK and Firebase events, wired to Meta's App Conversions API.

    Connect Mobile SDK and point Signals at your Mobile SDK and Firebase 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.

    Talk to our team Explore the setup

    mobile-sdk -> meta-app-capi :: live

    1. ● mobile sdk → meta.capi :: live
    2. > read app_events rows=22,908
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 19,472 matched

    WHAT THIS ENABLES

    Mobile SDK to Meta App Conversions

    Mobile SDK to Meta App Conversions: your Mobile SDK and Firebase 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 Mobile SDK and Firebase 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 Mobile SDK and Firebase events by app teams on the Mobile SDK or Firebase.

    WHAT FLOWS WHERE

    Mobile SDK to App CAPI, mapped.

    Each sync hands the in-app purchase and install events from your Mobile SDK and Firebase events to Signals, which hashes and filters every record, then Meta's App Conversions API logs the app conversions for MAID and hashed-email matching.

    Each sync hands the in-app purchase and install events from your Mobile SDK and Firebase events to Signals, which hashes and filters every record, then Meta's App Conversions API logs the app conversions for MAID and hashed-email matching.

    WHO THIS IS FOR

    Built for the teams that own the number.

    App advertisers whose Meta results ride on post-install value, with the records already in Mobile SDK and Firebase in-app events.

    App teams on the Mobile SDK or Firebase activating Meta's App Conversions API straight from Mobile SDK and Firebase events.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      The Signals Mobile SDK or a Firebase export to feed Meta's App Conversions API, sized for MAID and hashed-email matching.

    2. Map

      Signals receives your Mobile SDK and Firebase events, and its columns map to Meta's App Conversions API in the visual mapper, hashed and checked for MAID and hashed-email matching.

    3. Deliver

      On each run, Signals pulls your Mobile SDK and Firebase 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 YOU GET

    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 Mobile SDK and Firebase events and forwards each app event as it arrives.

    In-app revenue Meta can optimize on from your Mobile SDK and Firebase 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 Mobile SDK and Firebase events.

    ON THE WIRE

    What App CAPI actually receives.

    signals :: mobile-sdk.meta-app-capi :: wire

    1. ● signals :: event payload
    2. > POST /{dataset}/events action_source=app source=mobile-sdk.app_events
    3. event_name "fb_mobile_purchase" · event_time 1784495524
    4. em sha256 "a17c4e…" · madid "8f2b…"
    5. advertiser_tracking_enabled 1 · value 2578 · currency AED
    6. ✓ events_received 1 · dedupe matched
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Mobile SDK

    Mobile SDK to TikTok App eAPI

    Mobile SDK to TikTok App Events API: your Mobile SDK and Firebase events, hashed and…

    Learn more

    from Mobile SDK

    Mobile SDK to Snap App CAPI

    Mobile SDK to Snap App Conversions: your Mobile SDK and Firebase events, hashed and…

    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 more

    generic

    Meta App CAPI

    Datahash configures Meta App Events API using data from your MMP or SDK, verified against…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Mobile SDK Meta App CAPI sync run?

    Delivery tracks Mobile SDK, run by app teams on the Mobile SDK or Firebase: a near-real-time or scheduled sync of your Mobile SDK and Firebase events feeds Meta on that cadence. Each run forwards each app event as it arrives, so in-app revenue Meta can optimize on holds up on MAID and hashed-email matching. The live debugger confirms every delivery inline.

    What match rate should a Mobile SDK-sourced Meta App CAPI batch expect?

    Match rate follows identifier coverage in your Mobile SDK and Firebase events, which app teams on the Mobile SDK or Firebase control, not Mobile SDK itself. A record with a current hashed email or phone matches for Meta; one missing both cannot. First-run feedback from App Conversions API pinpoints MAID and hashed-email matching, the number app teams on the Mobile SDK or Firebase tune against.

    NEXT STEP

    Mobile SDK to Meta App CAPI, in production this week.

    Talk to our team All Mobile SDK use cases