SFMC review controls
Execution Governance for Salesforce Marketing Cloud teams.
How Campaign Builder helps Salesforce Marketing Cloud teams evaluate the control points around AI-assisted campaign execution before reviewed work moves into Marketing Cloud.
What it supports
Concrete workflow support, not generic AI copy.
This use case is grounded in implemented Campaign Builder routes, agents, shared SFMC clients, and documented review boundaries.
Campaign Builder resolves authenticated account, tenant, workspace, SFMC enterprise, business-unit, and credential context before agent or Factory workflows run.
Specialist agents, content blocks, Bruno, and Factory are mounted behind entitlement gates so connected SFMC credentials do not automatically unlock every execution path.
Bruno dry runs expose stage plans, missing inputs, pending write summaries, proposed artifacts, request journals, and manual Journey activation warnings before production-bound execution.
Factory and specialist write paths depend on prerequisites such as tool:factory entitlement, settings.factory.enabled, connected SFMC credentials, configured templates, folder IDs, and preview summaries.
Journey Agent and Marketing Cloud routes keep Journey Builder output draft-only, with activation readiness, blockers, warnings, and manualActivationRequired state visible for SFMC review.
Implementation map
What technical evaluators can trace.
`requireAuth`, SFMC signed-request handling, `/api/v1/sfmc`, `/api/v1/sfmc-connect`, and BU mapping helpers establish account, tenant, workspace, enterprise, and business-unit context.
Route-level gates protect Campaign, Content, Email, Journey, Image, Translator, Advisor, Audience, Bruno, content-block, and Factory surfaces before workflow logic can run.
`POST /api/v1/agent/bruno/execute-campaign` supports dryRun planning and durable run records with stage state, artifact ledgers, request journals, resume behavior, and manual activation warnings.
Email copy/update, slot updates, rewrite application, translation application, image insertion, Content Builder saves, Factory execution, and Bruno write skills use confirmed paths with preview summaries.
Factory routes cover campaign drafts, Content Builder folders, image uploads, Data Extensions, template-based emails, preview drafts, variants, and template review behind the `tool:factory` entitlement.
Security middleware and shared clients support CSRF checks for mutating browser requests, security headers, request ID propagation, encrypted SFMC secrets, redacted logging, and centralized error handling.
Review boundaries
Where Campaign Builder stops before launch risk.
Boundary
Execution governance is not a compliance certification; it is an implementation-backed review model for account scope, route access, evidence, and SFMC write boundaries.
Boundary
A connected Marketing Cloud account does not bypass agent entitlements, Factory prerequisites, preview review, or explicit confirmation for production-bound writes.
Boundary
Dry-run output is planning evidence, not a send, asset write, or Journey activation.
Boundary
Campaign Builder can create reviewed assets and Journey Builder drafts, but send approval, final launch decisions, and Journey activation remain inside Salesforce Marketing Cloud.
FAQ
Evaluation questions for Execution Governance.
What should an SFMC admin inspect before a Campaign Builder pilot?
Inspect the auth source, account and workspace scope, enterprise and business-unit mapping, entitlement list, connected credential source, dry-run stage plan, pending write summaries, Factory prerequisites, request IDs, and manual launch follow-up.
Does execution governance let AI bypass Marketing Cloud controls?
No. The useful control model is the opposite: Campaign Builder keeps route access entitlement-gated, production-bound writes confirmed, Journey activation manual, and SFMC context traceable.
Which evidence should remain after a governed run?
A reviewed run should leave scoped context, proposed or created artifacts, preview summaries, changed asset IDs where applicable, request journals, warnings, and explicit Marketing Cloud follow-up steps.
Next step
Review this workflow against your SFMC setup.
Bring one existing campaign, journey, email, Content Builder process, or Data Extension workflow to the demo so the evaluation can stay concrete.