Enterprise nurture programs fail review for the same reason every quarter. The agent drafted, the program shipped, and nobody can reconstruct who said the claim was approved. Dock pairs with Marketo and Salesforce Marketing Cloud to record the agent decision, the brand owner, and the legal sign-off as one attributed row. Marketo still owns the send. Dock owns the interpretation behind it. The reviewer chain is queryable months later.
Marketo and Salesforce Marketing Cloud stay the system of record for the raw data. Dock is the system of record for what the agent interprets. Each Dock row carries a pointer back to the platform record, agent identity, decision, reviewer, and timestamp. The agent re-fetches platform data via fresh API reads when it needs current state.
The review brief surface
One Dock table, nurture_review_briefs, holds every program waiting on a human. Rows are created by the agent the moment a Marketo program enters draft.
| program_id | track | agent | proposed_claim | brand_reviewer | legal_reviewer | status | | --- | --- | --- | --- | --- | --- | | MK-4421 | Mid-market expansion, Q3 | mei-marketing-agent | "Cuts review time 60%" | priya@ | dana@ | legal_hold | | MK-4422 | FinServ vertical drip | mei-marketing-agent | "SOC2 Type II certified" | priya@ | dana@ | approved | | MK-4423 | EMEA reactivation | mei-marketing-agent | "GDPR-aligned by default" | klaus@ | dana@ | brand_review |
Each row links back to the Marketo program ID. Reviewers see what the agent proposed, why, and what platform data it pulled. When legal asks "where did this claim come from," the answer is one click, not a Slack archaeology dig.
The workflow
The Mid-market expansion track needs a four-email sequence by Friday. The agent reads the Marketo program brief, drafts copy, and writes a nurture_review_briefs row with the proposed claims and the underlying source. Priya in brand sees the row in her Dock inbox, edits one subject line, and marks brand_approved. The row routes to Dana in legal. Dana flags the "60%" claim, asks for the customer study citation, and the agent re-fetches the source doc, posts the link, and updates the row. Dana approves. The agent pushes the final copy back to Marketo, sets the program to scheduled, and stamps the row sent_at. Three weeks later, when a prospect questions the claim, the full chain is one query.
Why this matters
Forrester reports that B2B marketing teams ship campaigns faster than they can learn from them, and the visibility vacuum widens when agents are in the loop (Forrester, B2B marketing research). Adobe documents Marketo's program and Smart Campaign primitives but treats human review as out of scope (Adobe Marketo Engage documentation). Dock fills that gap. The marketing pillar covers the broader pattern. The agent audit and compliance doc explains why the reviewer chain has to be queryable, not buried in a logs bucket. The agent identity primer covers why mei-marketing-agent is a real principal with its own credentials, not a service account shared across the team.
The same surface works for Dock for sales when the ABM team runs paid plays alongside nurture, and the sales playbook shows how the reviewer chain folds into pipeline review. Compliance leads tend to start from the audit doc.
Try it
Point your Marketo workspace at Dock and run one program through the review brief table this week. You will see the reviewer chain in the row before the program goes live.
FAQ
Does Dock replace Marketo? No. Marketo is the system of record for programs, sends, and engagement data. Dock holds the agent interpretation and the human reviewer chain that sits in front of it.
What about Salesforce Marketing Cloud? Same pattern. The Dock row points at the SFMC journey ID instead of the Marketo program ID. The reviewer surface is identical.
Who creates the brief row, the agent or a human? The agent. The moment a Marketo program enters draft status, the agent writes the row with its proposed claims and the platform records it pulled.
Can legal block a send from Dock? Yes. Until the legal_reviewer column is approved, the agent will not push the final copy back to Marketo or move the program out of draft.
