CONNECTIONS / Couchbase
Couchbase + Datahash: your documents become events.
Order and customer documents sit in Couchbase buckets, organized into scopes and collections. Signals queries them with N1QL on a schedule you set and delivers hashed events and audiences to every major ad platform, with no export.
- ● couchbase :: signals live
- > N1QL SELECT * FROM orders WHERE updated > $cursor docs=45,760
- > read bucket=commerce scope=retail collection=customers role=data_reader
- hash sha256(email,phone)
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 84%
The signal Couchbase yields, and receives.
Every kind of signal that moves between Couchbase and the platforms, through one hashed, deduplicated route.
- Offline conversions
- An N1QL query against a bucket and collection runs on your schedule, turning order and customer documents into events without anyone building an export.
- Lead conversions
- DCP, Couchbase's native change protocol, hands Signals only the documents a bucket has actually mutated, so cluster load stays flat as data grows.
- Custom audiences
- SHA-256 hashing happens the instant a bucket document is read, so no email or phone number in a JSON payload survives past that point.
- Lead generation inbound
- Field names vary scope to scope; the visual mapper still lines each one up against a platform's event fields, whatever the document's own shape.
Pick your platform. Every use case for it, in one place.
Every way Couchbase data moves, grouped by platform and ranked by how many use cases Couchbase 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 Couchbase with a data_reader role scoped to the bucket, over an encrypted channel.
-
Select
Point Signals at the scopes and collections that hold conversion documents.
-
Map
Align JSON fields from the bucket to events and identifiers in the visual mapper.
-
Go live
Verify a sample of bucket documents in the live debugger, then go live.
Couchbase questions, answered.
Does Datahash write to my database?
No. Signals connects with a data_reader role scoped only to the bucket, scope, and collections you choose, so it can read documents but never write, update, or delete one. Access can be limited to a single collection if that is all you want exposed, and removing the role at any point leaves the rest of the Couchbase cluster completely unaffected.
Is customer PII stored by Datahash?
Only hashed values leave Couchbase. Signals applies SHA-256 to emails and phone numbers the moment a bucket document is read, and Datahash Cloud stores no PII on its host servers, only the hashed output. Where data must stay inside your perimeter entirely, a self-hosted Core deployment runs the same hashing step before anything is delivered.
How often does the sync run?
You set the cadence, from a few minutes apart to once a day, and Couchbase's DCP change protocol means every run reads only documents mutated since the last one. Query load on the cluster stays flat even as a bucket grows, and different collections can run on different schedules, so an orders collection can sync far more often than a slowly changing customer profile.
NEXT STEP
See your Couchbase data working in every ad platform.
Ready to enable a use case, or still mapping what Couchbase data could do? Our team helps you find the right place to start.
