Find out which traffic actually paid.
Your analytics counts visits. Utlty counts revenue, and tells you where it came from.
Visitors
Revenue by source
Share of revenue
What it does
Connects your payments
Stripe first. Charges, refunds and renewals match back to the visit that started them.
Two attribution models
First touch and last touch, side by side. They answer different questions.
Watches for damage
Not "23 errors" but "23 people hit an error on checkout, and completions fell 14%".
One note a week
What moved, and whether it is worth your attention. No dashboard to hunt through.
Questions
Why is there an "unattributed" row?
Because some revenue cannot be traced to a source, and that is true of every analytics tool. Most hide it, which makes the rest of the numbers look more certain than they are. Utlty shows it every time.
How is this different from Google Analytics?
GA tells you how many people visited and, if you configure it carefully, how many converted. It does not know what they paid. Utlty reads your payment provider directly, so the revenue figures are real money, not modelled estimates.
Do I need a cookie banner?
There is a cookieless mode that stores nothing on the visitor's device, which in most EU jurisdictions removes the need for one. It trades away the ability to recognise a returning visitor, so multi-day attribution gets weaker. You choose per site, and the trade is stated where you choose it.
What will it cost?
A free tier that is genuinely useful, then around $9 a month for a single site with revenue attribution. Pricing is not final, and waitlist members will hear before it is.
When can I use it?
It is still being built. The waitlist gets one email when there is something real to try, and nothing else.