Jump to a popular page, or start typing.

    CONNECTIONS / Cockroach

    Cockroach + Datahash: live tables become ad signals.

    Conversion and customer data sit in Cockroach tables that stay available across nodes and regions. Signals reads them through the same PostgreSQL-compatible protocol your tools already use and delivers hashed events and audiences to every major ad platform.

    cockroach :: live

    1. ● cockroach :: signals live
    2. > SELECT * FROM orders AS OF SYSTEM TIME '-10s' WHERE updated_at > :cursor rows=38,552
    3. > read customers role=readonly_user
    4. hash sha256(email,phone)
    5. route meta · google · tiktok · snap
    6. ✓ 4 destinations synced · match 84%
    WHAT FLOWS THROUGH COCKROACH

    The signal Cockroach yields, and receives.

    Every kind of signal that moves between Cockroach 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
    Signals connects over Cockroach's PostgreSQL-compatible wire protocol, so a query runs on the cadence you set without a custom driver.
    Lead conversions
    Cockroach replicates and rebalances data across nodes automatically, and a read tied to a cursor column keeps working through that movement without duplicate or missed rows.
    Custom audiences
    Emails and phone numbers are SHA-256 hashed at ingestion, so no plaintext identifier from a Cockroach table ever reaches a destination.
    Lead generation inbound
    The visual mapper aligns whatever column names your schema uses to each platform's event fields, so a distributed table still becomes clean conversion signals.
    USE-CASE LISTING

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

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

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

    From authorization to delivered signal.

    1. Connect

      Connect Cockroach with a read-only SQL role scoped to the tables you name, over an encrypted channel.

    2. Select

      Point Signals at the tables or views that hold conversion data.

    3. Map

      Map columns to events and identifiers in the visual mapper.

    4. Go live

      Verify sample rows in the live debugger and go live.

    FAQ

    Cockroach questions, answered.

    Does Datahash write to my Cockroach cluster?

    No. Signals connects with a read-only SQL role granted SELECT on only the tables you name, using Cockroach's PostgreSQL-compatible wire protocol. That role can read rows but never write to your cluster, and because grants apply per database and table, you control exactly what the connection can see.

    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 reach a destination platform. A self-hosted Core deployment is available when data cannot leave your perimeter, hashing inside your own environment before anything is delivered.

    How often does the sync run?

    On a schedule you choose, from every few minutes to daily batches, with incremental extraction so each run reads only changed rows. Cockroach's distributed architecture keeps a query consistent even while nodes are added or fail over, so the sync holds up during a rolling upgrade or a regional outage.

    NEXT STEP

    See your Cockroach data working in every ad platform.

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