Product events, defined deliberately
A named event for each thing that matters — not a firehose of clicks that nobody can interpret six months later.
Analytics
The numbers you will be asked for.
Signups, activation, retention, usage. Collected from the first day, because they cannot be reconstructed later.
There are two different questions here and they need different tools. "How did people find us and did the campaign work?" is marketing analytics. "What did they do once inside, and did they come back?" is product analytics. Both are wired in at build time, because the one thing you cannot do is ask a question retroactively about events you never recorded. Everything respects consent — under Law 25 and the GDPR, tracking that ignores a refusal is a liability rather than an insight.
Off until you need it. Turning it on is a toggle — not a project, not a rebuild. See how capability arrives as you grow.
Providers
What we connect to
Available means built and running in production today. On request means we will build it for your application — it is not pre-built, and we will not imply otherwise.
Available
- Google Tag ManagerTag management without a deployment for each change
On request
- Google Analytics 4
- PostHogProduct analytics, self-hostable if residency matters
- Mixpanel
- Amplitude
- SegmentOne integration that feeds many destinations
- SnowflakeWarehouse export
- BigQueryWarehouse export
- Power BI
- Looker Studio
- MetabaseSelf-hosted BI over your own data
What you get
The part that is not just an API key
Funnels and retention
Where people drop out of sign-up, how many come back in week two, and which features correlate with staying. The questions investors ask.
Your data in your warehouse
A scheduled export into Snowflake or BigQuery so your analysts can work in the tools they know, against the whole dataset rather than a dashboard's summary.
Dashboards for the business
The four numbers you actually manage by, correct and current, rather than a generic template nobody opens twice.
Consent honoured properly
Analytics that respect a refusal, with consent recorded and versioned. Required under Law 25 and the GDPR, and increasingly asked about in security reviews.
For example
What this looks like in practice
Preparing for a raise
Activation and retention curves that exist because they were instrumented from day one, not estimated from a database query the week before the meeting.
Working out what to build next
Which features are actually used, by whom, and how often — so the roadmap is evidence rather than opinion.
An enterprise customer's own reporting
They want your data in their warehouse alongside everything else. A scheduled export is usually all that takes.