In-App Storage brings native-level dynamism to Synerise in-app campaigns with dedicated on-device storage. The result: fast, contextual, AI-ready in-app experiences that adapt to behavior in real time.
What’s new
In-App Storage provides a secure, user-specific data container inside your application. Each device user gets their own isolated dataset, ensuring that content logic, story progress, or personalization states never overlap - even on shared devices. Campaigns can now write, read, and update values directly within in-app executions, enabling dynamic, context-aware flows driven entirely on the device.
Why it's important
Every user interaction feeds a continuous, AI-driven journey. Context carries forward automatically. A user who stopped mid-story resumes exactly where they paused. A first-time visitor gets the full intro. A returning customer skips what they've already seen. All executed on-device, in real time, with zero latency.
This feature enables more advanced and personalized in-App scenarios, such as:
- hiding a story if it has already been viewed or displaying an alternative version,
- resuming a story from the exact point where the user previously stopped,
- showing different content on first view vs. subsequent views (e.g., intro vs. summary),
- tracking completed vs. partially viewed stories and adjusting messaging accordingly,
- personalizing call-to-action buttons based on prior interactions (e.g., “Continue” vs. “Watch again”).
With in-App storage, you can deliver more dynamic, contextual, and user-aware in-app experiences, all managed directly on the device.
How It Works
This system stores user-specific data as simple key–value pairs linked to individual user accounts rather than devices. This ensures that each user’s progress, preferences, and personalization remain separate, even if multiple people use the same device.
Data can be saved, retrieved, updated, or deleted as needed, and it can also be fully cleared when a user logs out or resets their preferences.
For implementation details, storage behavior, and available methods, please refer to the documentation.
