Matomo for SaaS companies
SaaS companies want to know how prospects become customers and what customers actually use in the product. I measure the journey from channel and newsletter through lead, trial and login to the paid plan, plus the use of individual features. Many of these projects are carried out together with agencies.
Sound familiar?
- 01From lead to customerWebsite, trial and billing sit in separate systems.
- 02Which features are used?Feature usage is the basis for product decisions, yet it often goes unmeasured.
- 03OnboardingWhere do new users get stuck before they see the value?
- 04Channels that workWhich channels bring leads that later buy, and not just sign-ups?
- 05Plans and upgradesPurchased plans, upgrades and products belong in the analysis.
- 06Website and app kept apartMarketing website and application run on different domains and are measured separately.
From channel to paid plan
Campaign, newsletter, lead, trial, login, purchase: I connect the stages into one journey, so you can see which channels bring paying customers and not just sign-ups. Purchased plans and products are added server-side from billing.
Usage inside the product
Which features are used, how often and on which plans? We agree a list of the important features, I measure them as events and build reports for product and sales.
Onboarding and logins
How many new accounts come back after the first login, and at which step does onboarding get stuck? Logins and setup steps show where customers need help.
Channels, newsletter and leads
Custom channel groups, clean campaign names and goals for leads and newsletter sign-ups show which channels are efficient. Leads and purchases can be reported server-side to ad platforms.
Website and application together
Marketing website and application get a shared profile across both domains. The journey from the first campaign to usage in the product hangs together, without you analysing two separate worlds.
FAQ
Frequently asked questions
Can we measure the use of individual features?
Yes, as events from the application, via the tracking code, the Tag Manager or server-side via the Tracking API. We agree beforehand which features count and what they are called.
How do we connect website and application?
With a shared profile across both domains, so that the journey from the first campaign to the login hangs together. Whether a user ID without real names is used for this is agreed with your data protection team.
Can purchases and upgrades from billing be included?
Yes, server-side: billing reports purchased plans, upgrades and products to Matomo, as goals or as e-commerce orders.
Do we need a separate product analytics tool for this?
Not necessarily. Events, goals and segments in Matomo cover many questions, extended with premium plugins for funnels and cohorts if you like.
Sounds like your project?
In an intro call we'll clarify where you stand and what comes first.
Your contactPeter Boehlke, Matomo consultant from Munich, 17 years in the Matomo team