CONNECTIONS / CouchDB / CouchDB to Meta Custom Audience
CouchDB documents into Meta, built for Meta lookalike and suppression seeds.
Signals reads your CouchDB documents through a read-only database user scoped to the CouchDB documents you name, then keeps Meta audiences synced as adds and removals so lists never drift so Meta sees match-ready audiences without an export.
- ● couchdb → meta.audience :: live
- > read segments rows=21,571
- hash sha256(email,phone) consent=filtered
- route meta deliver
- ✓ delivered · 17,904 matched
WHAT THIS ENABLES
CouchDB to Meta Custom Audience
Meta Custom Audience for CouchDB: Signals keeps Meta audiences synced as adds and removals so lists never drift straight from your CouchDB documents, hashed and consent-screened each time the read runs.
- Signals keeps Meta audiences synced as adds and removals so lists never drift, reading your CouchDB documents each time the read runs.
- Always-current lookalike seeds and exclusions, with no export step out of your CouchDB documents.
WHAT FLOWS WHERE
CouchDB to Custom Audience, mapped.
Each sync hands the customer segments from your CouchDB documents to Signals, which hashes and filters every record, then Meta's Custom Audiences API logs the match-ready audiences for audience refresh cadence.
Each sync hands the customer segments from your CouchDB documents to Signals, which hashes and filters every record, then Meta's Custom Audiences API logs the match-ready audiences for audience refresh cadence.
Built for the teams that own the number.
Application teams running CouchDB who need lookalike seeds and suppression lists that track your live customer base out of CouchDB documents.
From kickoff to verified events.
-
Connect
A read-only database user scoped to the CouchDB documents you name, mapped to Meta's Custom Audiences API and tuned for audience refresh cadence.
-
Map
Columns from your CouchDB documents align to Meta's Custom Audiences API in the visual mapper, hashed as the read runs and checked for audience refresh cadence.
-
Deliver
Each time the read runs, Signals reads your CouchDB documents and keeps Meta audiences synced as adds and removals so lists never drift, reads only the records changed since the last run, with audience refresh cadence watched in the debugger.
What ships with this use case.
Lookalike seeds and suppression lists that track your live customer base from your CouchDB documents, delivered each time the read runs.
Always-current lookalike seeds and exclusions out of your CouchDB documents, delivered each time the read runs without read load on the database climbing.
Match feedback on audience refresh cadence from Meta's Custom Audiences API each run, tied back to your CouchDB documents.
What Custom Audience actually receives.
- ● signals :: audience upload
- > POST /customaudiences source=couchdb.segments
- schema ["EMAIL_SHA256","PHONE_SHA256"]
- num_received 21,571 · num_invalid_entries 118
- audience_id "1651692" · session "upsert"
- ✓ accepted match=83%
Adjacent moves on the same stack.
from CouchDB
CouchDB to Google Customer Match
Google Customer Match for CouchDB: Signals projects your segments into Google Ads as…
Learn more
from CouchDB
CouchDB to TikTok Custom Audience
TikTok Custom Audience for CouchDB: Signals delivers first-party segments to TikTok as…
Learn more
same use case
ActiveCampaign to Meta Custom Audience
ActiveCampaign to Meta Custom Audience: Signals reads your ActiveCampaign contacts and deal…
Learn moregeneric
Meta Custom Audience
Build and refresh Meta Custom Audiences from your CRM, warehouse, or SingleView, with…
Learn moreAsked on almost every call.
How often does the CouchDB Meta Custom Audience sync run?
Delivery tracks CouchDB, run by application teams running CouchDB: a near-real-time or scheduled sync of your CouchDB documents feeds Meta on that cadence. Each run reads only the records changed since the last run, so always-current lookalike seeds and exclusions holds up on audience refresh cadence. The live debugger confirms every delivery inline.
What match rate should a CouchDB-sourced Meta Custom Audience batch expect?
Coverage of hashed identifiers across your CouchDB documents decides it, and application teams running CouchDB own that inside CouchDB. A live email or phone matches into Meta; neither, and it will not. First-run feedback flags audience refresh cadence, which application teams running CouchDB then raise inside your CouchDB documents.
NEXT STEP