invisit
Compare

Amplitude alternative: invisit vs Amplitude compared

Amplitude is product analytics: events tied to users, with behavioral cohorts, session replay and experiments, free up to 2M events a month. invisit is cookieless web analytics for your site, with AI referrals, crawler reads and payment revenue built in, at $199 for 10M events where Amplitude Plus costs $720.

.mdllms.txt

Written by the invisit team. Facts about Amplitude checked on , from their own pages.

Choose invisit if

  • You want site analytics without cookies, so there is no consent banner for it and no device ID that lasts a year.
  • You send millions of events: at 10M a month invisit costs $199 and Amplitude Plus $720 on monthly billing.
  • You want revenue read from Stripe, Paddle or another provider, split by source, without building attribution charts.
  • You want crawler reads, Search Console queries and heatmaps on every plan, Free included, not heatmaps from Plus up.
  • You want a script of about 9.8 KB instead of about 70 KB, and data kept forever instead of one to seven years.

Choose Amplitude if

  • You analyse signed-in users in a product: behavioral cohorts, retention, journeys and B2B accounts, across web and mobile apps.
  • You want session replay, feature flags, web experiments and in-app guides and surveys in the same tool as your analytics.
  • You send under 2M events a month and want to pay nothing, with unlimited seats; Amplitude stays cheaper than invisit up to about 3M.
  • You need history imported from Mixpanel, PostHog or GA4, or data synced from and to your warehouse and ad tools.
  • You need Enterprise controls such as SSO, SCIM, role-based access or a BAA for health data.

What a month costs

Monthly billing, cheapest plan step that covers the volume. invisit bills events (page views and custom events); Amplitude bills events across the organization, page views and autocaptured events included. Plus plan on monthly billing, from its bill estimator; the first 2M events are free. Yearly costs 20% less. Plus also sells MTU volumes; Growth and Enterprise are quoted.

Monthly price, invisit and Amplitude
A month ofinvisitAmplitude PlusPlus
10KFreeFree
100K$14Free
1M$49Free
10M$199$720

Feature by feature

Features, invisit and Amplitude
FeatureinvisitAmplitude
Privacy and setup
No cookies, no consent banner neededDaily-rotating hashAMP_ cookies by default; identityStorage none turns storage off
Data stored in the EUFalkenstein, Germany (Hetzner)US by default; EU data center in Frankfurt, per organization
Lightweight script (under 10 KB)About 9.8 KB gzipped; extras load on demandAbout 70 KB gzipped; Session Replay adds about 148 KB
Serve from your own domain@invisitdev/server proxySelf-hosted proxy, set with serverUrl
Open sourceTracker and SDKs, MITSDKs only, MIT
Import history from another toolNoFrom Mixpanel and PostHog in-app, GA4 through BigQuery; imports are billed
Analytics
Realtime viewYesLive event updates on one user profile at a time
Custom events and goalsYesCustom events, plus autocapture of clicks, forms and downloads
FunnelsYesYes
Per-visit timelinesEvery visit step by step at any age: in the dashboard, the API and MCPA session-grouped event stream on each user profile
Retention cohortsNoBuilt-in cohorts on Free; 20 custom on Plus, unlimited from Growth
HeatmapsClicks, rage and dead clicks, scroll depthClick, selector and scroll maps on Plus and up; need Session Replay
Session recordingsNo10K a month on Free and Plus, 20K on Growth; kept 1 month
Web vitalsNever billedAutocapture option, off by default; each report is a billed event
JavaScript error trackingGrouped, tied to visits, with its own allowance: 5K reports a month on FreeError clicks: a JS error within 2 s of a click; no grouped error report
AI assistant referralsChatGPT, Claude, Perplexity, Gemini and moreLLM Search channels in the default channel rules
Crawler reads (search and AI bots)Recorded server-side, never billed; by bot and by page, with AI training and AI answers apartKnown bots blocked at ingestion; no crawler report
RevenueRead from Stripe, Polar, Paddle, Dodo Payments, Creem and Lemon SqueezyStripe webhook source, or revenue events sent from your code
Revenue by sourcePaid plans: by source, campaign, landing page and short linkBuild it: channels and attribution in Data Tables over revenue events
Queries from Google Search ConsoleEvery plan: clicks, impressions, CTR and position, per site and pageNot in its source catalog
Beyond the dashboard
Traffic alertsSpikes, drops, silence and error spikes, to Slack, Discord, ntfy or a webhookNot on Free; limited on Plus, anomaly monitors from Growth
Email reportsEvery plan: what changed, on MondaysDashboard subscriptions on every plan
Public dashboardsYesPublic links and embeds on Growth and Enterprise
Short linksYesNo
On-page feedbackYesIn-app surveys: one on Free and Plus, more as an add-on
APIREST, with an OpenAPI documentIngestion, export, dashboard and cohort APIs
MCP server for AI assistantsYesOfficial remote server, OAuth sign-in, every plan
Plans
Free plan20K events a month, nearly every feature2M events and 10K replays a month, no card
Free trial14 days on monthly plans, card requiredNo trial; the Free plan has no time limit
Sites4 free, unlimited on paid plansMultiple projects, billed on the organization total
Team membersUnlimited, on every planUnlimited seats on every plan
Data keptForever, on every plan1 year on Free, 2 on Plus, 7 on Growth and Enterprise

Is Amplitude good for website analytics?

Amplitude can measure a website, but it is built for product analytics: events tied to users and devices, studied in segmentation, funnel, retention and journey charts, with experiments, session replay and in-app guides on the same data. invisit is web analytics: pages, sources, conversions and revenue for a site, without cookies and without asking visitors who they are.

Amplitude’s Browser SDK has you call setUserId() when someone signs in so their events join one user, and keeps a device ID in a cookie until then. Its plans add behavioral cohorts, Impact Analysis, Personas and cross-project portfolios. Web analytics is one view of that platform, alongside a Marketing Hub and channel reports.

invisit starts from the site. It reports pages, referrers and campaigns, AI assistant referrals, crawler reads, web vitals and revenue read from your payment provider, with funnels and a step-by-step record of every visit. identify(user.id) attaches a hashed id of your own to visits, but there are no retention cohorts.

Pick by the question you ask most often. “Which users who tried feature X in week one are still active in week eight” is an Amplitude question. “Where did today’s signups come from, and what did they pay” is an invisit one.

How much does Amplitude cost after the free 2M events?

Amplitude is free up to 2M events a month, and its Plus plan charges by event volume above that: $94 a month at 3M, $281 at 5M and $720 at 10M on monthly billing, as of November 2026. invisit costs $49 at 1M, $99 at 3M and $199 at 10M, so Amplitude costs less up to about 3M events a month and invisit costs less from 5M up.

Amplitude counts every event it ingests across the organization: page views, session start and end events, custom events, backfilled and imported events, and everything autocapture sends. Identify calls are not counted, per Amplitude’s limits docs. invisit bills page views, custom events, conversions and short-link clicks, and never bills bots, crawler reads, web vitals, heatmap clicks or engagement pings.

Events a month Amplitude Plus, monthly Amplitude Plus, yearly (per month) invisit, monthly
1M $0 $0 $49
3M $94 $75 $99
5M $281 $225 $199
10M $720 $576 $199
20M $1,575 $1,260 Contact us

A worked example: a SaaS site with 1M page views in 400K sessions sends 1.8M events with the Browser SDK’s default autocapture (1M page views plus a start and an end event per session), which is free on Amplitude and $49 on invisit. Set autocapture: true, as Amplitude’s own install examples do, and element clicks, dead and rage clicks, network errors and web vitals become events too. At two clicks per page view the same site sends 3.8M events, past the $94 step on Amplitude’s calculator and short of the $281 one. invisit still bills the 1M page views.

On Amplitude Free Plus Growth
Events 2M First 2M free, to 70M Quoted
Session replays a month 10K 10K 20K
Heatmaps No Yes Yes
Custom behavioral cohorts No 20 Unlimited
Alerts No Limited Anomaly monitors
Data kept 1 year 2 years 7 years

Yearly billing on Amplitude’s pricing page saves 20%, Plus can also be bought by monthly tracked users, and startups with under $10M in funding and fewer than 20 employees can get a year of Growth free. An invisit year costs nine months’ price, and every paid plan has every feature.

Amplitude’s Browser SDK sets first-party cookies by default, so on EU and UK sites it usually sits behind a consent banner; Amplitude’s consent docs make you responsible for consent and for how you classify its cookies. invisit sets no cookies and stores no device identifier, which is why its analytics need no banner.

The AMP_ cookie holds a device ID that persists across sessions, the user ID once you set one, and session state; AMP_MKTG_ holds UTM tags, the referrer and ad click IDs. Both last 365 days. Amplitude documents three ways to change that:

  • Delay init() until a visitor consents. Amplitude notes the SDK may create cookies as soon as it initialises, even when the visitor has opted out.
  • identityStorage: 'localStorage', which moves the same data off cookies. It is still storage on the device.
  • identityStorage: 'none', which stores nothing, so every visit gets a new device ID until the user signs in.

invisit leaves Global Privacy Control and Do Not Track to you (respectGpc and respectDnt), tells visitors apart with a hash that rotates every day, never stores raw IP addresses, and offers requireConsent for a policy that wants consent anyway (privacy guide).

Where does Amplitude store data, and can it stay in the EU?

Amplitude stores data on AWS in the United States by default, and runs an EU data center in Frankfurt, Germany, for organizations provisioned there. invisit stores every site’s data in Falkenstein, Germany, on Hetzner.

The region belongs to the organization, per Amplitude’s security page, and an EU organization keeps its data in the EU for Amplitude’s AI features too. The SDK must send to the EU endpoint with serverZone: 'EU', or events go to the wrong region and fail with an invalid API key. A few APIs, such as the User Profile API, are not offered in the EU region (API hosts).

invisit has no region to pick. Cloudflare, a US company, runs DNS and the CDN in front of it, and the DPA is at /legal/dpa.

How big is the Amplitude Browser SDK?

The script loader in Amplitude’s docs fetches a build of about 70 KB gzipped, and turning on Session Replay adds a plugin of about 148 KB more. invisit’s core script is about 9.8 KB gzipped, and its heatmap, feedback and interaction modules load only when used.

Script, measured 16 November 2026 Gzipped
Amplitude analytics-browser-2.49.2-min.js 69.6 KB
Amplitude plugin-session-replay-browser-1.36.7 148.2 KB
invisit invisit.js About 9.8 KB

Amplitude’s npm package also has a Lite build without autocapture, which its docs put at about 30% of the default. The Unified SDK, which bundles analytics with Session Replay, experiments and guides, is larger again and loads the guides bundle from the CDN at runtime.

Amplitude session replay and heatmaps: what each plan includes

Amplitude includes session replay on every plan: 10K sessions a month on Free and Plus, 20K on Growth and 50K on Enterprise, each kept one month unless you buy more. Its click, selector and scroll maps are built from replay data and start on Plus. invisit has heatmaps of clicks, rage clicks, dead clicks and scroll depth on every plan, Free included, and no session recordings.

Amplitude’s heatmap docs say heatmaps use an anonymised copy of the replay that is not subject to replay retention, and need Session Replay turned on. Rage and dead clicks are also autocapture events in Amplitude, counted toward the monthly volume.

If you debug by watching what one user did, Amplitude covers it and invisit does not. If you want to know where visitors click on a landing page without recording anyone, invisit does it on its free plan (heatmaps guide).

When Amplitude is the better choice

Amplitude is the better pick over invisit when your questions are about users inside a product, not visitors to a site. In particular:

  • Retention and behavior: retention, stickiness and journey charts, behavioral cohorts and their syncs to ad and messaging tools.
  • Apps as well as web: SDKs for iOS, Android, React Native and more, with one user across platforms.
  • One platform: session replay, feature flags, web experiments with a visual editor, and in-app guides and surveys, each with a free allowance.
  • B2B accounts: account-level analytics and group-level experiments, on paid packages.
  • Low volume: up to 2M events a month free with unlimited seats, and cheaper than invisit up to about 3M events.
  • History: in-app imports from Mixpanel and PostHog, and GA4 through BigQuery (GA4 import). invisit cannot import history.
  • Enterprise controls: SSO on Growth, SCIM and role-based access on Enterprise, and a BAA for health data on Growth and Enterprise.

Switching from Amplitude to invisit

Moving from Amplitude to invisit is a short code change plus a few weeks of running both. invisit cannot import Amplitude history, so export it first.

  1. Export your history. Amplitude’s Export API returns raw events as zipped JSON lines, by the hour, up to 365 days and 6 GB per request. Free plans keep one year of data and Plus two, so export before history ages out.
  2. Install invisit next to Amplitude with the script tag or npm package.
  3. Map the calls. invisit event names use letters, digits and _ . : -, so Sign Up Clicked becomes sign_up_clicked, with up to 32 properties per event (events guide).
src/analytics.ts
// Amplitude
import * as amplitude from '@amplitude/analytics-browser'

amplitude.init('AMPLITUDE_API_KEY', { autocapture: true })
amplitude.track('Sign Up Clicked', { plan: 'pro' })
amplitude.setUserId(user.id)

// invisit
import { identify, init, track } from '@invisitdev/web'

init({ site: '<site id>' })
track('sign_up_clicked', { plan: 'pro' })
identify(user.id)
Amplitude invisit
[Amplitude] Page Viewed from autocapture Counted by the tracker, no call needed
amplitude.track(name, properties) track(name, properties)
amplitude.setUserId(id) identify(id), stored hashed (identify)
amplitude.identify(new Identify().set(...)) No user properties; send what you need as event properties
amplitude.revenue() or the Stripe source Connect your payment provider
Deferred init() for consent requireConsent, only if your policy asks for it
  1. Run both for two to four weeks and compare. Visitor counts will differ: Amplitude counts a device ID kept in a cookie for up to a year, invisit a hash that rotates daily.
  2. Remove the Amplitude snippet. If your consent banner existed only for Amplitude, review whether your site still needs it.

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, and paid plans split it by the source behind each payment. Crawler reads show which search engines and AI bots read your pages, Google Search Console queries show what people searched, 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.

invisit or Amplitude? Common questions

Is invisit cheaper than Amplitude?

At 1M events a month invisit costs $49 a month, and Amplitude Plus is free. invisit bills page views and custom events; Amplitude bills events across the organization, page views and autocaptured events included. Prices checked against Amplitude's pricing page on November 16, 2026.

Does Amplitude have a free plan?

Yes, Amplitude has a free plan: 2M events and 10K replays a month, no card. invisit is free up to 20K events a month with no time limit, and its free plan has nearly every feature.

What does invisit have that Amplitude does not?

invisit includes lightweight script (under 10 KB), crawler reads (search and AI bots), queries from Google Search Console, and short links; Amplitude does not, as of November 16, 2026.

When should I choose Amplitude over invisit?

Amplitude suits you better than invisit when one of these is true. You analyse signed-in users in a product: behavioral cohorts, retention, journeys and B2B accounts, across web and mobile apps. You want session replay, feature flags, web experiments and in-app guides and surveys in the same tool as your analytics. You send under 2M events a month and want to pay nothing, with unlimited seats; Amplitude stays cheaper than invisit up to about 3M. You need history imported from Mixpanel, PostHog or GA4, or data synced from and to your warehouse and ad tools. You need Enterprise controls such as SSO, SCIM, role-based access or a BAA for health data.

When should I choose invisit over Amplitude?

invisit suits you better than Amplitude when one of these is true. You want site analytics without cookies, so there is no consent banner for it and no device ID that lasts a year. You send millions of events: at 10M a month invisit costs $199 and Amplitude Plus $720 on monthly billing. You want revenue read from Stripe, Paddle or another provider, split by source, without building attribution charts. You want crawler reads, Search Console queries and heatmaps on every plan, Free included, not heatmaps from Plus up. You want a script of about 9.8 KB instead of about 70 KB, and data kept forever instead of one to seven years.

Does Amplitude use cookies?

Yes. As of November 2026, Amplitude's Browser SDK 2 sets a first-party cookie named AMP_ plus the first 10 characters of your API key, holding a device ID that persists across sessions, and an AMP_MKTG_ cookie with UTM tags and referrer. Both last 365 days by default. identityStorage can move them to localStorage, or to none, which gives every visit a new device ID. invisit sets no cookies and tells visitors apart with a hash that rotates daily.

Is Amplitude GDPR compliant?

Amplitude offers a DPA with Standard Contractual Clauses, is certified under the EU-US Data Privacy Framework, and runs an EU data center on AWS in Frankfurt. Its consent docs leave consent to you and note the SDK may create cookies as soon as it initialises, even for opted-out users, so sites that need consent first should delay init. invisit stores data in Germany, sets no cookies and never stores raw IP addresses. Checked November 2026.

Do page views count as events in Amplitude?

Yes. As of November 2026, Amplitude counts every event it ingests toward the monthly volume, and Browser SDK 2 sends page views, session start and session end events by default. With autocapture set to true, clicks, rage and dead clicks, network errors and web vitals are events too. Identify calls do not count. invisit bills page views, custom events, conversions and short-link clicks, and never bills bots, crawler reads, web vitals, heatmap clicks or engagement pings.

What happens when an Amplitude Free plan goes over 2M events?

As of November 2026, Amplitude emails admins at 80%, 90% and 100% of a Free plan's limit. After a third month over the limit it blocks the account: charts and dashboards become unreachable until you upgrade, and if overages continue Amplitude deletes the account six months after the first block. invisit warns at 80% of a plan, records the whole first month over, and pauses new events only after a second month over in a row.

Can Amplitude show traffic from ChatGPT and other AI assistants?

Yes, as a channel. As of November 2026, Amplitude's default channel classifier groups AI referrals into LLM Search and Paid LLM Search by referrer and UTM tags, and its separate AI Visibility product tracks how ChatGPT and Google AI Overviews mention your brand. Amplitude blocks known bots at ingestion and has no report of crawler reads. invisit puts ChatGPT, Claude, Perplexity, Gemini, Copilot and others in their own AI tab, and records crawler reads server-side.

How big is the Amplitude JavaScript SDK?

The script loader in Amplitude's docs fetches analytics-browser 2.49.2 from Amplitude's CDN. On November 16, 2026 it measured 258,187 bytes raw and 69.6 KB gzipped. The Session Replay plugin, 1.36.7, adds 148.2 KB gzipped, and a Lite npm build without autocapture is about 30% of the default, per Amplitude. invisit's core script, invisit.js, is about 9.8 KB gzipped, with heatmap, feedback and interaction modules loading only when used.

More comparisons