CONNECTIONS / MongoDB
MongoDB + Datahash: your collections become events.
Order history and customer documents sit in MongoDB collections, often behind an application you already run. Signals reads them with a scoped query on a schedule you set and delivers hashed events and audiences to every major ad platform, with no export.
- ● mongodb :: signals live
- > find({ updatedAt: { $gt: cursor } }) collection=orders docs=38,214
- > read collection=customers role=readOnly
- hash sha256(email,phone)
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 82%
The signal MongoDB yields, and receives.
Every kind of signal that moves between MongoDB and the platforms, through one hashed, deduplicated route.
- Offline conversions
- Every scheduled pass filters a collection down to what changed, and those order and customer documents come out the other side as events, no export required.
- Lead conversions
- Change streams hand Signals only documents inserted or updated since the last pass, so a growing collection never means a heavier read.
- Custom audiences
- Every email and phone number in a matched document gets SHA-256 hashed before it moves anywhere else, so plaintext never leaves the read step.
- Lead generation inbound
- A collection's field names, however inconsistent across documents, still land in the right event fields once the visual mapper sees them.
Pick your platform. Every use case for it, in one place.
Every way MongoDB data moves, grouped by platform and ranked by how many use cases MongoDB supports.
- 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 MongoDB with a read-only role scoped to the database, over an encrypted channel.
-
Select
Point Signals at the collections that hold conversion documents.
-
Map
Map BSON fields from the collection to events and identifiers in the visual mapper.
-
Go live
Verify a sample of matched documents in the live debugger, then go live.
MongoDB questions, answered.
Does Datahash write to my database?
No. Signals authenticates with a role granted read access to the specific collections you choose, never write, update, or delete permissions. Scoping can go as narrow as a single collection, and because the role is fully revocable, removing it at any time leaves the rest of your MongoDB deployment untouched.
Is customer PII stored by Datahash?
Signals hashes emails and phone numbers with SHA-256 as soon as a document is read from the collection, so only hashed values travel any further. Datahash Cloud's host servers never store PII, only the hashed output that results. If data cannot leave your perimeter at all, a self-hosted Core deployment performs that same hashing step internally before delivery.
How often does the sync run?
Pick a cadence anywhere from every few minutes to once a day; change streams mean each run reads only documents inserted or updated since the last pass. That keeps query load on a MongoDB deployment flat even as a collection grows, and different collections can run on different schedules, so an orders collection can sync far more often than a slowly changing customer list.
NEXT STEP
See your MongoDB data working in every ad platform.
Ready to enable a use case, or still mapping what MongoDB data could do? Our team helps you find the right place to start.