How much does Clicky cost compared with invisit?
Clicky is cheaper at almost every volume. Pro costs $9.99 a month for 30,000 page views a day, about 900K a month, and Pro Platinum $19.99 for 100,000 a day, about 3M a month. invisit is free up to 20K events, $49 a month at 1M and $99 at 3M.
Clicky meters page views per day, totalled across all your sites, while invisit meters events per month. The table converts Clicky’s daily limits at 30 days a month, as of November 2026, from Clicky’s pricing and invisit’s pricing:
| A month of | Clicky (cheapest plan) | Clicky with heatmaps | invisit |
|---|---|---|---|
| 20K | Free | $14.99 | Free |
| 90K | Free | $14.99 | $14 |
| 250K | $9.99 | $14.99 | $24 |
| 900K | $9.99 | $14.99 | $49 |
| 3M | $19.99 | $19.99 | $99 |
| 10M | Custom | Custom | $199 |
Clicky gates features by plan as well as volume. Free has 1 site, 30 days of history and no goals, custom data or outbound link tracking. Pro adds the premium reports, Pro Plus ($14.99) adds heatmaps and uptime monitoring at the same 30,000 a day, and Pro Platinum raises the limits to 30 sites and 100,000 a day. invisit has every feature on every paid plan and nearly every feature on Free.
A daily limit behaves differently from a monthly one. A launch day with 50,000 page views is over Clicky Pro’s daily cap even if the month stays under 900K; Clicky’s comparison page mentions a 20% buffer for overages. invisit counts the month, so one spike only matters if it pushes the month over. 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.
A year paid up front costs about eight months’ price on Clicky ($79.99 for Pro) and nine on invisit. Clicky gives every new account 21 days of premium, up to 3 sites; invisit’s trial is 14 days with a card, on monthly plans.
Clicky’s visitor log and Spy against invisit’s visit timelines
Both tools show individual visits, which few privacy-friendly analytics tools do. Clicky’s visitor log lists every visit with its pages and actions, and Spy streams visitors as they arrive. invisit’s Visits lists every visit too, opens each one step by step, and marks the ones online now.
The difference is how long a visit lasts. Clicky’s pricing says paid plans keep history indefinitely “with the exception of individual visitors and actions”, which are only guaranteed for 6 months; Free keeps 30 days. invisit keeps every visit forever on every plan, so a visit from two years ago opens the same way as one from this morning, in the dashboard, the REST API and MCP.
Clicky goes further on who a visitor is. Clicky’s custom data attaches a username or email to a visit, and the log shows that name in place of the IP address. Clicky can also list one visitor’s earlier visits by IP address or unique ID and compare a visit with their first, which its privacy page says works better with cookies, off by default. invisit tells visitors apart with a hash that changes every UTC day, so it never links one anonymous person’s visits across days. identify(user.id) joins a signed-in person’s visits, and keeps only a hash of the id, never a name or email.
| Clicky | invisit | |
|---|---|---|
| Live view | Spy, plus an on-site widget | Visits online now |
| Single visits kept | 6 months guaranteed on paid plans, 30 days free | Forever, every plan |
| Named visitors | Username or email from your code | A hash of your own user id |
| Visit list in the API | 31 days and 1,000 items per request | visit-log with the dashboard’s filters |
Does Clicky use cookies, and where is its data stored?
By default Clicky sets no tracking cookies and anonymizes IP addresses, so neither tool needs a cookie banner for analytics in its default setup. The difference is location: Clicky stores and processes data in the US, and invisit stores it in Falkenstein, Germany.
Clicky’s privacy page applies visitor privacy to all visitors by default. Owners can apply it only to visitors in the EEA and Brazil, or to nobody, for fraud prevention; then Clicky logs full IP addresses and may set cookies for unique visitors, attribution and heatmap sampling. Visitors behind VPNs such as iCloud Private Relay always have the VPN’s full IP logged.
Clicky’s DPA says personal data is transferred to Roxr Software in the United States, where it is stored and processed, under the EU-US Data Privacy Framework. invisit runs Cloudflare, a US company, for DNS and the CDN in front of its German servers, and offers a DPA.
| Clicky | invisit | |
|---|---|---|
| Cookies by default | None | None |
| IP addresses | Anonymized by default; full IP if you opt out | Raw IPs never stored |
| Analytics stored in | United States | Falkenstein, Germany (Hetzner) |
| Consent switch | clicky_custom.visitor_consent logs full data |
Optional consent mode |
Clicky’s script size, ad blockers and proxy tracking
Clicky’s core tracker is about half the size of invisit’s. On November 16, 2026, the tracker clicky.com serves for itself measured 12,495 bytes, about 4.8 KB gzipped. invisit’s core invisit.js is about 9.8 KB gzipped. Both load heavier parts only when used: Clicky its heatmap, video and on-site widget code, invisit its heatmap, feedback and interaction modules.
Both serve tracking from your own domain to get past ad blockers. Clicky’s reverse proxy guides generate the config for Nginx, Caddy, Apache, .htaccess or PHP, and Clicky says its own numbers rose almost 20% after switching. invisit’s @invisitdev/server serves the script and the collection endpoint from your own domain, and the same package records crawler reads.
Heatmaps, uptime monitoring and what only Clicky has
Clicky bundles a few tools invisit does not have at all. Uptime monitoring is the biggest: Monitage checks HTTP, HTTPS, SSH, FTP, IMAP and ICMP from several locations, needs a majority to agree before alerting, and logs every outage, on Pro Plus and up. invisit alerts when traffic stops arriving, which is not the same as checking that a server answers.
Clicky also has split testing, video and audio analytics for HTML5, YouTube and JW Player (Clicky’s media tracking), organization names for visitors, a big screen mode, and a white label from $49 a month for agencies that resell analytics under their own brand.
Heatmaps exist on both sides but record different things. Clicky’s heatmaps show clicks, filterable by goal, split test, location or visit, and sample 50% of page views by default. invisit’s heatmaps show clicks, rage clicks, dead clicks and scroll depth, are on every plan, and are never billed.
Does Clicky have funnels, revenue and Search Console?
Partly, partly and no. Clicky’s goals can require a funnel of pages before they count, and its path analysis shows the pages before and after any page. invisit builds funnels from pages or events, shows where each step dropped off, and splits them by source, country or device.
Revenue in Clicky is a value you send with a goal from your code, such as clicky.goal('New user', 49.95), and its long-term metrics tie goals back to the referrer and campaign of the first visit. invisit connects to Stripe, Paddle, Polar, Lemon Squeezy, Creem or Dodo Payments and reads payments, refunds, disputes, fees and net, with no code in your checkout. On paid plans, one id passed at checkout splits that revenue by source, campaign, landing page and short link.
For search, Clicky’s search rankings come from the position Google leaves in some referrers, averaged per phrase. invisit connects Google Search Console on every plan and shows queries with clicks, impressions, CTR and position, per site and page.
Both show visits from AI assistants such as ChatGPT in a source of their own, and both have an MCP server: Clicky’s is a plugin you download and run over its API, invisit’s is a remote MCP server. The rest has no Clicky counterpart: web vitals, error tracking, crawler reads (Clicky filters bots out and says AI bot tracking comes later in 2026), and a feedback widget.
When Clicky is the better choice
Clicky is the better choice when price per page view matters most, when you want uptime monitoring in the same account, or when you want visitors named in a live log.
Price is Clicky’s clearest win: $19.99 a month covers about 3M page views with every feature it sells, where invisit costs $99. Even its free plan covers about 90K page views a month, though for 1 site, without goals and with 30 days of history.
Uptime checks, split tests, video analytics and a white label for resellers have no invisit equivalent. Clicky’s sub-users get read-only or admin access per site, which suits an agency giving each client one site; invisit roles cover a whole workspace.
And if you run a site where people sign in and you want to see “bobjones” in Spy as he clicks around, Clicky does that and invisit, by design, does not.
Switching from Clicky to invisit
- Create a site in invisit and install the script or
@invisitdev/webnext to Clicky’s (installation, frameworks). Both can run on the same pages. - Map each
clicky.log()call totrack(). Clicky logs an event as a URL such as#newsletter; invisit names it, with letters, digits and_ . : -, so#newsletterbecomesnewsletter_signup. - Map goals to conversions. A dynamic goal such as
New userbecomesnew_user, and its revenue comes from a payment provider connection instead of your code. - Replace
clicky_custom.visitorwithidentify(user.id), passing an opaque id from your database. invisit keeps only its hash, and redacts email addresses sent in event properties. - Export your Clicky history. Reports export as CSV or XML, and Clicky’s API returns visitor and action lists 31 days and 1,000 items at a time; only the last 6 months of single visits are guaranteed to be there.
- Run both for two to four weeks, then remove Clicky’s script. Expect totals to differ a little: Clicky counts each session as a “visitor”, and each tool filters bots its own way.
| Clicky | invisit |
|---|---|
clicky.log('#signup', 'Signup') |
track('signup_completed') |
clicky.goal('New user', 49.95) |
tracker?.conversion('new_user'), revenue from your payment provider |
clicky_custom.visitor = {...} |
identify(user.id) |
clicky_custom.goal = {...} |
tracker?.conversion(...) on that page |
// Before: Clicky, loaded by <script async data-id="101234567" src="//static.getclicky.com/js"></script>
var clicky_custom = clicky_custom || {}
clicky_custom.visitor = { username: 'bobjones', email: 'bob@example.com' }
clicky.log('#newsletter', 'Newsletter signup')
clicky.goal('New user', 49.95) // a dynamic goal with revenue from your code
// After: invisit
import { identify, init, track } from '@invisitdev/web'
const tracker = init({ site: '<site id>' })
identify(user.id) // an opaque id from your database, hashed on arrival
track('newsletter_signup')
tracker?.conversion('new_user', { plan: 'pro' }) // the amount comes from your payment provider