SFMC production handoff
How Campaign Builder hands campaign work to Salesforce Marketing Cloud production.
Campaign Builder gives SFMC teams a structured handoff from campaign idea to reviewed draft artifacts. Bruno coordinates the agent work, Factory prepares configured production drafts, and Marketing Cloud remains the system of record for final review and launch.
Handoff model
From idea to SFMC-ready work products.
The value is not generic content generation. The handoff is a sequence of implemented Campaign Builder work products that technical evaluators can inspect before any production-bound Marketing Cloud change.
Campaign intent becomes a campaignSpec
Campaign Agent turns typed intent, uploaded working files, workspace knowledge, audience direction, messaging, journey direction, Data Extension needs, validation warnings, and grounding references into a Bruno-compatible campaignSpec.
Bruno routes the work
Bruno discovers entitled Campaign, Content, Email, Journey, Image, Audience, localization, Advisor, Factory, Data Extension, and AMPscript skills, then collects missing inputs and stages write actions with preview summaries.
Specialist agents prepare reviewable assets
Content, Email, Journey, Image, and localization flows create drafts, channel variants, email copy, translations, image selections, journey plans, readiness warnings, and previewable outputs before SFMC writes run.
Factory creates configured SFMC drafts
Factory uses enabled account settings, SFMC credentials, configured templates, campaign drafts, folder creation, image upload, Data Extension creation, template-based email generation, preview drafts, variant previews, and template review.
Team handoff
What each SFMC production role reviews.
Campaign Builder compresses production handoffs by giving each role a concrete review surface instead of passing disconnected briefs, copy docs, image notes, journey plans, and admin requests.
Campaign manager
Reviews the Campaign Agent brief, audience logic, naming, assumptions, validation warnings, and Bruno dry-run stage plan before the team commits to SFMC draft creation.
Content and email producer
Uses Content Agent and Email Agent outputs for subject lines, preheaders, HTML or slot edits, source-backed content variants, translations, copy updates, and preview summaries without losing review control.
Journey builder
Checks the Journey Agent plan, drafted email copy, reference journey selection, clone or scratch draft path, activationReadiness, cloneArtifacts warnings, and manual fix-up notes before activating in SFMC.
SFMC admin or operator
Validates BU-to-workspace mapping, account-scoped Marketing Cloud credentials, entitlement scope, template prerequisites, Content Builder folders, Data Extensions, email assets, request IDs, and write confirmation evidence.
Artifacts to inspect
Evidence a buyer can ask to see.
A credible evaluation should produce visible artifacts from planning, orchestration, production, and SFMC access. These outputs map directly to Campaign Builder route families and documented implementation behavior.
SFMC execution boundaries
Where Campaign Builder prepares work and where SFMC keeps control.
The handoff works because production boundaries are explicit: reads and previews come first, confirmed writes stay scoped, Journey Builder activation is manual, and enterprise request controls remain visible.
Reads and previews first
Marketing Cloud access includes Content Builder asset lookup, email search, email preview, folder path lookup, journey retrieval, event definition lookup, and scoped Data Extension row access before teams choose write paths.
Confirmed production writes
Email copy/update, slot updates, rewrite application, translation application, Content Builder saves, image insertion, Factory execution, and Bruno write-skill execution are explicit confirmed paths.
Draft journey boundary
Campaign Builder can create or clone Journey Builder drafts and surface readiness warnings, but Journey activation remains a manual Salesforce Marketing Cloud decision.
Scoped enterprise context
SFMC sessions and operations rely on authentication, tenant and workspace scoping, BU mapping, entitlements, encrypted credentials, CSRF checks for browser mutations, request IDs, and redacted logging.
Pilot readiness
Checks before using the handoff in a real SFMC evaluation.
These checks keep an evaluation grounded in configured Campaign Builder behavior rather than broad AI promises. They also help separate preparation, preview, draft creation, and final SFMC launch control.
Confirm the account has the required agent and Factory entitlements before evaluating a workflow.
Verify the SFMC connection resolves token context and maps the right enterprise or business unit to the intended Campaign Builder workspace.
Review Factory prerequisites: settings.factory.enabled, connected SFMC credentials, and configured template assets for template-dependent email and preview flows.
Run Bruno in dry-run mode before confirmed execution and inspect proposed artifacts, missing inputs, stage warnings, and pending write actions.
Check that journey output is labeled as Draft, includes activationReadiness, and never claims Journey activation happens automatically.
Trace one request ID through Campaign Builder responses and outbound SFMC calls for the operation under review.
Specialist workflow coverage
The handoff spans the implemented agent surfaces.
Campaign Builder supports the production handoff through focused agents and tools. Each is useful because it feeds reviewed SFMC work instead of acting as an isolated chat surface.
Campaign and Bruno
Campaign Agent creates the brief and campaignSpec; Bruno stages dry runs, pending inputs, and confirmed execution.
Content, email, and localization
Agents create channel variants, email updates, slot-aware changes, translations, and localized variants with reviewable write paths.
Journey and audience
Journey Agent prepares draft plans, reference reuse, readiness evidence, and manual activation warnings; Audience planning supports Data Extension contracts.
Image and Factory
Image flows track provider search, saved assets, generation requests, credits, and SFMC insertion; Factory prepares folders, Data Extensions, emails, previews, and template review.
Evaluator FAQ
Questions that clarify the production boundary.
These answers keep buyer evaluation focused on implemented Campaign Builder capabilities and realistic SFMC operating responsibilities.
Is this a replacement for Salesforce Marketing Cloud?
No. Campaign Builder is an execution layer around SFMC production work. It plans, drafts, previews, localizes, and prepares assets while keeping reviewed writes and launch decisions inside the Marketing Cloud operating model.
What makes the handoff different from a generic AI copy tool?
The handoff is built around implemented Campaign Builder work products: campaignSpec, Bruno dry runs, specialist agent outputs, Factory draft artifacts, SFMC asset operations, request evidence, and explicit write boundaries.
Can Campaign Builder create live sends automatically?
No. It can create reviewed SFMC draft artifacts and confirmed asset writes where configured, but final sends and Journey activation remain manual Salesforce Marketing Cloud decisions.
Where should a technical buyer start validation?
Start with SFMC connection readiness, entitlement scope, one Campaign Agent brief, one Bruno dry run, Factory prerequisite checks, one email or Content Builder preview, and one draft-only Journey workflow.
Evaluation takeaway
Campaign Builder improves the SFMC handoff without hiding final review.
The practical outcome is faster production movement: structured campaign inputs, coordinated agent work, localized and previewed assets, Factory draft creation, and explicit SFMC review boundaries for the teams that still own launch quality.