Skip to main content
okflows

Preference centers

Build preference experiences around a clear data contract

Give customers a guided way to review and change communication preferences while keeping identity, editable choices, and Salesforce delivery behavior explicit.

Designed for operations

OK Flows can provide the customer-facing experience and mapped delivery layer. Your organization still defines the authoritative consent system, legal basis, retention policy, and downstream enforcement model.

A preference page is an operational boundary, not just a collection of toggles

The interface must show the right options to the right person, preserve trusted identity, capture the intended changes, and deliver an outcome that downstream systems can enforce. Treating all of that as one undifferentiated payload makes later auditing and support harder.

Trusted identity context

Resolve a stable audience reference before rendering so editable preferences stay connected to the intended customer record.

Purposeful choices

Present subscriptions, channels, or profile choices with clear labels instead of exposing the underlying destination schema.

Explicit delivery mapping

Map each selected value and operational field into the Salesforce structure chosen as part of the organization’s consent architecture.

Reviewable outcomes

Keep response and delivery state connected so support and operations can distinguish customer intent from an unsuccessful handoff.

Separate the four contracts every preference journey needs

  1. 01

    Identity

    Define the stable identifier used to resolve the customer without putting readable profile data in the link.

  2. 02

    Presentation

    Choose which preferences are shown, how they are explained, and which known values may be changed.

  3. 03

    Evidence

    Capture the timestamps, source, version, and context required by the organization’s governance model.

  4. 04

    Activation

    Deliver the mapped state to the system responsible for applying it across campaigns and channels.

Continue exploring

Preference-center data contracts

Define identity, presentation, evidence, and activation before implementing the interface.

Open page

Secure prefill

Resolve known audience context without exposing readable customer attributes in a campaign URL.

Open page

Data Extension mapping

Control how preference values and operational metadata reach Marketing Cloud.

Open page