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

    CONNECTIONS / Branch / Branch to Meta App CAPI

    Branch events into Meta, built for Meta's App Conversions API.

    Signals reads your Branch events through a Branch webhook pointed at Signals, then sends in-app purchases and installs to Meta so app campaigns optimize on revenue so Meta sees app conversions without an export.

    Talk to our team Explore the setup

    branch -> meta-app-capi :: live

    1. ● branch → meta.capi :: live
    2. > read app_events rows=17,904
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 14,681 matched

    WHAT THIS ENABLES

    Branch to Meta App Conversions

    Branch to Meta App Conversions: Signals reads your Branch 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.

    • Signals sends in-app purchases and installs to Meta so app campaigns optimize on revenue, reading your Branch events as in-app events fire.
    • In-app revenue Meta can optimize on, with no export step out of your Branch events.

    WHAT FLOWS WHERE

    Branch to App CAPI, mapped.

    Signals receives the in-app purchase and install events from your Branch 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 Branch events; Signals hashes and consent-screens each record before Meta's App Conversions API accepts 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, working out of Branch install and in-app events.

    Mobile teams running Branch who need app revenue events Meta can bid on beyond the MMP's last-click view out of Branch events.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A Branch webhook pointed at Signals, mapped to Meta's App Conversions API and tuned for MAID and hashed-email matching.

    2. Map

      Columns from your Branch events align to Meta's App Conversions API in the visual mapper, hashed as each postback arrives and checked for MAID and hashed-email matching.

    3. Deliver

      As in-app events fire, Signals reads your Branch events and sends in-app purchases and installs to Meta so app campaigns optimize on revenue, forwards each app event as it arrives, with MAID and hashed-email matching watched 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 from your Branch events, delivered as in-app events fire.

    In-app revenue Meta can optimize on out of your Branch events, delivered as in-app events fire without event volume climbing.

    Match feedback on MAID and hashed-email matching from Meta's App Conversions API each run, tied back to your Branch events.

    ON THE WIRE

    What App CAPI actually receives.

    signals :: branch.meta-app-capi :: wire

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

    Adjacent moves on the same stack.

    from Branch

    Branch to TikTok App eAPI

    Branch to TikTok App Events API: Signals reads your Branch events and reports in-app events…

    Learn more

    from Branch

    Branch to Snap App CAPI

    Branch to Snap App Conversions: Signals reads your Branch events and posts in-app purchases…

    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 Branch Meta App CAPI sync run?

    You set the cadence, from near-real-time to a nightly Branch sync of your Branch events into Meta. Since Signals forwards each app event as it arrives, app revenue events Meta can bid on beyond the MMP's last-click view keeps pace and mobile teams running Branch watch MAID and hashed-email matching. One scoped connection sets it up, cadence adjustable later.

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

    Match rate follows identifier coverage in your Branch events, which mobile teams running Branch control, not Branch 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 mobile teams running Branch tune against.

    NEXT STEP

    Branch to Meta App CAPI, in production this week.

    Talk to our team All Branch use cases