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 :: signals live
- > SELECT * FROM orders AS OF SYSTEM TIME '-10s' WHERE updated_at > :cursor rows=38,552
- > read customers role=readonly_user
- hash sha256(email,phone)
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 84%
The signal Cockroach yields, and receives.
Every kind of signal that moves between Cockroach and the platforms, through one hashed, deduplicated route.
- 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.
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.
- Offline conversions Google Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Offline conversions Google Store Sales Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Google Enhanced Conversions for Leads Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Google Customer Match Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Google Forms Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Meta Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Meta Conversions API for CRM Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Meta Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Meta Lead Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Snapchat Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Snapchat Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Snapchat Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Snapchat Lead Generation Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions TikTok Offline Events API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions TikTok CRM Events API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences TikTok Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation TikTok Lead Generation Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions LinkedIn Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions LinkedIn Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Lead generation LinkedIn Lead Generation Forms Campaign lead submissions created as records in real time, deduped before creation.
From authorization to delivered signal.
-
Connect
Connect Cockroach with a read-only SQL role scoped to the tables you name, over an encrypted channel.
-
Select
Point Signals at the tables or views that hold conversion data.
-
Map
Map columns to events and identifiers in the visual mapper.
-
Go live
Verify sample rows in the live debugger and go live.
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.