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

    CONNECTIONS / AppsFlyer / AppsFlyer to Meta App CAPI

    AppsFlyer in-app events into Meta, built for Meta's App Conversions API.

    Signals reads your AppsFlyer in-app events through an AppsFlyer data postback to 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

    appsflyer -> meta-app-capi :: live

    1. ● appsflyer → meta.capi :: live
    2. > read app_events rows=66,599
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 55,943 matched

    WHAT THIS ENABLES

    AppsFlyer to Meta App Conversions

    AppsFlyer to Meta App Conversions: your AppsFlyer in-app 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.

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

    WHAT FLOWS WHERE

    AppsFlyer to App CAPI, mapped.

    Each sync hands the in-app purchase and install events from your AppsFlyer in-app 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 AppsFlyer in-app 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, working out of AppsFlyer install and in-app event postbacks.

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

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      An AppsFlyer data postback to Signals, mapped to Meta's App Conversions API and tuned for MAID and hashed-email matching.

    2. Map

      Columns from your AppsFlyer in-app 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 AppsFlyer in-app 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 AppsFlyer in-app events, delivered as in-app events fire.

    In-app revenue Meta can optimize on out of your AppsFlyer in-app 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 AppsFlyer in-app events.

    ON THE WIRE

    What App CAPI actually receives.

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

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

    Adjacent moves on the same stack.

    from AppsFlyer

    AppsFlyer to TikTok App eAPI

    AppsFlyer to TikTok App Events API: your AppsFlyer in-app events, hashed and…

    Learn more

    from AppsFlyer

    AppsFlyer to Snap App CAPI

    AppsFlyer to Snap App Conversions: your AppsFlyer in-app 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 AppsFlyer Meta App CAPI sync run?

    The pace follows your AppsFlyer in-app events: Signals sends changes from AppsFlyer 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 growth teams running AppsFlyer keep MAID and hashed-email matching in view. Delivery needs no export and no manual upload.

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

    In AppsFlyer, match rate tracks the email and phone quality your AppsFlyer in-app events carry. Clean identifiers land for Meta; blank ones never will. The first App Conversions API report shows growth teams running AppsFlyer where MAID and hashed-email matching needs work, a data-quality task handled in AppsFlyer.

    NEXT STEP

    AppsFlyer to Meta App CAPI, in production this week.

    Talk to our team All AppsFlyer use cases