Personalization
Personalization
Make flows dynamic with user data, multiple languages, and collected input.
Personalization
Static screens get ignored. Personalized experiences convert. Setgreet gives you four tools to make every flow feel like it was built for the person seeing it.
Four pillars of personalization
| Pillar | What it does | Example |
|---|---|---|
| Variable Bindings | Insert user-specific data into component properties at render time. | "Welcome back, Sarah" instead of "Welcome back, user". |
| Localization | Deliver flow content in your users' native language. | The same onboarding flow in English, Spanish, and Japanese. |
| Form Data Collection | Capture user input and save it as a user attribute for later flows. | Ask a preference question, then target a future flow on the answer. |
| External Data | Render data from your own API inside a screen. | A product list filtered by the size the user just picked. |
These capabilities work together. You can localize a screen that contains variable bindings and collects form data -- all at the same time.
Why personalization matters
Generic in-app messages are easy to dismiss. When a flow addresses users by name, speaks their language, and adapts based on what they have already told you, engagement goes up meaningfully.
- Higher completion rates -- users are more likely to finish a flow that feels relevant to them.
- Better data quality -- when you reference what you already know, users trust you with more.
- Fewer flows, more impact -- one personalized flow can replace several static variants.
Personalization relies on user attributes set through the SDK identifyUser call. See User
Attributes for details on sending attribute data.
Next steps
- Variable Bindings -- connect user data to screen content.
- Localization -- add multi-language support to your flows.
- Form Data Collection -- capture and reuse user input.
- External Data -- render data from your own API.