Scratch to reveal
Scratch cards
Reveal a prize, entry, or no-win outcome directly inside the success surface.
Coating clearedPrize shown
61% revealedsingle-surface reveal
Bidirectional SFMC flow
Enterprise flows & surveys
Sophisticated, bidirectional flows
for customer data.for customer data enrichment.
Pull context in securely, guide the experience, and push mapped outcomes back to Salesforce Marketing Cloud or downstream tools.
Security
Blocks
Analytics
Accessibility
Templates
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.
Lead Capture Flow
98%
Single-question steps with keyboard navigation and mobile-first completion flows.
Salesforce
SFMC
Webhook
Survey Builder
85%
Image choices, conditional logic, and conversational UX that users appreciate.
Salesforce
SFMC
Webhook
Contact Flow
92%
Brand-first design with headers, footers, and visual customization.
Salesforce
SFMC
Webhook
Capture
Guide people through richer questions, visual choices, and step-based flows.
Response Tracker
Flow Opened
0s
First Question
3s
Email Captured
12s
All Fields Complete
28s
Submitting to SFMC
...
Govern
Keep context handoff, response tracking, and transport behavior inside controlled rules.
Activate
Return mapped outputs to Salesforce structures, journeys, and downstream campaign logic.
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.
Spin to reveal
Spin wheels
Use configured slices, mapped prizes, and a more deliberate result reveal sequence.
Slice targetedWheel settling
84% revealedserver-resolved
3 of a kind
Slots and match states
Build campaign moments that land on the resolved outcome without faking the reward logic.
Reels matchedResult locked
73% revealedmatch-state handoff
Team Fit
Made for the teams that own the data after submit.
OK | Flows fits best where the flow is only the first step and downstream systems still need the response to arrive cleanly.
CRMLifecycleCampaign OpsInsight
CRM teams
Downstream owner
Use governed flows to enrich customer records without handing transport logic to every campaign build.
Identity-safe enrichment
Controlled field mapping
Lifecycle marketing
Downstream owner
Capture preferences and follow-up signals in flows that can feed journeys and audience updates immediately.
Journey-ready outputs
Preference capture
Campaign operations
Downstream owner
Duplicate, brand, and launch flow variants quickly without turning every campaign into a custom project.
Reusable setup
Faster launches
Customer insight teams
Downstream owner
Collect richer feedback and compare engagement, drop-off, and response quality across programs.
Drop-off visibility
Response trends
Flow
A clear path from audience context to Salesforce-ready data.
This is the movement layer: where context starts, how flows collect it, and where the output goes after submit.
Audience context
Data Extensions
Automations
OK
data collected
Salesforce-native flow
Audience context enters first, responses are collected in OK | Flows, and the output leaves in a mapped structure.
Secure prefill patterns
Signed context resolves cleanly server-side and stays constrained to the fields the form should receive.
Validation chain
SignedScopedReplay-safe
Encrypted payload
verified at submit
Signature verified
verified at submit
Replay protected
verified at submit
Token handoff
bound to context
Hidden mapping
bound to context
Global edge delivery
Flows served from edge locations worldwide for fast, reliable response collection.
Salesforce activation outputs
After submit, one response can feed Data Extensions, journeys, audience updates, and follow-up logic.
Response payloadvalidated
ContactID
Preference
Metadata
Submitted at
Salesforce outputs
mapped and activation-ready
Data Extension
Journey trigger
Follow-up email
Audience update
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.
Delivery model
Map the response once. Deliver it with the operational behavior you need.
Per-form SFMC controls
Enable or disable delivery by form, isolate mappings, and keep business-unit level connection settings centralized.
Field mapping to Data Extensions
Map form answers and metadata into target Data Extension attributes with exact control over what lands where.
Insert and upsert modes
Choose whether forms create new records or update existing ones based on your operational schema.
Metadata that can travel with the response
form id
form slug
form name
response id
submit timestamp
raw answers
Insert mode
New row per response
Use when submissions should remain independent and historically traceable.
Upsert mode
Update based on a key
Use when the form should enrich or correct an existing customer record.
Comparison
Built for teams that need more than a generic submit button.
The difference is not only visual. The product is designed for governed transport, Salesforce writeback, and operational reuse after launch.
Governed transportSFMC writebackOps reuse
Capability
Generic form builders
OK | Flows
Capture experience
Flat fields and basic completion logic.
Step-based flows, visual choices, and campaign-grade flow surfaces.
Salesforce delivery
Manual exports or custom glue after submit.
Mapped delivery into Marketing Cloud with per-flow controls.
Context handoff
Exposed query params or fragile hidden-field workarounds.
Signed prefill patterns with governed server-side resolution.
Response behavior
Stops at submit and leaves downstream work outside the product.
Supports metadata, partial response capture, and activation-ready outputs.
Operational scale
One-off builds get messy as campaigns multiply.
Reusable settings, duplication, folders, and admin-level controls.
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 flows at once, not only for the person building a single flow.
Flow organization
Use folders and structured lists to manage larger sets of flows without losing operational clarity.
Nested folders
Quick search
Bulk actions
5x
Faster setup
100+
Flows managed
Team
Ready
Reuse and duplication
Duplicate flows quickly to create campaign variants without rebuilding from scratch.
One-click copy
Template library
Brand governance
Keep headers, footers, widths, and surface styling consistent across live campaign variants.
Shared styling
Reusable defaults
Centralized configuration
Keep integration settings and delivery controls manageable across campaigns.
Global defaults
Audit logs
Built for scale
The platform stays manageable after the fifth flow, not only the first one.
100+ flows
Team collaboration
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.
Audience entry
Preference capture
Collect declared preferences in a lower-friction flow and turn them into segmentation data teams can use immediately.
Faster segmentation
Audience entrybranded flowusable segment
Known contact
Enrichment flows
Fill profile gaps without sending people through a generic data-capture experience that feels disconnected from the campaign.
Richer profiles
Known contactguided capturericher profile
Campaign traffic
Survey programs
Run survey programs that generate more usable feedback and clearer performance signals than flat embedded flows.
Higher-quality feedback
Campaign trafficguided responsemeasurable insight
Submission
Triggered follow-up journeys
Turn flow submissions into follow-ups, audience updates, and downstream actions without rebuilding the activation layer each time.
Faster activation
Submissionmapped outputlive follow-up
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.
Audience
Data Ext
Trigger
seg
schema
event
Source context
Audience, Data Extension, and automation inputs define what the flow should know before the first step renders.
Secure intake layer
OK | Flows receives the response, applies controlled metadata, and keeps transport logic in one governed runtime.
Data Extension
Follow-up email
Journey trigger
Salesforce writeback
The final payload returns to Marketing Cloud with the write behavior and downstream routing already defined.
FAQ
Questions teams usually ask before they adopt the workflow.
The important questions tend to be about transport, Salesforce behavior, partial responses, and operational control.
DeliverySecurityPartial responsesBranding
How does Salesforce delivery work?
Form responses are mapped in OK | Flows and delivered into Marketing Cloud using the delivery behavior configured for that form, including metadata and downstream-ready outputs.
Can I insert new rows or update existing ones?
Yes. Forms can be configured to insert new records or upsert against an existing key so the response either creates or enriches the target record.
Can I capture partial responses before submit?
Yes. The platform supports partial-response capture so teams can recover intent even when a user does not reach the final submit step.
How is prefill secured?
Prefill and identity context are handled through signed transport patterns, constrained hidden mapping, and server-side resolution instead of openly exposing raw values.
Can each form have different branding?
Yes. Headers, footers, themes, widths, and other visual controls can be adjusted per form while still keeping governance and operational defaults centralized.
Get started
Build your first Salesforce-ready flow.
Collect richer answers, govern transport, and return mapped outputs without rebuilding the workflow for every campaign.
Signed context handoff
Mapped DE delivery
Campaign-grade UX