Changelog
What's new in Aback Analytics
Everything that shipped, newest first. Each entry describes work that is in the product today.
16 changes
Aback Analytics now looks and works like every Aback product, shows who is on your site right now, and costs less at every volume.
New5 changes
- A live globe on the Realtime page, next to the visitors on the site, each with a name, an avatar, the country, the page and the source, and a feed of what they do.
- A profile for every visitor: a year of activity at a glance, and every session with its pages, events and payments.
- A live demo on the landing page: the real shared dashboard of one of our websites, refreshed every minute.
- Search across the documentation with Cmd K or Ctrl K, an On this page rail, and links to the previous and next page.
- abackanalytics.com is the new address of Aback Analytics.
Improved5 changes
- The whole interface is built on Aback UI, the design system of every Aback product, with light as the default theme.
- The overview shows every key number above one chart that switches between them, with the previous period dashed, and breakdowns whose rows filter the report.
- One toolbar on every report holds the filters, pinned ranges, sharing and the period.
- Free covers 10,000 events a month with revenue attribution; Pro is $12 for 200,000 events and every integration; Business is $39 for 2,000,000.
- Funnels are computed from one read of the events, and goal reports stay fast with hundreds of goals.
Fixed6 changes
- A second checkout no longer starts a second subscription, and a late webhook can no longer move a plan back.
- The hourly job no longer stops data retention when an account has many alert rules.
- Server-side events count against the monthly quota, and the event and live APIs are rate limited per key.
- Viewers can no longer export visitor level data, and invites expire after seven days.
- An event delivered twice at the same moment is counted once.
- The tracking snippet points at the address that serves the script.
10 changes
Share a dashboard for any period, see who linked to you next to the visits they sent, and connect an AI assistant without handing it a key.
New8 changes
- Share links at /share/<token> that open a period and a granularity, such as ?period=last24h&granularity=hourly, with an optional via for who shared it.
- Mentions on Hacker News, Reddit and X that link to your domain, on the traffic chart and on the Sources page. Reddit and X need credentials on the deployment.
- A live map of the countries your visitors are in right now.
- Revenue from WooCommerce through its signed webhooks, with refunds as they grow.
- Deploy markers from a private GitHub repository, with a fine-grained token that is stored encrypted.
- The remote MCP server signs in with OAuth: an AI assistant asks, you pick the website it may read, and you can revoke it on the Developers page.
- Monthly retention cohorts over up to twelve calendar months.
- Aback Analytics can be installed as an app from the browser, on a phone or a computer.
Improved2 changes
- The last 24 hours as a rolling window, hourly charts for up to a week, weekly and monthly charts, the last twelve months and the year to date.
- Countries, devices and browsers on a shared dashboard when the owner turns them on, with the same privacy threshold.
14 changes
Connect the provider you sell with, follow a customer across devices, and answer more questions without leaving the dashboard.
New10 changes
- Revenue from Stripe, Paddle Billing, Lemon Squeezy, Polar and Shopify through their signed webhooks, with refunds, chargebacks and won disputes.
- identify links a visitor to your own user id, so a payment made on a laptop can be credited to a visit on a phone. Email addresses are refused.
- A visitor list and a profile with the timeline, the payments and the time to the first payment, and a way to delete a visitor.
- Tracking across your own domains, with a short-lived link parameter that is removed from the address on arrival.
- Saved segments, daily and weekly retention cohorts, a page explorer with the pages before and after, and the time between funnel steps.
- Site search terms, opt in per query parameter, with terms that look like email addresses or long numbers dropped.
- New and renewal subscription revenue, ad spend with the return on it, and an estimate of the revenue of each Search Console keyword.
- A live breakdown by country, page, source and device, AI crawler visits sent from your server, and deploy markers from a public GitHub repository.
- Imported Plausible history, shown apart from what Aback Analytics recorded, and email alerts that can watch one event.
- A remote MCP endpoint for AI assistants, read only, authenticated with an API key.
Improved1 change
- A failed webhook delivery is processed again when the provider retries it, and a renewal is credited to the visit that won the customer.
Fixed3 changes
- A Dodo dispute no longer takes the payment away twice.
- Paying customers are no longer added up across days.
- Navigating inside your own site is no longer counted as a referral.
10 changes
The script now records how people read and click, how fast your pages are for them, and the reports show how visitors become customers.
New9 changes
- Foreground time and scroll depth for every page, an engagement rate, and exit pages with an exit rate.
- Clicks on outbound links and file downloads, recorded automatically by host and path, never the query string.
- Goals declared in the markup with data-aback-goal, and goals that fire when an element scrolls into view.
- Core Web Vitals from the browsers of real visitors: LCP, INP and CLS at the 75th percentile, per page and per device.
- An AI assistant channel for visitors who arrive from ChatGPT, Perplexity, Claude, Gemini or Copilot.
- Revenue per visitor and paying conversion on the overview, and the path to purchase: days and visits before the first payment, channel performance and when payments happen.
- Regions, cities and hostnames, with a setting for how precise the location is. The address is never stored.
- Notes on the traffic chart, and spikes detected from the traffic with the source that drove them.
- Alerts in Slack and Discord, and weekly or monthly email reports.
Fixed1 change
- Reports over long ranges, such as the last twelve months, now load instead of failing.
6 changes
Payments can now be recorded from your own server and reported back against the source that produced them.
New6 changes
- Server-side revenue events with an idempotency key, so a repeated delivery is stored once and counted once.
- First touch and last touch attribution, both named explicitly, with a configurable lookback window.
- Payments that cannot be matched to a session inside the lookback window are reported as unmatched instead of being counted as direct traffic.
- Refunds reduce net revenue, and gross, refund and net totals are kept per currency so currencies are never added together.
- Revenue reports by source, medium, campaign, landing page, device and country.
- Payments can be sent from your own backend, including from a Dodo Payments checkout, and they are attributed to the source that produced them.
5 changes
You can now see where visitors drop out of a flow and what they did before a conversion.
New5 changes
- Funnels built from ordered pageviews and events, with a time window per step.
- Entrants, conversions, step to step conversion, overall conversion and drop-off for every funnel.
- Breakdowns of a funnel by source, country and device where the data exists.
- Visitor journeys that show the recorded sequence of pageviews and events before a goal or a payment.
- Journey access is restricted by role, and the timeline never exposes a full IP address or form content.
6 changes
The first usable version: install the script, see the traffic, and define the event that counts as a conversion.
New6 changes
- A small asynchronous tracking script that records pageviews, including single page app route changes.
- Website analytics for visitors, pageviews, sessions, sources, landing pages, devices and country.
- Custom events from the browser and from your own server, with a server-side event API.
- Goals that match an event name or a path, with conversion totals and a conversion rate.
- A website scoped read API with scoped API keys, where each secret is shown once and stored as a digest.
- Pseudonymous first party identifiers, no IP address storage and no device fingerprinting.
Try what just shipped
Free for your first 10,000 events a month. The limits of each plan are on the pricing page.