Docs
How it works
One install, then a publish → fetch → render loop that keeps conversion work out of release trains.
Onvert splits responsibility: your app owns the SDK and purchase plumbing; the dashboard owns screens, targeting, and experiments.
The loop
- Install — drop in the SDK and present flows at the right moments in your app
- Build — design onboarding and paywalls in the visual editor
- Publish — push a config version; no binary change required
- Track — watch step-level funnel metrics and iterate
What happens at launch
On cold start (and when you ask for a refresh), the SDK fetches the latest published configuration for your app key. Flows are rendered with native components — not a web view — so they feel like part of your product.
What stays in your app
- StoreKit / Play Billing (or your IAP wrapper) for completing purchases
- Entitlement unlocks after a successful transaction
- Where and when a flow is presented in the navigation tree
What moves to the dashboard
- Screen order, copy, imagery, and layout
- Paywall plans, trials, and offer framing
- A/B variants and traffic splits
- Audience targeting rules for which flow a user sees