Glossary
The terms you'll meet across Onbixo and these docs, in one place.
| Term | Meaning |
|---|---|
| Flow | One onboarding experience - a tour, tooltip, checklist, resource center, announcement, or survey. |
| Flow type | What kind of experience a flow is; decides how it looks and behaves. |
| Runtime | The small script you install; it fetches, targets, and renders your flows on your app. |
| Draft | The version of a flow you are editing. Not visible to users until published. |
| Published | The live version of a flow that your users see. |
| End user | A person who uses your app and may be shown your flows. |
| identify | The API call that tells Onbixo who the current end user is, with traits. |
| Trait | A piece of data about a user or company (plan, role, size) used for targeting. |
| Targeting | The rules that decide who sees a flow. |
| Audience | A saved, reusable targeting rule referenced by flows. |
| Trigger | What decides when a flow shows (load, delay, scroll, click, manual). |
| Frequency | How often a flow may re-appear (once, up to N, or a cooldown). |
| Launcher | The floating corner button that opens a checklist or resource-center panel. |
| Resource center | A launcher used as a help hub: help links and relaunchable flows. |
| Workspace | A container for flows, team, install key, and analytics. You can belong to several. |
| Role | Your permission level in a workspace: owner, admin, editor, or viewer. |
| MAU | Monthly active users - the capped band each plan includes. |
| Install key | Your API key; lets the runtime load your flows on approved domains. |
| Allowed origins | The domains permitted to load your flows with a given key. |
| Extension | The browser add-on that captures element selectors as you build flows. |
| A/B test | Running two versions of one flow at the same time to see which does better. Growth and above - see A/B testing. |
| Control | Version A in a test: the flow as it already was, used as the baseline to beat. |
| Variant | Version B in a test: the changed copy of the flow being tried against the control. |
| Sticky assignment | Once a user is put in version A or B they keep seeing that one, so a test measures versions rather than coincidence. |
| Promote | Copy the winning version into your draft and end the test. The version that lost is kept in History. (A test with no winner is closed with End test instead.) |
| Invalidated | A test whose result cannot be trusted because a change to one of its versions was published while it ran. End it, or restart it to measure cleanly from now. |
| End test | Stop a test without promoting either version. Traffic stops being split and what it found is kept as a record. |
| Restart | Keep the run so far as a record and begin measuring again from now - used when a version changes mid-test. |
| Survey | A flow that asks a question instead of showing something: NPS, a rating, a choice list, or open text - see Surveys and NPS. |
| NPS | Net Promoter Score. One 0-10 question ("how likely are you to recommend us?"), scored as the share of promoters minus the share of detractors - a number from -100 to +100. |
| Promoter | Someone who answered 9 or 10 on an NPS question. |
| Passive | Someone who answered 7 or 8. Counted in the total, but adds nothing to the score either way. |
| Detractor | Someone who answered 6 or below. Subtracted from the score. |
| Response rate | The share of people shown a survey who answered at least one question. |
New to the product? Start with Core concepts, which ties these together.
Last updated: Sep 2, 2026
Was this page helpful?
Thanks for the feedback.
Still need help? We're happy to lend a hand.
Contact us
Esc
Type to search across every page.