Skip to content
Marketing ⇄ Data warehouse

Bingads to MotherDuck integration — real-time, two-way sync

Keep Bingads and MotherDuck in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Bingads and MotherDuck

Put modeled data to work and measure what it drives: MotherDuck and Bingads keep contacts, audiences, and campaign results in step in real time, in both directions.

MotherDuck is where your team models customers, product usage, and revenue into trusted tables; Bingads runs the campaigns, audiences, and messages that reach those people. The two overlap wherever the same person, account, or segment matters to both, and when the bridge between them is a nightly export or a hand-built list, marketing targets stale data while analytics never sees what the campaign returned.

Stacksync syncs Databases, Schemas, Tables, Views in MotherDuck with Campaigns, Ad Groups, Ads, Keywords & Negative Keywords in Bingads field by field, in real time, and in both directions. You decide which system owns which fields — a computed score or segment can flow out to Bingads while sends, opens, and conversions flow back to MotherDuck — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Land CRM and operational database records in MotherDuck so a small team gets warehouse-style analytics without cluster management
  • 02 Sync modeled MotherDuck tables outward to operational tools for activation
  • 03 Push campaign structure - campaigns, ad groups, ads, keywords, and negative keywords - from a planning database into Microsoft Advertising through the Campaign Management or Bulk service.
  • 04 Sync shared budgets and automated bid strategies so finance-approved spend and bids in an internal tool apply to live Microsoft Advertising campaigns.

Common sync patterns

Suppression and consent stay aligned

Unsubscribes, bounces, and consent or opt-out flags held in either system propagate to the other, so no one is messaged after opting out and MotherDuck holds the current state for auditing.

Enrich records with warehouse context

Product-usage counts, plan tier, region, or account owner computed in MotherDuck appear on the matching record in Bingads, so targeting, routing, and personalization use up-to-date context.

Activate a modeled audience

A segment or score built in MotherDuck — high-intent accounts, churn risk, a lifetime-value tier — lands as an audience or contact field in Bingads, so campaigns target the people your data actually points to instead of a static export.

What you can sync between Bingads and MotherDuck

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Bingads objects MotherDuck objects How this pairing syncs
Audiences & Remarketing Lists Remarketing, customer-match, in-market, and similar audiences; read and create/associate to keep audience lists aligned with a CDP or CRM. Schemas Namespaces within a database used to organize synced tables. Audiences & Remarketing Lists is specific to Bingads and Schemas to MotherDuck — each maps to any object or custom field on the other side.
Conversion Goals & Offline Conversions Conversion goals (read/create) plus ApplyOfflineConversions, which imports offline conversion events (closed deals, qualified leads) back into Microsoft Advertising to inform bidding. Tables The main landing target for synced records and source for analysis. Conversion Goals & Offline Conversions is specific to Bingads and Tables to MotherDuck — each maps to any object or custom field on the other side.
Ad Extensions (Assets) Sitelink, callout, image, call, and other extensions/assets associated to campaigns and ad groups; CRUD via Campaign Management. Views Modeled projections used as outbound sync sources. Ad Extensions (Assets) is specific to Bingads and Views to MotherDuck — each maps to any object or custom field on the other side.
Accounts, Customers & Users Customer Management hierarchy - accounts, customers, and users - read and managed to mirror agency/MCC-style structure and access into an internal database. Database Shares Read-only copies of a database shared with other users or teams. Accounts, Customers & Users is specific to Bingads and Database Shares to MotherDuck — each maps to any object or custom field on the other side.
Performance Reports Campaign, ad group, keyword, geographic, and audience performance via the asynchronous Reporting service (submit, poll, download); read-only spend and conversion data. Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. Performance Reports is specific to Bingads and Attached Local DuckDB Databases to MotherDuck — each maps to any object or custom field on the other side.
Campaigns Search, Audience, Shopping, and Performance Max campaigns with budget, status, and campaign-type settings; full create/read/update/delete through the Campaign Management service (or Bulk for scale). Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. Campaigns is specific to Bingads and Databases to MotherDuck — each maps to any object or custom field on the other side.

How changes propagate between Bingads and MotherDuck

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Bingads MotherDuck Interval-based propagation

DetectionStacksync polls Bingads for changes on an incremental schedule, reading only records changed since the previous pass. No webhooks or change-data-capture.

DeliveryEach detected change is applied to MotherDuck as a row-level write, with types converted between the two schemas.

MotherDuck Bingads Interval-based propagation

DetectionStacksync polls MotherDuck for changes on an incremental schedule, reading only records changed since the previous pass. Polling.

DeliveryEach detected change is written to Bingads through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Bingads: Service-specific throttling rather than one global limit. Ad Insight caps calls per user per minute with a 60-second sliding window at the customer level. The Bulk service caps download/upload calls and, once hit, returns 'no more bulk upload or download calls will be permitted for this account,' clearing after up to 15 minutes; Campaign Management caps entities per call, so large changes go through Bulk.
  • MotherDuck: Subject to the platform's compute and concurrency limits rather than per-request API rate limits.
What ships with Bingads ⇄ MotherDuck

Connect Bingads and MotherDuck for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Bingads–MotherDuck connection.

Real-time

Two-way sync

Changes in Bingads or MotherDuck instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Bingads or MotherDuck data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Bingads or MotherDuck record.

Observability

Monitoring

Track your Bingads ⇄ MotherDuck sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Bingads and MotherDuck.

How the Bingads and MotherDuck connectors work

Bingads

Integration surface
SOAP web services (Bing Ads API v13): Campaign Management, Bulk, Reporting, Customer Management, Customer Billing, and Ad Insight services, plus offline conversion import. SDKs for C#, Java, Python, and PHP; a Sandbox environment mirrors production.
Authentication
OAuth 2.0 (Microsoft identity platform / Azure AD) access tokens passed in the SOAP AuthenticationToken header, plus a Microsoft Advertising Developer Token that authorizes API access; calls are scoped by CustomerId and account (CustomerAccountId).
Change detection
No webhooks or change-data-capture. Reporting is asynchronous - submit a report request, poll until it completes, then download the file. Current campaign state is refreshed via scheduled Bulk downloads (full or by last-sync date) or entity list calls.
Capabilities
read · write
Rate limits
Service-specific throttling rather than one global limit. Ad Insight caps calls per user per minute with a 60-second sliding window at the customer level. The Bulk service caps download/upload calls and, once hit, returns 'no more bulk upload or download calls will be permitted for this account,' clearing after up to 15 minutes; Campaign Management caps entities per call, so large changes go through Bulk.

MotherDuck

Integration surface
SQL through DuckDB clients and drivers using a MotherDuck (md:) connection
Authentication
Access token created in MotherDuck (Settings > General > Create Token), pasted into Stacksync; database name and schema configurable if not using defaults
Change detection
Polling; no log-based CDC or webhook surface is exposed
Capabilities
read · write
Rate limits
Subject to the platform's compute and concurrency limits rather than per-request API rate limits
MotherDuck setup guide
How it works

How to connect Bingads to MotherDuck — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Bingads and MotherDuck with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Bingads connected
    MotherDuck connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Bingads and MotherDuck objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Bingads ⇄ MotherDuck
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Bingads MotherDuck
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Bingads and MotherDuck integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 407 integrations available for Bingads and MotherDuck.

Popular · 8 of 407
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.