Template readiness
Validate SFMC templates before Campaign Builder production work.
Campaign Builder can accelerate campaign execution when Salesforce Marketing Cloud templates, folders, and slot metadata are ready. This guide shows what technical evaluators should verify before Factory, Email Agent, Content Blocks, Journey Agent, Content Agent, or Bruno create reviewed draft artifacts.
Readiness checklist
What to verify before a template-based pilot.
Template readiness is the difference between a credible SFMC execution demo and a generic content-generation demo. Start with access, folders, template IDs, slots, dry runs, and evidence.
Workflow impact
Where configured templates affect Campaign Builder.
Campaign Builder exposes several template-aware paths. Each one should be evaluated against real SFMC assets and the exact Business Unit context used by the marketing team.
Factory production
Factory depends on settings.factory.enabled, tool:factory entitlement, connected SFMC credentials, and configured template assets before template-based emails, previews, variants, or AI template review can be evaluated.
Email Agent updates
Email Agent can search, preview, copy, rewrite, translate, update headers or HTML, and apply slot-aware updates when template slot metadata is available; production writes require confirmation and return Bruno preview summaries.
Content Blocks
Content Block workflows are template-constrained: suggestions should use approved template context, avoid introducing unsupported HTML structures, and keep selected image or block writes reviewable in Content Builder.
Journey Agent drafts
Journey Agent can reuse reference journeys, prepare email assets, and create draft Journey Builder flows, but EMAILV2 selection warnings and Journey activation remain manual Marketing Cloud review steps.
Bruno orchestration
Bruno routes entitled skills, collects missing inputs, dry-runs proposed stages, and stages confirmed write actions; template prerequisites should appear before Factory or Email write skills execute.
Content Agent publishing
Content Agent can create source-backed drafts, variants, localization metadata, Knowledge saves, Content Builder saves, and CloudPage rendering when configured folder and template settings are present.
Evidence packet
Keep the proof trail attached to the template test.
A template pilot should leave behind enough evidence for SFMC admins to see what Campaign Builder read, proposed, changed, and left for manual Marketing Cloud review.
Template inventory
Record template asset IDs, customer keys where used, folder IDs, visible slot keys, slot labels, and whether the asset is an HTML email or template-based email accessible to the connected Business Unit.
Read and preview proof
Save the Email Agent preview-safe fields, template slot metadata, folder path lookup, Factory template-check output, and any rendered draft preview before a write is confirmed.
Write-boundary proof
For copy, update, rewrite, translation, slot changes, Factory email creation, or Content Builder saves, keep the confirmation state, previewSummary, changed fields, source and target IDs, and requestId.
Manual SFMC follow-up
Keep Journey activationReadiness, EMAILV2 or entry-event warnings, send approval status, and the Marketing Cloud review owner visible after Campaign Builder creates draft artifacts.
Boundaries
Template readiness does not remove SFMC controls.
The goal is faster production setup with clearer review evidence. Approval, write scope, and governance remain controlled by Salesforce Marketing Cloud and Campaign Builder confirmation boundaries.
No hidden template fallback
CloudPage and template-dependent flows depend on configured account templates or SFMC template assets rather than built-in production templates.
Confirmation before writes
Email copy, update, slot update, rewrite, translation, Content Builder saves, and Factory execution are reviewed production-bound paths.
Launch stays in Marketing Cloud
Campaign Builder prepares drafts, previews, and evidence. Journey activation and final send decisions remain manual Salesforce Marketing Cloud work.
Template FAQ
Questions to settle before production evaluation.
These answers keep buyer conversations grounded in implemented SFMC template behavior and explicit Campaign Builder write boundaries.
Can Campaign Builder use any SFMC email template automatically?
No. Template-dependent workflows need accessible Content Builder assets, connected Marketing Cloud credentials, and usable template or slot metadata. The site should be evaluated against configured customer templates, not a generic promise.
What happens when slots are available?
Email Agent and Journey email creation paths can preserve template structure and update selected slots or headers. Evaluators should verify slot usage in preview summaries and resulting asset payloads.
Does template review approve a campaign for launch?
No. Factory template-review can provide AI feedback on AMPscript, HTML structure, conditional comments, inline styles, and impression-region concerns. Send approval, final QA, and Journey activation remain in SFMC.
What should a pilot prove first?
Start with read access, template inventory, folder IDs, slot metadata, and dry-run evidence. Then test one confirmed draft write with a requestId and asset ID trail.
Evaluation takeaway
Start with one real template and one reviewed draft write.
The most useful proof is not a polished sample email. It is a traceable run against an accessible SFMC template: read the template, inspect slots, dry-run the proposed work, confirm one bounded write, then review the resulting draft and remaining manual launch steps inside Marketing Cloud.