New: no-code event targeting is live. See how →
Onbixo
Skip to content

Core concepts

A handful of ideas that the rest of the docs build on. Read this once and the whole product will make sense.

Flows

A flow is one onboarding experience you show to users. Every flow has a type that decides how it looks and behaves:

  • Tour - a multi-step guided walkthrough with a spotlight.
  • Tooltip - a single hint anchored to one element.
  • Checklist - a getting-started task list in a corner launcher.
  • Resource center - an always-on help hub (links + relaunchable flows).
  • Announcement - a multi-step modal for product news.

You build flows in the visual editor and install them once; publishing pushes them live.

Draft vs. published

Every flow has a draft (what you are editing) and a published version (what your users see). Edits autosave to the draft and never affect the live flow until you click Publish. This means you can safely edit a live flow without disrupting anyone.

The runtime

The runtime is the small script you install on your app. It fetches your published flows, decides which to show (targeting + frequency), and renders them - in isolation, so it never clashes with your styles or code. It is the same code that powers the dashboard's live preview, so previews are accurate.

End users and identify

Your end users are the people who use your app. By default the runtime tracks them anonymously (per device). If you call identify with a user id and traits, flows can target those traits and remember progress across devices.

Targeting

Targeting decides who sees a flow - by page, days since signup, traits, events, device, or country, combined with AND/OR groups. You can also save a targeting tree as a reusable audience. Empty targeting means "show everyone." See Targeting.

Frequency and triggers

A trigger decides when a flow shows (on load, after a delay, on scroll, on click, or manually from your code). Frequency caps how often it may re-appear (once, up to N times, or on a cooldown). See Frequency & triggers.

Workspaces and teams

A workspace holds your flows, install key, team, and analytics. You can belong to several workspaces and switch between them, with a role in each (owner, admin, editor, viewer). Billing is per person, and a workspace is billed to its owner. See Workspaces & teams.

Plans and MAU

Plans are flat monthly rates with a capped band of monthly active users (MAU). If you hit the cap, new users beyond it simply stop seeing flows until the next month - never a surprise overage bill. See Plan & billing.

Last updated: Aug 5, 2026

Was this page helpful?
Still need help? We're happy to lend a hand. Contact us