# Open Analytics

> Open Analytics is a privacy-first Google Analytics alternative: realtime visitors, funnels and revenue attribution from one lightweight, cookieless script. GDPR-friendly with no consent banner. Open source and self-hostable.

## Key facts

- Pricing: Starter $9/mo, Growth $19/mo, Pro $49/mo (or ten months' price paid yearly). Every feature is on every plan; the tiers differ only in monthly events (50K/500K/5M), billable sites (1/5/10) and team seats (owner only / 5 / 10). Custom enterprise plans exist above Pro.
- There is no free plan, but there is a 7-day free trial on whichever plan you pick, with that plan's limits. A card is taken up front and nothing is charged today; on day 7 the chosen plan's price is charged automatically and the plan continues. The charge date is shown in the product for the whole trial. Cancelling before that date costs nothing. The subscription is the whole business model, so visitor data is never sold or used for advertising.
- By default (Light mode) the tracker sets no cookies and collects no personal data, so sites using it need no consent banner, including in the EU.
- In Light mode visitors are counted with a daily-rotating anonymous hash, so no profile follows anyone between days or between sites.
- Pro mode is an opt-in setting on every plan: it remembers a visitor across days, subdomains and the site's own domains with a first-party cookie, either after the site's consent banner calls oa.consent('granted') or from the first page, and adds new vs returning visitors, weekly retention cohorts and per-visitor history. An optional first-party proxy on the site's own host keeps it working in Safari and past ad blockers.
- The script is a single async tag, around 2 KB compressed, with no SDK and no build step.
- Open source under AGPLv3 and self-hostable: run it on your own infrastructure, or use the hosted service.
- Included on every plan: realtime dashboard, funnels and conversions, revenue attribution via Stripe or Polar, Core Web Vitals, visitor journeys, campaign and UTM reports, custom events, public dashboards, weekly email digest, import and export.
- Imports are supported from Plausible, Fathom and other tools, with a review step before anything reaches the dashboard and one-click rollback.

## Pages

- [Open Analytics: open-source, privacy-first web analytics](https://getopen.so/): The product: realtime visitors, funnels, revenue attribution and Core Web Vitals from one cookieless script. Includes pricing and the questions we are asked most.
- [Pricing](https://getopen.so/pricing): Three sizes priced by events a month, $9, $19 and $49, with every feature on every plan; how the 7-day trial charges, how the meters compare with other tools, and the questions asked before paying.
- [Changelog](https://getopen.so/changelog): What shipped, newest first: realtime presence, revenue attribution, imports from other analytics providers.
- [Contact](https://getopen.so/contact): How to reach the people building Open Analytics: questions, migrations, enterprise plans.
- [Privacy Policy](https://getopen.so/privacy): What the tracker collects and what it never collects: no cookies, daily-expiring identifiers, EU hosting, self-serve deletion.
- [Privacy Notice Template](https://getopen.so/privacy/template): Ready-made privacy policy language for sites running Open Analytics: copy it, change the name, done.
- [Terms of Service](https://getopen.so/terms): Terms covering the hosted service: plans, acceptable use, the DPA, and how leaving works.
- [Open Analytics vs Plausible](https://getopen.so/vs/plausible): Plausible and Open Analytics are both open-source, cookieless analytics you can self-host, and neither needs a consent banner. Plausible is the more established product, with a longer track record. Open Analytics goes further: revenue attributed back to its source, per-visitor journeys, funnels, and questions answered in plain English.
- [Open Analytics vs Fathom](https://getopen.so/vs/fathom): Fathom and Open Analytics come from the same school: cookieless, privacy-first analytics that need no consent banner. Fathom is deliberately minimal and aggregate-only (no funnels, no per-visitor journeys), and its open-source Lite version has been frozen since 2020. Open Analytics is open source and adds what Fathom leaves out: funnels, every visitor's journey, revenue attributed to its source, and plain-English answers, from $9 instead of $15.
- [Open Analytics vs Google Analytics](https://getopen.so/vs/google-analytics): Google Analytics is free and enormously capable, with deep Google Ads integration and raw exports to BigQuery. It also runs on cookies, requires a consent banner in Europe, and keeps free-tier data for at most 14 months. Open Analytics answers the same everyday questions from one cookieless script: realtime journeys, revenue attributed to its source, Core Web Vitals, and no banner between you and your visitors.
- [Open Analytics vs DataFast](https://getopen.so/vs/datafast): DataFast and Open Analytics ask the same question: which visits actually turn into revenue. Both attribute payments to their source and follow individual journeys on a live globe. DataFast is closed source, and its attribution rides a first-party cookie; its own docs say switching on cookieless mode weakens it. Open Analytics is open source and cookieless from the first pageview, with full revenue attribution and no consent banner to install, plus Core Web Vitals and plain-English answers.
- [Open Analytics vs Simple Analytics](https://getopen.so/vs/simple-analytics): Simple Analytics and Open Analytics share the same foundation: cookieless counting, no consent banner, and an AI you can ask questions in plain English. Simple Analytics is the stricter minimalist (it refuses even IP addresses) and meters pageviews from $20 a month. Open Analytics starts at $9 and goes deeper on one script: realtime journeys on a live globe, revenue attributed back to its source, and Core Web Vitals.
- [Open Analytics vs Umami](https://getopen.so/vs/umami): Umami and Open Analytics are both open-source, cookieless analytics you can self-host, with funnels and Core Web Vitals in the box. Umami's free cloud tier is genuinely generous, and its 38,000-star community is the largest in the category. Open Analytics goes further where money meets traffic: payments attributed to their source through your payment provider, journeys on a live globe, and questions answered in plain English.
- [Blog](https://getopen.so/blog): Guides, comparisons and answers on privacy-first web analytics: Google Analytics alternatives, cookieless tracking, GDPR, and how to measure what matters.
- [The privacy-first analytics guide](https://getopen.so/blog/privacy-first-analytics-guide): A complete guide to privacy-first web analytics: what it is, why teams switch from Google Analytics, how cookieless tracking works, how to stay GDPR-compliant, which metrics matter, and how to choose a tool.
- [The best Google Analytics alternatives in 2026](https://getopen.so/blog/best-google-analytics-alternatives): Seven Google Analytics alternatives compared on price, privacy and what they actually measure: Open Analytics, Plausible, Fathom, Umami, Simple Analytics, DataFast and Matomo. Which one fits depends on whether you count pageviews or events, and whether you need a cookie banner.
- [The best Plausible alternatives in 2026](https://getopen.so/blog/best-plausible-alternatives): Five Plausible alternatives compared: Open Analytics, Fathom, Umami, Simple Analytics and Matomo. Plausible is excellent at the simple, cookieless dashboard; the alternatives below win on revenue attribution, price, self-hosting or depth.
- [The best Fathom Analytics alternatives in 2026](https://getopen.so/blog/best-fathom-alternatives): Five Fathom alternatives compared: Open Analytics, Plausible, Umami, Simple Analytics and Matomo. Fathom is strong on flat, multi-site pricing; the alternatives below win on the entry price, free self-hosting, or a per-visitor journey Fathom does not keep.
- [The best Matomo alternatives in 2026](https://getopen.so/blog/best-matomo-alternatives): Five lighter Matomo alternatives compared: Open Analytics, Plausible, Umami, Fathom and Simple Analytics. Matomo is the deepest open-source analytics, but most teams want less weight, here is what to run instead.
- [The best cookieless analytics tools in 2026](https://getopen.so/blog/best-cookieless-analytics-tools): Cookieless analytics tools measure traffic without a cookie or a consent banner. Here are the five best (Open Analytics, Plausible, Fathom, Umami and Simple Analytics) compared on price, metering and depth.
- [The best open-source analytics tools in 2026](https://getopen.so/blog/best-open-source-analytics-tools): Open-source web analytics you can read, audit and self-host: Open Analytics, Umami, Matomo, Plausible and Fathom Lite, compared on licence, hosting and features.
- [Plausible vs Fathom vs Simple Analytics (2026)](https://getopen.so/blog/plausible-vs-fathom-vs-simple-analytics): A side-by-side of the three best-known privacy-first analytics tools (Plausible, Fathom and Simple Analytics) on price, metering, self-hosting and depth, with Open Analytics as the option that adds revenue attribution the other three lack.
- [Plausible vs Fathom (2026)](https://getopen.so/blog/plausible-vs-fathom): Plausible versus Fathom on price, metering, sites and self-hosting, the two best-known privacy-first analytics tools compared, with Open Analytics as the option that adds revenue attribution neither one has.
- [Google Analytics vs Plausible (2026)](https://getopen.so/blog/google-analytics-vs-plausible): Google Analytics 4 versus Plausible on price, privacy, cookie banners and depth, and where Open Analytics fits for teams that want privacy without giving up revenue attribution.
- [Google Analytics vs Fathom (2026)](https://getopen.so/blog/google-analytics-vs-fathom): Google Analytics 4 versus Fathom on price, privacy, cookie banners and sites, and where Open Analytics fits for teams that want privacy plus revenue attribution.
- [Umami vs Plausible (2026)](https://getopen.so/blog/umami-vs-plausible): Umami versus Plausible on price, metering, self-hosting and licence, two open-source, cookieless analytics tools compared, with Open Analytics as the option that adds revenue attribution.
- [The best analytics for SaaS in 2026](https://getopen.so/blog/best-analytics-for-saas): SaaS analytics has to follow a visitor from first touch to paying customer. Here are the best privacy-first tools for SaaS (Open Analytics, Plausible, Fathom and Umami) ranked on funnels, revenue attribution and journeys.
- [The best analytics for ecommerce in 2026](https://getopen.so/blog/best-analytics-for-ecommerce): Ecommerce analytics has to connect a sale to the campaign that drove it. Here are the best privacy-first tools for online stores (Open Analytics, Plausible, Fathom and Matomo) ranked on revenue attribution and conversion tracking.
- [The best analytics for startups in 2026](https://getopen.so/blog/best-analytics-for-startups): Startups need analytics that is cheap, cookieless and shows what earns. Here are the best options (Open Analytics, Plausible, Umami and Fathom) ranked on price, revenue insight and time-to-value.
- [The best analytics for bloggers in 2026](https://getopen.so/blog/best-analytics-for-bloggers): Bloggers need simple, cookieless analytics that shows what people read and where they came from. Here are the best options (Open Analytics, Plausible, Umami and Simple Analytics) ranked on simplicity and price.
- [The best analytics for agencies in 2026](https://getopen.so/blog/best-analytics-for-agencies): Agencies manage analytics across many client sites and need shareable dashboards. Here are the best options (Open Analytics, Fathom, Plausible and Umami) ranked on multi-site pricing, sharing and client reporting.
- [The best analytics for WordPress in 2026](https://getopen.so/blog/best-analytics-for-wordpress): The best privacy-first analytics for WordPress (Open Analytics, Plausible, Matomo and Fathom) compared on setup, cookie banners and depth. All install with a snippet or plugin and need no consent banner.
- [The best analytics for Next.js in 2026](https://getopen.so/blog/best-analytics-for-nextjs): The best privacy-first analytics for Next.js (Open Analytics, Plausible, Umami and Fathom) compared on setup, App Router support, cookie banners and developer features like an MCP server.
- [The best analytics for small business in 2026](https://getopen.so/blog/best-analytics-for-small-business): Small businesses need analytics that is cheap, simple and needs no legal review. Here are the best options (Open Analytics, Plausible, Umami and Simple Analytics) ranked on price, simplicity and no cookie banner.
- [The best analytics for marketers in 2026](https://getopen.so/blog/best-analytics-for-marketers): Marketers need campaign attribution and revenue by channel, not just pageviews. Here are the best privacy-first tools (Open Analytics, Plausible, Fathom and Matomo) ranked on UTM reporting, revenue attribution and funnels.
- [The best analytics for React apps in 2026](https://getopen.so/blog/best-analytics-for-react): React single-page apps need analytics that tracks client-side route changes without cookies. Here are the best options (Open Analytics, Plausible, Umami and Fathom) for React, with SPA pageview tracking and Core Web Vitals.
- [How to switch from Google Analytics to a privacy-first tool](https://getopen.so/blog/how-to-switch-from-google-analytics): A step-by-step guide to moving off Google Analytics without losing continuity: run both in parallel, tag your conversions, connect revenue, then cut over and drop the cookie banner.
- [How to track custom events in web analytics](https://getopen.so/blog/how-to-track-events): A step-by-step guide to tracking custom events (signups, purchases, clicks) in privacy-first analytics, using data attributes, no-code rules, or a one-line JavaScript call.
- [How to set up a conversion funnel](https://getopen.so/blog/how-to-set-up-a-conversion-funnel): A step-by-step guide to building a conversion funnel in analytics: choose the goal, define the ordered steps as pages and events, then read the drop-off to find what to fix.
- [How to track revenue with Stripe in your analytics](https://getopen.so/blog/how-to-track-revenue-with-stripe): A step-by-step guide to connecting Stripe to your analytics so each payment is attributed back to the visit, page and campaign that produced it, without cookies.
- [Is Google Analytics GDPR compliant?](https://getopen.so/blog/is-google-analytics-gdpr-compliant): Whether Google Analytics is GDPR compliant depends on configuration and consent, and several EU regulators have raised concerns about data transfers. Here is what the issue is, what Google changed, and how cookieless analytics sidesteps it entirely.
- [GDPR-compliant analytics: the tools that need no consent banner](https://getopen.so/blog/gdpr-compliant-analytics): GDPR-compliant analytics tools store no personal data and set no cookies, so they need no consent banner. Here are the best (Open Analytics, Plausible, Fathom, Umami and Simple Analytics) and what makes them compliant.
- [Do I need a cookie consent banner?](https://getopen.so/blog/do-i-need-a-cookie-consent-banner): Whether you need a cookie consent banner depends on whether your site stores or reads non-essential cookies. Here is a simple way to decide, and why cookieless analytics lets many sites drop the banner entirely.
- [What is revenue attribution?](https://getopen.so/blog/what-is-revenue-attribution): Revenue attribution ties each payment back to the visit, page and traffic source that produced it, so you can see which channels and pages actually earn, not just which get traffic. Here is how it works and why most analytics tools do not do it.
- [What is bounce rate?](https://getopen.so/blog/what-is-bounce-rate): Bounce rate is the share of visits where someone views one page and leaves without any further interaction. Here is how it is calculated, what counts as a bounce, what a good bounce rate looks like, and why GA4 reports it differently.
- [What is session duration?](https://getopen.so/blog/what-is-session-duration): Session duration is how long a visit to your site lasts, from the first pageview to the last recorded interaction. Here is how it is measured, why the last page is tricky, and what GA4's 'average engagement time' changed.
- [What is an engaged session?](https://getopen.so/blog/what-is-an-engaged-session): An engaged session is GA4's replacement for the bounce: a visit that lasted longer than 10 seconds, had a conversion, or included two or more pageviews. Here is what it means, how engagement rate works, and why bounce rate is now its inverse.
- [What is UTM tracking?](https://getopen.so/blog/what-is-utm-tracking): UTM tracking uses tags added to a link's URL to tell analytics where a visitor came from, the source, medium and campaign. Here is what each UTM parameter means, how to build them, and how they power campaign reporting.
- [What is a conversion funnel?](https://getopen.so/blog/what-is-a-conversion-funnel): A conversion funnel is the sequence of steps a visitor takes toward a goal (like landing, signup, and purchase) with drop-off measured at each step. Here is how funnels work, how to read them, and what they reveal.
- [What is event tracking?](https://getopen.so/blog/what-is-event-tracking): Event tracking records specific actions visitors take (clicks, signups, purchases) beyond just pageviews. Here is what an event is, how it differs from a pageview, and how event-based analytics works.
- [First-party vs third-party analytics](https://getopen.so/blog/first-party-vs-third-party-analytics): First-party analytics runs from your own domain and keeps data in your control; third-party analytics loads from an external service and shares it. Here is the difference, why it matters for privacy and accuracy, and how it affects ad blockers.
- [What is web analytics?](https://getopen.so/blog/what-is-web-analytics): Web analytics is the measurement and analysis of website traffic and behaviour, who visits, where they come from, what they do, and whether they convert. Here is what it measures, the core metrics, and how privacy-first analytics differs.
- [What are unique visitors?](https://getopen.so/blog/what-are-unique-visitors): Unique visitors is the count of distinct people who visited your site in a period, each counted once no matter how often they returned. Here is how it differs from pageviews and sessions, and how cookieless tools count it.
- [Pageviews vs sessions: what's the difference?](https://getopen.so/blog/pageviews-vs-sessions): Pageviews count every page load; sessions count visits. Here is the difference between pageviews and sessions, how a session starts and ends, and which metric to use for what.
- [What is referral traffic?](https://getopen.so/blog/what-is-referral-traffic): Referral traffic is visitors who arrive by clicking a link on another website, rather than from search, ads or typing your URL. Here is how it works, how it differs from direct and organic traffic, and how to read it.
- [What is cookieless analytics?](https://getopen.so/blog/what-is-cookieless-analytics): Cookieless analytics measures website traffic without storing a cookie or any personal data in the visitor's browser. Because nothing identifying is stored, sites using it need no consent banner under GDPR and ePrivacy. Here is how it works and what it can and cannot see.
- [Open Analytics documentation](https://getopen.so/docs): What Open Analytics is, how the pieces fit together, and where to start.
- [Quick start](https://getopen.so/docs/quick-start): From zero to live numbers in a few minutes: create a site, install the tracker, watch the first pageview arrive.
- [Installing the tracker](https://getopen.so/docs/install): The snippet, the CLI installer, where the tag goes, and how to confirm it works.
- [Install on HTML / static sites](https://getopen.so/docs/install/html): Add Open Analytics to a HTML / static sites site: where the snippet goes and how to verify it.
- [Install on Next.js](https://getopen.so/docs/install/nextjs): Add Open Analytics to a Next.js site: where the snippet goes and how to verify it.
- [Install on TanStack Start](https://getopen.so/docs/install/tanstack-start): Add Open Analytics to a TanStack Start site: where the snippet goes and how to verify it.
- [Install on React (Vite / CRA)](https://getopen.so/docs/install/react): Add Open Analytics to a React (Vite / CRA) site: where the snippet goes and how to verify it.
- [Install on Vue.js](https://getopen.so/docs/install/vue): Add Open Analytics to a Vue.js site: where the snippet goes and how to verify it.
- [Install on Nuxt](https://getopen.so/docs/install/nuxt): Add Open Analytics to a Nuxt site: where the snippet goes and how to verify it.
- [Install on SvelteKit](https://getopen.so/docs/install/sveltekit): Add Open Analytics to a SvelteKit site: where the snippet goes and how to verify it.
- [Install on Remix](https://getopen.so/docs/install/remix): Add Open Analytics to a Remix site: where the snippet goes and how to verify it.
- [Install on Astro](https://getopen.so/docs/install/astro): Add Open Analytics to a Astro site: where the snippet goes and how to verify it.
- [Install on Gatsby](https://getopen.so/docs/install/gatsby): Add Open Analytics to a Gatsby site: where the snippet goes and how to verify it.
- [Install on WordPress](https://getopen.so/docs/install/wordpress): Add Open Analytics to a WordPress site: where the snippet goes and how to verify it.
- [Install on Webflow](https://getopen.so/docs/install/webflow): Add Open Analytics to a Webflow site: where the snippet goes and how to verify it.
- [Install on Shopify](https://getopen.so/docs/install/shopify): Add Open Analytics to a Shopify site: where the snippet goes and how to verify it.
- [Script options](https://getopen.so/docs/script): Every attribute the snippet accepts: test mode, debug logging, and the privacy signals.
- [Custom events](https://getopen.so/docs/custom-events): Three ways to track events: data attributes, no-code rules in the dashboard, and the JavaScript API.
- [Identifying your users](https://getopen.so/docs/identify): Attach your own pseudonymous user ID to events with oa.identify, and what that changes.
- [Privacy and consent](https://getopen.so/docs/privacy): What is collected and what never is, GPC and DNT handling, the consent API, and cookie banners.
- [Visitor modes: Light and Pro](https://getopen.so/docs/visitor-modes): Light counts visitors without remembering them; Pro remembers them across days for new and returning visitors, retention and visitor history.
- [Cross-domain visitors](https://getopen.so/docs/cross-domain): How a Pro site keeps one visitor across its own domains with the _oa link parameter, and where that stops working.
- [First-party proxy](https://getopen.so/docs/proxy): Serve the tracker from your own host so Safari keeps remembering Pro visitors and ad blockers do not block it: recipes and the Check proxy step.
- [Ignore your own visits](https://getopen.so/docs/ignore): Keep your own browsing out of your numbers with #oa-ignore, per browser, with nothing to install.
- [Web Vitals](https://getopen.so/docs/web-vitals): Core Web Vitals (LCP, CLS, INP, FCP, TTFB) collected by the same script, at no extra cost.
- [The dashboard](https://getopen.so/docs/dashboard): Reading your numbers: intervals, comparisons, timezones, and every breakdown explained.
- [Realtime](https://getopen.so/docs/realtime): Who is on your site right now: the live counter, the visitor feed, and how presence works.
- [Funnels](https://getopen.so/docs/funnels): Define a sequence of pages and events and see where people drop off.
- [Public dashboards](https://getopen.so/docs/share): Share your numbers with a link: what the three switches publish, and how to revoke a link.
- [Widgets](https://getopen.so/docs/widgets): Publish one number as a live iframe you can embed anywhere, no account needed to view.
- [Revenue attribution](https://getopen.so/docs/revenue): Connect Stripe or Polar and see which pages, channels and campaigns actually earn.
- [Importing history](https://getopen.so/docs/import): Bring your history from Plausible, Fathom and other tools, review it before it lands, roll it back with one click.
- [Team and roles](https://getopen.so/docs/team): Invite people to a site, what owner, admin and viewer can each do, and how billing transfers work.
- [Email reports](https://getopen.so/docs/emails): The weekly digest that brings every site's week to your inbox, product updates, and the switches that govern them.
- [Timezones](https://getopen.so/docs/timezones): The three clocks: your dashboard timezone, a site's reporting timezone, and the share page's viewer picker.
- [Usage and billing](https://getopen.so/docs/usage-billing): Which events count against your plan, which are always free, and what happens when a subscription lapses.
- [The read API](https://getopen.so/docs/api): Query your analytics from your own code: authentication, endpoints, and the range parameters.
- [API keys](https://getopen.so/docs/api-keys): Tracking keys and read keys: what each one can do and how to handle them.
- [The CLI](https://getopen.so/docs/cli): getopen on npm: install the tracker with oa init, sign in with oa login, read stats from the terminal.
- [MCP: connect an AI agent](https://getopen.so/docs/mcp): Give Claude, ChatGPT or any MCP client scoped access to your analytics, and revoke it any time.
- [The AI assistant](https://getopen.so/docs/assistant): Ask questions about your traffic in plain language, and what the assistant can and cannot see.
- [Troubleshooting](https://getopen.so/docs/troubleshooting): No data arriving, numbers lower than other tools, events counted twice: the checklist for each.

## Notes

- Customer dashboards and public share links are excluded from indexing by design: a shared dashboard is public by its owner's choice, which is not the same as consenting to be findable in search.