Salesforce Marketing Cloud execution
How Campaign Builder turns campaign ideas into Salesforce Marketing Cloud execution.
Campaign Builder sits between marketing intent and SFMC production work. Bruno coordinates specialist agents, Factory workflows, and authenticated Marketing Cloud operations so teams can move from brief to reviewed draft assets with fewer manual handoffs.
Execution operating model
What changes for SFMC campaign teams.
Campaign Builder improves the production path by turning campaign intent into traceable work products: a structured plan, specialist agent outputs, reviewed Factory artifacts, and explicit Marketing Cloud operations.
From scattered intake to a campaignSpec
Campaign Agent normalizes the idea, uploaded context, audience direction, messaging, journey direction, and Data Extension needs into a brief and campaignSpec that Bruno and downstream workflows can consume.
From handoffs to orchestrated specialist skills
Bruno routes work to entitled Campaign, Content, Email, Journey, Image, Audience, localization, Advisor, and Factory capabilities, asks for missing inputs, and stages confirmed writes instead of turning chat into hidden SFMC changes.
From one-off asset work to Factory drafts
Factory uses account-scoped campaign drafts, folder creation, image uploads, Data Extension creation, template-based email generation, previews, variant previews, and template review to prepare repeatable SFMC production artifacts.
From risky launch automation to reviewed SFMC execution
Marketing Cloud operations remain explicit: Content Builder and email writes are confirmed, journey creation produces drafts, Data Extension access stays scoped, and Journey activation remains a manual SFMC decision.
End-to-end flow
From a campaign idea to reviewed SFMC drafts.
The strongest product motion is execution transformation: reduce production handoffs while keeping campaign quality, account context, and safe Marketing Cloud boundaries visible.
Plan the campaign
Campaign Agent turns typed intent, uploaded files, workspace knowledge, and session context into a normalized brief, audience direction, email content plan, Data Extension plan, journey plan, validation warnings, and a Bruno-compatible campaignSpec.
Create channel-ready content
Content and Email Agent workflows draft from briefs, images, templates, and existing SFMC email assets. Email writes are previewed and confirmed before subject line, preheader, HTML, slot, copy, rewrite, or translation updates are applied.
Prepare journeys for review
Journey Agent uses a tool-driven chat loop to extract briefs, revise a journeyDraftPlan, draft email copy, check readiness, and search or clone reference journeys. It creates Journey Builder drafts only; activation remains manual in Marketing Cloud.
Localize and select imagery
Shared localization fields support source language, target locales, tone, and HTML preservation across Bruno, Email, and Content flows. Image Agent supports provider search, saved image assets, generation requests, credits, and SFMC insertion.
Route-backed evidence
Where technical evaluators can verify the execution claims.
Campaign Builder evaluation should not stop at screenshots or generated copy. The strongest proof is a trace from Campaign Agent planning through Bruno orchestration, Factory draft production, SFMC operations, and the guardrails that decide which writes can run.
Planning and Bruno handoff
Campaign planning is visible through `/api/v1/agent/campaign/generate-brief` and `/api/v1/agent/campaign/execute-campaign`, which produce normalized briefs, build packages, validation warnings, grounding references, and Bruno-compatible campaignSpec payloads.
Orchestrated execution
Bruno execution runs through `/api/v1/agent/bruno` and `/api/v1/agent/bruno/execute-campaign`, where entitled skills, missing inputs, pending write previews, dry-run stage plans, durable run records, request journals, and resume behavior can be reviewed.
Factory draft production
Factory is mounted at `/api/v1/factory` behind the `tool:factory` entitlement, with route families for campaign drafts, folders, image uploads, Data Extensions, template-based emails, preview drafts, variant previews, and template review.
Marketing Cloud connection and operations
`/api/v1/sfmc`, `/api/v1/sfmc-connect`, and `/api/v1/marketingcloud` cover SFMC launch, OAuth callback, BU mapping, token-context verification, Content Builder assets, folders, email assets, journeys, event definitions, and Data Extension access.
Specialist agent surfaces
`/api/v1/emails`, `/api/v1/agent/content`, `/api/v1/agent/journey`, `/api/v1/agent/image`, `/api/v1/agent/translator`, `/api/v1/agent/advisor`, and `/api/v1/agent/audience` keep email reuse, content creation, draft journeys, image work, localization, guidance, and audience planning inspectable as separate workflows.
Guardrail evidence
Evaluator checks should include first-party or SFMC session source, tenant and workspace identity, entitlement gates, account-scoped credentials, CSRF behavior for browser mutations, requestId propagation, encrypted SFMC secrets, and manual Journey activation boundaries.
Bruno Super Agent
One orchestration layer for specialist execution.
Bruno is the coordination layer across Campaign, Content, Email, Journey, Image, Audience, localization, Advisor, and Factory workflows. Its campaign execution endpoint can run dry plans first, then confirmed draft artifact creation after review.
Factory production workflow
Configured drafts before production writes.
Factory is not a generic content exporter. It is the implemented build tool for turning structured campaign inputs into account-scoped SFMC draft artifacts after entitlement, account settings, credentials, and template prerequisites are satisfied.
Confirm account readiness
Factory is available only when the account has the factory tool entitlement, account settings.factory.enabled is true, SFMC credentials are connected, and template-dependent flows have configured SFMC template assets.
Save the campaign draft
The campaigns router persists structured Factory campaign drafts and version metadata in the account-scoped Factory Campaigns collection before production assets are prepared.
Create the production structure
Factory asset routes create Content Builder campaign folders, Data Extension folders, upload image assets, and track image-analysis jobs for reviewed campaign inputs.
Generate and review SFMC outputs
Factory email and preview routes check templates, generate template-based emails, return raw or rendered previews, produce variant previews, and run AI template review before teams continue in Marketing Cloud.
Factory and SFMC operations
What Campaign Builder can prepare inside Marketing Cloud.
Factory is an entitlement-gated production workflow engine mounted under the Campaign Builder API. It relies on account SFMC credentials, configured templates, and shared Marketing Cloud clients rather than disconnected file exports.
Content Builder asset creation, patching, image upload, email search, email preview, and folder path lookup.
Journey retrieval, recent/search lookup, event definition lookup, draft cloning, and scratch draft creation from a configured journey template.
Data Extension planning, creation, custom creation, and row access through shared REST/SOAP SFMC clients where needed.
Factory campaign drafts, folders, image uploads, template-based emails, preview drafts, variant previews, and AI template review.
Implementation map
What evaluators can trace back to implemented route families.
The website positioning is grounded in Campaign Builder source surfaces, not standalone claims. These are the product areas a technical buyer can verify when reviewing Campaign Builder inside an SFMC environment.
Campaign brief to Bruno execution spec
Campaign planning is implemented through the Campaign Agent route family, where generate-brief and execute-campaign flows produce a normalized brief, build package, validation warnings, and campaignSpec for Bruno execution.
Agent handoffs stay entitlement-gated
Specialist surfaces for Campaign, Content, Email, Journey, Image, Translator, Advisor, Audience, Bruno, and Factory are mounted behind server-side entitlement checks before the workflows can read account context or call SFMC.
Factory produces configured SFMC drafts
Factory depends on enabled account settings, Marketing Cloud credentials, and configured templates before it creates campaign drafts, folders, uploaded image assets, Data Extensions, template-based emails, previews, or template reviews.
Marketing Cloud operations use shared clients
SFMC reads and writes run through the Marketing Cloud route family and shared REST/SOAP clients for Content Builder assets, email assets, journeys, event definitions, folder lookup, and Data Extension row access.
Advisor and localization remain support layers
Advisor routes provide account-grounded chat, saved advice, snippet context, job polling, and feedback, while translator/localization flows preserve target locale, tone, and HTML intent for reviewed content and email work.
Operational evidence follows requests
Campaign Builder propagates request IDs through responses and outbound SFMC calls, centralizes error formatting, encrypts SFMC secrets at rest, and keeps mutating browser requests behind CSRF checks.
Technical evaluator FAQ
The practical boundaries buyers should verify.
Campaign Builder is most useful when evaluators understand the difference between AI-assisted preparation, confirmed SFMC writes, and manual Marketing Cloud launch control.
Does Campaign Builder launch journeys automatically?
No. Campaign Builder can create or clone Journey Builder drafts and return readiness warnings, but activation remains a manual step inside Salesforce Marketing Cloud.
How does Campaign Builder know which SFMC assets it can access?
SFMC access comes from the authenticated account or workspace connection. Business-unit launches are mapped to Campaign Builder tenant and workspace IDs before sessions, credentials, or scoped tenant data are used.
What does a dry run do before production execution?
Bruno campaign execution can run with dryRun enabled to produce a stage plan and proposed artifacts without SFMC side effects. Confirmed runs use journaling and can resume failed or partial stages.
Where do image and localization workflows fit?
Image flows support provider search, saved assets, generation requests, credits, and SFMC insertion. Localization inputs such as source language, target locale, tone, and HTML preservation are shared across Bruno, Email, and Content workflows.
Pilot proof checklist
What to ask Campaign Builder to show in a real SFMC evaluation.
A credible pilot should produce observable artifacts at each stage instead of relying on broad AI claims. These checks keep the evaluation tied to implemented Campaign Builder surfaces and the SFMC boundaries your team will operate.
Campaign planning artifact
Ask for a Campaign Agent brief that includes audience direction, message structure, journey direction, Data Extension planning, validation warnings, and the Bruno-ready campaignSpec that later execution stages consume.
Bruno dry-run evidence
Review a Bruno dry run before production-bound execution. It should show entitled skills, missing inputs, stage planning, proposed artifacts, pending write actions, and manual Journey activation warnings without changing SFMC assets.
Factory readiness and outputs
Confirm Factory is enabled for the account and has SFMC credentials plus configured templates before testing campaign drafts, Content Builder folders, uploaded images, Data Extensions, template-based emails, previews, or template review.
Marketing Cloud write boundary
Trace which operations are reads, previews, draft creation, or confirmed writes. Email copy/update, slot edits, translation application, Content Builder saves, image insertion, Factory execution, and Bruno write-skill execution should be explicit.
Localization and image provenance
Check that localization flows preserve source language, target locale, tone, HTML structure, and tokens, and that image flows retain provider/source metadata, saved asset details, generation request state, and credit usage where applicable.
Enterprise request controls
Verify authentication mode, account and workspace scope, BU mapping, entitlement checks, encrypted SFMC credentials, CSRF protection for browser mutations, request IDs, centralized errors, and log redaction around the workflow under review.
Enterprise guardrails
Built around scoped access and explicit write boundaries.
Campaign Builder is designed for enterprise SFMC teams: authentication, entitlements, BU-to-workspace mapping, account-scoped credentials, request tracing, and manual review boundaries are part of the execution model.
Tenant and workspace scoping
SFMC enterprise and business unit context is mapped to Campaign Builder tenant and workspace IDs before local sessions or tenant data access are issued.
Confirmed production writes
Email copy/update, slot updates, rewrite application, translation application, image insertion, Factory execution, and Bruno write-skill execution use confirmed write paths with preview summaries.
Credential and request hygiene
SFMC secrets are encrypted at rest, shared SFMC clients propagate request IDs, mutating browser requests use CSRF checks, and logs avoid exposing sensitive payloads.
Evaluation takeaway
Campaign Builder speeds production without hiding SFMC review.
A buyer evaluating Campaign Builder should expect practical execution acceleration: structured briefs, generated and localized content, safer email updates, draft journey preparation, image workflows, Factory draft artifacts, and SFMC asset operations that respect account scope and confirmation requirements.