Technical FAQ
Campaign Builder technical FAQ for Salesforce Marketing Cloud evaluators.
These answers summarize what the implemented product does, where SFMC writes are bounded, and which controls a technical buyer should verify before piloting Campaign Builder.
Evaluator checklist
Questions to answer before the first SFMC pilot.
The right evaluation starts with account scope, entitlements, connected SFMC credentials, Factory readiness, and the human review points around Marketing Cloud writes.
Access and account scope
How is Campaign Builder connected to Salesforce Marketing Cloud? Can every account use every agent or production tool? How does Campaign Builder keep SFMC business units separated?
Agent execution
What does Bruno actually orchestrate? What does Campaign Agent produce before Bruno execution? Where do Content, Email, Image, and localization workflows fit?
Factory and SFMC writes
What must be ready before Factory can create SFMC draft assets? Which SFMC artifacts can Factory prepare? Does Campaign Builder automatically activate Journey Builder journeys?
Review boundaries
Which actions require explicit confirmation? What operational evidence follows requests? Is this a compliance attestation?
Pilot readiness
The SFMC setup checks that prevent false starts.
A credible pilot should prove the same constraints the implementation enforces in production: authenticated sessions, BU mapping, entitlement gates, account-scoped credentials, Factory configuration, and reviewed write actions.
Choose the launch and auth model
Confirm whether the pilot starts from a first-party Campaign Builder session, bearer API token, SFMC signed_request launch, or SFMC mc_token session. Same-origin browser writes must carry the CSRF token expected by the implemented auth middleware.
Map SFMC enterprise and business unit scope
For SFMC app launches, verify the enterprise ID and business unit ID are mapped to the intended Campaign Builder tenant and workspace before any local session or tenant-owned data access is issued.
Enable only the required entitlements
Turn on the specific agent and tool entitlements the pilot needs, such as campaign-agent, content-agent, email-agent, journey-agent, image-agent, translator-agent, advisor-agent, bruno-super-agent, audience-agent, content-blocks, and tool:factory.
Connect account-scoped SFMC credentials
Use the account Marketing Cloud connection for server-to-server or web-app credentials, then verify the connection status and token context before Content Builder, Journey Builder, Email, Data Extension, or Factory routes are evaluated.
Check Factory prerequisites before build work
Factory pilots need the tool:factory entitlement, settings.factory.enabled set to true, connected SFMC credentials, and configured template assets before campaign drafts, folders, Data Extensions, template emails, previews, or template review can run.
Define the review and activation boundary
Dry-run Bruno execution first, inspect pending write previews, and keep Journey activation as a manual Salesforce Marketing Cloud step after draft creation, warnings, and any EMAILV2 or entry-event fix-up notes are reviewed.
Pilot evidence
What a technical evaluator should see after the first dry run.
A useful Campaign Builder pilot should leave concrete evidence that the account, SFMC connection, agent permissions, Bruno plan, Factory prerequisites, and review boundaries are working before production-bound writes are confirmed.
Authenticated SFMC context
The session path should be clear: first-party cb_auth, bearer JWT, SFMC signed_request, or mc_token. Mutating same-origin browser calls should include the expected CSRF token, and failed calls should return a requestId for tracing.
Business unit mapping proof
For SFMC launches, the enterprise ID and business unit ID should resolve to the intended Campaign Builder tenant and workspace before agent routes, Factory routes, or tenant-owned data access are used.
Scoped capability surface
Only entitled workflows should be available in the pilot account. Campaign, Content, Email, Journey, Image, Translator, Advisor, Audience, Bruno, content-block, and Factory surfaces are separate gates.
Verified Marketing Cloud connection
The SFMC connection check should resolve token context from account-scoped server-to-server or web-app credentials before Content Builder, Journey Builder, Email, Data Extension, or Factory work is evaluated.
Dry-run Bruno execution output
A Bruno dry run should show the proposed stage plan and artifacts without SFMC side effects. A confirmed execution should create durable run state with stage status, artifact ledger, request journal, and resume support.
Factory and activation boundary
Factory evidence should include template checks, campaign drafts, folder or Data Extension preparation, template-based email previews, and visible warnings that Journey activation remains manual in Marketing Cloud.
SFMC execution evidence packet
Artifacts to collect before a buyer trusts the pilot.
The strongest technical evaluation is a packet of concrete artifacts, not a generated-copy demo. These items map Campaign Builder's planning, Bruno orchestration, Factory production, and Marketing Cloud boundaries to evidence an SFMC admin can review.
Campaign Agent planning packet
Capture the normalized brief, audience direction, message structure, email content plan, Data Extension plan, journey plan, validation warnings, grounding references, build package, and Bruno-compatible campaignSpec before execution is discussed.
Bruno dry-run and confirmation packet
Keep the dry-run response showing proposed stages, missing inputs, pending write previews, manual activation notes, and the confirmed run record with stage state, artifact ledger, request journal, and resume status when production-bound work is approved.
Factory prerequisite and output packet
Record the tool:factory entitlement, settings.factory.enabled value, SFMC credential check, configured template assets, template review result, campaign draft, folder paths, Data Extension draft, generated email, and preview or variant preview outputs.
Marketing Cloud boundary packet
Separate read evidence, preview evidence, draft creation evidence, and confirmed write evidence. Journey activation, send approval, and final launch decisions should remain visible as manual Salesforce Marketing Cloud steps.
Evaluator proof matrix
What to verify before trusting an SFMC execution claim.
Use these checkpoints to connect Campaign Builder's website claims to implemented behavior in the product source: route access, SFMC context, structured planning output, dry-run execution, Factory readiness, and traceable write boundaries.
Agent access is entitlement-filtered
Verify the account can only reach enabled Campaign, Content, Email, Journey, Image, Translator, Advisor, Audience, Bruno, content-block, and Factory surfaces. The implementation uses server-side entitlement checks instead of hiding unavailable agents only in navigation.
SFMC context is resolved before work starts
Confirm the session has account, workspace, enterprise, and business-unit context before Content Builder, Journey Builder, Email, Data Extension, or Factory routes are used. SFMC launch flows should map BU identity to the intended tenant and workspace.
Campaign planning creates executable structure
A Campaign Agent run should produce more than copy: normalized brief fields, audience direction, email content plan, Data Extension plan, journey plan, validation warnings, grounding references, and a Bruno-compatible campaignSpec.
Bruno dry runs avoid SFMC side effects
The first Bruno campaign execution should run with dryRun enabled so evaluators can inspect proposed stages, missing inputs, pending write previews, and manual activation notes before any draft-building call is confirmed.
Factory readiness is checked explicitly
Before Factory production work, verify tool:factory entitlement, settings.factory.enabled, connected SFMC credentials, configured template assets, and template checks for folders, Data Extensions, emails, preview drafts, variants, and template review.
Production writes leave traceable evidence
Confirmed write paths should expose preview or summary evidence, preserve request IDs through responses and outbound SFMC calls, avoid logging sensitive payloads, and keep Journey activation as a manual Marketing Cloud decision.
Access and account scope
Access and account scope FAQ.
How is Campaign Builder connected to Salesforce Marketing Cloud?
Campaign Builder uses authenticated account or workspace Marketing Cloud connections. The implemented auth model supports first-party sessions, bearer tokens, SFMC Canvas signed requests, and SFMC cookie sessions, then normalizes tenant, account, workspace, enterprise, and business-unit context before protected routes run.
Can every account use every agent or production tool?
No. Route families are mounted behind entitlement checks. Campaign, Content, Email, Journey, Image, Translator, Advisor, Audience, Bruno, Factory, and content-block surfaces only run when the authenticated account has the matching agent, tool, or block entitlement.
How does Campaign Builder keep SFMC business units separated?
Business-unit launches are mapped into Campaign Builder tenant and workspace identity. Tenant-owned database operations are account-scoped, and production standalone sessions are prevented from entering BU-scoped workspaces when the workspace does not match the account.
Agent execution
Agent execution FAQ.
What does Bruno actually orchestrate?
Bruno classifies requests, discovers entitled shared skills, gathers missing inputs, stages pending write actions with preview summaries, supports dry runs, and can run durable campaign execution with stage state, artifact ledgers, request journals, and resume support.
What does Campaign Agent produce before Bruno execution?
Campaign Agent can turn typed intent, uploaded context, session context, and workspace knowledge into a normalized brief, audience direction, email content plan, Data Extension plan, journey plan, validation warnings, build package, grounding references, and a Bruno-compatible campaignSpec.
Where do Content, Email, Image, and localization workflows fit?
Content Agent creates and refines content from briefs, images, templates, existing assets, variants, translations, and configured Content Builder exports. Email Agent searches, previews, copies, rewrites, translates, and updates SFMC emails through confirmed write skills. Image Agent supports provider search, saved assets, generation requests, credits, and SFMC insertion. Localization flows carry source language, target locale, tone, and HTML-preservation inputs across reviewed content and email work.
Factory and SFMC writes
Factory and SFMC writes FAQ.
What must be ready before Factory can create SFMC draft assets?
Factory requires the tool:factory entitlement, account settings.factory.enabled set to true, connected SFMC credentials, and configured SFMC template assets for template-dependent email and preview flows.
Which SFMC artifacts can Factory prepare?
Factory routes can save campaign drafts, create Content Builder campaign folders, create Data Extension folders, upload images, create Data Extensions, generate template-based emails, return raw or rendered previews, produce variant previews, and run AI template review.
Does Campaign Builder automatically activate Journey Builder journeys?
No. Journey Agent can plan, search, clone, or create Journey Builder drafts and return activation readiness warnings, but Journey activation is never automatic. Final activation remains a manual Salesforce Marketing Cloud step.
Review boundaries
Review boundaries FAQ.
Which actions require explicit confirmation?
Production-bound actions such as SFMC email copy or update, slot updates, rewrite application, translation application, image insertion, Content Builder publishing, Factory execution, and Bruno write-skill execution are staged for review and require confirmation instead of running as hidden chat side effects.
What operational evidence follows requests?
The implementation assigns request IDs, propagates request context through approved SFMC HTTP clients, centralizes error responses, redacts sensitive logs, and encrypts stored SFMC secrets and refresh tokens with AES-256-GCM.
Is this a compliance attestation?
No. Campaign Builder has implemented application guardrails such as authentication, entitlements, tenant scoping, CSRF checks, security headers, request tracing, redacted logging, and encrypted SFMC secrets. Those controls should be evaluated as product implementation evidence, not as a standalone certification claim.
Implementation evidence
Route-backed capabilities evaluators can trace.
Campaign Builder's buyer-facing claims map to implemented route families, shared SFMC clients, entitlement middleware, and documented production boundaries.
Core agent routes
/api/v1/agent/campaign, /api/v1/agent/content, /api/v1/emails, /api/v1/agent/journey, /api/v1/agent/image, /api/v1/agent/translator, /api/v1/agent/advisor, and /api/v1/agent/bruno are authenticated and entitlement-gated.
Factory routes
/api/v1/factory covers campaign drafts, config and brand language rows, folders, image uploads, Data Extensions, template emails, previews, variants, and template review.
Marketing Cloud routes
Campaign Builder uses Marketing Cloud route families and shared REST/SOAP clients for Content Builder assets, email assets, journeys, event definitions, folders, and Data Extension row access.
Journey boundary
Journey Agent draft creation can call createJourneyFromScratch or createJourneyFromTemplate, while activationReadiness keeps manualActivationRequired visible for SFMC review.
Image and content paths
Image Agent can search providers, save account assets, check credits, and insert selected assets into SFMC; Content Agent can send reviewed content to Marketing Cloud when configured folder and template settings exist.
Auth and security controls
Protected routes use normalized account context, entitlement middleware, account-scoped database access, CSRF validation for mutating browser requests, security headers, and request-aware logging.
Next reading
Use the FAQ with the execution articles.
Pair this FAQ with the Bruno, Factory, localization, Advisor, and end-to-end execution articles when reviewing Campaign Builder with marketing operations, SFMC admins, and security stakeholders.