Most Marketo instances are three admins old. The first one built it fast during implementation. The second inherited it, added their own layer of programs and workarounds, and left. The third — maybe that's you — is now running campaigns on top of automation nobody fully understands, fields nobody remembers creating, and a sync that mostly works.
None of that means the instance is broken. It means nobody currently knows whether it's broken. That's what an audit is for: not a cleanup, not a migration, just a documented answer to the question "what does this thing actually do, and where is it costing us?"
Here's what a thorough Marketo audit covers, and what each area typically turns up.
Database health: where the money leaks quietly
Marketo prices by database size, which makes database hygiene one of the few audit areas with a direct line to the invoice.
Start with the unmarketable population: how many records are duplicates, hard bounces, unsubscribes with no other value, or contacts with no email address at all? In most instances we see, 15–30% of the database is paying rent without doing work. Then look at field completeness on the fields that actually drive segmentation and scoring — not all 400 fields, the eight that matter. If "Industry" is blank on half your database, every segmentation built on it is quietly wrong.
The audit output here isn't "the database is messy." It's a count, a cost, and a purge/retention policy you can defend to whoever owns the Marketo contract.
Campaign and program performance: what's actually working
Pull the last 12–18 months of program performance and look for patterns, not individual wins. Which channels convert past the click? Which nurtures have engagement decaying stream by stream? Which programs were cloned from a template that had tracking misconfigured — meaning a year of "results" is actually a year of unmeasured sends?
The most common finding isn't underperformance. It's unmeasurable performance: period costs missing, program statuses never updated, acquisition programs untagged. You can't optimize what was never instrumented, and an audit is usually the first time anyone lists how much activity falls in that bucket.
The CRM sync: where trust goes to die
If marketing and sales report different lead numbers, the explanation almost always lives in the sync. The audit checks:
Sync errors and their causes — permission failures, picklist mismatches, records failing validation rules on the CRM side. Marketo retries quietly, and a sync that's been erroring for months can look healthy from the outside. Field mapping drift — fields that exist in both systems but mean different things, or one-way syncs that someone assumed were two-way. Lifecycle alignment — whether a "lead" in Marketo and a "lead" in the CRM are even the same concept, and where records silently fall out of the funnel between systems.
This section of the audit usually produces the single highest-impact fix on the list, because sync issues corrupt every report downstream of them.
Automation sprawl: the workflows nobody dares touch
Every mature instance has them: smart campaigns built years ago, still active, purpose unknown. The audit inventories every active trigger and batch campaign and answers three questions per item — what does it do, what does it touch, and does anything still depend on it?
The output is a registry, not a purge. Deleting mystery automation without documentation is how outages happen. Documenting it is how you earn the right to retire it safely later. Expect to find duplicated logic (three campaigns doing overlapping lead routing), triggers firing on fields no longer populated, and at least one workflow that exists solely to compensate for a problem that was fixed two admins ago.
Scoring and lifecycle: does the model match reality?
Lead scoring models are usually written once, at implementation, based on guesses about behavior. The audit compares the model against actuals: do high-scoring leads convert? Are scoring thresholds routing junk to sales — or worse, holding back real buyers? Is there score decay, or does a webinar attended in 2023 still count?
The same lens applies to lifecycle stages: are stage definitions documented, are the transitions automated or tribal knowledge, and do marketing's stages reconcile with the CRM's?
Compliance and deliverability: the ones you can't defer
Consent capture, unsubscribe handling, data retention — reviewed against GDPR and whatever your own privacy policy claims. (We're operators, not lawyers; the audit flags, your counsel decides.) On the deliverability side: authentication records, sender reputation signals, and whether communication limits actually exist or every business unit can email the whole database on the same Tuesday.
From findings to a fix list
An audit that ends in a 40-page document nobody reads is decoration. The output that matters is a single prioritized list where every finding has three attributes: revenue impact, effort to fix, and owner. Quick wins — the sync error that takes an hour to fix, the suppression list that isn't suppressing — get separated from structural work like a scoring rebuild or a database purge policy.
That list is the real deliverable. It works whether the fixes are done by your team, by us, or by another vendor entirely.
When to audit
Three moments make an audit obviously worth it: you've inherited the instance and the person who knew where the bodies are buried is gone; something big is coming — a migration, a new CMO, a compliance review — and you need current state before committing to a plan; or renewal is approaching and nobody can say which features and database tiers you actually use.
If none of those apply but the numbers between marketing and sales haven't matched in two quarters — that's the fourth moment.
This is the long-form version of what we cover in a stack audit — one call, one week, one document, and the findings are yours whether you hire us afterward or not. If the whole stack needs the same treatment, not just Marketo, start at account & stack audits.