Get Statlark working on your site
Statlark is one line of script to install. The guides below cover that, plus how to connect Stripe so your revenue shows up next to the sources that earned it.
Revenue attribution
Install the tracker, then tie Stripe payments back to the visitors — and the marketing sources — that drove them.
Reading your data
What the numbers mean — revenue per visitor, paying conversion, how channels are classified, the visitor journey, and lifetime value.
Goals & conversions
Track the conversions that matter, pick your #1 KPI, and get an email the moment a goal fires.
Identifying users
Turn anonymous visitors into durable people with statlark.identify() — merged across every device, with lifetime value and a full cross-device journey.
Excluding traffic
Keep your own visits, staging sites, admin pages and bot-heavy regions out of your numbers.
Script configuration
Every data-* option on the snippet — subdomain tracking, localhost, Do Not Track, debug, the visitor ID, and resetting on sign-out.
JavaScript SDK
Install from npm and initialize in code with initStatlark() — a typed API for goals, identify and revenue, plus a React provider. A thin wrapper over the tracker for SPAs and frameworks.
First-party proxy
Route the tracker and its events through your own domain — same-origin, ad-blocker-resistant, and still geo-aware, with no change to the tracker.
REST API
Pull your revenue, visitors and sources over HTTP — and push conversions, revenue and identity server-side with bearer tokens.
Cookie consent banner
A site-styled banner that holds Statlark's analytics cookie until visitors accept — shown only where consent is required, with a re-open control.
Attribution badge
Add a paste-in “Analytics by Statlark” badge to your footer — the Slark mascot plus a plain link home. No JavaScript, no requests, five variants.
AI discoverability
Make your site citable by ChatGPT, Claude, Perplexity and AI Overviews — allow the AI crawlers, publish llms.txt, and structure pages so an engine can quote them.
Your account and your data
How workspaces and sites fit together, exporting everything, removing a single site, and closing your account for good.
Working out what to measure rather than how to wire it up? Learn covers the metrics themselves — revenue per visitor, paying conversion, lifetime value and attribution — without assuming you use Statlark.
Reading this with an agent? There’s an llms.txt index of these pages and an OpenAPI spec for the REST API. Making your own site agent-readable? We wrote up how.