01Numbers you can check

A revenue number you can't check is a guess. Every sale in Tally has a receipt: the visits behind it, what tied the payment to them, the method and how sure it is. When nothing links a sale, the receipt says so. It is never guessed.

Coverage says how much of your revenue is linked to a visitor, each reason the rest isn't, and the code that fixes it, with the money each fix is worth.

See a receipt

02Four payment providers

StripeConnect Stripe with a restricted key that can only read. Tally imports your past 365 days, then takes each payment as it happens, and links it to a visitor by the strongest evidence it has.
PaddleConnect Paddle Billing with an API key limited to four permissions. Tally reads every completed transaction, tells new sales from renewals and upgrades, and links each to the visitor whose id rode in the checkout's custom data.
Lemon SqueezyConnect a Lemon Squeezy store with an API key. Tally reads orders and subscription invoices with their refunds, and links each sale to the visitor whose id came through the checkout's custom data, or by the buyer's email.
PolarConnect Polar with an organization access token limited to five scopes. Tally reads purchases and subscription cycles with their refunds and lost disputes, and links each to the visitor through checkout metadata, a checkout link's reference, or email.

The snippet goes on any site

One tag, about 3 KB, in the head of every page. It counts engaged time, scroll depth, goals, clicks on links to other sites and single-page app routes, and it reads DataFast's calls and goal attributes, so switching is a tag swap.

03Every view

Receipts: Open any sale and see the chain behind it: the buyer's first visit, the visits after, the one credited, what tied the payment to that browser, and the payment, each with an id you can look up with your provider. Then the method that linked it and how sure that is. See it
Coverage: The share of your revenue that is linked to a visitor, every reason the rest isn't, and the code that fixes each one. See it
Path to purchase: How long buyers take from their first visit, how many visits and pages it takes, how many buy on the first visit, and a flow from the source that first brought each buyer to the one credited with the sale. See it
Lifetime value: Each customer counted under the source of their first visit, with everything they've paid since: renewals, upgrades and refunds included, with the average and the repeat rate. See it
Peak hours: The period laid out by weekday and hour, for visits, sales or revenue, with the busiest three hours named only when the data supports it. See it
AI crawlers: AI crawlers' requests by crawler, operator, purpose and page, counted apart from visitors. Most never run a page's script, so a few lines on your server report them: snippets for Next.js, Cloudflare Workers and Express. See it
What they read: Engaged time that runs only while someone reads, and how far down each page they scroll, with buyers' reading against everyone else's. See it
Visitors and journeys: One row per visitor: where they are, where their latest visit came from and the pages it took, engaged time, and what they've paid. Open a row for every visit, and a journey for each page, goal and payment. See it
Sources with revenue: Referrers as the sources you'd name them (t.co is x.com), each in a channel, with visitors sent by AI assistants in a channel of their own, and the revenue behind every row. See it
Readable Direct: Visits with no referrer, read for what they most likely were: typed or bookmarked, a shared link, a return from checkout, or an app's own browser.
Goals and funnels: Goals with their completions, converting visitors, conversion and the revenue of the visitors who converted, and funnels of steps you put together.
Session replay: Recorded visits, off until you turn them on, with every input masked and passwords never recorded. Watch the visit behind a sale from its receipt. See it
Heatmaps: Where people click on a page and how far down they read it. See it
Live: Who is on the site right now, on a globe or a flat map. See it
Alerts and digests: A sale, a refund, a traffic spike or drop, and a daily or weekly digest, by email, Slack, Discord, Telegram or webhook. See it
API, CLI and MCP: A REST API, a command line and an MCP server for AI assistants, over the same numbers as the dashboard. See it
Labs: Your visitors as an ecosystem that moves week by week, and a river from first source to sale, drawn only from what they did. See it

04Three privacy modes

CookieOne first-party cookie recognises returning visitors for a year. In the EU and the UK such a cookie usually needs consent.
CookielessNo cookie at all: a visitor is counted once a day, so there is nothing for a cookie banner to cover.
Consent-firstCookieless until your banner says yes, then the cookie; a no or a withdrawal deletes it.

The IP address is used to find the city and dropped; it is never stored. Each site picks its own mode.

The privacy notice

05One plan, every site

One plan with every site and every feature, priced by events (a pageview or a goal): from $9 a month for 10k events to $169 a month for 10M. A year costs 9 months.

Every account starts with 14 days free, no card needed. The first 100 customers get 30% off for as long as they stay subscribed, and customers with an Outpost plan get 50% off while they have it; the two don't combine.

Every step of the plan

06How it compares

Each comparison is dated and sourced from the other product's own pages, and says where the other product is better.

07Made by Outpost

Tally is made by Outpost (opens in a new tab), the growth platform, at Tesseract Systems Corporation. It is a product of its own, with its own accounts.