Jump to a popular page, or start typing.

    CONNECTIONS / Apache Cassandra

    Apache Cassandra + Datahash: partitions become events.

    Order history, transaction logs, and event records sit across partitioned Cassandra tables built for high write throughput. Signals reads them with CQL on a schedule you set and delivers hashed events and audiences to every major ad platform, with no export.

    apache-cassandra :: live

    1. ● apache-cassandra :: signals live
    2. > CQL SELECT * FROM orders WHERE token(id) > :cursor records=58,204
    3. > read keyspace=commerce table=customers role=analytics_ro
    4. hash sha256(email,phone)
    5. route meta · google · tiktok · snap
    6. ✓ 4 destinations synced · match 81%
    WHAT FLOWS THROUGH APACHE CASSANDRA

    The signal Apache Cassandra yields, and receives.

    Every kind of signal that moves between Apache Cassandra and the platforms, through one hashed, deduplicated route.

    What flows Every platform Offline conversions Lead conversions Custom audiences Lead generation Signals hash · dedupe· route Google Meta Snap TikTok LinkedIn OpenAI
    Offline conversions
    Query results for a partition key range post on the cadence you set, so order and transaction data becomes events with no export job in between.
    Lead conversions
    Reading resumes from a token cursor each run, so a table built for constant writes never needs a full scan just to find what changed.
    Custom audiences
    SHA-256 replaces every email and phone number the instant a row is read, so nothing plaintext survives past ingestion.
    Lead generation inbound
    Whatever column names a keyspace happens to use, the visual mapper lines them up against each platform's event fields, wide-column schema included.
    USE-CASE LISTING

    Pick your platform. Every use case for it, in one place.

    Every way Apache Cassandra data moves, grouped by platform and ranked by how many use cases Apache Cassandra supports.

    Google 5 Meta 4 Snap 4 TikTok 4 LinkedIn 3 OpenAI 1
    HOW IT CONNECTS

    From authorization to delivered signal.

    1. Connect

      Connect Apache Cassandra with a read-only role scoped to the keyspace, over an encrypted channel.

    2. Select

      Point Signals at the tables and partitions that hold conversion data.

    3. Map

      Map columns to events and identifiers in the visual mapper.

    4. Go live

      Verify sample records in the live debugger and go live.

    FAQ

    Apache Cassandra questions, answered.

    Does Datahash write to my database?

    No. The connection uses a read-only role scoped to the keyspace and tables you name, so Signals can query partitioned data but can never insert, update, or delete a record. You control which tables the role can see, and revoking it at any time leaves the rest of your Cassandra cluster untouched.

    Is customer PII stored by Datahash?

    Identifiers are SHA-256 hashed at ingestion, and no PII is stored on host servers in Datahash Cloud, so only hashed values ever reach a destination. A self-hosted Core deployment is available when data cannot leave your perimeter, in which case hashing happens inside your own environment before delivery.

    How often does the sync run?

    Cassandra syncs on the schedule you set, anywhere from every few minutes to daily batches, and each run pages through only the partition range that changed since the last cursor. A cluster built for high write throughput barely notices the extra read load, and cadence can differ per table, so a fast-moving order log can sync more often than a slowly changing customer table.

    NEXT STEP

    See your Apache Cassandra data working in every ad platform.

    Ready to enable a use case, or still mapping what Apache Cassandra data could do? Our team helps you find the right place to start.