Skip to main content

Enterprise flows & surveys

Bidirectional flows for customer data enrichment.

Pull context in securely, guide the experience, and push mapped outcomes back to Salesforce Marketing Cloud or downstream tools.

Compatibility

Built around the Salesforce-side objects and delivery behaviors campaign workflows already depend on.

Marketing Cloud
Data Extensions
Journeys
CloudPage handoff
Signed prefill
Insert / Upsert

One platform for capture, governance, and activation.

Capture richer answers, govern how context moves, and return outputs your team can use immediately.

01

Capture

Richer answers through visual choices, conversational questions, and focused step-by-step form flows.

02

Govern

Control how context moves with governed handoffs, response tracking, and predictable transport rules.

03

Activate

Send mapped outcomes into Salesforce structures, journeys, and downstream campaign logic your team can use immediately.

Gamified Flows

Turn flows into reward experiences without losing operational control.

Configure reveal mechanics, prize inventory, discount codes, and post-submit reward moments from the same builder. The outcome resolves server-side first. The mechanic only reveals it.

01

Server-resolved outcomes

Resolve the prize, entry, discount code, points, or no-win state securely before the interface reveals it.

02

Scratch cards

Turn an already stored campaign outcome into a tactile scratch-to-reveal moment.

03

Spin wheels

Use wheel motion to reveal the stored result without allowing the browser to choose the prize.

04

Slots and match states

Present server-owned reward states through branded slot and match mechanics.

05

Salesforce-ready delivery

Return the resolved outcome with the completed response and mapped campaign metadata.

Team Fit

Made for the teams that own the data after submit.

OK Flows fits best where the form is only the first step and downstream systems still need the response to arrive cleanly.

01

Clean customer data in

Capture the context CRM and campaign teams need and map each response to a predictable destination.

02

Useful signals out

Move mapped outcomes into journeys, audiences, downstream reporting, and performance analysis.

03

CRM teams

Enrich customer records with identity-safe data and controlled field mapping.

04

Lifecycle marketing

Turn preferences and follow-up signals into journey-ready audience updates.

05

Campaign operations

Reuse governed setups and launch branded form variants without custom builds.

06

Customer insights

Compare engagement, drop-off, and response quality across every program.

Flow

A clear path from audience context to Salesforce-ready data.

This is the movement layer: where context starts, how forms collect it, and where the output goes after submit.

01

Protected audience context

Bring known customer context into the experience without exposing raw audience data.

02

Signed prefill

Resolve scoped, replay-safe values server-side before the first question appears.

03

Team-ready responses

Give campaign and lifecycle teams clean records they can review, route, and act on.

04

Salesforce-ready mapping

Validate each response, match it to trusted identity, and create mapped records for Data Extensions and journeys.

05

Global edge delivery

Serve forms close to every audience while retaining one governed output structure.

06

Activation outputs

Turn one accepted submission into the downstream records and actions its campaign requires.

Salesforce

Map responses into Marketing Cloud without rebuilding the delivery model each time.

Connection settings stay centralized. Each form controls mapping, metadata, and insert or upsert behavior at the point of delivery.

01

Centralized connection

Keep credentials and business-unit settings in one governed place.

02

Field mapping

Map answers directly into the Data Extension attributes that need them.

03

Delivery metadata

Send form, response, and submission context alongside every mapped answer.

04

Insert or upsert

Create a new row or update an existing customer record using a chosen key.

Comparison

Built for teams that need more than a generic submit button.

The difference is not only visual. OK Flows is designed for governed transport, Salesforce writeback, and operational reuse after launch.

01

Step-based capture

Available in OK Flows and purpose-built custom implementations.

02

SFMC writeback

Available in OK Flows and purpose-built custom implementations.

03

Signed context handoff

Available in OK Flows and purpose-built custom implementations.

04

Partial response capture

Built into OK Flows without a separate custom recovery implementation.

05

Reusable delivery settings

Centralized in OK Flows for reuse across campaign forms.

06

Admin-level operations

Built into OK Flows for teams managing an active form estate.

Operations

Operational features that make the platform usable at team scale.

The product also has to work for marketers and operators who manage many active forms at once, not only for the person building a single flow.

01

Organize at scale

Use folders, structured lists, and centralized configuration to keep a growing form estate understandable.

02

Reuse campaign work

Duplicate proven forms and carry shared brand decisions into each campaign variant without rebuilding.

03

Keep teams moving

Find, review, and manage active forms quickly as campaigns, collaborators, and delivery rules multiply.

Use Cases

A product story grounded in real use cases.

Use cases make the value concrete: better segmentation, richer profiles, more usable feedback, and faster follow-up.

01

Preference capture

Turn declared interests from campaign entry points into segmentation data teams can use immediately.

02

Survey programs

Guide respondents through focused questions and produce higher-quality feedback than flat embedded forms.

03

Triggered follow-up journeys

Move mapped submissions into audience updates and downstream actions without rebuilding activation.

04

Enrichment flows

Fill known profile gaps through guided capture that feels connected to the campaign.

05

Response analytics

Reveal completion, drop-off, and response quality so teams can improve each program.

06

Localized campaigns

Keep branded form experiences clear and useful across languages and regional audiences.

Architecture

A delivery model technical teams can understand and trust.

Source context enters with rules already defined, OK Flows governs the intake layer, and Salesforce receives a mapped payload ready for action.

01

Source context

Audience, Data Extension, and automation inputs arrive with the rules required before the first step renders.

02

Governed intake

One controlled runtime applies response metadata and transport logic consistently.

03

Mapped writeback

Fields move from form to payload to Salesforce through an inspectable mapping model.

04

Security controls built in

Signed context, server-side credentials, and owner-scoped access reduce exposure across the delivery path.

05

Runtime visibility

Validation, mapping status, and delivery outcomes stay visible at every handoff.

06

Salesforce-ready delivery

Insert or upsert behavior and routing are defined before the payload reaches Marketing Cloud.

FAQs

Questions teams usually ask before they adopt the workflow.

Can't find what you're looking for? Contact our customer support team

Salesforce delivery

Security and branding

Can't find what you're looking for? Contact our customer support team

Experience seamless payments.
Experience seamless payments.

Build your first Salesforce-ready form.

Collect richer answers, govern transport, and return mapped outputs without rebuilding the workflow for every campaign.

Get started