Skip to content
Database ⇄ Marketing

InterSystems IRIS to Marketo integration — real-time, two-way sync

Keep InterSystems IRIS and Marketo 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 InterSystems IRIS and Marketo

Give your team Marketo's contacts, campaigns, and engagement in InterSystems IRIS: query them with SQL, push audiences built from your own data back to Marketo, and skip the marketing API.

Marketo holds the people, audiences, and campaign activity that marketing runs on, but that data sits behind interfaces built for marketers, not for your internal systems. Engineers and analysts who need contacts, list membership, or engagement, for reporting, attribution, or product logic, end up writing integration code against a rate-limited API and maintaining it forever. Meanwhile the customer and usage data marketers want for targeting already lives in InterSystems IRIS, hard to get into campaigns without manual exports.

Stacksync mirrors Activities and Lead Changes, Static Lists, Programs and Program Members, Smart Campaigns from Marketo into Globals, Namespaces, Stored Procedures, Tables in InterSystems IRIS field by field, in real time, and in both directions. Marketing records become rows your code can query and join with product and customer data; audiences and attributes computed in InterSystems IRIS, from usage, orders, or account status, sync back into Marketo to drive campaigns and ads, with Marketo kept authoritative for engagement. You decide which side owns which fields, and Stacksync resolves conflicts by rules you set.

Common use cases

  • 01 Replicate IRIS tables to Postgres so application teams can build against a familiar database
  • 02 Sync operational tables in IRIS bi-directionally with a CRM so business teams work on IRIS-backed data without SQL access
  • 03 Sync Opportunities and Opportunity Roles into Marketo so revenue and pipeline data can drive account-aware nurture and reporting.
  • 04 Two-way sync Marketo Leads with a Postgres or warehouse table, matched on email, so RevOps queries and updates marketing profiles in SQL while marketers keep working in Marketo.

Common sync patterns

Build audiences from your own data

Segments computed in InterSystems IRIS from product usage, orders, or account status sync into Marketo as lists or audiences, so campaigns and ads target the people your data says they should.

Engagement and results next to the customer

Opens, clicks, sends, RSVPs, or ad activity from Marketo land in InterSystems IRIS beside the matching customer record, ready for reporting and revenue attribution.

React to marketing changes as row changes

A new lead, form fill, or list change in Marketo arrives as a row change in InterSystems IRIS, so scoring, jobs, and notifications run in the tooling your team already uses.

What you can sync between InterSystems IRIS and Marketo

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.

InterSystems IRIS objects Marketo objects How this pairing syncs
Schemas Schema organization scopes which tables a sync connection can see. 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. Schemas is specific to InterSystems IRIS and Smart Campaigns to Marketo — each maps to any object or custom field on the other side.
Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. 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. Persistent Classes is specific to InterSystems IRIS and Leads to Marketo — each maps to any object or custom field on the other side.
Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. 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. Globals is specific to InterSystems IRIS and Companies to Marketo — each maps to any object or custom field on the other side.
Namespaces Namespaces partition databases and determine the connection context for integrations. 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. Namespaces is specific to InterSystems IRIS and Opportunities and Opportunity Roles to Marketo — each maps to any object or custom field on the other side.
Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. 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. Stored Procedures is specific to InterSystems IRIS and Custom Objects to Marketo — each maps to any object or custom field on the other side.
Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. Activities and Lead Changes Engagement feed (opens, clicks, form fills, Data Value Changes) read via GET /rest/v1/activities.json using a paging token from /rest/v1/activities/pagingtoken.json (sinceDatetime), plus Get Lead Changes and Get Deleted Leads; read-only, also available via async Bulk Activity Extract. Tables is specific to InterSystems IRIS and Activities and Lead Changes to Marketo — each maps to any object or custom field on the other side.

How changes propagate between InterSystems IRIS and Marketo

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.

InterSystems IRIS Marketo Interval-based propagation

DetectionStacksync polls InterSystems IRIS for changes on an incremental schedule, reading only records changed since the previous pass. Polling (timestamp or query-based).

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

Marketo InterSystems IRIS 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 InterSystems IRIS as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • InterSystems IRIS: Constrained by database resources rather than published API rate limits.
  • 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.
What ships with InterSystems IRIS ⇄ Marketo

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the InterSystems IRIS and Marketo connectors work

InterSystems IRIS

Integration surface
SQL over JDBC/ODBC, plus object and REST access layers
Authentication
Database credentials
Change detection
Polling (timestamp or query-based); no standard webhook surface
Capabilities
read · write
Rate limits
Constrained by database resources rather than published API rate limits

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.
How it works

How to connect InterSystems IRIS to Marketo — 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 InterSystems IRIS and Marketo 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
    InterSystems IRIS connected
    Marketo connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

InterSystems IRIS and Marketo 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 427 integrations available for InterSystems IRIS and Marketo.

Popular · 7 of 427
All InterSystems IRIS integrations All Marketo 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