Introducing Trakily: analytics that start from revenue
Why we built Trakily, what it does today, and how it connects your traffic to the payments it brings.
Sunny Bundel2 min readFounders ask their analytics one question more than any other: what should I do more of? Most tools answer with visitors and pageviews. We built Trakily to answer with customers and revenue.
The gap we kept running into
Traffic numbers are easy to collect and easy to misread. A post can bring thousands of visitors and no customers; a small newsletter mention can bring a handful of visitors who all buy. If your analytics stop at the visit, both look like “traffic”, and the second one is easy to miss.
The payment data that tells them apart already exists, in Stripe or wherever you get paid. It just lives in a different tool, with no idea which visit led to which sale.
What Trakily does
- A small tracking script records visits, sources, campaigns, pages, goals and outbound clicks. Install it in one line on any site.
- A read-only connection to your payment provider (Stripe, Polar, Lemon Squeezy, Paddle, Dodo Payments or Razorpay) imports payments, refunds and subscriptions, including your history.
- Attribution links each payment to the visitor who made it, using the visitor id you pass at checkout, the checkout id on your thank-you page, or the customer's email.
- One dashboard where every channel, referrer, campaign, page and country shows revenue, conversion rate and revenue per visitor next to visitors.
Around that core
- SaaS metrics from your subscriptions: MRR, churn, NRR, LTV and MRR movements.
- Customer journeys: every visit, goal and payment of each new customer, in order.
- AI traffic: visits from ChatGPT, Claude, Perplexity and other assistants in their own channel, plus optional server-side tracking of AI crawlers.
- Google Search Console keywords with estimated revenue, Meta Ads spend and ROAS, and history imports from GA4 and Plausible.
- Goal alerts by email, Slack or Discord, a weekly summary, and traffic spike emails.
How we think about privacy
By default Trakily uses two first-party cookies on your own domain, because remembering a visitor for longer than a day is what makes revenue attribution work. We say so plainly rather than calling it cookieless. If you'd rather avoid cookies, a cookieless script is one checkbox away, with trade-offs we spell out in a separate post.
Getting started
Every account starts with a 14-day free trial, no card needed. The quickstart takes about five minutes, and the guides cover the common setups. We'd love to hear what you think.
Trakily shows which channels bring paying customers, not just visitors. Start a 14-day free trial; no card needed.