Analytics integrations
Connect the product analytics you already use and onboarding checkups diagnose from evidence — what dropped users did instead, not just where they dropped.
Sunboard's funnel tells you where users drop out of onboarding. Your
product analytics tool knows what they did instead. Connect the two and
every checkup (/sunboard.analyze, the experience
dashboard, sunboard analytics experience --enrich) is grounded in evidence:
the pages dropped users left for, the buttons they rage-clicked, the errors
they hit, the traffic source they came from, and session replays of real
users failing the step.
Because your agent drives Sunboard, it isn't limited to Sunboard's own data. An integration is how you hand it the rest of the picture.
How every integration works
The same rules apply to any provider we connect to:
- Explicit opt-in. Nothing is ever queried until a workspace owner or admin connects the provider with a read-only API key, per environment. Connect production; that is where real users drop off.
- Read-only, on demand. Sunboard asks targeted questions about the exact users who dropped at a funnel edge, at diagnosis time. It never mirrors or stores your analytics data; only short-lived aggregates.
- Write-only credentials. The API key is verified against the provider before it is saved, encrypted at rest, used only server-side, and never displayed again.
- Strictly additive. No connection means Sunboard behaves exactly as it does today; a provider outage degrades to a note in the output, never an error.
Connections are managed in Settings → Integrations in your project
dashboard, or with sunboard integrations in the terminal.
Providers
Amplitude and Mixpanel are on the roadmap; the integration layer is built provider-plural. If you want one of them (or something else), tell us and we'll prioritize it.