GuidesAudience

SaaS analytics: activation, retention and churn signals

Signup to activation to paid, with a timeline for every account. Hosted in the EU.

Privytics is product analytics for SaaS teams that need to see what happens after the signup form. You track anonymous events with the web SDK, call identify() with your own user id once someone logs in, and from then on funnels, retention cohorts and the per-user timeline all resolve to real accounts. Event data is stored in Germany, and the anonymous layer sets no cookies.

Why SaaS products teams use Privytics

Your user id is the join key, not a device

A SaaS user signs up on a laptop, gets the invite email on a phone and comes back three weeks later in a different browser. identify() with the id from your own users table stitches those sessions into one profile, so activation and retention are measured per account instead of per device. This is the identified layer: it goes beyond the cookieless default, it is opt-in, and you need your own lawful basis for it.

Onboarding funnels over events you named yourself

Activation is specific to your product: created a workspace, invited a teammate, connected a source, shipped the first thing that matters. You define those steps as tracked events and build the funnel over them, so the drop-off you see is between your real steps rather than between generic pageviews.

Retention by signup week, not by calendar month

Cohorts group users by when they first appeared, so you can compare the week you changed onboarding against the week before it. That is the view that tells you whether an onboarding change actually held, which a monthly active user chart will hide for a quarter.

A per-user timeline you can open during a support thread

When a customer writes in, the profile view shows that account's events in order: what they did, in what sequence, and where it stopped. Support and product read the same timeline instead of reconstructing it from application logs.

Set it up

About five minutes, on the free plan, without a credit card.

  1. Install and initialise the web SDK

    Setting apiUrl is required. Without it the SDK sends events to OpenPanel's own hosted API instead of Privytics. If you would rather not add a dependency, the plain script tag from https://privytics.com/op1.js takes the same options.

    // npm install @openpanel/web
    import { OpenPanel } from '@openpanel/web';
    
    export const op = new OpenPanel({
      clientId: 'YOUR_CLIENT_ID',
      apiUrl: 'https://api.privytics.com',
      trackScreenViews: true,
      trackOutgoingLinks: true,
    });
  2. Identify the user after login

    Pass the id from your own users table as profileId. Everything tracked from that point is attributed to the profile, which is what makes cohorts and the per-user timeline work. This is the identified layer, so decide your lawful basis for it before you ship. Call clear() on logout so a shared machine does not attribute the next session to the previous account.

    // after your login or session-restore call resolves
    op.identify({
      profileId: user.id,
      email: user.email,
      firstName: user.firstName,
      lastName: user.lastName,
      properties: {
        plan: user.plan,
        workspace_id: user.workspaceId,
        signup_week: user.signupWeek,
      },
    });
    
    // on logout
    op.clear();
  3. Track the activation path as named events

    Keep the list short and stable. Name events after what the user did, in past tense, and put the variable parts in properties rather than in the event name. Five to ten well-chosen events give you a usable funnel; fifty ad hoc ones give you a cleanup project.

    // 1. account created
    op.track('signup_completed', { plan: 'free', source: 'pricing_page' });
    
    // 2. first real setup step
    op.track('workspace_created', { workspace_id: workspace.id });
    
    // 3. the collaboration moment
    op.track('teammate_invited', { invited_count: 3 });
    
    // 4. the moment the product does its job
    op.track('integration_connected', { provider: 'github' });
    op.track('first_report_created', { report_type: 'funnel' });
    
    // 5. the commercial steps
    op.track('trial_started', { plan: 'pro' });
    op.track('plan_upgraded', { from_plan: 'free', to_plan: 'pro' });

Questions

How do I measure activation in a SaaS product?

Pick the two or three actions that predict a user sticking around, track each as its own event, then build a funnel over them in order. Because you call identify() after login, the funnel counts accounts rather than browsers, so a user who signs up on a laptop and finishes setup on a phone still counts once.

Can I see every event for one specific customer?

Yes, once that user has been identified. The profile view lists that account's events in order, which is the view to open when a support thread says the product did nothing. Users who were never identified stay in the anonymous layer and have no per-account timeline.

Do I need consent to use identify() with my own user ids?

We cannot answer that for you, and you remain the data controller. What we can describe is the split: the default tracking layer writes no cookies and counts visitors with a daily-rotating salted hash of IP, user agent and project id. The moment you call identify() with your own user id, you are processing identifiable data about a known person and you need your own lawful basis for it.

When is Privytics the wrong tool for a SaaS team?

If your analytics already lives in your own warehouse and you want models built in dbt and explored in SQL, a warehouse-native stack fits better. If you need in-product messaging, surveys or feature-flag experimentation attached to the same events, those are separate product categories and we do not cover them. If your main question is paid acquisition attribution across ad platforms with server-side conversion APIs, use a marketing attribution tool. Privytics is for the product behaviour question: who activated, who came back, and where the drop-off is.

What does it cost to start?

The free tier is 10,000 events per month, one project and 12 months retention, with no credit card. Paid plans start at EUR 10 for 100k events per month and add session replay and 5 years of event history. Session replay is opt-in per project and masks all text and inputs by default.