About
There are a lot of analytics tools. Most take weeks to set up, slow your site down, get expensive as you grow and collect more about your visitors than they should. We built ClickClacks to fix those things.
Our story
Whenever we needed to know what people were doing on a site or in a product, setting up the analytics tool became a project of its own. It took weeks to get a useful chart, the script was heavy enough to show up in page speed reports, and the price went up every time the team grew.
Privacy was usually handled by collecting everything and adding a cookie banner. And most of these tools still expect you to build every report by hand, when you could ask a question and get the answer.
Below are the eight problems we set out to fix and what ClickClacks does about each.
The problems
01 · The problem
You write a tracking plan, configure a tag manager and install an SDK for each framework before the first chart shows anything.
What we did1 script tag
You add one script tag. It captures pageviews, clicks and scroll depth without extra code, and you can add custom events later.
The quickstart02 · The problem
Large analytics scripts add to page load time, which hurts the conversion rate they are there to measure.
03 · The problem
Many tools charge per seat, hide the price behind a sales call, and get much more expensive when your team or traffic grows.
What we didFrom $49
You pay for the events you track, and the prices are published. Every plan has unlimited seats and a 14-day free trial that needs no card.
Pricing04 · The problem
Most trackers set cookies by default, need a consent banner to do it, and collect personal data they have no use for.
What we did0 cookies
The tracker sets no cookies and does not store IP addresses by default. It strips tokens, passwords, emails and card numbers from URLs in the browser and never captures form text. You can run it as opt-out or opt-in, and it respects Global Privacy Control.
Security and privacy05 · The problem
You build each report by hand. Where there is an AI assistant, it was added later and is given your raw data.
What we did12 MCP tools
You can ask a question in plain words inside the app, or from Claude, Codex or any MCP client. The AI model only receives totals. It never receives a person, a session or a raw event.
How Ask works06 · The problem
One tool counts visitors and another counts users, so it is hard to tell which visits became customers.
What we did1 project
Your marketing site and your app are two sources in one project, so a funnel can start on a landing page and end on a paid plan. Mobile apps and servers send to the same project.
Funnels07 · The problem
A dashboard only helps when someone opens it, so a drop can go unnoticed for weeks.
What we didAutomatic
Friction findings report rage clicks and stalls while they are happening, and alerts notify you when a number moves.
Friction08 · The problem
With ordinary statistics, looking at a running experiment early makes the result unreliable, so you have to wait for it to finish.
What we didCheck any day
Experiments use always-valid intervals, so you can check the result on any day.
ExperimentsWhat ClickClacks is
Web analytics show who visited your site. Product analytics show what people did in your app. To see which visits turned into customers, and where the rest dropped out, you need both in one place.
ClickClacks puts your marketing site and your app in one project and follows the same person across both, even on different domains. Funnels, retention, experiments and heatmaps then cover the full path.
It covers web, product and behavioural analytics from a single script tag. Mobile apps built with React Native or Expo send to the same project through an SDK, and your servers through an API.
One person, one journey example
Who it's for
01
02
03
Install one script tag and see your first report in minutes.
About 5 KB · pageviews, clicks and scroll depth, automatically