Launched this week
Analytiics
Web and product analytics, set up by your coding agent
35 followers
Web and product analytics, set up by your coding agent
35 followers
Web and product analytics, set up by your coding agent. Your tracking plan lives in your repo and powers typed events, charts, funnels and CI checks. Understand visitors and revenue, measure anonymous traffic without cookies, and start free.
Liinks
Hey Product Hunt! I’m Charlie, the maker of Analytiics 👋
The idea behind Analytiics is simple: analytics should be part of the way you build your app.
Give your coding agent this prompt:
Your agent reads your codebase, adds tracking for meaningful actions, and works through verifying the first events. You approve sign-in and review the changes.
The part I’m most excited about is what happens after setup. Your tracking plan lives in analytics.yaml, alongside your code. That file powers typed event helpers, charts and funnels. CI checks help catch mismatches as your app changes, so tracking can be reviewed with the features it measures.
You also get traffic analytics, customer journeys, Stripe revenue tracking and a live visitor globe. Anonymous traffic uses no tracking cookies, and you choose which dashboard widgets to make public.
The public beta is open to everyone. The free plan includes one project and 25,000 events per month.
You can explore real traffic on the Thiings dashboard before connecting anything.
What’s the first question you’d want Analytiics to answer about your app?
If the agent creates the event names themselves, won't the notation end up being inconsistent? Can you provide the naming conventions in advance?
Tracking plan in the repo with CI checks is the part I'd actually use — every analytics setup I've had drifted from the code within a month. Practical question: I just moved my pricing page to an embedded checkout that runs in a cross-origin iframe (the payment provider's domain), so the "purchase" event never fires on my page — I only learn about it from a webhook later. Can Analytiics take a server-side event from that webhook and stitch it back to the anonymous visitor who clicked "Go Pro", without cookies? That's the funnel step I'm blind on today.
Liinks