Secure prefill
Bring known customer context into a flow without exposing it
Resolve trusted audience data on the server, prefill the experience, and control which values respondents can see or change.
Designed for operations
Secure prefill is designed for personalized journeys where context improves the experience but raw customer data should not travel as readable URL parameters.
Personalization should reduce friction, not weaken the data boundary
Known audience context can remove repeated questions and make a journey feel relevant. Passing sensitive values directly in a link, however, can expose them through browser history, copied URLs, or analytics. OK Flows uses an opaque reference so the server can resolve the context before rendering the journey.
Opaque references
Use a non-descriptive token in the journey link instead of putting readable profile attributes in the query string.
Server-side resolution
Resolve the associated context before it becomes form state, keeping the lookup away from the public client.
Editable-field control
Decide which resolved values should be visible, hidden, locked, or available for correction.
Mapped continuity
Carry trusted identifiers through to the final delivery so enrichment remains tied to the intended record.
A safer personalization path
- 01
Create the context
Associate the required audience attributes with a short-lived or controlled opaque reference.
- 02
Share the journey
Place only that reference in the campaign link sent to the intended respondent.
- 03
Resolve and render
Load the context on the server and apply the configured visibility and edit rules.
- 04
Deliver the enriched result
Submit collected answers together with the identifiers required by the destination mapping.