Data Extension workflow

How Campaign Builder prepares Salesforce Marketing Cloud Data Extension work.

Data Extensions sit between campaign planning and SFMC execution. Campaign Builder supports that handoff through Campaign Agent planning, Factory creation routes, preview audience lookup, Journey Agent setup, and scoped row reads.

Execution path

Where Data Extensions fit in the campaign workflow.

The implemented flow starts with a campaignSpec and ends with reviewable SFMC audience structures, preview contacts, or draft journey inputs. It is production support, not automatic campaign launch.

Plan the audience structure

Campaign Agent can include audience direction and a Data Extension plan in the build package and Bruno-compatible campaignSpec, so audience setup is part of the execution handoff instead of an afterthought.

Create Factory Data Extensions

Factory exposes standard and custom Data Extension creation paths for configured campaign production work, including sanitized names, customer keys, field definitions, folder resolution, and provenance metadata.

Search sendable audiences

Factory preview routes can search sendable Data Extensions by name and return minimal records such as name, customerKey, objectId, and categoryId for review and preview selection.

Load preview variants

Factory preview variants read scoped rows by Data Extension key, dedupe contact keys, and return contact attributes for rendering review rather than turning row access into a broad data export.

Support Journey Agent setup

Journey Agent can list sendable Data Extensions, create or reuse an audience Data Extension, seed deterministic sample rows, and prepare an EmailAudience entry event for draft journey setup.

Keep SFMC review in place

Data Extension work supports campaign production, email previews, and journey drafts. It does not send campaigns, activate journeys, or bypass Salesforce Marketing Cloud launch review.

Implementation evidence

The claims map to concrete Campaign Builder routes.

A technical evaluator can trace each Data Extension claim back to Campaign Agent output, Factory route families, preview routes, and Journey Agent SFMC helpers.

Campaign planning handoff

Campaign Agent build output can include audience direction, Data Extension plans, validation warnings, and a campaignSpec that Bruno uses for downstream execution planning.

Factory creation routes

POST /api/v1/factory/data-extensions and POST /api/v1/factory/data-extensions/custom create configured audience structures after Factory entitlement, account settings, and SFMC connection checks.

Data Extension folders

POST /api/v1/factory/assets/folder/data-extension prepares Data Extension folder structure through Factory asset routes before related campaign production artifacts are reviewed.

Preview audience lookup

GET /api/v1/factory/preview/data-extensions searches sendable Data Extensions, while GET /api/v1/factory/preview/variants reads preview rows by audience Data Extension key.

Email preview requirements

POST /api/v1/factory/emails/:id/preview requires an email ID, Data Extension key, and contact key before rendering an SFMC email preview.

Journey Agent audience setup

Journey Agent SFMC helpers list sendable Data Extensions, create or reuse a sendable audience Data Extension, upsert sample rows through the Data Events API, and build EmailAudience entry-event payloads for draft journeys.

Guardrails

Data Extension access stays scoped and prerequisite-driven.

Campaign Builder treats Data Extension operations as SFMC-facing production support. That means account context, Factory readiness, credential scope, and row-read boundaries matter before any evaluator judges the workflow.

Factory Data Extension routes require authentication, the tool:factory entitlement, settings.factory.enabled, connected SFMC credentials, and a resolved SOAP endpoint before creation work continues.

Custom Data Extension creation validates the customer key format, normalizes field definitions, resolves a Data Extensions folder path, and returns source and rollbackEligible provenance metadata.

Shared SFMC clients attempt REST rowset reads by name or key first, fall back to SOAP Retrieve for identifier errors, flatten rows for downstream consumers, and support ContinueRequest paging.

Token handling uses shared Marketing Cloud token helpers, cached access tokens, token refresh on 401 during Data Extension reads, and request-aware error paths.

Rows are read through scoped account or workspace Marketing Cloud credentials, not unrestricted database access or cross-tenant local collections.

Pilot evidence

What to inspect before trusting Data Extension execution.

Data Extension evaluation should focus on the planned audience contract, configured write path, preview data scope, and the evidence left by Bruno or Factory runs.

Ask Campaign Agent for a build package that names the audience, required fields, Data Extension plan, validation warnings, and Bruno campaignSpec handoff.

Confirm Factory readiness before testing Data Extension creation: entitlement, settings.factory.enabled, SFMC credentials, template prerequisites where needed, and target folder behavior.

Review the dry-run or stage plan for proposed Data Extensions, customer keys, field definitions, retention-policy warnings, provenance gaps, and rollback eligibility.

Use preview lookup to verify which sendable Data Extensions are visible, which contact key is used, and which row attributes are returned for email preview variants.

For Journey Agent work, verify whether an existing audience Data Extension was reused or a new sendable audience Data Extension and sample rows were created for draft setup.

Data Extension FAQ

The operational questions buyers usually ask first.

The useful evaluation question is not whether AI can mention audiences. It is whether the product can prepare, inspect, and constrain the SFMC Data Extension work that campaigns actually depend on.

Does Campaign Builder create Data Extensions directly in SFMC?

Yes. Factory includes standard and custom Data Extension creation routes for configured campaign production workflows, and Journey Agent can create or reuse a sendable audience Data Extension for draft journey setup.

Can Campaign Builder read Data Extension rows?

Yes, where the connected SFMC account or workspace credentials allow it. Preview and audience workflows use scoped SFMC clients for row reads and return review-oriented rows or attributes.

Does Data Extension planning launch a campaign?

No. Data Extension planning and creation prepare audience structures for reviewed SFMC execution. Final send eligibility, campaign launch, and Journey activation remain Marketing Cloud review steps.

What should a technical evaluator inspect?

Inspect the planned fields, customer key, folder path, sendable Data Extension lookup, preview contact key, row-read scope, Factory readiness gates, and Bruno run warnings before approving production work.

Evaluation takeaway

Data Extension work connects planning to reviewed SFMC execution.

For Salesforce Marketing Cloud teams, Campaign Builder's Data Extension value is the operational bridge: campaign intent becomes an audience contract, Factory or Journey Agent prepares the needed SFMC structures, and previews use scoped row context before final launch review.

Request a demo View Factory workflow