Product analytics for SaaS teams
Follow the journey from a visitor's first landing page to the action that makes your product useful. SaaS Pro Max puts website traffic and product events in the same application, so you can investigate a signup drop without switching between unrelated dashboards.
- 100.0% of entryViewed pricing4,127
- 31.2% of Viewed pricing continuedLargest drop: 68.8% lost31.2% of entryStarted signup1,286
- 57.7% of Started signup continued18.0% of entryCreated organization742
- 68.9% of Created organization continued12.4% of entrySent first event511
- Viewed pricing4,127100.0% of entry
- 31.2% of Viewed pricing continuedLargest drop: 68.8% lostStarted signup1,28631.2% of entry
- 57.7% of Started signup continuedCreated organization74218.0% of entry
- 68.9% of Created organization continuedSent first event51112.4% of entry
| Step | Reached | Step conversion | Not continued | Share of entry |
|---|---|---|---|---|
| Viewed pricing | 4,127 | 100.0% | 0 | 100.0% |
| Started signup | 1,286 | 31.2% | 2,841 | 31.2% |
| Created organization | 742 | 57.7% | 544 | 18.0% |
| Sent first event | 511 | 68.9% | 231 | 12.4% |
Steps mix a path (/pricing) with events (signup started, organization created) because both live in the same events table.
Find where activation breaks
Build a funnel from pageviews and custom events, such as viewing pricing, starting signup and completing setup. Inspect conversion, drop-off and time between steps. Separate visitors whose conversion window is still open from those who did not continue, then investigate participants when your permissions allow it.
See who returns and what they do
Choose starting and returning actions for retention cohorts, and compare daily, weekly or monthly behavior. Use paths and engagement reports to explore what happens around a key action. Incomplete cohorts stay marked, so an unfinished observation period does not look like a sudden fall in retention.
Keep the evidence behind the chart
Break traffic down by page, source, campaign, device and geography, then open the events behind a result. Production and staging have separate keys and data. Person profiles and revenue use the same identifiers, making a useful product action traceable to the customer journey when those modules are enabled.
Put it to work.
Start with one application and verify the data you send.
- Install the script tag or the browser or React SDK and configure your consent flow.
- Send a named event for your activation milestone and identify signed-in users with your own stable IDs.
- Build a funnel, compare mature retention cohorts and inspect the events behind a change.
Analytics reflects the events you collect and retain. Daily visitor totals and range-wide unique users have different definitions; the reference explains them. IP addresses are hashed, and personal details require a separate permission.
Module availability and retention vary by plan. Compare plans and limits.