DataLook
Privacy-friendly analytics for small SaaS teams — built around your success event, not pageviews.
Welcome to the DataLook docs. DataLook shows you which of your visitors actually became customers — and which traffic sources brought them. This guide gets you from "I have a website" to "I know which traffic source actually converts" in about five minutes.
What you'll learn
Install in 5 minutes
Paste one script tag, watch pageviews flow in.
Install guides
Per-framework setup for 25 stacks — standard + proxy install on one page each.
Define success
URL match, button click, or one-line code call. Pick whichever fits your stack.
SDK reference
Every public method on the analytics object, plus the data-track attribute.
Server events
POST confirmed conversions from your backend. Ad-blocker immune.
First-party proxy
Serve our SDK from your own domain. Ad blockers can't see us.
Security & CSP
What the script does, the CSP directives it needs, and why proxying is safest.
Self-hosting
Why it's not supported in V1, what that means for your data, and what to ask if you need it.
What makes this different
Most analytics tools track everything — every click, every scroll — and leave you to figure out what mattered. DataLook inverts that. You define one success event ("signup", "purchase", "booking") and the whole product reports against it.
That means the dashboard answers questions like:
- Which traffic source produced real signups, not just visits?
- Which pages did converters look at before they converted?
- How is today's conversion rate doing against last week's?
V1 ships with English, Arabic (RTL), and French. If you switch to Arabic, the entire dashboard mirrors itself correctly — including charts and tables.
Need help?
Drop into the GitHub Discussions or email us. Two-person team — we read everything.