Client side upsert
Identity looked up first, then records routed.
Sync Facebook Ads into MongoDB with Polytomic by modelling insight reports and writing them as documents. Upsert happens client side: this ETL path looks the identity up in groups of a hundred, then routes matches to updates and the rest to inserts.
Identity looked up first, then records routed.
Country, device, age, gender, platform, action type.
Seven by default. Raise it for full attribution.
Polytomic is bi-directional by default, so you can move data the other way just as easily.

Jonathan Krangel
VP Global Head of Revenue Operations
“Polytomic handles so many ETL and sync jobs at Cursor. They are a true partner to us.”
Follow these simple steps to connect Facebook Ads with MongoDB in minutes
Connect Facebook Ads
Connect MongoDB
Create sync
Enable sync
Connect Facebook Ads to Polytomic with OAuth, or with your own Meta system user token.
Connect MongoDB to Polytomic using an Atlas SRV string or explicit host details.
Sync data in either direction between Facebook Ads and MongoDB. Choose the source data and destination objects for the direction you need.
Map the fields, choose the sync schedule and behavior, then save and enable the sync.
Get answers to common questions about the integration process
Sync data in either direction between Facebook Ads and MongoDB.
Use both integrations' source and destination capabilities in one managed sync workflow.
Enterprise encryption and security protocols ensure your data remains protected.
Get up and running in minutes with our step-by-step integration guide.