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

    CONNECTIONS / Singular / Singular to Meta App CAPI

    From Singular events to Meta's App Conversions API.

    Connect Singular and point Signals at your Singular 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

    singular -> meta-app-capi :: live

    1. ● singular → meta.capi :: live
    2. > read app_events rows=21,603
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 15,770 matched

    WHAT THIS ENABLES

    Singular to Meta App Conversions

    Singular to Meta App Conversions: your Singular 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 Singular 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 Singular events by growth teams running Singular.

    WHAT FLOWS WHERE

    Singular to App CAPI, mapped.

    Each sync hands the in-app purchase and install events from your Singular 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 Singular 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 Singular install and in-app events.

    Growth teams running Singular activating Meta's App Conversions API straight from Singular events.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A Singular postback to Signals to feed Meta's App Conversions API, sized for MAID and hashed-email matching.

    2. Map

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

    In-app revenue Meta can optimize on from your Singular 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 Singular events.

    ON THE WIRE

    What App CAPI actually receives.

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

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

    Adjacent moves on the same stack.

    from Singular

    Singular to TikTok App eAPI

    Singular to TikTok App Events API: your Singular events, hashed and consent-checked, feed…

    Learn more

    from Singular

    Singular to Snap App CAPI

    Singular to Snap App Conversions: your Singular events, hashed and consent-checked, feed…

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

    You set the cadence, from near-real-time to a nightly Singular sync of your Singular 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 growth teams running Singular watch MAID and hashed-email matching. One scoped connection sets it up, cadence adjustable later.

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

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

    NEXT STEP

    Singular to Meta App CAPI, in production this week.

    Talk to our team All Singular use cases