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

    CONNECTIONS / Cockroach / Cockroach to Meta Custom Audience

    From Cockroach tables to Meta lookalike and suppression seeds.

    Connect Cockroach and point Signals at your Cockroach tables; it keeps Meta audiences synced as adds and removals so lists never drift each time the read runs, hashed and consent-checked for Meta.

    Talk to our team Explore the setup

    cockroach -> meta-custom-audience :: live

    1. ● cockroach → meta.audience :: live
    2. > read segments rows=51,768
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 45,556 matched

    WHAT THIS ENABLES

    Cockroach to Meta Custom Audience

    Meta Custom Audience for Cockroach: Signals keeps Meta audiences synced as adds and removals so lists never drift straight from your Cockroach tables, hashed and consent-screened each time the read runs.

    • Customer segments from your Cockroach tables activated for Meta, as Signals keeps Meta audiences synced as adds and removals so lists never drift.
    • Lookalike seeds and suppression lists that track your live customer base, drawn from your Cockroach tables by platform teams running CockroachDB.

    WHAT FLOWS WHERE

    Cockroach to Custom Audience, mapped.

    A scheduled read pulls the customer segments from your Cockroach tables; Signals hashes and consent-screens each record before Meta's Custom Audiences API accepts the match-ready audiences for audience refresh cadence.

    A scheduled read pulls the customer segments from your Cockroach tables; Signals hashes and consent-screens each record before Meta's Custom Audiences API accepts 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, with the records already in Cockroach tables and secondary indexes.

    Platform teams running CockroachDB activating Meta lookalike and suppression seeds straight from Cockroach tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the Cockroach tables you name to feed Meta's Custom Audiences API, sized for audience refresh cadence.

    2. Map

      A scheduled read pulls your Cockroach tables, and its columns map to Meta's Custom Audiences API in the visual mapper, hashed and checked for audience refresh cadence.

    3. Deliver

      On each run, Signals pulls your Cockroach tables, keeps Meta audiences synced as adds and removals so lists never drift, and reads only the records changed since the last run, with audience refresh cadence in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Lookalike seeds and suppression lists that track your live customer base on every run, as Signals reads your Cockroach tables and reads only the records changed since the last run.

    Always-current lookalike seeds and exclusions from your Cockroach tables, with read load on the database steady because Signals reads only the records changed since the last run.

    A per-run match report from Meta's Custom Audiences API on audience refresh cadence, straight out of your Cockroach tables.

    ON THE WIRE

    What Custom Audience actually receives.

    signals :: cockroach.meta-custom-audience :: wire

    1. ● signals :: audience upload
    2. > POST /customaudiences source=cockroach.segments
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. num_received 51,768 · num_invalid_entries 215
    5. audience_id "1666715" · session "upsert"
    6. ✓ accepted match=88%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Cockroach

    Cockroach to Google Customer Match

    Google Customer Match for Cockroach: Signals projects your segments into Google Ads as…

    Learn more

    from Cockroach

    Cockroach to TikTok Custom Audience

    TikTok Custom Audience for Cockroach: Signals delivers first-party segments to TikTok as…

    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.

    How often does the Cockroach Meta Custom Audience sync run?

    The pace follows your Cockroach tables: Signals sends changes from Cockroach to Meta each time the read runs. Because it reads only the records changed since the last run, lookalike seeds and suppression lists that track your live customer base stays current while platform teams running CockroachDB keep audience refresh cadence in view. Delivery needs no export and no manual upload.

    What match rate should a Cockroach-sourced Meta Custom Audience batch expect?

    Coverage of hashed identifiers across your Cockroach tables decides it, and platform teams running CockroachDB own that inside Cockroach. A live email or phone matches into Meta; neither, and it will not. First-run feedback flags audience refresh cadence, which platform teams running CockroachDB then raise inside your Cockroach tables.

    NEXT STEP

    Cockroach to Meta Custom Audience, in production this week.

    Talk to our team All Cockroach use cases