Know which traffic
turns into revenue.
Aback Analytics shows where visitors come from, what they do, and which channels bring paying customers. One small script, no cookies, and revenue from the payment provider you already use.
- Free up to 10,000 events a month
- No card to start
- Set up in two minutes
Example SaaS
example.com
- Visitors
- 14,877+23% against the previous period
- Revenue
- $12,846.00
- Revenue per visitor
- $0.86
- Pageviews
- 35,704+18% against the previous period
- Bounce rate
- 41.0%
- Visit duration
- 2m 34s
- Organic Search5,653
- Direct3,570
- Social2,529
- Referral1,636
- Ai Assistant893
- /21,215
- /pricing9,922
- /blog/attribution-guide6,159
- /docs4,106
- /signup3,080
United States4,612
United Kingdom1,339
Germany1,190
India1,190
Canada744
An example dashboard with invented numbers, so you can see the layout.
Revenue from where you already sell
- Dodo Payments
- Stripe
- Paddle
- Lemon Squeezy
- Polar
- Shopify
- WooCommerce
- Payment API
How it works
From the first visit to the first payment
Three steps, and the reports fill in on their own. Nothing to model, no tag manager, no analyst.
- 01
Add one script
One async tag, under 5 KB compressed. Pageviews, sources, campaigns, devices and countries arrive on their own, single page apps included.
- 02
Mark what matters
Name a signup, a trial or any click as a goal, from the browser, with an HTML attribute, or from your server.
- 03
Connect revenue
Link Dodo Payments, Stripe, Paddle or another provider. Every payment is tied back to the visit and the channel that brought it.
Revenue attribution
See the channel behind every payment
Pageviews do not pay the bills. Aback ties each payment to the visit that started it, so you can put your time into the channels that bring customers.
- First touch and last touch, named and explained, with the window shown
- Refunds netted, every currency kept apart, amounts in exact cents
- A payment is recorded once, however often the provider retries
- Unmatched revenue is shown as unmatched, never guessed
Revenue by channel
Example data| Channel | Visitors | Customers | Revenue | Per visitor |
|---|---|---|---|---|
| Organic search | 4,812 | 61 | $3,904 | $0.81 |
| X | 1,390 | 29 | $2,262 | $1.63 |
| Hacker News | 902 | 14 | $1,105 | $1.23 |
| AI assistants | 655 | 12 | $1,020 | $1.56 |
| Direct | 3,104 | 31 | $2,449 | $0.79 |
X sends a quarter of the visitors that search does, and each one is worth twice as much.
Live visitors
Example data- Curious Ferret/pricingGooglenow
- Maple Yak/blog/attribution-guideX1m
- Mellow Wolf/signupChatGPT2m
- Lively Jaguar/Hacker News4m
Live view and visitor profiles
Watch people arrive, then follow one
A globe shows where visitors are right now. Open anyone to see every visit, page and payment, with a year of activity at a glance.
- A memorable name and avatar for each visitor, made from a random id
- Your own user id instead, once you call identify after sign in
- Every browser of one user joined in a single profile
- Viewers see totals only; single visitors stay with admins and analysts
Goals, funnels and journeys
Find the step where customers give up
Count the actions that matter, line them up into a funnel, and read the paths of the people who made it, and of the ones who did not.
- Goals from JavaScript, an HTML attribute, a scroll into view or your server
- Funnels of pages and events, with the source and revenue of each step
- Journeys before and after a conversion, filtered by channel or country
Trial funnel
Example data- 1Visited the landing page12,480 100%
- 2Opened pricing3,620 29%
77% leave between pricing and the trial
- 3Started a trial846 6.8%
- 4Paid147 1.2%
For developers and AI agents
Built to be wired in, not clicked around
A typed SDK, a server API for events and payments, scoped keys you can rotate, and an MCP server so your assistant can answer questions about your traffic.
- A public tracking id, separate from secret keys that never reach the browser
- Idempotent server events, with machine readable errors
- An OpenAPI reference with examples that run
<script async src="https://<your-host>/track.js"
data-website-id="<your tracking id>"></script>aback("track", "signup", { plan: "pro" });
<button data-aback-goal="trial_started">Start trial</button>"Which channel brought the most paying customers last month?"
ā Read through the Aback MCP server, with your approval.And much more
Everything a founder checks in the morning
Mentions on the chart
Posts about you on X and Reddit sit on the traffic chart, so a spike explains itself.
Commits on the chart
Connect a GitHub repository and see which release moved signups, from a private repository too.
Search Console keywords
The queries people searched before they arrived, next to the revenue those visits made.
AI crawlers and assistants
See which AI bots read your pages, and the visitors ChatGPT, Claude and Perplexity send you.
Public share links
Share a live dashboard with a link that can expire. Small numbers stay hidden on a public page.
Alerts by webhook or email
Hear about a drop in visitors, a jump in revenue or a goal that stopped converting.
Email reports
A weekly or monthly summary of traffic, goals and revenue, sent to the team.
Web vitals
LCP, INP and CLS from real visits, by page, recorded by the same script.
Retention cohorts
Which week's visitors came back, and how many of them stayed.
Plausible import
Bring your Plausible history over, and see it next to what Aback records from day one.
API, CSV export and MCP
A read API, a server event API, exports, and an MCP server so an AI assistant can read your reports.
An app for your phone
Install the dashboard on iOS or Android from the browser, and check revenue on the go.
Privacy
Useful numbers, without watching people
Aback records what a report needs and nothing else. The full list, and how long each part is kept, is in the docs.
What is recorded
- The page path and title of each pageview, with sensitive query parameters removed.
- The referring site and the utm_source, utm_medium, utm_campaign, utm_term and utm_content parameters.
- A device class, a browser and system family, and a screen size class.
- A country, from the network edge, stored as a two letter code.
- The events you send, with their properties.
- One random visitor id, derived on the server and never shared between websites.
What is never recorded
- IP addresses. No stored event contains one.
- Form contents, keystrokes or anything a visitor types.
- Device fingerprints, canvas hashes or font lists.
- Cookies. The script sets none.
- Identifiers that follow a person across websites.
Compare
More for less than DataFast
DataFast is a good product and the closest one to ours. Here is how the two compare on the things people ask about most.
| Ā | Aback Analytics | DataFast |
|---|---|---|
| Free plan | Yes, 10,000 events a month | No, a 14 day trial |
| Revenue attribution on the free plan | Yes, through the payment API | No free plan |
| Price for 200,000 events a month | $12 | $29 Starter, $59 Growth |
| Price for 2,000,000 events a month | $39 | $89 Starter, $179 Growth |
| Websites on the cheapest paid plan | 5 | 1 |
| X and Reddit mentions | From $12 | Growth plan, from $19 |
| Alerts | Webhook or email, on traffic, revenue or goals | Email, on goals |
| CSV export | Yes | Not in their docs |
| Cookies set by the default script | None | A visitor cookie and a session cookie |
DataFast prices and features as published on datafa.st and in its documentation on 29 October 2026, monthly billing. Tell us if something changed and we will correct it.
Pricing
Start free. Pay when it pays for itself.
Every plan has revenue attribution. Prices are in US dollars per month.
Free
Traffic, goals and revenue attribution for a first product.
$0/ month
- 10,000 events a month
- 1 website
- 30 days of history
- Goals, a funnel and revenue attribution
Pro
Every report, every integration and a year of history.
$12/ month
- 200,000 events a month
- 5 websites
- 1 year of history
- Journeys, profiles and every integration
Business
For teams and agencies running many websites.
$39/ month
- 2,000,000 events a month
- 25 websites
- 2 years of history
- Team roles and email reports
Questions
Asked before you sign up
Is there really a free plan?
Yes. One website, 10,000 events a month, goals, a funnel and revenue attribution through the payment API, with no card. Upgrade for the payment connectors, more websites, more events or a longer history.
Does the script use cookies?
No. It keeps one random id in the local storage of your website and sends no IP address with it. It can honour Do Not Track, and aback.optOut() turns it off for a visitor. Whether you need consent depends on where you and your visitors are; we do not give legal advice.
Do I need revenue to use it?
No. Traffic, goals, funnels, journeys and the live view all work without a payment provider. Revenue adds the money to the same reports.
Which payment providers work?
Dodo Payments, Stripe, Paddle, Lemon Squeezy, Polar, Shopify and WooCommerce connect from the Pro plan; the payment API works on every plan, for anything else. Payments are kept in each currency, refunds are netted, and a payment is recorded once even if the provider sends it twice.
Does it work with single page apps?
Yes. Route changes in Next.js, React and other frameworks are counted as pageviews without extra code.
What happens when I go over my plan?
Events past the monthly limit are not recorded until the next month starts or you upgrade. Your dashboard and history stay open the whole time.
Can I move from Plausible or Google Analytics?
You can import your Plausible export. A Google Analytics import is not available yet.
Can an AI assistant read my analytics?
Yes. Connect Claude or another assistant to the MCP server; you approve access with OAuth and can revoke it at any time.
Find the revenue in your traffic
Free for your first 10,000 events a month. Your first visit shows up within seconds of adding the script.