llms.txt
# Statlark
> Revenue-first web analytics: see which marketing actually earns, not just which sends traffic.
Statlark is a web analytics tool for people selling something online. It tracks visitors, sources and pages like any analytics tool, and additionally attributes revenue: every payment is traced back to the first-touch marketing source, landing page and campaign that earned it. Install is one line of script, or an npm SDK. Revenue arrives from a Stripe connection or the REST API.
Use it when the question is "which marketing earns money". It is not the tool for session replay, heatmaps, product-analytics funnels, or A/B testing — it does none of those.
Plans start at $9/month for 10k events with a 14-day free trial; see /pricing.
Operated from Romania by an independent developer. Cookie-optional: a cookieless mode sets no device storage at all, and a consent banner is available for cookie mode.
Docs last reviewed 2026-09-25.
## Docs
- [Revenue attribution](https://statlark.com/docs/revenue-attribution): install the tracker, then tie Stripe payments back to the visitors and sources that earned them.
- [Reading your data](https://statlark.com/docs/reading-your-data): what the numbers mean — revenue per visitor, paying conversion, how channels are classified, the visitor journey, and lifetime value.
- [Goals & conversions](https://statlark.com/docs/goals-conversions): track the conversions that matter, pick your #1 KPI, and get alerts.
- [Identifying users](https://statlark.com/docs/identifying-users): statlark.identify() turns anonymous visitors into durable, cross-device people with lifetime value.
- [Excluding traffic](https://statlark.com/docs/excluding-traffic): keep your own visits, staging, and bot-heavy regions out of your numbers.
- [Script configuration](https://statlark.com/docs/script-configuration): every data-* option on the snippet, plus cookieless/GDPR mode, the visitor ID, resetting the visitor on sign-out with statlark.reset(), and what to check when a site records no events at all.
- [JavaScript SDK](https://statlark.com/docs/javascript-sdk): install @statlark/web from npm and initialize with initStatlark() — a typed API for goals, identify, revenue and reset() on sign-out, plus a React provider.
- [First-party proxy](https://statlark.com/docs/first-party-proxy): route the tracker and its events through your own domain.
- [Cookie consent banner](https://statlark.com/docs/consent): 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](https://statlark.com/docs/badge): a paste-in "Analytics by Statlark" footer badge — no JavaScript, no requests, five variants.
- [AI discoverability](https://statlark.com/docs/ai-discoverability): make your site discoverable and citable by AI search engines and agents — robots.txt for AI crawlers, llms.txt, structured data, and extractable page structure.
- [Plans, trial and billing](https://statlark.com/docs/billing): 14-day free trial with no card; Starter and Growth plans at 10k or 100k events a month; what counts as an event (pageview, goal, identify — not payments, exclusions or bots); custom events and outbound clicks don't count; usage is shown in Settings and follows your billing cycle, not the calendar month; card, plan change, cancel and invoices in the Stripe portal; retention 3 or 5 years
- [Your account and your data](https://statlark.com/docs/your-account): workspaces vs sites and why the site ID decides where hits land; export the whole workspace as JSON; remove one site (type the domain, plus an emailed code when it holds data); delete the account and its login irreversibly.
## Learn
- [How to track revenue per visitor](https://statlark.com/learn/track-revenue-per-visitor): how to calculate and track revenue per visitor (RPV), per traffic source rather than site-wide.
- [How to attribute revenue to marketing channels](https://statlark.com/learn/attribute-revenue-to-marketing-channels): credit each payment back to the marketing channel that earned it, instead of ranking channels by traffic.
- [How to measure paying conversion rate](https://statlark.com/learn/measure-paying-conversion-rate): measure the share of visitors who become paying customers, and how that differs from a goal conversion rate.
- [How to track customer lifetime value](https://statlark.com/learn/track-customer-lifetime-value): track per-person lifetime value across devices by resolving payments and sessions to one durable identity.
- [First-touch vs last-touch attribution](https://statlark.com/learn/first-touch-vs-last-touch-attribution): choose between first-touch and last-touch attribution, and why the model has to be frozen at capture time rather than applied at read time.
- [How to track Stripe revenue in your analytics](https://statlark.com/learn/track-stripe-revenue-in-analytics): join Stripe charges to analytics sessions so revenue lands next to the campaign and landing page that earned it.
## API
- [REST API reference](https://statlark.com/docs/api): read revenue, visitors, sources, breakdowns, pages, goals and realtime; write payments, goals and identity server-side with bearer tokens.
- [OpenAPI spec](https://statlark.com/api/v1/openapi.json): machine-readable OpenAPI 3.1 description of every endpoint.
