Analytics
See how installers move through your install template and where they get stuck.
Analytics tells you whether your install template actually works for real people. It tracks each attempt as a session and records how far installers get, so you can validate that beginners are completing the install — and spot exactly where they get confused.
This ties directly to the Inboard north star: a non-technical user finishing the install on any supported platform with confidence. Analytics is how you prove that's happening and keep improving it.
What a session is
A session is one installer's run through your install template, from the moment the widget opens to the moment they finish or give up. Inboard records progress through the session so you can measure both success and friction.
What Inboard measures
| Insight | What it tells you |
|---|---|
| Session start | An installer opened the widget and began the install. |
| Per-step progress | Which step each installer reached, and how many cleared each one. |
| Completion | The installer finished every requirement and verification passed. |
| Drop-off | The step where installers stopped, so you can see exactly where they leave. |
| Verification outcomes | Whether verification checks passed or failed at each step. |
| Platform breakdown | Which platforms (WordPress, Shopify, Webflow, Squarespace, …) installers are on. |
| Time on step | How long installers spend before moving on — a signal for confusing steps. |
Reading the dashboard
The dashboard summarises sessions for an install template so you can answer three questions quickly:
- Are people completing? Compare completed sessions against started sessions. A healthy template converts most starts into completions.
- Where do they get stuck? Look at the drop-off and per-step progress. A sharp fall at one step usually means that requirement's instructions are unclear, or the verification is too strict.
- Which platforms struggle? Use the platform breakdown to see whether one platform's guide needs better wording or an extra screenshot.
Improving your guides
Once you've found a problem step, the fix is usually in the install template configuration:
- Rewrite or shorten the requirement instructions for the step where installers drop off.
- Pre-fill more variables so steps are copy-paste-ready instead of asking installers to figure out values themselves.
- Switch a strict automated check to self-report if installers complete the step but verification keeps failing — see the verification methods in Configuration.
Make one change, then watch the next batch of sessions to confirm drop-off improved.
Privacy
Analytics counts events and progress; it does not capture secret variable values, which never leave the installer's browser. For data retention, IP capture, and geo handling, see Security.