CONNECTIONS / Clickhouse
Clickhouse + Datahash: event tables become ad signals.
Event and customer data land in Clickhouse tables built for fast scans over huge volumes. Signals reads them on a schedule you set and delivers hashed events and audiences to every major ad platform, with no export.
- ● clickhouse :: signals live
- > SELECT * FROM events WHERE event_time > :cursor rows=118,204
- > read customer_attributes role=readonly
- hash sha256(email,phone)
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 81%
The signal Clickhouse yields, and receives.
Every kind of signal that moves between Clickhouse and the platforms, through one hashed, deduplicated route.
- Offline conversions
- Clickhouse tables are typically ordered by a timestamp or event key, so Signals can read past a cursor on that column without a full table scan even at hundreds of millions of rows.
- Lead conversions
- Because Clickhouse organizes data into partitions, a run touches only the partitions holding new or updated rows, keeping load on the cluster low as event volume grows.
- Custom audiences
- Emails and phone numbers are SHA-256 hashed at ingestion, so no plaintext identifier from a Clickhouse table ever reaches a destination.
- Lead generation inbound
- The visual mapper aligns whatever column names a MergeTree or Distributed table uses to each platform's event fields, so clickstream or log-shaped data still becomes clean conversion signals.
Pick your platform. Every use case for it, in one place.
Every way Clickhouse data moves, grouped by platform and ranked by how many use cases Clickhouse supports.
Google 5 
Meta 4 
Snap 4 
TikTok 4 
LinkedIn 3 
OpenAI 1 - 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 Clickhouse with a read-only user restricted to the tables you name, over an encrypted channel.
-
Select
Point Signals at the tables or views that hold conversion and event data.
-
Map
Map columns to events and identifiers in the visual mapper.
-
Go live
Verify sample rows in the live debugger and go live.
Clickhouse questions, answered.
Does Datahash write to my Clickhouse cluster?
No. Signals connects with a read-only user restricted to the tables and views you name, so it can scan rows but never insert, update, or delete data. Clickhouse's own grants let you scope that account to specific databases, and you can revoke the credential at any time without affecting ingestion into the rest of your cluster.
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 platform. If event data cannot leave your perimeter, a self-hosted Core deployment runs the same hashing step inside your own environment before anything is delivered.
How often does the sync run against Clickhouse?
On a schedule you choose, from every few minutes to daily batches. Because Clickhouse is built to scan very large tables quickly, incremental queries against a growing MergeTree table stay fast, so a high-volume event table can sync as often as a small reference table without straining the cluster.
NEXT STEP
See your Clickhouse data working in every ad platform.
Ready to enable a use case, or still mapping what Clickhouse data could do? Our team helps you find the right place to start.
