A lot of Marketo "audits" start at the campaign layer because that is where the visible work happens. New programs. A cleaner folder structure. A tightened tokens list. Smart-list filters rewritten so they actually reference fields that exist. The work shows up in screenshots, which makes it easy to scope, easy to bill, and easy for marketing leadership to point at when someone asks what we have been doing for the last six weeks.
I have run a lot of these audits. The output is usually clean. The campaigns run faster. The folder structure becomes navigable. The documentation gets a refresh. And then three months later, the marketing operations lead is asking the same questions they were asking before the audit started, and the VP of marketing is wondering why the numbers feel off again.
This piece is about why that happens, and how I scope Marketo work differently now.
What the standard audit is measuring
The conventional Marketo audit measures the instance. Smart campaign QA findings. Deprecated token usage. Programs that have not fired in ninety days. Fields with low fill rates. Suppression segments that overlap. Lifecycle programs that do not track everyone they should. The deliverable is usually a spreadsheet with severity ratings and effort estimates, and the cleanup follows naturally from that list.
