SaaS analytics
Understand the journey from interest to repeat use.
Connect your SaaS acquisition, signup, activation, retention, and purchase questions in one reporting workflow.
- Account creation
- First useful action
- Return visits
First, define the value your product provides
Consider a fictional project-management SaaS. Its team decides that a new customer reaches initial value after creating a project and inviting a teammate.
This is an illustrative workflow. The event names are examples, not automatically collected product events or a customer result.
Find where useful visits come from
Review sources, campaigns, landing pages, and engagement. Add a signup goal so the acquisition report answers more than how many people arrived.
Compare first-click and last-click attribution when you want to understand the role of different sources.
Inspect the activation path
Send events for account creation, project creation, and teammate invitation. Define a funnel with the appropriate window. Save it so the team reviews the same path later.
If fewer people reach the invitation step, inspect the relevant page engagement and journey. Use a heatmap when page interaction can clarify the question.
Check whether people return
Use weekly retention cohorts and event-based segments to examine repeat use. Keep the collection and consent settings appropriate for connecting activity across days.
A higher activation rate alone does not prove stronger retention. Review both before you conclude that a change helped.
Connect the business outcome
Send purchase events and review recorded revenue by currency. Compare the purchase goal's attribution with the earlier signup result.
Share the aggregate report, set a useful alert, and repeat the review after the next release. Read product analytics, revenue, and setup.
Get to know your product
through the people who use it.
Explore with example data. No account needed.