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

    CONNECTIONS / Datahash API / Datahash API to Meta Custom Audience

    Post customer segments to the Datahash API, wired to Meta lookalike and suppression seeds.

    Send customer segments to one documented REST endpoint from any backend, in any language; Signals keeps Meta audiences synced as adds and removals so lists never drift, hashed and consent-checked, with no pixel and no warehouse read.

    Talk to our team Explore the setup

    datahash-api -> meta-custom-audience :: live

    1. ● datahash-api → meta.audience :: live
    2. > POST /v1/events source=api.audience_members count=33,358
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ 202 accepted · 28,688 forwarded

    WHAT THIS ENABLES

    Datahash API to Meta Custom Audience

    Datahash API to Meta Custom Audience: post your customer segments to one REST endpoint and Signals keeps Meta audiences synced as adds and removals so lists never drift, hashed and consent-checked server-side before Meta sees it.

    • Signals keeps Meta audiences synced as adds and removals so lists never drift, from events your backend posts server-side.
    • Lookalike seeds and suppression lists that track your live customer base, without a pixel, a connector, or a nightly export.

    WHAT FLOWS WHERE

    Datahash API to Custom Audience, mapped.

    Your backend posts each event to the Datahash API, which hashes and consent-screens it server-side, then Meta's Custom Audiences API records the match-ready audiences for audience refresh cadence.

    Your backend posts each event to the Datahash API, which hashes and consent-screens it server-side, then Meta's Custom Audiences API records the match-ready audiences for audience refresh cadence.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Performance teams running first-party suppression and lookalike seeds, whose engineers would rather POST an event than maintain a connector.

    Backend and platform teams driving Meta lookalike and suppression seeds by sending customer segments straight from their own stack.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Create an API key in the Signals console and point your backend at the endpoint that feeds Meta's Custom Audiences API.

    2. Map

      Map your event payload to Meta's Custom Audiences API fields once; per-request validation flags bad events instead of dropping the batch.

    3. Deliver

      Post events as they happen and Signals keeps Meta audiences synced as adds and removals so lists never drift, hashing server-side, with audience refresh cadence shown in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Lookalike seeds and suppression lists that track your live customer base from a single server-side call.

    Always-current lookalike seeds and exclusions, with identifiers hashed at ingestion or sent pre-hashed.

    Per-event status and match feedback on audience refresh cadence from Meta's Custom Audiences API, returned inline in the live debugger.

    ON THE WIRE

    What Custom Audience actually receives.

    signals :: datahash-api.meta-custom-audience :: wire

    1. ● signals :: audience upload
    2. > POST /customaudiences source=api.audience_members
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. num_received 33,358 · num_invalid_entries -86
    5. audience_id "1695533" · session "upsert"
    6. ✓ accepted match=86%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Datahash API

    Datahash API to Google Customer Match

    Datahash API to Google Customer Match: post your customer segments to one REST endpoint and…

    Learn more

    from Datahash API

    Datahash API to TikTok Custom Audience

    Datahash API to TikTok Custom Audience: post your customer segments to one REST endpoint…

    Learn more

    same use case

    ActiveCampaign to Meta Custom Audience

    ActiveCampaign to Meta Custom Audience: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Meta Custom Audience

    Build and refresh Meta Custom Audiences from your CRM, warehouse, or SingleView, with…

    Learn more
    FAQ

    Asked on almost every call.

    Which backends can send to Meta Custom Audience through the Datahash API?

    Any backend that can make an HTTPS request. You POST customer segments as JSON to one documented endpoint and Signals forwards the match-ready audiences to Meta's Custom Audiences API; identifiers are hashed at ingestion or sent pre-hashed, and performance teams running first-party suppression and lookalike seeds track audience refresh cadence in the debugger.

    How fresh are Meta Custom Audience events sent over the API?

    As fresh as you post them. The API accepts events in near real time, so lookalike seeds and suppression lists that track your live customer base reaches Meta moments after your backend fires the call, with per-event status returned inline. There is no batch window and no scheduled read, which keeps audience refresh cadence current for the teams driving Meta lookalike and suppression seeds.

    NEXT STEP

    Datahash API to Meta Custom Audience, in production this week.

    Talk to our team All Datahash API use cases