SFMC execution demo script
Run a Campaign Builder demo that proves the SFMC execution path.
Use one real campaign idea to show how Campaign Builder moves from authenticated Marketing Cloud context to Campaign Agent planning, Bruno dry-run orchestration, specialist agent outputs, Factory drafts, and reviewed SFMC handoff evidence.
Demo run
Follow the same sequence a safe SFMC pilot should use.
This script keeps the walkthrough grounded in implemented Campaign Builder routes and review artifacts instead of broad AI marketing claims.
Prove the SFMC context first
Start by showing the active auth source, account, tenant, workspace, enterprise ID, business unit ID, token-context result, and whether the route is using first-party, bearer, SFMC signed_request, or SFMC cookie session context.
Show entitlement scope before AI work
Confirm which Campaign, Content, Email, Journey, Image, Translator, Advisor, Audience, Bruno, content-block, and Factory capabilities are enabled for the account before invoking a specialist workflow.
Create the campaign planning artifact
Use Campaign Agent to turn the buyer's campaign idea, uploaded context, and workspace knowledge into a normalized brief, audience direction, email plan, Data Extension plan, journey direction, validation warnings, build package, and Bruno-compatible campaignSpec.
Run Bruno as a dry run
Ask Bruno to route the campaignSpec through entitled skills, collect missing inputs, show pending write actions with preview summaries, and produce a dry-run stage plan without Salesforce Marketing Cloud side effects.
Inspect selected specialist outputs
Demonstrate only the workflows relevant to the campaign: Email Agent reuse and updates, Content Agent source-backed variants, Journey Agent draft planning, Image Agent search or saved assets, localization, Advisor guidance, or Audience Agent planning.
Review Factory and SFMC drafts
Where Factory is enabled, inspect campaign drafts, Content Builder folders, image uploads, Data Extensions, template-based emails, preview drafts, variants, and template review before continuing in Marketing Cloud.
Proof artifacts
What the evaluator should capture before the demo ends.
Every successful walkthrough should leave artifacts an SFMC admin or campaign operations lead can inspect after the call.
Campaign Agent planning output
Keep the top brief, uploaded-context references, grounding references, assumptions, taxonomy, email definitions, Data Extension plan, journey plan, validation warnings, buildPackage, and campaignSpec.
Bruno orchestration output
Keep dryRun output, missing inputs, entitled skill choices, pending action previewSummary fields, stage plan, proposed artifacts, durable run state, artifact ledger, request journal, resume evidence, and manual Journey activation warnings.
Email and content evidence
Capture SFMC email search and preview results, copy targets, subject and preheader changes, slot-aware update summaries, rewrite drafts, translations, Content Builder save targets, and CloudPage or asset preview evidence where configured.
Journey and audience evidence
Capture journeyDraftPlan, reference journey search or clone choice, email copy artifacts, audience handoff or Data Extension contract, activationReadiness, blockers, warnings, and manualActivationRequired state.
Image and localization evidence
Record provider/source metadata, saved image details, generation request state, credit usage, SFMC insertion target, source language, target locale, tone guidance, and HTML or token preservation decisions.
Factory and SFMC readiness evidence
Verify tool:factory entitlement, settings.factory.enabled, connected SFMC credentials, configured template assets, template checks, folders, Data Extensions, email previews, variants, and template review findings.
Specialist agent checks
Choose the agent paths that match the real campaign.
The demo should not enable every workflow by default. Pick the implemented agent or Factory paths that match the buyer's SFMC production work.
Email Agent
Search and preview accessible SFMC emails, then copy, rewrite, translate, or update subject, preheader, HTML, or slots only through confirmed write paths.
Journey Agent
Extract or refine the journey brief, search or clone reference journeys, draft email copy, check readiness, and create Journey Builder drafts while keeping activation manual.
Image Agent
Use provider search, saved image assets, generation requests, credit state, and confirmed SFMC insertion where the account has image providers and Marketing Cloud credentials configured.
Localization
Show source language, target locale, tone, HTML preservation, token handling, localizedVariants, Email Agent translation, Content Agent localization, or Translator records.
Route evidence
Map the demo claims to implemented Campaign Builder surfaces.
A technical evaluator should be able to trace the demo from authenticated SFMC context through agent planning, Bruno orchestration, Factory production, and confirmed write boundaries.
Auth and SFMC connection
`/api/v1/sfmc`, `/api/v1/sfmc-connect`, `requireAuth`, Marketing Cloud access helpers, and BU mapping utilities establish scoped SFMC context before agent work runs.
Campaign planning
`/api/v1/agent/campaign/generate-brief` and `/api/v1/agent/campaign/execute-campaign` create normalized briefs, build packages, validation warnings, grounding references, and campaignSpec payloads.
Bruno orchestration
`/api/v1/agent/bruno/execute-campaign` and `/api/v1/agent/bruno/runs/:id` expose dry-run plans, durable run records, stage state, request journals, artifact ledgers, resume behavior, and confirmed execution boundaries.
Factory production
`/api/v1/factory` covers campaign drafts, Content Builder folders, image uploads, Data Extensions, template emails, previews, variants, and template review behind the `tool:factory` entitlement.
Specialist workflows
`/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 the agent work inspectable.
Boundaries
Keep the demo inside reviewed SFMC execution.
Campaign Builder helps teams prepare reviewed Marketing Cloud work. The demo should make final SFMC approval and Journey activation boundaries visible.
Do not count a Bruno dry run as a send, write, or Journey activation.
Do not claim Factory can run before tool:factory, settings.factory.enabled, SFMC credentials, and configured templates are ready.
Do not present disabled agents as available for an account that lacks the matching entitlement.
Do not treat generated content as approved content; buyers should review previews, summaries, and SFMC draft artifacts.
Do not imply Campaign Builder bypasses Salesforce Marketing Cloud review, send approval, or manual Journey activation.
FAQ
Questions to ask before confirming SFMC-facing work.
What should the buyer bring to the demo?
Bring one real campaign idea with audience, offer, message direction, channel expectations, and any source files or existing SFMC assets the team would normally use.
What makes this different from a copy-generation demo?
The walkthrough should produce implementation evidence: SFMC context, entitlement scope, Campaign Agent planning artifacts, Bruno dry-run output, selected specialist outputs, Factory readiness, and reviewed SFMC draft boundaries.
When should confirmed writes be shown?
Only after the dry run, prerequisites, preview summaries, and SFMC targets are reviewed. Production-bound actions such as email copy/update, Content Builder saves, image insertion, Factory execution, and Bruno write-skill execution require explicit confirmation.
Does the demo prove launch automation?
No. Campaign Builder can prepare reviewed assets and Journey Builder drafts, but final send approval, Journey activation, and launch decisions remain inside Salesforce Marketing Cloud.
Next reading
Use the deeper evaluator guides to verify each stage.
Pair this demo script with the SFMC pilot plan, evaluation evidence matrix, Bruno orchestration guide, Factory workflow, and write-boundaries article.