Add-on · Product analytics
One signal interface. Every analytics tool behind it.
Every Wizard variant consumes product-usage signal through a single 5-signal interface. The connectors vary; the interface doesn't. Every tenant gets signal — no exceptions.
Why a unified signal layer
Every team's analytics stack is different. Some have Pendo. Some have Mixpanel. Some have nothing. The Wizard variants that need product-usage signal — CSM for health scoring, Marketing for segment research, Leader for adoption reporting — shouldn't care which one.
So we built a single unified interface: the 5-signal vector. Every adapter implements the same interface. Downstream Wizards never know whether the signal came from Pendo, Mixpanel, or the native fallback scorer. The fallback ships with every deployment, so usage-signal-dependent skills work on day one, before any analytics connector is wired up.
Every adapter is read-only. Wizard never writes to the tenant's analytics tool. OAuth scopes are narrowed to the fields named in the connector manifest — nothing broader.
The five signals
Depth
How deep in the product surface the account uses — breadth of features touched, core-workflow adoption.
Frequency
Cadence of usage across the account — DAU / WAU-like signal, power-user count, engagement streaks.
Power-user ratio
Share of the account's users hitting the engagement threshold Wizard learned for this tenant.
Adoption velocity
Rate at which net-new users activate, reach first value, and reach repeated value.
Engagement drift
Week-over-week delta vs the account's own 60-day baseline. Early-warning signal for churn.
Next step
Wire usage signal into every Wizard variant.
Request beta access and we'll scope your analytics stack during the walkthrough. If you don't have one yet, the native fallback covers you from day one.