CONNECTIONS / MongoDB / MongoDB to Meta Custom Audience
From MongoDB collections to Meta lookalike and suppression seeds.
Signals reads your MongoDB collections through a read-only database user scoped to the MongoDB collections you name, then keeps Meta audiences synced as adds and removals so lists never drift so Meta sees match-ready audiences without an export.
- ● mongodb → meta.audience :: live
- > read segments rows=29,750
- hash sha256(email,phone) consent=filtered
- route meta deliver
- ✓ delivered · 22,313 matched
WHAT THIS ENABLES
MongoDB to Meta Custom Audience
MongoDB to Meta Custom Audience: Signals reads your MongoDB collections and keeps Meta audiences synced as adds and removals so lists never drift, hashed and consent-checked each time the read runs.
- Signals keeps Meta audiences synced as adds and removals so lists never drift, reading your MongoDB collections each time the read runs.
- Always-current lookalike seeds and exclusions, with no export step out of your MongoDB collections.
WHAT FLOWS WHERE
MongoDB to Custom Audience, mapped.
Each sync hands the customer segments from your MongoDB collections 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 MongoDB collections 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 MongoDB who need lookalike seeds and suppression lists that track your live customer base out of MongoDB collections.
From kickoff to verified events.
-
Connect
A read-only database user scoped to the MongoDB collections you name, mapped to Meta's Custom Audiences API and tuned for audience refresh cadence.
-
Map
Columns from your MongoDB collections 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 MongoDB collections 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 MongoDB collections, delivered each time the read runs.
Always-current lookalike seeds and exclusions out of your MongoDB collections, 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 MongoDB collections.
What Custom Audience actually receives.
- ● signals :: audience upload
- > POST /customaudiences source=mongodb.segments
- schema ["EMAIL_SHA256","PHONE_SHA256"]
- num_received 29,750 · num_invalid_entries 29
- audience_id "1667518" · session "upsert"
- ✓ accepted match=75%
Adjacent moves on the same stack.
from MongoDB
MongoDB to Google Customer Match
MongoDB to Google Customer Match: Signals reads your MongoDB collections and projects your…
Learn more
from MongoDB
MongoDB to TikTok Custom Audience
MongoDB to TikTok Custom Audience: Signals reads your MongoDB collections and delivers…
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 MongoDB Meta Custom Audience sync run?
The pace follows your MongoDB collections: Signals sends changes from MongoDB to Meta each time the read runs. Because it reads only the records changed since the last run, lookalike seeds and suppression lists that track your live customer base stays current while application teams running MongoDB keep audience refresh cadence in view. Delivery needs no export and no manual upload.
What match rate should a MongoDB-sourced Meta Custom Audience batch expect?
In MongoDB, match rate tracks the email and phone quality your MongoDB collections carry. Clean identifiers land for Meta; blank ones never will. The first Custom Audiences API report shows application teams running MongoDB where audience refresh cadence needs work, a data-quality task handled in MongoDB.
NEXT STEP