GuidesAudience

Free analytics for side projects, no cookie banner

10,000 events a month on the free tier. No card, no trial clock, no cookies.

Privytics has a free tier built for projects that may never make money: 10,000 events a month, one project, 12 months of retention, no credit card and no trial that runs out. It is cookieless by default, so the analytics adds no consent banner to a weekend site. Two script tags in your `<head>` and page views start arriving.

Why Side projects teams use Privytics

The free tier is a tier, not a trial

10,000 events a month, one project, 12 months of retention, no credit card at signup and no expiry date. A small site that gets a few hundred visitors a month will sit inside that allowance indefinitely. The limits are published here rather than discovered later: one project only, no session replay on free, community support with no SLA.

Nothing to bolt a consent banner onto

The default tracker sets no cookies and writes no identifier to the device. Visitors are counted with an anonymous id that resets every day. On a side project that is the difference between shipping on Sunday evening and spending it wiring up a consent management platform. You are still the data controller and the call is yours, but there is no stored identifier to ask about.

Product analytics, not just a hit counter

Funnels, retention, cohorts, dashboards, user profiles, custom events and the REST API are all in the free tier. When the side project starts looking like a real product you can ask which step of your signup people drop at, without migrating off the tool you started on. Session replay and the 5 year retention window are the parts that need a paid plan.

Your data stays in one place you can point at

Event data is stored in Germany, and Privytics is a managed build of the open-source OpenPanel engine (AGPL-3.0). If you later want to run it yourself, the engine is public. Privytics is an independent product and is not affiliated with, endorsed by or sponsored by OpenPanel.

Set it up

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

  1. Paste two script tags into your <head>

    Works on anything you can edit a template for: a static site, an Astro or Hugo build, a CMS theme, a single index.html. Replace YOUR_CLIENT_ID with the client id from your Privytics project. Setting apiUrl is required. Leave it out and the SDK sends events to OpenPanel's hosted API instead of yours.

    <script>
      window.op=window.op||function(){var n=[];return new Proxy(function(){arguments.length&&n.push([].slice.call(arguments))},{get:function(t,r){return"q"===r?n:function(){n.push([r].concat([].slice.call(arguments)))}} ,has:function(t,r){return"q"===r}}) }();
      window.op('init', {
        apiUrl: 'https://api.privytics.com',
        clientId: 'YOUR_CLIENT_ID',
        trackScreenViews: true,
        trackOutgoingLinks: true,
        trackAttributes: true,
      });
    </script>
    <script src="https://privytics.com/op1.js" defer async></script>
  2. Pick five events and name them properly

    With 10,000 events a month you have room for roughly 10,000 page views, or fewer once custom events are added, so spend them on the handful of moments that tell you whether the project works. Use lowercase snake_case verbs in the past tense, keep the name stable, and push the variable part into properties instead of into the event name. Two events called checkout_started_pro and checkout_started_free cannot be counted together later. One checkout_started with a plan property can.

    // The moment someone gets past the landing page
    window.op('track', 'signup_started', {
      source: 'hero_cta',
    });
    
    window.op('track', 'signup_completed', {
      plan: 'free',
    });
    
    // The moment they actually use the thing
    window.op('track', 'project_created', {
      template: 'blank',
    });
    
    window.op('track', 'export_downloaded', {
      format: 'csv',
    });
    
    // The moment money is involved
    window.op('track', 'checkout_started', {
      plan: 'pro',
      interval: 'monthly',
    });
  3. Track clicks from markup, without writing JavaScript

    You enabled trackAttributes in step one, so any button or anchor carrying data-track fires that event on click. Every other data-* attribute on the element is sent as an event property. Useful when the side project is a landing page and a form, and you do not want a JS file just for analytics.

    <button
      data-track="checkout_started"
      data-plan="pro"
      data-interval="monthly"
    >
      Upgrade
    </button>

Privytics runs the open-source OpenPanel engine, so the upstream Side projects SDK reference applies here too. Point apiUrl at Privytics and the data lands in your Privytics project.

Questions

What is the best free analytics for a side project?

Depends what you need to see. If you only want to know how many people visited, a page view counter is enough and several are free. Privytics is worth it when you want to follow a person through a flow: 10,000 events a month, one project, 12 months retention, funnels and retention included, no credit card. Be honest about which of those two you actually need.

How far does 10,000 events a month go?

Every page view is one event, and every track() call is one event. A site tracking page views only fits about 10,000 views a month. Add five custom events per active user and the budget goes faster. The allowance also covers one project, not two: a second site means a paid plan, because pointing both at the same client id would mix their events into one dataset. If your project is busier than the free tier, the first paid step is EUR 10 for 100,000 events a month.

Do I need a cookie banner on a small personal site?

We cannot answer that for you, and anyone who says they can is selling something. You remain the data controller. What we can describe is the design: the default tracker sets no cookie and stores no identifier on the device, and the visitor id is a salted hash of IP, user agent and project id that rotates daily. If you turn on identify() with your own user ids, you are processing identifiable data and need your own lawful basis for it.

When is Privytics the wrong choice for my side project?

A few cases. If you want session replay to watch how people fumble your UI, that is paid plans only and opt-in per project, so the free tier will not give it to you. If you need a support contract or an SLA, free is community support only. If you want analytics stitched to server-side revenue data across several products, one project will not hold it. And if you genuinely only ever want a visitor count in your repo's README, this is more tool than the job needs.