Adobe Marketo Engage

What it is

Adobe Marketo Engage is the enterprise B2B marketing automation platform Adobe bought in 2018: email, forms, landing pages, lead scoring, nurture programs, and the Smart Campaign trigger engine that thousands of RevOps runbooks are built on. Its moat has always been the same two things — a programmable campaign model that a skilled admin can bend to almost any lead lifecycle, and a deep bi-directional sync with Salesforce and Microsoft Dynamics 365.

2026 is the year Adobe repositioned it as agentic. At Adobe Summit in April, Adobe announced callable agents that run as Smart Campaign flow steps (for example, normalizing job title, company, and phone fields before a lead reaches the CRM or a router like LeanData), a conversational “agent-first” workspace for building and QA-ing programs, and a native, Adobe-hosted MCP server. Adobe’s community team announced the MCP server as generally available on 2026-09-30, exposing more than 100 operations across programs, Smart Campaigns, emails, snippets, forms, lists, people, and folders.

The scoped use case

A marketing ops team at a Salesforce-centric B2B company with 50,000+ marketing contacts, multiple business units or regions, and a lead lifecycle complex enough to need program-level tokens, partitions, and scoring models that a single admin can version. In that setup, the new MCP server earns its keep: an ops lead can point Claude at the instance and ask it to audit which Smart Campaigns still reference a retired field, or to clone and re-token a webinar program for a new region, instead of clicking through the tree by hand.

Pricing reality

Adobe publishes no prices. Four packages — Growth, Select, Prime, Ultimate — are quoted annually and scaled by marketing-database size. Per Adobe’s package descriptions, Select adds event and webinar marketing and basic attribution; Prime adds target account management, predictive audiences, workspaces and partitions, and a sandbox; Ultimate adds Marketo Measure (formerly Bizible) and the upgraded tier of Dynamic Chat.

Real-world band, from third-party pricing trackers (estimates, not Adobe quotes, checked 2026-10-18): Growth roughly $14,000–30,000/year, Select $30,000–60,000, Prime $60,000–120,000, Ultimate $120,000 and up. Licensing is the smaller half of the bill. Budget one dedicated admin (commonly cited at $90,000–130,000 salary) or a managed-service partner, plus a one-time implementation of $25,000–150,000. One published audit put a 15,000-contact Growth customer at about $54,000/year all-in against roughly $10,000 for HubSpot Professional.

Best for

Marketing ops leaders at mid-market and enterprise B2B companies (roughly $50M+ revenue) running Salesforce or Dynamics as system of record, with a full-time Marketo admin and lifecycle logic that has outgrown HubSpot’s workflow model.

Not for you if you have no dedicated admin. Marketo without an owner degrades into a tree of unmaintained Smart Campaigns, and the license only pays back when someone is engineering programs every week.

Versus the alternatives

• HubSpot Marketing Hub — the top alternative by customer count and the one most Marketo shops evaluate at renewal. Pick it when time-to-value and UX outrank programmability: Professional runs about $890/month for 2,000 marketing contacts, plus a $3,000 onboarding fee, and its CRM-native data model removes the sync layer entirely. Pick Marketo instead when Salesforce stays the system of record and you need partitions across business units.
• Salesforce Marketing Cloud Account Engagement (Pardot) — the other incumbent by share. Pick it when the org is all-in on Salesforce and wants published pricing: list runs $1,250 to $15,000 per org per month, with 10,000 contacts included on every tier except Premium. Pick Marketo when you need Dynamics support or a more programmable campaign engine.
• The composable path — the newest challenger to Marketo is not a suite but a stack: HubSpot or Account Engagement for email, with Clay for enrichment, n8n or Workato for lifecycle logic, and 6sense or Demandbase for ABM. Pick it when your Marketo instance mostly sends email and the complex logic could live in code you control.

Watch-outs

• The API quota is shared, and agents spend it. The REST API defaults to 50,000 calls per day per subscription, 100 calls per 20 seconds, and 10 concurrent calls. Every MCP-driven audit, your CRM sync middleware, and your enrichment tools all draw from the same pool. Guard: give the MCP server its own API user and role, run large audits off-hours, and check the daily usage report before turning any agent loose on the full database.
• The MCP server is non-destructive by design. Delete operations — forms, folders, snippets, tokens, removing leads from static lists — were missing from the server as of a July 2026 community report, and Adobe’s own blog describes AI access as non-destructive. Guard: treat it as an audit and build tool; keep cleanup in the UI or your own scripts against the REST API, and confirm with Adobe that MCP is enabled on your instance before planning around it.
• Adobe is pruning features. The SEO tool was deactivated on 2026-03-31, Grab Images from Web is deprecated in the October 2026 release, and since 2026-09-30 Get Lead Activities and Get Lead Changes calls filtered by a static list of 10,000+ leads fail with error 1003. Guard: read the monthly release notes as a change log for your integrations, and test every middleware job that uses listId before the next renewal.
• Agent status is uneven. The MCP server is GA; callable agents and the AI assistant were still marked “coming soon” on parts of Adobe’s site. Guard: buy on what runs in your sandbox today, not the Summit keynote, and write the agent features you need into the order form if they drive the decision.