Marketo Pricing: Four Packages and No Rate Card

A marketing operations lead builds a budget line for Marketo Engage from the figures in three roundups, which put the entry somewhere around a thousand dollars a month. The quote comes back structured on axes none of the roundups mentioned, and the number is not close. The roundups were not lying. They were reconstructing a price list that Adobe publishes nowhere on its own packaging page as fetched on 2 September 2026, and each one reconstructed it differently.

Adobe does publish something useful, and it is more specific than a talk to sales page usually is. Its page, headed "Marketo Engage pricing and packaging", carries four named packages, a feature matrix, and a set of hard published limits that constrain the quote whatever the rate turns out to be. Reading those limits is a better preparation for the call than any circulating figure.

Everything below is read from business.adobe.com as fetched on 2 September 2026, with a dated snapshot retained.

Four packages, and a Get pricing button on every one

The page is subtitled as simple, capability rich packages. Four packages sit under it, each with a one line description and its own "Get pricing" button, and no rate appears anywhere on the page.

Growth is described as "Core marketing email, segmentation, automation and measurement." Select is described as "Essential marketing automation and measurement." Prime is described as "Lead- and account-based marketing with journey analytics and AI personalization." Ultimate is described as "The most powerful marketing automation with premium attribution."

Underneath, a feature matrix runs the four packages against roughly thirty rows covering the lead and account database, "Native CRM Integration (SFDC, MSD & Veeva)", audience segmentation and targeting, advanced dynamic content and personalisation, custom user roles, campaign and journey automation, cross channel nurturing, scoring and routing, email and social marketing, landing pages and forms, search engine optimisation, paid media targeting, campaign reporting, secure domains, custom data objects, event and webinar marketing, interactive webinars, a marketing calendar, attribution dashboards, predictive content, dynamic chat, target account management, predictive audiences, advanced journey analytics, a sandbox, workspaces and partitions, and "Marketo Measure".

That matrix is where the useful numbers are, because most of its cells are inclusion ticks but five rows carry actual published values.

The package descriptions are also more informative than they first look, because they name the boundary Adobe is drawing rather than a feeling about size. Growth and Select are both described in terms of email, segmentation, automation and measurement, which is the core marketing automation job. Prime is the first package whose description reads "Lead- and account-based marketing with journey analytics and AI personalization.", so account based work is the boundary between the second and third packages rather than a bolt on. Ultimate is separated from Prime by one named thing, "premium attribution", which puts Marketo Measure at the top of the ladder. A team that needs multi touch attribution is therefore looking at the top package on the vendor's own description, and a team that needs account based targeting is looking at the third, whatever the seat count says.

The five limits Adobe does publish

Users. Growth carries 10. Select, Prime and Ultimate each carry 25. That is the single most load bearing number on the page, because it means the entry package is sized for a small team and the step from Growth to Select is a step in seat allowance as much as in capability.

API calls per day. The row is headed "API Calls (Daily)", and Growth carries "20k Calls / Day" against "50k Calls / Day" on the other three. For anyone syncing a CRM bidirectionally and running enrichment on top, that ceiling decides whether an integration design works, and it is worth checking against your own current call volume before the package conversation rather than after.

Custom data objects and fields. Three of the four packages carry the same published allowance, written on the page as "10 Objects - 2M Records". That record count is a real constraint on any account based model that stores its own object graph alongside the lead record.

Predictive content. Three packages carry "50 Assets". Interactive webinars are listed as Unlimited on one package and "Unlimited w/ Concurrency" higher up, which is a different thing: the second is about how many can run at once.

GrowthCore email, segmentation and measurement

• 10 users
• 20k API calls per day
• Core email, segmentation, automation
• Campaign reporting and insights

SelectEssential marketing automation

• 25 users
• 50k API calls per day
• 10 objects and 2M records
• 50 predictive content assets

Prime and UltimateAccount based marketing and attribution

• 25 users each
• 50k API calls per day
• Journey analytics and AI personalisation
• Premium attribution on the top package

One reading caution, because it changes what can honestly be said about the matrix. The inclusion marks in most cells are icons rather than text, so they do not extract from the page's bytes. Every feature attribution above is taken from a row carrying a textual value or from the package descriptions themselves. Anything sharper would be a guess about a graphic, and the page's own answer to that problem is a link reading "Download the PDF" for the full packaging list.

The axis every third party names and Adobe's page does not

Read the pages ranking for this query and they disagree about almost everything except one thing: they all say the bill is driven by the size of your mailable database. Their estimates run from around a thousand dollars a month to a band of forty to two hundred thousand dollars.

That agreement is interesting precisely because Adobe's own packaging page carries no database size ladder as fetched on 2 September 2026. Its database row is a feature line with no number attached, and the only record count on the page is inside the "10 Objects - 2M Records" custom data objects allowance, which is a different thing entirely.

So the reader arrives with a question the vendor answers structurally and leaves with numbers no vendor surface supports. The honest position is narrow. Adobe publishes no price on its Marketo Engage packaging page as fetched on 2 September 2026, it publishes four packages and five limits, and the closing call to action is simply "Get customized pricing for Marketo Engage." If contact volume is going to set your bill, it is a question for the call, and it should be asked as a ladder rather than as a single number.

Before the quote conversation

• ✓Yes: You know your current mailable contact count and its growth rate
• ✓Yes: You have measured your peak daily API call volume against the published ceiling
• ✓Yes: You know how many people genuinely need a seat, against 10 on the entry package
• ✓Yes: You have asked whether the contact ladder is a step or a per unit rate
• ✕No: You are budgeting from a figure you found in a roundup
• ✕No: You are assuming attribution is included below the top package

Who this product is sold to, in Adobe's own words

It is fair to ask whether a B2B revenue team is even the buyer here, given that Adobe sells Marketo Engage alongside a large creative and digital experience catalogue and its customer stories page now covers the whole company rather than this product.

The product page answers it plainly. Adobe describes Marketo Engage as an AI powered enterprise marketing automation solution built to "grow predictable pipeline and revenue". Its feature sections promise to "Align marketing and sales teams around the best leads and accounts", name sophisticated lead scoring, describe delivering buyer engagement data directly to sales teams in the CRM, and describe bi directional native CRM integration, which the packaging matrix names as "Native CRM Integration (SFDC, MSD & Veeva)".

That is a pipeline product sold to a revenue organisation, and the vocabulary is consistent across both surfaces. The scoring and routing half of it is the machinery described in lead scoring, and the nurture half is lead nurturing. Whether the constraint it addresses is your actual constraint is a separate question, and the diagnosis order for that is in demand gen strategy.

Where Marketo shows up in a stack you already own

One practical note that changes how the quote should be read. Marketo Engage is very frequently the integration a neighbouring tool gates behind its own higher tier, which means the total cost of running it is rarely just the Adobe line.

Calendly places its Marketo and Pardot connections on the Teams tier rather than Standard, so a scheduler that routes inbound demo requests into the same system costs more because Marketo is in the stack, which is set out in Calendly pricing. Webflow names Marketo among the firmographic integrations on the quoted enterprise version of its optimisation product rather than the self serve one, covered in Webflow pricing. Wistia's own answer about who its mid tier is priced for names Adobe Marketo Engage among its top integrations, which is the tell described in Wistia pricing.

None of those is a Marketo cost. All of them are costs that appear because Marketo is the automation layer, and a budget that counts only the platform line will be short by the difference between two tiers on three other products.

The short version

Adobe publishes four Marketo Engage packages, Growth, Select, Prime and Ultimate, each with a "Get pricing" button and no rate. The page's real content is the limits: 10 users on Growth against 25 on the rest, "20k Calls / Day" against "50k Calls / Day", an allowance written as "10 Objects - 2M Records", and "50 Assets" of predictive content.

The database sizing that every third party names as the main cost driver is not on the vendor's packaging page, so treat it as the first question for the call and ask for it as a ladder.

The feature matrix marks inclusion with icons rather than text, so per package feature attribution below the rows carrying values is not readable from the page, and Adobe's own answer to that is the downloadable packaging list.

Count the seats, measure the API volume, and price the neighbouring tools that gate their Marketo connector behind a higher tier. If the shortage is qualified conversations rather than the automation carrying them, see what a first campaign produces against your own market.

Package names, descriptions and every published limit above are read from Adobe's Marketo Engage pricing and packaging page, and the product positioning from its Marketo Engage product page, both fetched on 2 September 2026 with dated snapshots retained. Adobe published no rate on either surface at that fetch. Verify current terms with the vendor before relying on them.