Technical Audit on Marketing Cloud Engagement
A read-only technical debt audit of a Marketing Cloud Engagement account that business, marketing ops and developers can each act on.
Overview
A strictly read-only technical debt audit of a Marketing Cloud Engagement account that business stakeholders, marketing operations and developers can each act on.
The audit reviews nine areas: Data Extensions, Automation Studio, Journey Builder, AMPscript/SSJS code, Content Builder, APIs and integrations, governance and security, deliverability compliance, and deliverability intelligence. Each area gets a 1–5 score, every finding is linked to a pricing lever, and findings are sorted into System health, Efficiency and Hygiene readings.
This version adds role-specific views, email, SMS, push and WhatsApp analytics, and an optional Marketing Cloud Advanced migration view. Nothing in the account is created, changed, run or deleted.
What you get
- Findings report — all nine areas, each with evidence, healthy signs, pricing impact and a three-line reading for business, ops and developer audiences
- Scorecard — a score-by-area chart, the three readings against benchmarks (including a 60% clutter line) and a plain-language glossary
- Interactive canvas with a role switch — business stakeholders see cost, contract exposure and decisions; marketing ops see where to fix things in the screens; developers see technical root causes. Each role gets its own tabs, headline figures, filters, table columns, roadmap items and open questions
- Channel analytics — which journeys actually sent and engaged by email, and whether SMS, push or WhatsApp exist, ending with a clear call on what to carry forward and what to leave off
- Remediation roadmap — ranked into Now (0–30 days), Next (30–90 days) and Later (90+ days), with impact, effort, pricing effect and owner role for every item. Written as recommendations only
- Pricing lever summary — across contacts, sends, storage, API calls, capacity, add-ons and labour, with recommended contract checks
- Unverified, and how to check — a table with view-only steps for anything the audit couldn't read
- Marketing Cloud Advanced migration view (optional) — on request, ranks which journeys and assets to rebuild as Flows and which to retire, maps each concept to its Advanced equivalent, and sets out the consent and data approach. It appears in the report and as a canvas tab, with no separate document
How it works
- Discovery — a short interview covering the audience, pain points, Business Unit scope, approval for public DNS checks and any contract terms
- Baseline inventory — takes stock of the account
- Evidence, area by area — retention and primary keys on data tables, automation schedules, journey goals, exits and suppression, email code and consent links, content folders and staleness, send history, sender governance and public email authentication records
- Channel performance — matches journey email steps to their emails and send history, so each journey's real performance (or lack of it) is visible by channel
- Score and publish — scores findings, links them to pricing levers and tags them by audience, then publishes the report and an interactive canvas that reshapes itself for each role
- Migration view (optional) — builds the Marketing Cloud Advanced view when you ask for it
Anything that can't be confirmed is marked Unverified, with view-only steps to check it.
Key configurations
- Strictly read-only — no personal data in outputs, only counts, rates and patterns
- No contract, no guesses — without a contract, every pricing lever is marked "Unverified – verify against your contract"
- Tagged by role — every finding lists the roles it matters to, plus a "where to fix" note and a technical-detail note
- Opt-in migration view — the Marketing Cloud Advanced view is labelled as outside the audit scope, ranked by design value and readiness when no performance history exists, and anchored to the documented release baseline
Before you start
- A Marketing Cloud Engagement connection with read access to data, automations, journeys, content, tracking and setup
- Marketing Cloud Advanced is optional, for the migration view
- Optionally, a brand kit and your contract or order form
- You'll be asked to approve the public DNS checks
This is an advanced recipe with six steps (five core, plus the optional migration view). A typical run takes 1.5–3 hours. Find the recipe in the Library and run it from there.