Jump to a popular page, or start typing.

    CONNECTIONS / Couchbase / Couchbase to Meta Custom Audience

    Your Couchbase buckets, wired to Meta lookalike and suppression seeds.

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

    couchbase -> meta-custom-audience :: live

    1. ● couchbase → meta.audience :: live
    2. > read segments rows=15,965
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 14,369 matched

    WHAT THIS ENABLES

    Couchbase to Meta Custom Audience

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

    • Customer segments from your Couchbase buckets 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 Couchbase buckets by engineering teams on Couchbase.

    WHAT FLOWS WHERE

    Couchbase to Custom Audience, mapped.

    Signals reads the customer segments from your Couchbase buckets each time the read runs, hashes and screens each record, and posts the match-ready audiences to Meta's Custom Audiences API, keeping audience refresh cadence in view.

    Signals reads the customer segments from your Couchbase buckets each time the read runs, hashes and screens each record, and posts the match-ready audiences to Meta's Custom Audiences API, keeping audience refresh cadence in view.

    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 Couchbase buckets, scopes, and collections.

    Engineering teams on Couchbase activating Meta lookalike and suppression seeds straight from Couchbase buckets.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

      A scheduled read pulls your Couchbase buckets, 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 Couchbase buckets, 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 Couchbase buckets and reads only the records changed since the last run.

    Always-current lookalike seeds and exclusions from your Couchbase buckets, 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 Couchbase buckets.

    ON THE WIRE

    What Custom Audience actually receives.

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

    1. ● signals :: audience upload
    2. > POST /customaudiences source=couchbase.segments
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. num_received 15,965 · num_invalid_entries -293
    5. audience_id "1687193" · session "upsert"
    6. ✓ accepted match=90%
    FAQ

    Asked on almost every call.

    How often does the Couchbase Meta Custom Audience sync run?

    You set the cadence, from near-real-time to a nightly Couchbase sync of your Couchbase buckets into Meta. Since Signals reads only the records changed since the last run, lookalike seeds and suppression lists that track your live customer base keeps pace and engineering teams on Couchbase watch audience refresh cadence. One scoped connection sets it up, cadence adjustable later.

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

    In Couchbase, match rate tracks the email and phone quality your Couchbase buckets carry. Clean identifiers land for Meta; blank ones never will. The first Custom Audiences API report shows engineering teams on Couchbase where audience refresh cadence needs work, a data-quality task handled in Couchbase.

    NEXT STEP

    Couchbase to Meta Custom Audience, in production this week.