most click tracking knows exactly what you pressed. mine knows the button's name, and nothing else.
i'm om yaduvanshi, 18, an applied ai developer building cloudline, a cookieless analytics tool. day 14 of 90, building in public.
the default i skipped
most analytics auto-capture every click. the button text, the link target, where on the page it sits. the idea is you instrument nothing and find everything later.
i skipped the everything-later part. a pageview in cloudline stores exactly four things: page, referrer, screen size, time. clicks follow the same rule. if you didn't name the click, it isn't stored.
how it works
you name each button yourself:
<button data-cloudline-track="signup-hero">start free</button>
when someone presses it, cloudline records the label "signup-hero" and the page it happened on. that's the whole record. the button text, the href, the coordinates, the visitor's device. none of that goes in.
for buttons built in js:
Cloudline.track('click', { label: 'signup-hero' })
only the label you pass is stored. the function signature makes the rule hard to break. there is nowhere to put more data.
what shows up
clicks land in the dashboard per page, next to pages, referrers and scroll depth. same dashboard that holds up to 50 sites. you get the funnel shape without the surveillance shape.
the tradeoff, stated plainly
you have to name every button you care about. nothing auto-instruments, so a button you forget to tag is invisible. some tools will track clicks you didn't know you wanted. cloudline won't. i chose that on purpose.
what ships today: pages, referrers, screen sizes, scroll depth, engaged time, button clicks, funnels, live visitors. revenue attribution is on the roadmap, not shipped yet.
cloudline is free for early users while i keep building it. cookieless analytics, and your buttons keep their secrets.
— om yaduvanshi
Top comments (0)