Skip to main content

Customer data enrichment

Collect what is missing without losing who the customer is

Use trusted audience context to ask fewer questions, keep identity fields controlled, and deliver newly captured attributes into Salesforce Marketing Cloud.

Designed for operations

OK Flows separates resolved context from respondent input. Signed prefill still passes through normal display and answer validation; it is not treated as automatically trustworthy application data.

Enrichment fails when identity and editable profile data are treated alike

A customer may need to correct a name, add interests, or provide missing attributes without being asked for information the campaign already knows. But allowing the same experience to overwrite its own match key can detach the response from the intended record or create a duplicate profile.

Ask only for gaps

Use resolved audience context to skip known questions and focus the journey on attributes that are missing or genuinely need confirmation.

Protect the match key

Keep the stable identifier used for delivery separate from profile values the respondent is allowed to review or change.

Map each new attribute

Connect captured answers and metadata to the destination fields expected by the enrichment Data Extension or downstream process.

Preserve delivery state

Store the completed response before downstream delivery so a failed handoff does not erase the customer’s submitted information.

A four-stage enrichment contract

  1. 01

    Resolve

    Use an opaque, form-specific reference to load known context on the server before the flow begins.

  2. 02

    Classify

    Separate trusted identity, display-only context, editable known values, and unanswered attributes.

  3. 03

    Capture

    Guide the customer through only the relevant questions with validation and conditional paths.

  4. 04

    Activate

    Deliver the stable key, enriched attributes, and required metadata using the configured mapping behavior.

Continue exploring