Ship deep Marketo integrations in days

Marketo exposes leads, activities, and custom objects through a REST API that runs on each customer’s own instance, and every instance has its own fields. With Ampersand, you can get this integration live for your customers in days.

Schedule a demo See Marketo guide

Build a custom data model to handle complex configurations

No two Marketo instances are the same. Every customer has custom fields, custom objects, and their own lead lifecycle. AI agents need infrastructure that understands Marketo at the per-tenant level.

3 / 4 customers

3 / 8 customers
  • Customer A: Lead (standard), Company (standard), Product Usage (custom)
  • Customer B: Lead (standard), Opportunity (standard), List (standard)
  • Customer C: Company (standard), Campaign (standard), Event Registration (custom)

Enable software and agents to take bi-directional action

With Ampersand, your engineers don’t need to learn Marketo’s REST API, its activity types, or its custom object model. Simply declare the actions you want your agents to take: read, write, proxy.

Example. Read: “Sync every lead that changed since the last run.”

  1. Ampersand gets an access token for this customer’s Marketo instance.
  2. Ampersand requests only the leads that changed since the last sync.
  3. The changed leads come back, page by page.
  4. Ampersand applies this customer’s field mappings.
  5. Ampersand sends the leads to your product.

Ensure your Marketo integration is always available

  • Managed auth

    Ampersand runs Marketo’s OAuth client credentials flow and refreshes access tokens for every customer’s instance.

  • Incremental lead sync

    After a full historic backfill, lead syncs read only the leads that changed, so your integration moves less data on every run.

  • Schema drift detection

    Get notified when fields are created, deleted, or changed in any customer’s Marketo, before the change breaks your integration.

Not all Marketo integrations are created equal

Marketo holds the leads and activity history that marketing and sales teams act on. With Ampersand, your developers can create a best-in-class Marketo integration.

In-House DIY Build Unified APIs Embedded iPaaS Ampersand
Data schema that works for all customers Lots of switch statements and special casesOnly access standard objects and fieldsBuild customer-specific workflows Flexible model with mappings
Object coverage Write and maintain clients for leads, activities, and custom objectsOnly common models and their standard fieldsLimited to the objects its prebuilt actions cover Leads, companies, opportunities, activities, and custom objects
Schema drift protection Manual incident debuggingNot supportedNot supported Get notified about schema changes
OAuth token custody You own the tokens, but you also have to manage refreshesVendor lock-inVendor lock-in Export at any time via API
Integration workflow Imperative custom codeSingle API clientDrag-and-drop, not integrated with Git Declarative manifest you can version control
Build vs. Buy Unified API vs. Ampersand

The Marketo objects your agents can read and write

Ampersand reads and writes Marketo leads and companies, writes opportunities and named accounts, and reads campaigns, lists, and custom objects.

Objects What’s included Read Write
Leads and companies
  • Leads
  • Companies
  • Salespersons
Supported Supported
Accounts and opportunities
  • Opportunities
  • Named accounts
  • Named account lists
Not supported Supported
Activities
  • Activities
  • Custom activities
  • Activity types
Partly supported, see the note below the table Supported
Campaigns, lists, and custom objects
  • Campaigns
  • Lists
  • Custom objects
Supported Not supported

Reading activities is in private preview. Incremental reads cover leads and activities; other objects are read in full on each scheduled read.

See every object in the docs

Questions people ask before they book a demo

  • Which Marketo objects can I read and write?

    You can read and write leads, companies, and salespersons. You can write opportunities, named accounts, named account lists, custom activities, and activity types, and read campaigns, lists, and custom objects.

  • Does Ampersand read only the leads that changed?

    Yes. After a full historic backfill, Read Actions pick up only changed leads and activities. Other objects are read in full on each scheduled read.

  • Do I need to register an app with Marketo?

    No. Marketo uses the OAuth 2.0 client credentials grant, so you don’t set up a provider app before you start. Ampersand gets and refreshes the access token for each customer’s instance.

  • Does Ampersand offer a unified API?

    Ampersand doesn’t offer a unified API. It works with Marketo’s own objects and fields as each customer sets them up, which differs from how a unified API works. We also give you the primitives to build your own unified data model.