Data Extension mapping
Map form responses into Salesforce Marketing Cloud with intent
Define how answers, identifiers, and response metadata land in a Marketing Cloud Data Extension—then choose insert or upsert behavior for the flow.
Designed for operations
The destination stays explicit: connection settings are centralized while each form owns the mapping and delivery behavior it requires.
A successful submit is not the same as a usable record
A form can collect valid answers and still create downstream work when field names, types, keys, or repeated-submission behavior are unclear. A delivery map makes that contract reviewable before the campaign goes live and traceable when an outcome needs investigation.
Field-level control
Connect each response or metadata value to the destination field that should receive it.
Insert or upsert
Make repeated-submission behavior an explicit form decision instead of an implicit integration assumption.
Shared connection
Reuse approved connection settings while allowing forms to keep campaign-specific destinations and mappings.
Delivery evidence
Keep the form response and delivery result connected so failures can be understood and retried deliberately.
A mapping workflow technical and campaign teams can review
- 01
Select the destination
Identify the target Data Extension and the field structure it expects.
- 02
Map the payload
Pair answers, audience identifiers, and operational metadata with destination fields.
- 03
Choose record behavior
Use insert for new rows or upsert when a known key should update an existing record.
- 04
Verify delivery
Inspect the resulting status and retain enough context to diagnose an unsuccessful handoff.