Ask buyers what frustrates them about their marketing automation platform and the answer depends on which one they run. Marketo, Eloqua and Pardot users most often say the platform takes specialists to run and that its builders feel dated; HubSpot users rarely say either, and instead say their requirements have outgrown their setup, or that its workflows suit their B2C needs less well. Across all four, buyers describe data that does not sync cleanly with the CRM or report well, cost that becomes hard to justify as the database or deployment grows, and AI that has not kept pace with what they expect. Outgrowing the platform is the complaint behind most completed moves; cost is the one named most often in planned ones. This page covers the marketing automation product; for HubSpot and Salesforce as CRMs, see top complaints about CRM platforms, and for the ratings and the pre-purchase view, what marketing automation buyers wish they'd known.
The six complaints — graded
Each complaint is classified by how buyers in these interviews typically respond: tolerating the issue, working around it, waiting for the vendor, or reconsidering the contract. These are observed responses, not fixed severity ratings; the same limitation may be manageable for one company and unacceptable for another.
It takes specialists to run
The complaint that separates the enterprise platforms from HubSpot. “It just takes someone really, really technical to be able to use Marketo,” one buyer says; another that “It is not simple, so it actually requires a dedicated team to operate.” A Pardot user calls it “not a type of tool that is for non-technical people or non-technical teams.” Most companies staff for it, with marketing operations teams, certified administrators and consultants, and accept a single point of failure when that person leaves. It is still named in several moves off Marketo and Eloqua, most often towards HubSpot.
Named for this: Marketo · Eloqua · Pardot · HubSpot
Outgrown, or the wrong fit
This complaint appears across the platforms but takes different forms. Some HubSpot buyers report that their campaigns or lifecycle requirements have become more sophisticated than their current setup comfortably supports; others find its workflows less suited to their particular B2C needs. Marketo and Eloqua buyers describe narrower limitations involving templates, segmentation, custom objects or campaign execution. These are buyer assessments of fit, not universal limits on what each platform can support. “HubSpot is a good tool for SMBs, but I think it lacks sophistication as your email marketing programs transform,” says one, and a former user found it “much more B2B; it's not very friendly in creating workflows and user journeys.” On the enterprise side, one buyer calls Marketo's “landing page creation capabilities” “pretty bad, in my opinion.” Platform fit is the most frequently cited reason for completed moves in these interviews. Some enterprises replaced Marketo with Salesforce Marketing Cloud to meet requirements they felt Marketo was not satisfying, while some B2C brands left HubSpot for platforms they considered better suited to their workflows.
Named for this: HubSpot · Eloqua · Marketo · Pardot
CRM synchronization and reporting fall short
Buyers describe two related data frustrations: difficulty keeping marketing automation records synchronized with their CRM, and reporting that does not provide the detail or flexibility they need. The causes vary. Synchronization problems may involve integrations, field mappings or implementation decisions, while reporting complaints concern the information teams can access and analyze. An Eloqua user says “where it leaves us desiring more is their reporting and analytics.” Many buyers respond by fixing their configurations, exporting data or using separate analytics tools rather than changing platforms. These problems can also influence replacement decisions: one company moved from HubSpot to Marketo after recurring Salesforce synchronization difficulties, and a Marketo user says “one thing that would cause us to more actively consider switching is if the data syncing continues to break as often as it does.” The interviews do not establish that every such problem originates in the marketing automation product itself.
Named for this: Pardot · HubSpot · Marketo · Eloqua
Dated interface and builders
Old-looking screens, slow loads and, above all, email and landing-page builders. “Our lifecycle team for marketing struggles to build in Marketo because the email builder is not user-friendly,” says one buyer; an Eloqua user finds “the tool seems a little bit dated.” Buyers rarely leave over it. They bolt on a separate email builder, or move landing pages to another tool, and keep the platform underneath. HubSpot users raise it least.
Named for this: Marketo · Eloqua · Pardot
Cost and the pricing model
Buyers describe two related frustrations: costs that rise as their contact databases grow, and the expense of licensing a platform for the people or capabilities they need. HubSpot and Pardot users describe higher charges tied to contact or record volumes, while a Marketo buyer objects to the overall pricing required for their organization. The common complaint is that the total cost becomes difficult to justify as the deployment grows. A HubSpot user says “every time you go above a certain threshold, they start charging you more money”; a Pardot user that “they can charge quite a lot for the records”; and a Marketo user says “But we looked at pricing of just the range of users, and it's just too expensive.” Cost is the reason named most often in planned and evaluated moves, and it is behind several completed ones.
Named for this: Marketo · HubSpot · Eloqua · Pardot
AI and innovation haven't kept pace
The complaint that buyers' platforms have not moved as fast as their expectations, especially on AI. “Marketo really hasn't innovated in a number of years around marketing automation or AI,” one buyer says; another that “Eloqua's roadmap is falling behind its competitors”; and a HubSpot user that “the AI aspect of HubSpot needs a little more work.” Marketo and Eloqua users raise it most. Most wait for their vendor; a few are evaluating newer, AI-first platforms, and at least one has moved to one.
Named for this: Marketo · Eloqua · HubSpot · Pardot
Who leaves, and why? Completed moves in these interviews run in every direction. Salesforce Marketing Cloud is the most common destination, mostly for enterprises whose requirements Marketo was no longer meeting; smaller teams move from Marketo or Eloqua to HubSpot for ease of use; some B2C brands leave HubSpot for platforms they find better suited; and one company moved from HubSpot to Marketo because its Salesforce sync kept breaking. Outgrowing the platform is the reason named most often in completed moves; cost and complexity lead in planned and evaluated ones, where HubSpot is the platform most often under consideration.
Due for a stack physical?
Book mine →The stories behind the complaints
The counter-current: what keeps marketing automation buyers in place
Each platform has its defenders. Marketo is valued for its flexibility and its connection to Salesforce; for a Pardot user, being native to Salesforce is the point: “Pardot saves the day every time.” HubSpot's ease of use is what its fans lead with: “I think it blows everything else out of the water.” But the strongest force is switching cost. Programmes built over years are wired into everything, and “The migration of an email marketing automation system is so costly,” as one operations leader puts it, before counting the cost of retraining. Buyers also blame their own setup more than in most categories: “I'm trying not to let my frustrations with how we implement Marketo taint my comments about the tool itself,” says one. Before you conclude the platform is the problem, separate what the vendor controls — the builders, the pricing model, the pace of AI — from what depends on your CRM, your data and the people you have to run it.
What this means — whether you run one or you're buying one
If you already run a marketing automation platform, most complaints are handled internally: buyers staff for complexity, bolt on builders, export data to fix reporting, and wait for AI features. Outgrowing the platform and its pricing model are different, because they are the complaints most likely to end in a move. If you're evaluating one, our recommendations — not practices buyers describe — are to model the full contract cost two years out, including contact or record tiers, user access, required features and other applicable charges, not just today's database size; to have the person who will build campaigns, not an administrator, build one during the trial; to test the sync with your own CRM data; and to be honest about whether you need enterprise depth or ease of use, since that is the line the complaints divide along. For cost, see what buyers actually pay for marketing automation; for where buyers go, Marketo alternatives, HubSpot alternatives, Eloqua alternatives and Pardot alternatives.
Common questions
What are the most common complaints about marketing automation platforms?
Among the Marketo, HubSpot, Eloqua and Pardot users in these interviews, six complaints recur: the platform takes specialists to run; buyers outgrow it or find it the wrong fit; data does not sync cleanly with the CRM or report well; the interface and email and landing-page builders feel dated; cost, whether from contact or record tiers or from licensing; and AI and innovation that has not kept pace with what buyers expect. Outgrowing the platform is the complaint behind most completed moves, and cost is the one named most often in planned and evaluated ones.
What are the biggest complaints about Marketo?
Marketo users in these interviews most often say it takes someone highly technical, or a dedicated operations team, to run; that its interface and email and landing-page builders feel dated; that data syncing with the CRM breaks or reporting is shallow; and that the cost becomes hard to justify as the deployment grows. Many still value its flexibility and its connection to Salesforce.
What are the biggest complaints about HubSpot as a marketing automation platform?
HubSpot users in these interviews rarely say it needs specialists or looks dated; ease of use is what they praise. Their complaints are that their email programmes have grown more sophisticated than their setup comfortably supports, that some find its workflows less suited to their B2C needs, that contact-tier pricing climbs as the database grows, and that data and reporting have gaps. For complaints about HubSpot as a CRM, see the CRM complaints page.
What are the biggest complaints about Eloqua?
Eloqua users in these interviews most often say it needs a central specialist team to run, that it has specific capability gaps for their programmes, that its interface feels dated, and that reporting leaves them wanting more. In some teams only one or two people can use it at all.
Why do companies switch marketing automation platforms?
In these interviews completed moves most often follow a capability limit or a team outgrowing the platform, and they run in every direction: enterprises moving from Marketo to Salesforce Marketing Cloud to meet requirements they felt were not being met, smaller teams moving from Marketo to HubSpot for ease of use, and some B2C brands leaving HubSpot for platforms better suited to their workflows. Cost is named most often in planned and evaluated moves. Many unhappy users stay, held by programmes built over years and the cost of migrating and retraining.
A physical for your tech stack
Peer-powered: built from hundreds of verified buyer interviews, and fitted to the tools you already run. You get a shortlist for your stack and your next steps.
Book my stack physicalFree · no password · your answers are anonymized before they inform research like this.