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

    App CAPI

    Server-side app conversion tracking that survives ATT.

    Move your app conversion tracking to CAPI across Meta, Snap, and TikTok, working with your MMP, Tracking SDK or independently.

    Talk to our team Supported Platforms

    signals :: live

    1. > event web.purchase cart_value=214.00
    2. hash sha256(email,phone) pii=cleared
    3. dedupe event_id=8f3a match pixel+server
    4. route meta.capi emq 8.4
    5. route google.enhanced match ok
    6. route snap.capi match ok
    7. ✓ delivered 4/4 destinations in 182ms

    THE PROBLEM

    ATT opt-outs and SKAN limits starved app campaigns of the signal they optimize on. Platforms now reward advertisers who deliver app events server-side with hashed identifiers; the rest bid on partial data.

    WHAT IT DOES

    Benefits of App CAPI with Signals.

    Ingests events from your MMP (AppsFlyer, Adjust, Branch, Kochava, Singular) or direct SDK.

    Routes to each ad platform's app CAPI equivalent, including Meta App CAPI, Snap App CAPI, and TikTok App Events API.

    Preserves match rate through hashed identifiers.

    SUPPORTED DESTINATIONS

    Pick your platform playbook.

    Each destination has its own verified setup, documented end to end.

    meta

    Meta App CAPI

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

    Learn more

    tiktok

    TikTok App Events API

    Datahash sends in-app events to TikTok server-side, so installs and post-install actions attribute and optimize correctly. Events run alongside your MMP setup, with identifiers hashed and a delivery status on every event.

    Learn more

    snap

    Snap App CAPI

    Server-side app conversion tracking into Snap, integrated with your MMP.

    Learn more

    THE PIPELINE

    What flows where.

    Your sources on the left, verified destinations on the right. Signals hashes, dedupes, and routes in the middle.

    web.pixel app.sdk crm.webhook Signals hash · dedupe· route meta.capi google.enhanced snap.capi [ one pipeline, every destination ]
    BENEFITS

    Why teams move server-side here.

    Better optimization on iOS in the ATT world.

    Consistency of measurement across web and app.

    One pipeline serving Meta, Snap, and TikTok app endpoints.

    SETUP

    The setup, end to end.

    1. Connect source

      Configure your MMP postbacks or API endpoints.

    2. Map a DNS

      Create a first-party sub-domain entry to improve redundancy.

    3. Add destinations

      Toggle Meta App CAPI, Snap App CAPI, and TikTok App Events API.

    4. Verify

      Deduped events confirmed in each platform's events manager.

    5. Go live

      Match rate and event quality reporting from day one.

    FAQ

    Questions your team will ask.

    Do we still need our MMP?

    Yes. Your MMP remains the attribution source of truth. Signals sits alongside it, taking its postbacks or exports and delivering them to each platform's app CAPI with the identifiers the platforms need.

    What identifiers do you use?

    Hashed email and phone where your app captures them, plus device identifiers permitted under each user's ATT status. Everything is hashed before delivery.

    What about ATT opt-outs?

    Opted-out users are routed without restricted device identifiers, relying on consented hashed contact identifiers instead. Delivery stays policy-compliant while preserving as much match signal as each opt-in state allows.

    NEXT STEP

    Book a App CAPI working session.

    We map your source data, propose an integration plan, and give you a live setup in the same call where possible.

    Talk to our team Explore integrations