Campaign workspace
Plan from the campaign brief, not a blank SFMC screen.
Campaign Builder captures objectives, audiences, messaging, channel direction, and draft history before work moves into Marketing Cloud assets.
SFMC campaign execution layer
Turn campaign ideas into reviewed Salesforce Marketing Cloud drafts.
Campaign Builder coordinates Bruno and specialist agents to plan campaigns, generate email and content, prepare journeys, localize variants, and move approved work toward SFMC assets with enterprise guardrails.
Brief to buildFrom campaign idea to SFMC draft assets
One workflowBruno coordinates agents, inputs, and review
Review firstSFMC writes stay scoped and confirmed
Inside the app
The campaign operating layer for Marketing Cloud.
Campaign Builder gives marketers and admins a focused workspace for the work that happens before Content Builder assets and Journey Builder drafts are reviewed in Marketing Cloud.
Campaign control
Plan, brief, and hand off from one campaign workspace.
Give marketers a single place to turn goals, audiences, messages, and channel plans into Marketing Cloud draft work.
- Campaign dashboard
- Brief and idea history
- Search, duplicate, and reuse
Content generation
Generate email, content, and journey copy with review built in.
Bruno creates first drafts, variants, subject lines, and campaign copy while keeping team review and brand context visible.
- Multi-format content cards
- Live preview panel
- Brand-aware suggestions
Admin setup
Configure templates, blocks, and defaults once.
Admins can standardize content blocks, factory defaults, brand language, and rollout settings across the Marketing Cloud org.
- Setup checklist
- Template helpers
- Subscription-managed access
Screenshots
See Bruno and the SFMC workflow paths the site describes.
The public site should show the product doing the work: campaign planning, Bruno-led content production, and configured Marketing Cloud setup.
Bruno and content
Coordinate specialist agents from one execution thread.
Bruno routes work to Campaign, Content, Email, Journey, Image, localization, Advisor, and Factory flows while keeping review steps visible.
SFMC setup
Use configured templates, defaults, and account guardrails.
Admin setup supports templates, blocks, brand language, Factory defaults, subscription-managed access, and SFMC-connected production paths.
Campaign workflow
Move from marketing intent to Salesforce execution without handoff drag.
Brief
Describe the audience, objective, offer, and channels in natural language.
Generate
Create campaign ideas, copy variants, journey notes, and content blocks.
Configure
Map generated assets to your approved Marketing Cloud templates and brand defaults.
Handoff
Move faster from approved brief to reviewed draft artifacts for Salesforce Marketing Cloud.
From idea to SFMC execution
Specialist agents do the production work Bruno coordinates.
Campaign Builder is not a standalone content generator. It connects campaign planning, content, email, journey, image, localization, and Factory workflows to the Salesforce Marketing Cloud assets your team already reviews and launches.
Start with execution architecture
Use these pages to understand how Campaign Builder coordinates agents, Factory, SFMC operations, and confirmed write boundaries before evaluating individual workflows.
Validate SFMC readiness
Check authentication, business-unit mapping, account-scoped credentials, pilot evidence, production handoff evidence, security guardrails, and reviewed production write paths.
Inspect specialist workflows
Review the implemented agent surfaces for planning, content, email, audience, journey, image, localization, account-grounded recommendations, and workspace knowledge reuse.
Read how Campaign Builder turns ideas into SFMC executionSee how Bruno coordinates specialist agentsSee how Factory prepares reviewed SFMC draftsReview Data Extension planning and scoped row accessReview the technical FAQ and SFMC boundariesReview Knowledge grounding and workspace taxonomyVerify SFMC connection readinessReview SFMC security evidenceTrace request, audit, and SFMC execution evidenceMap SFMC reads, drafts, writes, and manual launch boundariesPlan a grounded SFMC pilotRun a buyer demo that proves the SFMC execution pathCollect buyer proof points for an SFMC technical evaluationTrace the production handoff from campaignSpec to reviewed SFMC draftsReview account-grounded Advisor guidanceSee how Campaign Agent creates SFMC build packagesSee how Content Agent creates SFMC-ready contentSee how Content Block creates template-constrained SFMC blocksSee how Email Agent reuses SFMC emails safelySee how Audience Agent prepares SFMC audience plansSee how Journey Agent creates reviewed SFMC draftsSee how Image Agent prepares SFMC-ready assetsSee how localization preserves SFMC review boundaries
Campaign Agent
Turns an idea, upload, or workspace context into a normalized brief, audience direction, email plan, Data Extension plan, journey plan, validation warnings, and a Bruno-compatible campaignSpec.
Content and Email Agents
Create content from briefs, images, and existing assets; generate variants; preview SFMC emails; rewrite or translate copy; and apply safer subject, preheader, HTML, or slot updates only through confirmed write paths.
Journey Agent
Builds Journey Builder draft plans from chat or uploaded briefs, searches or clones reference journeys, drafts email copy, checks readiness, and keeps activation as a manual Marketing Cloud step.
Image and Localization
Supports provider search, generation requests, saved image assets, SFMC image insertion, and shared localization fields that preserve language, tone, and HTML intent across Bruno, Content, and Email flows.
Bruno orchestration
Bruno discovers entitled skills, gathers missing inputs, previews write actions, and runs durable campaign execution with dry-run, resume, and request journaling support.
Factory production flows
Factory creates campaign drafts, Content Builder folders, image uploads, Data Extensions, template-based emails, preview drafts, variant previews, and AI template reviews.
SFMC operations
Campaign Builder reads and writes Content Builder assets, email assets, journeys, entry events, folders, and Data Extensions through authenticated account or workspace Marketing Cloud connections.
Enterprise guardrails
Authentication, entitlements, BU-to-workspace mapping, tenant scoping, CSRF checks, security headers, redacted logging, request IDs, and encrypted SFMC secrets bound execution to the right account.
Technical evaluator notes
What actually reaches Salesforce Marketing Cloud?
Campaign Builder is designed for reviewed execution: it moves campaign work toward SFMC assets, previews, folders, Data Extensions, and draft journeys while preserving human approval at the points that change production systems.
What can Campaign Builder create in Salesforce Marketing Cloud?
Factory and agent workflows can prepare campaign drafts, Content Builder folders, uploaded images, Data Extensions, template-based emails, preview drafts, and draft journeys. Journey activation stays inside Marketing Cloud for manual review.
How does Bruno keep specialist agents coordinated?
Bruno discovers entitled skills, collects missing inputs, shows pending write actions with preview summaries, and can run campaign execution through the Bruno campaign endpoint after confirmation.
Which SFMC assets can teams reuse?
Campaign Builder can search and retrieve accessible email assets, Content Builder assets, folders, journeys, event definitions, and Data Extension rows through the connected account or workspace Marketing Cloud credentials.
Where are the safe write boundaries?
Production writes require authentication, entitlement checks, tenant and workspace scoping, request tracing, and explicit confirmation for SFMC email copy/update, image insertion, content publishing, Factory, and Bruno write-skill execution.
SFMC operation matrix
Know whether a workflow is reading, drafting, writing, or waiting for Marketing Cloud review.
Campaign Builder is easiest to evaluate when each demo action is mapped to an implemented Salesforce Marketing Cloud boundary: safe read, draft creation, confirmed write, or manual launch step.
Open the full SFMC operations indexReads and previews
Email, Content, Journey, Image, Data Extension, and folder workflows retrieve accessible SFMC records through the mapped account or workspace connection before proposing changes.
Inspect read pathsDraft-building
Campaign Agent build packages, Journey draft plans, Factory campaign drafts, Content Builder folders, image uploads, Data Extensions, template emails, previews, variants, and template review all produce reviewable artifacts.
Review Factory draftsConfirmed writes
Email copy or update, Content Builder saves, image insertion, Factory production, and Bruno write-skill execution require entitlement checks, scoped credentials, pending action previews, and request tracing.
Check write boundariesManual launch
Journey Agent and Marketing Cloud draft creation keep activationReadiness, blocker warnings, EMAILV2 notes, entry-event follow-up, send approval, and Journey activation visible for human review in SFMC.
Verify Journey handoffDemo proof path
Ask Campaign Builder to prove the execution path, not just generate copy.
A strong demo should leave traceable artifacts from the implemented workflow: Campaign Agent planning, Bruno orchestration, Factory readiness, SFMC draft outputs, and the manual Marketing Cloud launch boundary.
Review the SFMC pilot planStart with one real campaign brief
Capture the normalized brief, audience direction, email content plan, Data Extension plan, journey plan, validation warnings, build package, grounding references, and Bruno-compatible campaignSpec.
Run Bruno in dry-run mode
Inspect entitled skills, missing inputs, pending write actions, preview summaries, proposed stages, artifact ledger, request journal, resume behavior, and manual Journey activation warnings before confirming work.
Check SFMC and Factory readiness
Verify mapped enterprise and business-unit context, account-scoped Marketing Cloud credentials, token context, tool:factory entitlement, settings.factory.enabled, configured templates, and folder or Data Extension prerequisites.
Review draft outputs inside Marketing Cloud
Confirm what was prepared as a draft: Content Builder assets, email copies or updates, localized variants, image insertion, Data Extensions, Factory previews, template reviews, and Journey Builder drafts that still require manual activation.
Buyer proof checklist
Turn the demo into evidence an SFMC admin can verify.
Use this checklist to keep a Campaign Builder evaluation concrete: every claim should map to implemented routes, scoped account context, dry-run evidence, preview artifacts, or reviewed draft outputs inside Salesforce Marketing Cloud.
Mapped SFMC session
Capture auth source, enterprise ID, business unit ID, tenant ID, workspace ID, token-context result, CSRF behavior for browser writes, and requestId on failures.
Connection readinessEntitled workflow scope
Show which Campaign, Content, Email, Journey, Image, Translator, Advisor, Audience, Bruno, content-block, and Factory capabilities are enabled for the account.
Security evidenceCampaign Agent build package
Keep the normalized brief, uploaded-context references, grounding references, validation warnings, Data Extension plan, journey plan, and Bruno-compatible campaignSpec.
Campaign Agent workflowBruno dry-run output
Review missing inputs, entitlement-filtered skills, pending write summaries, proposed stages, artifact ledger, request journal, resume behavior, and manual Journey activation warnings.
Bruno orchestrationFactory and draft artifacts
Verify tool:factory entitlement, settings.factory.enabled, account SFMC credentials, configured templates, Content Builder folders, image uploads, Data Extensions, email previews, variants, and template review.
Factory workflowReviewed write boundaries
Separate reads, previews, draft creation, confirmed writes, and manual-only launch controls before treating any output as ready for Marketing Cloud execution.
Write boundariesWalkthrough evidence
What a real SFMC execution demo should leave behind.
A useful walkthrough should end with artifacts your SFMC admin can inspect: planning output, dry-run orchestration, readiness checks, scoped draft outputs, and the boundary that keeps final launch decisions inside Marketing Cloud.
Open the SFMC evidence matrixCampaign Agent package
Keep the generated brief, build package, validation warnings, grounding references, Data Extension plan, journey plan, email definitions, and campaignSpec from the generate-brief or execute-campaign flow.
Bruno dry-run record
Review entitled skills, missing inputs, pending write summaries, proposed stages, artifact ledger, request journal, resume behavior, and manual Journey activation warnings before confirming execution.
Factory and SFMC readiness
Verify mapped BU context, account-scoped credentials, token-context results, tool:factory entitlement, settings.factory.enabled, configured templates, folder paths, and Data Extension prerequisites.
Reviewed Marketing Cloud drafts
Inspect the actual draft outputs: Content Builder folders or assets, uploaded images, Data Extensions, email copies or template-based emails, preview drafts, localized variants, and Journey Builder drafts.
Pilot evidence
Evaluate the first SFMC pilot against production evidence.
A useful Campaign Builder pilot should prove the same controls the implementation uses before production-bound work runs: mapped SFMC context, entitled workflows, dry-run artifacts, and reviewable draft outputs.
Confirm mapped SFMC context
Start by verifying the connected enterprise, business unit, tenant, workspace, and account-scoped credentials that each agent or Factory route will use.
Run Bruno before writes
Use Bruno dry runs to inspect the proposed stage plan, campaignSpec, artifact ledger, request journal, and missing inputs before confirming execution.
Inspect Factory prerequisites
Check the Factory entitlement, settings.factory.enabled, connected SFMC credentials, template assets, folder paths, Data Extension plans, and preview routes before asking for production drafts.
Keep final launch in SFMC
Validate that Campaign Builder creates reviewable assets and draft journeys while send approval, Journey activation, and final production decisions remain inside Marketing Cloud.
Trust model
Built for teams that need SFMC control, not unchecked automation.
Campaign Builder's strongest trust story is already in the implementation: authenticated account context, entitlement checks, tenant and workspace scoping, confirmed write paths, request tracing, redacted logs, CSRF protection, security headers, and encrypted SFMC secrets.
Entitlement-gated agents and Factory toolsBusiness-unit to workspace mappingManual Journey activation boundaryConfirmed SFMC email, content, image, Factory, and Bruno write actions
Authenticated SFMC context
Campaign Builder uses authenticated account, tenant, workspace, enterprise, and business-unit context before agent workflows or Marketing Cloud operations run.
Scoped credentials and write paths
SFMC credentials stay server-side and encrypted in the product implementation; production-bound writes are scoped, previewed, and confirmed instead of hidden inside chat.
Request traceability and hygiene
The implementation documents request IDs, redacted logging, CSRF checks for mutating browser requests, security headers, entitlement gates, and safer error formatting.
Use cases
Start with the SFMC production work your team repeats most.
Campaign Builder is easier to evaluate when each workflow is concrete. These pages explain the implemented paths for Content Blocks, Journey creation, Email generation, Data Extensions, Factory production, SFMC connection readiness, Advisor guidance, and Bruno orchestration.
Campaign Planning
Turn campaign intent, uploads, and workspace knowledge into normalized briefs, build packages, and Bruno-ready execution specs.
Content Blocks
Create and publish reviewed Content Builder assets and reusable block content from campaign context.
Journey Creation
Plan, clone, or create Journey Builder drafts while keeping activation manual inside Marketing Cloud.
Email Generation
Search, preview, copy, rewrite, translate, and update SFMC emails through confirmed write paths.
Localization Workflow
Translate campaign copy, email fields, HTML, slots, and Content Builder-ready variants while preserving SFMC tokens and review boundaries.
Data Extensions
Plan audience structures, create Factory Data Extensions, and read scoped Data Extension rows where configured.
Factory Production
Prepare SFMC campaign drafts, folders, image uploads, Data Extensions, template emails, previews, variants, and template reviews.
SFMC Connection Readiness
Validate credentials, token context, BU-to-workspace mapping, and admin setup before agent or Factory execution.
Advisor Guidance
Review campaign strategy with account-grounded knowledge, saved recommendations, snippet context, feedback, and async job support.
Bruno Orchestration
Route campaign work across specialist skills, pending inputs, confirmed writes, dry runs, and resumable Factory-backed execution.
Execution Governance
Verify account scope, entitlements, dry-run evidence, Factory prerequisites, confirmed writes, and manual SFMC launch boundaries.
Bruno AI
Campaign assistant online
Create a reactivation campaign for subscribers inactive for 90 days.
I can draft a three-step journey, audience notes, subject-line variants, and Marketing Cloud content block recommendations.
Make the offer more premium and less discount-led.
Updated: concierge-style value proposition, loyalty framing, and two A/B subject line sets ready for review.
Bruno AI
A campaign assistant that understands the work before the send.
Bruno helps marketers translate plain-English campaign intent into structured content, audience notes, and review-ready draft assets that fit your Salesforce Marketing Cloud setup.
Read the Bruno orchestration modelNatural-language campaign briefs
Subject lines, CTAs, and message variants
Template-aware recommendations
Waitlist capture synced through the same lead API
Join the Bruno waitlist
Salesforce ecosystem
Designed around Marketing Cloud teams, not another platform to maintain.
Campaign Builder runs alongside Salesforce Marketing Cloud Engagement: installed-package sessions, Content Builder assets, Journey Builder drafts, email asset workflows, audience planning, and business-unit workspaces. Journey activation remains a manual Marketing Cloud step.
Marketing Cloud App
Runs from Marketing Cloud with signed-request or OAuth session handling and business-unit context.
Content Builder
Generates, updates, and publishes approved content assets into Salesforce Marketing Cloud Content Builder.
Journey Builder Drafts
Plans, clones, and creates draft journeys for manual review before activation inside Journey Builder.
Email Agent
Searches, previews, rewrites, translates, copies, and updates accessible Marketing Cloud email assets.
Audience + Data Extensions
Supports audience planning and Data Extension reads for scoped campaign and journey workflows.
BU Workspaces
Maps Marketing Cloud enterprises and business units to Campaign Builder tenants and workspaces with audit trails.
Demo booking
Book a focused SFMC execution walkthrough.
The fastest way to evaluate Campaign Builder is to bring one real campaign workflow: a brief-to-email path, a journey draft, a Content Builder block process, or a Data Extension production step.
Map your current SFMC campaign production path
Show how Bruno routes work to specialist agents
Review Factory, email, journey, localization, and Data Extension boundaries
Identify the first workflow to pilot safely
success@campaignbuilder.appDemo requests are validated server-side, stored in MongoDB, and routed to Salesforce.
Response within one business dayWe will focus the demo on the SFMC workflow you want to improve first.
Book your Campaign Builder demo
Tell us which SFMC workflow you want to evaluate first.