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

    CONNECTIONS / Apache Cassandra / Apache Cassandra to Meta Custom Audience

    From Cassandra tables to Meta lookalike and suppression seeds.

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

    apache-cassandra -> meta-custom-audience :: live

    1. ● apache cassandra → meta.audience :: live
    2. > read segments rows=67,476
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 59,379 matched

    WHAT THIS ENABLES

    Apache Cassandra to Meta Custom Audience

    Apache Cassandra to Meta Custom Audience: Signals reads your Cassandra tables and keeps Meta audiences synced as adds and removals so lists never drift, hashed and consent-checked each time the read runs.

    • Customer segments from your Cassandra 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 Cassandra tables by platform teams running Cassandra.

    WHAT FLOWS WHERE

    Apache Cassandra to Custom Audience, mapped.

    A scheduled read pulls the customer segments from your Cassandra 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 Cassandra 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 Cassandra tables and materialized views.

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

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

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

    Always-current lookalike seeds and exclusions from your Cassandra 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 Cassandra tables.

    ON THE WIRE

    What Custom Audience actually receives.

    signals :: apache-cassandra.meta-custom-audience :: wire

    1. ● signals :: audience upload
    2. > POST /customaudiences source=apache-cassandra.segments
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. num_received 67,476 · num_invalid_entries -209
    5. audience_id "1650677" · session "upsert"
    6. ✓ accepted match=88%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Apache Cassandra

    Apache Cassandra to Google Customer Match

    Apache Cassandra to Google Customer Match: Signals reads your Cassandra tables and projects…

    Learn more

    from Apache Cassandra

    Apache Cassandra to TikTok Custom Audience

    Apache Cassandra to TikTok Custom Audience: Signals reads your Cassandra tables and…

    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 Apache Cassandra Meta Custom Audience sync run?

    You set the cadence, from near-real-time to a nightly Apache Cassandra sync of your Cassandra tables 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 platform teams running Cassandra watch audience refresh cadence. One scoped connection sets it up, cadence adjustable later.

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

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

    NEXT STEP

    Apache Cassandra to Meta Custom Audience, in production this week.

    Talk to our team All Apache Cassandra use cases