# 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 and billable sites.
- There is no free plan and no free trial: the subscription is the whole business model, so visitor data is never sold or used for advertising.
- Free for open-source projects: OSI-licensed with a public repository, by application.
- The tracker sets no cookies and collects no personal data, so sites using it need no consent banner, including in the EU.
- Visitors are counted with a daily-rotating anonymous hash, so no profile follows anyone between days or between sites.
- 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, Core Web Vitals, visitor journeys, campaign and UTM reports, custom events, public dashboards, unlimited team members, 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.
- [Changelog](https://getopen.so/changelog): What shipped, newest first: realtime presence, revenue attribution, imports from other analytics providers.
- [Free analytics for open source](https://getopen.so/oss): Open Analytics is free for OSI-licensed projects with a public repository. Qualification rules and the application form.
- [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.
- [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 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.
- [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 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.
- [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.