Straight answers. No enterprise fog.
What LeetLytics is, how install works, what free and paid tiers include, and the features we deliberately leave out so the product stays simple and cheap to run.
What is LeetLytics?
LeetLytics is agent-first analytics for small businesses. It shows traffic, pages, events, breakages, health, and alerts in plain English so you and your agent can understand what is happening without becoming analytics operators.
How long does install take?
Day zero is one action plus a first page view: paste the browser snippet, install the WordPress plugin, connect Shopify, or add the SDK. Most teams reach a first dashboard signal in minutes, not an afternoon of event modeling.
Is LeetLytics cookieless?
Yes by default. Core tracking does not set LeetLytics browser cookies. You can still send your own pseudonymous identifiers if you need them, and workspaces support hostname allowlists plus path exclusions.
What does it cost?
Free tier: 1 site, 1k events/month, 14-day summary history, 1 alert — no credit card. Paid self-serve starts at $9.99/month (Starter) and scales to $199/month (Scale) based on event volume, sites, summary history, and alert limits. Longer history is distilled into daily rollups; raw per-event detail stays short. See /pricing for the full table.
Does it work with Shopify, WordPress, and Next.js?
Yes. Shopify uses an OAuth app plus web pixel (no day-zero pixel JSON hand-editing). WordPress ships a plugin with a public workspace key. Next.js and other apps use @leetlytics/sdk for page views, trackEvent, and optional fetch breakage tracking. Deep links: /install#shopify, /install#wordpress, /install?platform=developer.
Do you offer session replay or full APM?
Not as a product. Optional masked session snapshots can attach to grouped Alerts when you opt in — inputs, emails, and tokens are masked by default, and we do not capture keystrokes. Slow traces can feed the same grouped Alerts using route templates, not raw URLs; we do not sell APM. The product stays focused on plain-English traffic, pages, events, breakages, health, and alerts.
How do conversions work?
Conversions are optional and server-side.
POST /api/conversions accepts idempotent provider-agnostic payment events with a hashed workspace conversion key. Native Stripe, Lemon, or Polar webhook UIs are not day-zero product surfaces; use the conversions API when you are ready.Where is data stored?
Operational analytics data lives in Neon Postgres with low-cardinality rollups. There is no ClickHouse or customer warehouse connector in the launch product.