Skip to content
Marketing ⇄ Data warehouse

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

Keep Marketo 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 Marketo and MotherDuck

Put modeled data to work and measure what it drives: MotherDuck and Marketo 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; Marketo 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 Views, Database Shares, Attached Local DuckDB Databases, Databases in MotherDuck with Custom Objects, Activities and Lead Changes, Static Lists, Programs and Program Members in Marketo 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 Marketo 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 Sync modeled MotherDuck tables outward to operational tools for activation
  • 02 Share curated, synced datasets with other teams through read-only database shares
  • 03 Extract Marketo Activities (opens, clicks, form fills, Data Value Changes) through Bulk Activity Extract or Get Lead Activities into a warehouse for lead scoring and multi-touch attribution.
  • 04 Load purchase or product-usage records into Custom Objects linked to Leads so nurture campaigns branch on behavior mastered in another system.

Common sync patterns

Keep the contact and audience list current

New and updated contacts, leads, or audience members flow between MotherDuck and Marketo, so the marketing audience reflects the people in your warehouse and corrections propagate instead of the two sides drifting apart.

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 Marketo, so targeting, routing, and personalization use up-to-date context.

What you can sync between Marketo 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.

Marketo objects MotherDuck objects How this pairing syncs
Programs and Program Members Marketing programs read via /rest/v1/programs.json; program membership and member status managed via /rest/v1/leads/programs/{programId}.json and the program status endpoint for acquisition and attribution reporting. Views Modeled projections used as outbound sync sources. Programs and Program Members is specific to Marketo and Views to MotherDuck — each maps to any object or custom field on the other side.
Smart Campaigns Automation flows read via /rest/v1/campaigns.json and run against a set of Leads by requesting a trigger campaign with POST /rest/v1/campaigns/{id}/trigger.json, so downstream logic can push Leads into a Marketo flow. Database Shares Read-only copies of a database shared with other users or teams. Smart Campaigns is specific to Marketo and Database Shares to MotherDuck — each maps to any object or custom field on the other side.
Leads Core person records (called Leads/People), deduped on email address by default or a configured dedupe field; read via GET /rest/v1/leads.json with a filterType, upserted via POST /rest/v1/leads.json (action createOrUpdate/createOnly/updateOnly), bulk-imported via CSV through POST /bulk/v1/leads.json, and bulk-exported via /bulk/v1/leads/export/create.json. Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. Leads is specific to Marketo and Attached Local DuckDB Databases to MotherDuck — each maps to any object or custom field on the other side.
Companies Company records linked to Leads via a company link field; read and upserted through /rest/v1/companies.json, typically mastered in a CRM or ERP and written into Marketo for account context. Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. Companies is specific to Marketo and Databases to MotherDuck — each maps to any object or custom field on the other side.
Opportunities and Opportunity Roles Revenue objects synced via /rest/v1/opportunities.json and /rest/v1/opportunities/roles.json; roles associate an opportunity with a Lead, so pipeline data can drive nurture and scoring. Schemas Namespaces within a database used to organize synced tables. Opportunities and Opportunity Roles is specific to Marketo and Schemas to MotherDuck — each maps to any object or custom field on the other side.
Custom Objects Auxiliary data tables described via /rest/v1/customobjects.json and read/written via /rest/v1/customobjects/{apiName}.json, linked to Leads by a dedupe/link field so campaigns branch on records like purchases or subscriptions. Tables The main landing target for synced records and source for analysis. Custom Objects is specific to Marketo and Tables to MotherDuck — each maps to any object or custom field on the other side.

How changes propagate between Marketo 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.

Marketo MotherDuck Interval-based propagation

DetectionStacksync polls Marketo for changes on an incremental schedule, reading only records changed since the previous pass. Polling: Get Lead Changes and Get Lead Activities from a paging token seeded by a sinceDatetime, plus Get Deleted Leads, or Bulk Extract filtered on.

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

MotherDuck Marketo 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 Marketo through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Marketo: Interactive calls are capped at 100 per 20 seconds (error 606) and a maximum of 10 concurrent calls (error 615) per instance, neither increasable; a default daily quota of 50,000 calls (increasable, resets midnight CST) applies. Bulk Extract shares a 500 MB/day export quota across data types with at most 2 concurrent jobs and 10 queued.
  • MotherDuck: Subject to the platform's compute and concurrency limits rather than per-request API rate limits.
What ships with Marketo ⇄ MotherDuck

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Marketo 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 Marketo or MotherDuck record.

Observability

Monitoring

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

Trading partners

EDI

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

How the Marketo and MotherDuck connectors work

Marketo

Integration surface
Marketo REST API (JSON over HTTPS) for Leads, Companies, Opportunities, Custom Objects, Activities, Lists, Programs, and Campaigns, plus an asynchronous Bulk Import (leads) and Bulk Extract (leads/activities/program members/custom objects) API and an Asset REST API for emails, forms, and landing pages
Authentication
OAuth 2.0 client_credentials (2-legged): GET the Identity URL /oauth/token?grant_type=client_credentials with a Custom Service client_id and client_secret to receive an access token valid for 3600 seconds, then send it as Authorization: Bearer on each call. The instance base URL is https://{munchkinId}.mktorest.com; passing the token as an access_token query parameter is deprecated (removal July 31, 2026).
Change detection
Polling: Get Lead Changes and Get Lead Activities from a paging token seeded by a sinceDatetime, plus Get Deleted Leads, or Bulk Extract filtered on createdAt/updatedAt. Marketo's Webhooks are Smart Campaign flow-step outbound HTTP calls to a URL, not a general record-change subscription, so there is no push feed of arbitrary CRUD.
Capabilities
read · write
Rate limits
Interactive calls are capped at 100 per 20 seconds (error 606) and a maximum of 10 concurrent calls (error 615) per instance, neither increasable; a default daily quota of 50,000 calls (increasable, resets midnight CST) applies. Bulk Extract shares a 500 MB/day export quota across data types with at most 2 concurrent jobs and 10 queued.

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 Marketo 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 Marketo 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
    Marketo connected
    MotherDuck connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Marketo 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 · Marketo ⇄ 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
    Marketo MotherDuck
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Marketo 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

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

Popular · 6 of 409
All Marketo integrations All MotherDuck integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own