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.
Does Amplitude need a cookie banner?
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.
- 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.
- Install invisit next to Amplitude with the script tag or npm package.
- Map the calls. invisit event names use letters, digits and
_ . : -, soSign Up Clickedbecomessign_up_clicked, with up to 32 properties per event (events guide).
// 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 |
- 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.
- Remove the Amplitude snippet. If your consent banner existed only for Amplitude, review whether your site still needs it.