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

    CONNECTIONS / Adjust / Adjust to Meta App CAPI

    Adjust postbacks into Meta, built for Meta's App Conversions API.

    Connect Adjust and point Signals at your Adjust postbacks; 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

    adjust -> meta-app-capi :: live

    1. ● adjust → meta.capi :: live
    2. > read app_events rows=38,826
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 30,673 matched

    WHAT THIS ENABLES

    Adjust to Meta App Conversions

    Adjust to Meta App Conversions: Signals reads your Adjust postbacks and sends in-app purchases and installs to Meta so app campaigns optimize on revenue, hashed and consent-checked as in-app events fire.

    • In-app purchase and install events from your Adjust postbacks 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 Adjust postbacks by mobile teams running Adjust.

    WHAT FLOWS WHERE

    Adjust to App CAPI, mapped.

    Signals reads the in-app purchase and install events from your Adjust postbacks as in-app events fire, hashes and screens each record, and posts the app conversions to Meta's App Conversions API, keeping MAID and hashed-email matching in view.

    Signals reads the in-app purchase and install events from your Adjust postbacks as in-app events fire, hashes and screens each record, and posts the app conversions to Meta's App Conversions API, keeping MAID and hashed-email matching in view.

    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 Adjust install and in-app event postbacks.

    Mobile teams running Adjust activating Meta's App Conversions API straight from Adjust postbacks.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      An Adjust callback pointed at Signals to feed Meta's App Conversions API, sized for MAID and hashed-email matching.

    2. Map

      Signals receives your Adjust postbacks, 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 Adjust postbacks, 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 Adjust postbacks and forwards each app event as it arrives.

    In-app revenue Meta can optimize on from your Adjust postbacks, 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 Adjust postbacks.

    ON THE WIRE

    What App CAPI actually receives.

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

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

    Adjacent moves on the same stack.

    from Adjust

    Adjust to TikTok App eAPI

    Adjust to TikTok App Events API: Signals reads your Adjust postbacks and reports in-app…

    Learn more

    from Adjust

    Adjust to Snap App CAPI

    Adjust to Snap App Conversions: Signals reads your Adjust postbacks and posts in-app…

    Learn more

    same use case

    App Events to Meta App CAPI

    App Events to Meta App Conversions: your app conversion events, hashed and consent-checked,…

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

    Delivery tracks Adjust, run by mobile teams running Adjust: a near-real-time or scheduled sync of your Adjust postbacks 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 Adjust-sourced Meta App CAPI batch expect?

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

    NEXT STEP

    Adjust to Meta App CAPI, in production this week.

    Talk to our team All Adjust use cases