CONNECTIONS / CouchDB
CouchDB + Datahash: your changes feed becomes events.
Order and customer documents live in CouchDB databases, each revision tracked with its own _rev. Signals follows the built-in _changes feed on a schedule you set and delivers hashed events and audiences to every major ad platform, with no export.
- ● couchdb :: signals live
- > GET /orders/_changes?since=cursor docs=29,540
- > read database=customers role=analytics_ro
- hash sha256(email,phone)
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 80%
The signal CouchDB yields, and receives.
Every kind of signal that moves between CouchDB and the platforms, through one hashed, deduplicated route.
- Offline conversions
- Signals follows the _changes feed on your schedule, so order and customer documents in a database become events without a separate export step.
- Lead conversions
- Resuming from the last sequence token means only documents added or revised since then come through, never a scan of the whole database.
- Custom audiences
- Every email and phone number is hashed with SHA-256 as it comes off the feed, so plaintext identifiers never make it past that read.
- Lead generation inbound
- A database's own field names, whatever they are, get lined up by the visual mapper against each platform's event fields.
Pick your platform. Every use case for it, in one place.
Every way CouchDB data moves, grouped by platform and ranked by how many use cases CouchDB 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 CouchDB with a read-only role scoped to the database, over an encrypted channel.
-
Select
Point Signals at the databases that hold conversion documents.
-
Map
Map JSON fields from the database to events and identifiers in the visual mapper.
-
Go live
Verify sample documents pulled from the changes feed in the live debugger, then go live.
CouchDB questions, answered.
Does Datahash write to my database?
No. The role Signals uses is read-only and scoped to the specific databases you name, so it can follow the _changes feed but never write a document back. Nothing outside those databases is visible to the role, and pulling access at any time has no effect on the rest of your CouchDB instance.
Is customer PII stored by Datahash?
Only hashed identifiers ever leave your CouchDB instance. Every email and phone number is run through SHA-256 as Signals reads it off the _changes feed, and Datahash Cloud never stores PII on its host servers, just the hashed result. A self-hosted Core deployment handles that same hashing inside your own environment when data cannot leave your perimeter.
How often does the sync run?
Sync cadence is yours to set, from every few minutes to once-daily batches, and each run picks up the _changes feed exactly where the last one left off using its sequence token. A CouchDB instance sees no added read load as a database grows, and cadence can differ per database, so an orders database can run more often than a slowly changing customer list.
NEXT STEP
See your CouchDB data working in every ad platform.
Ready to enable a use case, or still mapping what CouchDB data could do? Our team helps you find the right place to start.
