[invisit](https://invisit.dev) · [Docs](https://invisit.dev/docs) · [llms.txt](https://invisit.dev/llms.txt) · [llms-full.txt](https://invisit.dev/llms-full.txt) # invisit vs Fathom > Fathom suits agencies that want client email reports, a 2 KB script and GA4 import. invisit suits teams that need funnels, per-visit timelines, team logins, alerts and revenue from their payment provider. At 1M pageviews invisit costs $49 a month and Fathom $60; under 20K, invisit is free. - Page: https://invisit.dev/compare/fathom - Facts about Fathom last verified: 2026-11-03, from [usefathom.com](https://usefathom.com)'s own pages - Pricing: monthly billing, the cheapest plan step that covers each volume. invisit bills events (page views and custom events); Fathom bills pageviews, custom events and API requests. ## At a glance - Price at 1M events a month: invisit $49, Fathom $60, so invisit costs 18% less than Fathom. - Free plan: invisit, up to 20K events a month with no time limit. Fathom: No. Plans start at $15 for 100K pageviews. - Only invisit, of the two: Data stored in the EU, Serve from your own domain, Funnels, Per-visit timelines, Heatmaps, Web vitals, Crawler reads (search and AI bots), Traffic alerts, Short links, On-page feedback, Free plan, Team members. - Where Fathom is ahead: You run an agency: Fathom emails weekly or monthly client reports, gives each client a share link, and includes 50 or more sites on every plan. ## Choose invisit if - You need funnels, per-visit timelines or event properties, not only an event name and a value. - Several people need their own logins with viewer, member or owner roles; Fathom has one login per account. - Revenue should come from Stripe, Paddle or another payment provider, refunds and fees included, not from values in your code. - You want alerts when traffic spikes, drops or stops, plus heatmaps, web vitals and crawler reads. - You want a free plan for a small site, or analytics data stored in the EU (Falkenstein, Germany). ## Choose Fathom if - You run an agency: Fathom emails weekly or monthly client reports, gives each client a share link, and includes 50 or more sites on every plan. - You want your Google Analytics 4 history imported, or Search Console terms beside your traffic. invisit does neither. - You want the smallest script: Fathom's measured about 2 KB gzipped, invisit's about 8.5 KB. - Your traffic sits between 250K and 500K or between 3M and 5M a month, where Fathom's price steps are lower. - You want one plain dashboard of pages, referrers and events, with nothing else to learn. ## Pricing | A month of | invisit | Fathom | | --- | --- | --- | | 10K | Free | $15 | | 100K | $14 | $15 | | 1M | $49 | $60 | | 10M | $199 | $200 | Source: [usefathom.com](https://usefathom.com/pricing). One plan with every feature, from 100K pageviews, so small sites pay $15. Extra sites cost $10 a month per 50. API calls count as pageviews. A year costs ten months' price. ## Features ### Privacy and setup | Feature | invisit | Fathom | | --- | --- | --- | | No cookies, no consent banner needed | Yes. Daily-rotating hash | Yes. No cookies; a visitor hash that rotates daily ([usefathom.com](https://usefathom.com/docs/troubleshooting/cookies)) | | Data stored in the EU | Yes. Falkenstein, Germany (Hetzner) | No. EU visits processed in the EU; analytics stored in the US ([usefathom.com](https://usefathom.com/features/data-isolation)) | | Lightweight script (under 10 KB) | Yes. About 8.5 KB gzipped; extras load on demand | Yes. About 2 KB gzipped ([usefathom.com](https://usefathom.com/docs/script/embed)) | | Serve from your own domain | Yes. @invisitdev/server proxy | No. Custom domains ended in March 2023 ([usefathom.com](https://usefathom.com/changelog/mar2023-firewall-settings)) | | Open source | Partly. Tracker and SDKs, MIT | Partly. Hosted product closed; the older Fathom Lite is MIT ([github.com](https://github.com/usefathom/fathom)) | | Import history from another tool | No | Yes. Google Analytics 4, without events ([usefathom.com](https://usefathom.com/docs/features/ga-importer)) | ### Analytics | Feature | invisit | Fathom | | --- | --- | --- | | Realtime view | Yes | Yes. Current visitors, pages and referrers, in 5-minute intervals ([usefathom.com](https://usefathom.com/docs/start/dashboard)) | | Custom events and goals | Yes | Yes. Event name and an optional value; no custom properties ([usefathom.com](https://usefathom.com/docs/events/overview)) | | Funnels | Yes | No ([usefathom.com](https://usefathom.com/features)) | | Per-visit timelines | Yes. Every visit step by step: live in the dashboard, any age through the API and MCP | No. Entry and exit pages, but no single-visit view ([usefathom.com](https://usefathom.com/docs/start/measurement)) | | Retention cohorts | No | No ([usefathom.com](https://usefathom.com/features)) | | Heatmaps | Yes. Clicks, rage and dead clicks, scroll depth | No ([usefathom.com](https://usefathom.com/features)) | | Session recordings | No | No ([usefathom.com](https://usefathom.com/features)) | | Web vitals | Yes. Never billed | No ([usefathom.com](https://usefathom.com/features)) | | AI assistant referrals | Yes. ChatGPT, Claude, Perplexity, Gemini and more | Yes. An AI tab: ChatGPT, Claude, Perplexity, Gemini and more ([usefathom.com](https://usefathom.com/docs/features/sources)) | | Crawler reads (search and AI bots) | Yes. Recorded server-side, never billed | No. Bots blocked and counted by type; no per-crawler report ([usefathom.com](https://usefathom.com/docs/features/bot-detection)) | | Revenue | Yes. Read from Stripe, Polar, Paddle, Dodo Payments, Creem and Lemon Squeezy | Yes. Event values in cents, sent from your code, every plan ([usefathom.com](https://usefathom.com/docs/events/ecommerce-conversions)) | ### Beyond the dashboard | Feature | invisit | Fathom | | --- | --- | --- | | Traffic alerts | Yes. Spikes, drops and silence, to Slack, Discord, ntfy or a webhook | No ([usefathom.com](https://usefathom.com/features)) | | Email reports | No | Yes. Weekly or monthly, unlimited, one site or several ([usefathom.com](https://usefathom.com/docs/features/email-reports)) | | Public dashboards | Yes | Yes. Public, passworded, or per-person links with expiry ([usefathom.com](https://usefathom.com/docs/features/shared-dashboards)) | | Short links | Yes | No ([usefathom.com](https://usefathom.com/features)) | | On-page feedback | Yes | No ([usefathom.com](https://usefathom.com/features)) | | API | Yes. REST, with an OpenAPI document | Yes. Reports and site management; each call counts as a pageview ([usefathom.com](https://usefathom.com/api/v1)) | | MCP server for AI assistants | Yes | Partly. Third-party servers only, none official ([github.com](https://github.com/mackenly/mcp-fathom-analytics)) | ### Plans | Feature | invisit | Fathom | | --- | --- | --- | | Free plan | Yes. 20K events a month, nearly every feature | No. Plans start at $15 for 100K pageviews ([usefathom.com](https://usefathom.com/pricing)) | | Free trial | Yes. 14 days | Partly. 7 days, card required ([usefathom.com](https://usefathom.com/docs/start/trials)) | | Sites | Yes. 4 free, unlimited on paid plans | Yes. 50 or more by plan; 50 extra for $10 a month ([usefathom.com](https://usefathom.com/docs/troubleshooting/sites)) | | Team members | Yes. Unlimited, on every plan | No. One login per account; view-only share links ([usefathom.com](https://usefathom.com/docs/features/shared-dashboards)) | | Data kept | Yes. Forever, on every plan | Yes. Full history while subscribed ([usefathom.com](https://usefathom.com/pricing)) | ## Why teams pick invisit invisit starts from a simple question: who actually came to your site, and what brought them there? So it leads with people, not only totals. Each visit keeps its pages and events in order, next to where it came from, including the AI assistants that now send real visitors. It also covers the jobs that usually need a second tool. Revenue arrives straight from your payment provider, crawler reads show which search engines and AI bots read your pages, and heatmaps, web vitals, short links and feedback sit in the same dashboard. Every paid plan has every feature, so there is no tier to outgrow. And it stays out of your visitors’ way: no cookies, no banner, nothing that follows anyone from one day to the next. ## How much does Fathom Analytics cost compared with invisit? Fathom costs $15 a month for up to 100K pageviews and $60 a month at 1M, on monthly billing. invisit is free up to 20K events, $14 a month at 100K and $49 at 1M. Neither gates features by plan, so the bill follows traffic alone, and Fathom's price steps land below invisit's in two ranges. Prices at the volumes in between, as of November 2026, from [Fathom's pricing](https://usefathom.com/pricing) and [invisit's pricing](/pricing): | A month of | Fathom | invisit | | ---------- | ------ | ------- | | 50K | $15 | $14 | | 200K | $25 | $24 | | 250K | $45 | $24 | | 500K | $45 | $49 | | 2M | $100 | $99 | | 3M | $140 | $99 | | 5M | $140 | $199 | Fathom counts pageviews, custom events and every API request against one allowance shared by all your sites. invisit counts page views, custom events, conversions and short-link clicks, never bots, crawler reads, web vitals or feedback. Going over works differently. When usage stays over, Fathom emails you, then after reminders and a final notice locks dashboard and API access while it keeps collecting ([Fathom's plan limits](https://usefathom.com/docs/account/limits)). invisit warns at 80%, records the first month over in full, and in a second month over in a row pauses new events at the limit. Fathom sells extra site packs ($10 a month per 50) and higher API rate limits ($19 to $399 a month). A year paid up front costs ten months' price on Fathom and nine on invisit. Fathom's trial is 7 days with a card; invisit's is 14 days without one. A worked example: a SaaS with 300K page views and 20K signup and checkout events a month uses 320K of either allowance. Fathom's 500K plan costs $45 a month or $450 a year. invisit's 1M step costs $49 a month or $441 a year, so Fathom is $4 cheaper monthly and invisit $9 cheaper yearly. ## Fathom for agencies: sites, client email reports and share links Fathom is built for agencies in ways invisit is not: every Fathom plan includes at least 50 sites, email reports go to clients on a schedule, and each client can get a dashboard link of their own. invisit has unlimited sites on every paid plan, but no scheduled email reports. Fathom's site allowance grows with the plan, per [Fathom's site limits](https://usefathom.com/docs/troubleshooting/sites): | Fathom plan | A month | Sites included | | ------------ | ---------- | -------------- | | 100K to 500K | $15 to $45 | 50 | | 1M | $60 | 75 | | 2M | $100 | 100 | | 5M | $140 | 150 | | 10M | $200 | 200 | Beyond that, packs of 50 more sites cost $10 a month each, up to 15 packs. An agency with 120 small client sites and 400K pageviews in total pays $45 for the 500K plan plus two packs: $65 a month. On invisit the same traffic costs $49 a month, whatever the number of sites. [Fathom's email reports](https://usefathom.com/docs/features/email-reports) are unlimited, weekly or monthly, for one site or a roll-up of several, to any address. [Fathom's share links](https://usefathom.com/docs/features/shared-dashboards) give each client a URL with an optional password and expiry date; viewers can filter and download CSVs but never see your other sites. On invisit, a client follows a public dashboard, with an optional password, instead of a weekly email. invisit roles cover a whole workspace rather than one site, so an agency gives each client a workspace of its own. ## Can you add team members to a Fathom account? No. As of November 2026, a Fathom account has one login, and Fathom's docs say it is "in the process of adding fully functional user accounts". invisit has workspaces with viewer, member and owner roles, and team members are included on every plan, free included. Until then, Fathom gives colleagues the same share link a client gets. Viewers can change dates, filter and download, but cannot change settings, and only the site owner can remove data. [Fathom's password guidance](https://usefathom.com/docs/account/password) asks you not to share the account password and to share dashboards instead. For a team where developers add events and marketers read campaigns, that one-login model is often the deciding gap. invisit [workspaces](https://invisit.dev/docs/guides/workspaces.md) give each person a sign-in and a role. ## Where does Fathom store data, and does it need a cookie banner? Neither Fathom nor invisit sets cookies, and both tell visitors apart with a hash that rotates daily, so neither follows anyone from one day to the next. The difference is location: Fathom stores its anonymized analytics on US infrastructure, and invisit stores data in Falkenstein, Germany. [Fathom's EU isolation](https://usefathom.com/features/data-isolation) routes visitors from the EU, the UK, Switzerland, Norway, Iceland and Liechtenstein to EU servers in Falkenstein, Helsinki and Nuremberg, where the IP address is stripped before anything reaches the US. Everyone else is processed in the US, and the anonymized records are stored there. [Fathom's DPA](https://usefathom.com/legal/dpa) lists BunnyWay (Slovenia) and AWS (USA) as sub-processors; Fathom is a Canadian company. | | Fathom | invisit | | ---------------------- | ----------------------------------------------------- | ----------------------------------------- | | Cookies | None | None | | Visitor hash | IP, user agent and site, salt rotated at midnight UTC | Rotates every day; raw IPs never stored | | Analytics stored in | US infrastructure | Falkenstein, Germany (Hetzner) | | Do Not Track | Counted unless you add `data-honor-dnt="true"` | Counted unless you add `data-respect-dnt` | | Global Privacy Control | Not mentioned in Fathom's docs | Counted unless you add `data-respect-gpc` | Fathom's Extreme EU Isolation (`https://cdn-eu.usefathom.com/script.js`) processes every visitor's request in the EU. Fathom calls that a choice about processing location; its data isolation page still says anonymized analytics are stored in the US. invisit runs Cloudflare, a US company, for DNS and the CDN in front of its German servers, and offers a [DPA](/legal/dpa). Fathom says its analytics need no consent banner; invisit adds an optional [consent mode](https://invisit.dev/docs/guides/privacy.md#requiring-consent) for sites whose policy asks for consent anyway. ## Fathom's script size, ad blockers and custom domains Fathom's tracker is smaller than invisit's. On November 3, 2026, `cdn.usefathom.com/script.js` measured 6,981 bytes, about 2 KB gzipped, against about 8.5 KB gzipped for invisit's core `invisit.js`, whose heatmap, feedback and interaction modules load only when used. Fathom no longer offers a way to serve its script from your own domain. [Fathom ended custom domains in March 2023](https://usefathom.com/changelog/mar2023-firewall-settings), saying uBlock and other blockers had caught up with them; domains set up before then keep working. [Fathom's bot detection docs](https://usefathom.com/docs/features/bot-detection) also warn that a reverse proxy can make real visitors look like bots unless you turn bot blocking off. invisit's [`@invisitdev/server`](https://invisit.dev/docs/server/sdk.md#proxy) serves the script and the collection endpoint from your own domain, and the same package records [crawler reads](https://invisit.dev/docs/server/sdk.md#crawler-reads). ## Does Fathom have funnels, visit timelines or alerts? No. Fathom reports pages, referrers, campaigns and events in aggregate, and has no funnels, no single-visit view and no traffic alerts; invisit includes all three. Both show visits from AI assistants such as ChatGPT, Claude, Perplexity and Gemini in their own tab. The gap starts with what an event can carry. A Fathom event is a name plus an optional `_value` in cents ([Fathom's events docs](https://usefathom.com/docs/events/overview)). An invisit event takes up to 32 properties, so `track('signup', { plan: 'pro' })` can later split a chart by plan, and invisit builds [funnels](https://invisit.dev/docs/guides/events.md#funnels) from pages or events, split by source, country or device. Fathom does track sessions: a visit's referrer carries across its pages, and entry and exit pages show where visits start and end. It does not show one visit's pages and events in order. invisit keeps that timeline for every visit (live visits open in the dashboard, any visit at any age through the API and MCP), and [`identify(user.id)`](https://invisit.dev/docs/guides/events.md#identify-signed-in-users) attaches your own hashed user id. Revenue works differently too. Fathom adds up the `_value` you send from your code, with a currency per event ([Fathom's ecommerce docs](https://usefathom.com/docs/events/ecommerce-conversions)). invisit [connects to Stripe, Paddle, Polar, Lemon Squeezy, Creem or Dodo Payments](https://invisit.dev/docs/guides/revenue.md#connect-a-provider) and reads payments, refunds, disputes, fees and net, with no code in your checkout. The rest has no Fathom counterpart: alerts on spikes, drops and silence to Slack, Discord, ntfy or a webhook; click and scroll heatmaps; web vitals from real visitors; crawler reads (Fathom blocks bots and counts them by type); short links; a feedback widget; and a remote [MCP server](https://invisit.dev/docs/api/mcp.md). Fathom has no official MCP server, though its Luna assistant, added in October 2026, answers questions about your stats in the dashboard. ## When Fathom is the better choice Fathom is the better choice for agencies that report to clients by email, for sites leaving Google Analytics that want their GA4 history, and for anyone who wants the smallest script and the fewest screens. Client reporting is Fathom's clearest win: scheduled email reports for one site or many, a share link per client, and [site transfers](https://usefathom.com/docs/troubleshooting/transfer) to a client's own account. invisit has no email reports. History comes next. [Fathom's GA4 importer](https://usefathom.com/docs/features/ga-importer) brings in daily pageview history (not events), and its Search Console integration puts search terms, clicks, impressions and position beside your traffic. invisit cannot import history and has no Search Console integration. Fathom's script is about a quarter the size of invisit's, and Fathom costs less from just over 250K up to 500K a month ($45 against $49) and from just over 3M up to 5M ($140 against $199). Fathom also keeps the list of things to learn short: one dashboard page, saved views, chart milestones, and a way to remove spam visits from past data. If you read traffic once a week and never need a funnel, that restraint is the product working as intended. ## Switching from Fathom to invisit 1. Create a site in invisit and install the script or `@invisitdev/web` next to Fathom's ([installation](https://invisit.dev/docs/web/installation.md), [frameworks](https://invisit.dev/docs/web/frameworks.md)). Both can run on the same pages. 2. Map each `fathom.trackEvent()` call to `track()`. invisit event names use letters, digits and `_ . : -`, so a name with spaces such as `newsletter signup` becomes `newsletter_signup`. 3. Replace `_value` with a [payment provider connection](https://invisit.dev/docs/guides/revenue.md#connect-a-provider), and keep the plan or product as an event property. 4. Export your Fathom history. [Fathom's custom export](https://usefathom.com/docs/features/exporting) downloads pageview or event data as CSV for any range up to All Time, with the dimensions you choose. 5. Run both for two to four weeks. Expect totals to differ a little, since each tool filters bots its own way. 6. Remove Fathom's script and cancel in its billing settings. After the paid period ends, Fathom queues your data for deletion within 60 days ([Fathom's cancel page](https://usefathom.com/docs/account/close)). ```ts title="src/analytics.ts" // Before: Fathom, loaded by