CONNECTIONS / PostgreSQL
PostgreSQL + Datahash: your tables become ad-platform events.
Conversion data and customer attributes sit in PostgreSQL tables and views. Signals reads them on a schedule you set and delivers hashed events and audiences to every major ad platform, with no export.
- ● postgresql :: signals live
- > SELECT * FROM orders WHERE updated_at > :cursor rows=42,318
- > read customers role=analytics_ro
- hash sha256(email,phone)
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 83%
The signal PostgreSQL yields, and receives.
Every kind of signal that moves between PostgreSQL and the platforms, through one hashed, deduplicated route.
- Offline conversions
- A query runs on the cadence you set, so a table of orders or conversions leaves PostgreSQL as events without anyone scheduling an export.
- Lead conversions
- Change detection reads only the rows that moved since the last cursor, keeping load on the database low even on very large tables.
- Custom audiences
- Emails and phone numbers are SHA-256 hashed at ingestion, so no plaintext identifier from your tables ever reaches a destination.
- Lead generation inbound
- The visual mapper aligns whatever column names your schema uses to each platform's event fields, so an unusual table shape still becomes clean conversion signals.
Pick your platform. Every use case for it, in one place.
Every way PostgreSQL data moves, grouped by platform and ranked by how many use cases PostgreSQL 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 PostgreSQL with read-only credentials 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.
PostgreSQL questions, answered.
Does Datahash write to my database?
No. The connection uses read-only credentials and only queries the tables and views you explicitly allow, so Signals can read conversion data but can never insert, update, or delete a row. You scope the database user to the minimum it needs, and you can revoke it at any time without affecting the rest of your PostgreSQL instance.
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 are matched to a platform. A self-hosted Core deployment is available when data cannot leave your perimeter, in which case the hashing happens 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 touches only changed rows. That keeps load on your PostgreSQL instance low even as tables grow, and the cadence can differ per table, so a fast-moving orders table can sync more often than a slowly changing customer list.
NEXT STEP
See your PostgreSQL data working in every ad platform.
Ready to enable a use case, or still mapping what PostgreSQL data could do? Our team helps you find the right place to start.
