[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 DataFast

> DataFast ties each payment to the visitor and channel that brought it, using a cookie and a visitor id passed into your checkout. invisit reads payments from your provider with no checkout code, sets no cookies, stores data in Germany, and costs less than DataFast Growth at every volume from 10K to 10M events.

- Page: https://invisit.dev/compare/datafast
- Facts about DataFast last verified: 2026-11-03, from [datafa.st](https://datafa.st)'s own pages
- Pricing: monthly billing, the cheapest plan step that covers each volume. invisit bills events (page views and custom events); DataFast bills pageviews, payments and goals you track.

## At a glance

- Price at 1M events a month: invisit $49, DataFast Starter $69, DataFast Growth $139, so invisit costs 65% less than DataFast Growth.
- Free plan: invisit, up to 20K events a month with no time limit. DataFast: No. Only a 14-day trial, no card.
- Only invisit, of the two: Data stored in the EU, Heatmaps, Web vitals, Short links, On-page feedback, Free plan.
- Where DataFast is ahead: You want revenue, MRR, LTV and churn split by channel, campaign and visitor, and can pass a visitor id into your checkout.

## Choose invisit if

- You want revenue from Stripe, Paddle, Polar, Lemon Squeezy, Creem or Dodo Payments beside traffic, with no code in your checkout.
- You want analytics without cookies by default, and data stored in Germany.
- You run several sites or work as a team: paid plans have unlimited sites, and team members come with every plan.
- You want a free plan, heatmaps, web vitals, short links or traffic alerts to Slack and Discord.
- You want your data kept forever, and crawler reads that are never billed.

## Choose DataFast if

- You want revenue, MRR, LTV and churn split by channel, campaign and visitor, and can pass a visitor id into your checkout.
- You sell through Shopify or WooCommerce, or want Meta Ads ROAS and Search Console keywords with revenue estimates.
- You want X and Reddit mentions on your chart, phone apps, weekly email reports, or a React Native SDK.
- You are leaving Plausible and want to bring your history with you.
- You run one site at 2M to 10M events a month, where DataFast Starter ($89 to $169) costs less.

## Pricing

| A month of | invisit | DataFast Starter | DataFast Growth |
| --- | --- | --- | --- |
| 10K | Free | $9 | $19 |
| 100K | $14 | $19 | $39 |
| 1M | $49 | $69 | $139 |
| 10M | $199 | $169 | $339 |

Source: [datafa.st](https://datafa.st/#pricing). Events are summed across all your sites. Over the limit, tracking continues but the dashboard locks until you upgrade. A year costs ten months' price. A 10M+ step costs $199 (Starter) or $399 (Growth).

## Features

### Privacy and setup

| Feature | invisit | DataFast |
| --- | --- | --- |
| No cookies, no consent banner needed | Yes. Daily-rotating hash | Partly. Default script sets a 1-year cookie; cookieless script is opt-in ([datafa.st](https://datafa.st/docs/gdpr-cookieless-tracking)) |
| Data stored in the EU | Yes. Falkenstein, Germany (Hetzner) | No. Mostly outside the EU, including the US ([datafa.st](https://datafa.st/dpa)) |
| Lightweight script (under 10 KB) | Yes. About 8.5 KB gzipped; extras load on demand | Yes. About 5 KB gzipped ([datafa.st](https://datafa.st/js/script.js)) |
| Serve from your own domain | Yes. @invisitdev/server proxy | Yes. Managed subdomain proxy, or guides for your own server ([datafa.st](https://datafa.st/docs/managed-proxy)) |
| Open source | Partly. Tracker and SDKs, MIT | No. No public source; npm SDK labelled MIT ([npmjs.com](https://www.npmjs.com/package/datafast)) |
| Import history from another tool | No | Yes. From Plausible ([datafa.st](https://datafa.st/docs/import-from-plausible)) |

### Analytics

| Feature | invisit | DataFast |
| --- | --- | --- |
| Realtime view | Yes | Yes. Live globe, plus a 30-minute Now view ([datafa.st](https://datafa.st/changelog/real-time-map)) |
| Custom events and goals | Yes | Yes. Goals with up to 10 parameters ([datafa.st](https://datafa.st/docs/custom-goals)) |
| Funnels | Yes | Yes. With revenue at each step ([datafa.st](https://datafa.st/docs/conversion-funnels)) |
| Per-visit timelines | Yes. Every visit step by step: live in the dashboard, any age through the API and MCP | Yes. Visitor journeys and profiles; not in cookieless mode ([datafa.st](https://datafa.st/changelog/goal-tracking)) |
| Retention cohorts | No | No. New vs returning visitors only ([datafa.st](https://datafa.st/changelog/new-returning-visitors)) |
| Heatmaps | Yes. Clicks, rage and dead clicks, scroll depth | No. Scroll goals, but no click or scroll maps ([datafa.st](https://datafa.st/changelog)) |
| Session recordings | No | No ([datafa.st](https://datafa.st/changelog)) |
| Web vitals | Yes. Never billed | No ([datafa.st](https://datafa.st/changelog)) |
| AI assistant referrals | Yes. ChatGPT, Claude, Perplexity, Gemini and more | Yes. AI channel: ChatGPT, Perplexity, Claude, Gemini, Copilot ([datafa.st](https://datafa.st/changelog/channel-filters)) |
| Crawler reads (search and AI bots) | Yes. Recorded server-side, never billed | Yes. Server-side package; 100K requests included, then $9 per 1M ([datafa.st](https://datafa.st/docs/bot-traffic-tracking)) |
| Revenue | Yes. Read from Stripe, Polar, Paddle, Dodo Payments, Creem and Lemon Squeezy | Yes. Provider connection; attribution via checkout metadata or redirect ([datafa.st](https://datafa.st/docs/revenue-attribution-guide)) |

### Beyond the dashboard

| Feature | invisit | DataFast |
| --- | --- | --- |
| Traffic alerts | Yes. Spikes, drops and silence, to Slack, Discord, ntfy or a webhook | Partly. Email alerts on goals and payments, plus an on/off traffic spike notice ([datafa.st](https://datafa.st/docs/api/account/websites/update)) |
| Email reports | No | Yes. Weekly email summary ([datafa.st](https://datafa.st/changelog/email-reports)) |
| Public dashboards | Yes | Yes. Public dashboard with the live globe, plus widgets ([datafa.st](https://datafa.st/changelog/public-dashboard)) |
| Short links | Yes | No ([datafa.st](https://datafa.st/changelog)) |
| On-page feedback | Yes | No ([datafa.st](https://datafa.st/changelog)) |
| API | Yes. REST, with an OpenAPI document | Yes. Read and write REST API, plus a CLI ([datafa.st](https://datafa.st/docs/api)) |
| MCP server for AI assistants | Yes | Yes. Official remote server, OAuth or token ([datafa.st](https://datafa.st/docs/mcp-introduction)) |

### Plans

| Feature | invisit | DataFast |
| --- | --- | --- |
| Free plan | Yes. 20K events a month, nearly every feature | No. Only a 14-day trial, no card ([datafa.st](https://datafa.st/#pricing)) |
| Free trial | Yes. 14 days | Yes. 14 days, no card ([datafa.st](https://datafa.st/#pricing)) |
| Sites | Yes. 4 free, unlimited on paid plans | Partly. 1 on Starter, 30 on Growth ([datafa.st](https://datafa.st/#pricing)) |
| Team members | Yes. Unlimited, on every plan | Partly. 1 on Starter, 30 on Growth ([datafa.st](https://datafa.st/#pricing)) |
| Data kept | Yes. Forever, on every plan | Yes. 3 years on Starter, 5+ years on Growth ([datafa.st](https://datafa.st/#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 DataFast cost at 100K, 1M and 10M events?

As of November 2026, DataFast's Starter plan costs $19 a month at 100K events, $69 at 1M and $169 at 10M. DataFast's Growth plan costs $39, $139 and $339. invisit costs $14, $49 and $199 at the same volumes, and is free up to 20K events a month.

DataFast has no free plan. Both products give you a 14-day trial without a card.

The two [DataFast plans](https://datafa.st/#pricing) meter the same events but set different limits. Starter allows one website, one team member and three years of data. Growth allows 30 websites, 30 team members and five or more years, and adds X and Reddit mentions and X link attribution. Every invisit paid plan has every feature, unlimited sites and data kept forever, so the like-for-like comparison is with Growth, and invisit costs less than Growth at every volume.

Against Starter the picture is closer. Between the steps in the price table above:

| Events a month | DataFast Starter | DataFast Growth | invisit         |
| -------------- | ---------------- | --------------- | --------------- |
| 250K           | $49 (500K step)  | $99             | $24             |
| 500K           | $49              | $99             | $49 (1M step)   |
| 2M             | $89              | $179            | $99 (3M step)   |
| 5M             | $129             | $259            | $199 (10M step) |

A SaaS with 300K page views a month pays $49 on DataFast Starter's 500K step and $49 on invisit's 1M step. Add a second website and Starter no longer fits: DataFast Growth at 500K costs $99.

DataFast counts pageviews, goals and payments as events, summed across all your sites. invisit bills page views, custom events, conversions and short-link clicks, and never bills bots, crawler reads, web vitals or feedback.

Going over the limit works differently. [DataFast's terms](https://datafa.st/tos) say it keeps recording, emails you at 75%, and locks the dashboard at 100% until you move to a plan that covers the month's usage. invisit warns at 80%, records the whole first month over, and pauses new events only in a second month over in a row. Yearly billing costs ten months' price on DataFast and nine on invisit.

## How does DataFast attribute revenue to traffic sources?

DataFast ties each payment to the visitor who made it, so it can split revenue, MRR, LTV and churn by channel, campaign, page and country. invisit reads payments, refunds, disputes, fees and net from your payment provider and charts them beside your traffic, with no code in the checkout.

Connecting Stripe, Lemon Squeezy, Polar, Paddle, Shopify or WooCommerce puts revenue on DataFast's charts. Attribution is a second step, which [DataFast's guide](https://datafa.st/docs/revenue-attribution-guide) sets up per checkout type:

| Your checkout                                                   | What DataFast needs                                                                     |
| --------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| Stripe, Polar, Lemon Squeezy or Paddle checkout                 | The `datafast_visitor_id` and `datafast_session_id` cookies passed as checkout metadata |
| Stripe payment links, Polar checkout links, Lemon Squeezy links | A success URL back to your site carrying the session, checkout or order id              |
| Any flow where you know the buyer's email                       | `window.datafast('payment', { email })` on the success page                             |
| Shopify or WooCommerce                                          | The store integration, nothing more                                                     |
| Dodo Payments or a custom provider                              | The visitor id in metadata, plus a webhook or a call to DataFast's Payment API          |

Once that works, DataFast builds on it. Funnels show revenue at each step, Google Search Console keywords get revenue estimates, Meta Ads campaigns get ROAS, and a revenue prediction scores live visitors once a site has 1,000 visitors and 10 attributed payments.

invisit connects Stripe, Paddle, Polar, Lemon Squeezy, Creem or Dodo Payments from [its revenue settings](https://invisit.dev/docs/guides/revenue.md#connect-a-provider). Every plan shows revenue totals and charts beside traffic, and paid plans list each charge. If the question you need answered is which channel produced each sale, DataFast is built for it. If you want revenue next to traffic with nothing to wire into checkout, invisit does that.

## Does DataFast need a cookie banner?

DataFast's default script sets first-party cookies, and DataFast's own [GDPR guide](https://datafa.st/docs/gdpr-cookieless-tracking) says you may need a cookie banner for it, depending on law and setup. invisit sets no cookies and stores no device identifiers, so its analytics need no consent banner by default.

The current `script.js` sets `datafast_visitor_id` for a year on your root domain, with first-seen and session-count cookies of the same length and a 30-minute `datafast_session_id`. That year-long id is what lets DataFast join a visit in March to a purchase in June. [DataFast's terms](https://datafa.st/tos), which predate its cookieless option, ask customers to show a consent banner before the script collects data.

Since April 2026 DataFast also offers `script.cookieless.js`, which identifies visitors with a hash of IP address, user agent and domain whose salt rotates about every 24 hours. DataFast states the costs plainly: returning-visitor reports and the User and Journey tabs become unavailable or less reliable, identify does not apply the same way, and revenue attribution over weeks or months is less complete. Its [announcement](https://datafa.st/changelog/cookieless-tracking-script) advises keeping the default script if attribution is central to your business.

invisit's only mode is close to that design. A hash that rotates daily tells visitors apart, raw IP addresses are never stored, and Global Privacy Control and Do Not Track can be honoured with [`respectGpc` and `respectDnt`](https://invisit.dev/docs/guides/privacy.md). An optional [consent mode](https://invisit.dev/docs/guides/privacy.md#requiring-consent) covers policies that want consent anyway. DataFast's docs do not mention Global Privacy Control or Do Not Track.

## Where does DataFast store analytics data?

DataFast's [data processing agreement](https://datafa.st/dpa) says most of its infrastructure is outside the EU, including in the United States. It names AWS, Vercel, Mapbox, OpenAI, MongoDB, Upstash, Tinybird and ClickHouse as subprocessors. invisit stores analytics data in Falkenstein, Germany, on Hetzner, with Cloudflare (a US company) in front for DNS and CDN.

For EU visitors' data, DataFast relies on its subprocessors' compliance, including Standard Contractual Clauses where relevant. The agreement is with JustShipIt Pte. Ltd. and governed by Singapore law. invisit's [DPA](/legal/dpa) is published on its site.

## Does DataFast track AI crawlers and ChatGPT referrals?

Yes, and so does invisit. DataFast groups visits from ChatGPT, Perplexity, Claude, Gemini and Copilot into an AI channel, and records crawler requests with a server-side package. invisit puts ChatGPT, Claude, Perplexity, Gemini, Copilot and seven more assistants in [their own AI tab](/blog/ai-assistant-traffic), and records crawler reads with [`@invisitdev/server`](https://invisit.dev/docs/server/sdk.md#crawler-reads).

The difference is billing. [DataFast's bot traffic](https://datafa.st/docs/bot-traffic-tracking) includes 100,000 accepted requests per account each billing cycle, then $9 a month per extra million. Reaching the allowance pauses bot ingestion, not web analytics. invisit never bills crawler reads. DataFast's crawler report also checks requests against published crawler IP ranges and lists reads of `robots.txt`, `llms.txt` and sitemaps.

## Where DataFast is the better choice

DataFast is the better pick when revenue by source is the point. Revenue per visitor, MRR, LTV and churn by channel, revenue at each funnel step, and a live score of who is likely to buy all come from tying payments to visitors. invisit's revenue view charts totals, fees and net beside traffic instead.

DataFast also reaches further outside the website. Shopify and WooCommerce stores connect directly. Meta Ads spend turns into ROAS. Google Search Console keywords appear with revenue estimates, an integration invisit does not have. Growth adds X and Reddit mentions on the chart and the exact X posts that sent buyers, and GitHub commits can sit beside traffic too.

There are smaller wins. DataFast imports Plausible history, which invisit cannot do. It has iOS and Android apps for reading the dashboard, a React Native SDK for tracking apps (invisit is web analytics only), weekly email reports, and a CLI for agents. Its `script.js` is about 5.3 KB gzipped against invisit's 8.5 KB. And for a single site at 2M to 10M events a month, DataFast Starter costs less than invisit.

## Switching from DataFast to invisit

Run invisit next to DataFast for two to four weeks, then cancel DataFast once the numbers line up. Expect visitor counts over multi-day ranges to differ: DataFast's cookie recognises a returning browser for a year, and invisit's hash rotates every day.

1. Export what you want to keep. DataFast's DPA says data is available through its API and that it does not provide archive exports or raw event logs, so pull aggregates with the [DataFast API](https://datafa.st/docs/api) or its CLI, for example `datafast --json analytics timeseries --fields visitors,revenue --interval day --from 2024-01-01`. After you cancel, DataFast tracks for 30 more days and then deletes the data. invisit cannot import this history.
2. [Install invisit](https://invisit.dev/docs/web/installation.md) next to the DataFast script. Both can run on the same pages.
3. Replace each `window.datafast('goal_name', {...})` call with `track()`. DataFast goal names (lowercase letters, digits, `_`, `-` and `:`) are already valid invisit names, and invisit takes up to 32 properties where DataFast stops at 10. invisit redacts email addresses in property values, so drop `email` parameters. Replace `data-fast-goal` attributes with `data-invisit-event`, and their parameters with `data-invisit-prop-*` attributes.
4. Swap `window.datafast('identify', ...)` for [`identify(user.id)`](https://invisit.dev/docs/guides/events.md#identify-signed-in-users).
5. [Connect your payment provider](https://invisit.dev/docs/guides/revenue.md#connect-a-provider). Keep the `datafast_visitor_id` metadata and `payment` calls until DataFast is switched off, then remove them.
6. If you proxied DataFast or used `@datafast/ai-crawl`, `@invisitdev/server` covers both with its [proxy](https://invisit.dev/docs/server/sdk.md#proxy) and [crawler reads](https://invisit.dev/docs/server/sdk.md#crawler-reads).

```ts title="src/analytics.ts"
// DataFast
window.datafast('initiate_checkout', { plan: 'pro' })
window.datafast('identify', { user_id: user.id, name: user.name })
window.datafast('payment', { email: user.email })

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

init({ site: '<site id>' })
track('initiate_checkout', { plan: 'pro' })
identify(user.id)
// Payments: connect your provider in invisit, no call needed
```

## Common questions

### Is invisit cheaper than DataFast?

At 1M events a month invisit costs $49 a month, and DataFast Starter costs $69 a month and DataFast Growth costs $139 a month, so invisit costs 65% less than DataFast Growth. invisit bills page views and custom events; DataFast bills pageviews, payments and goals you track. Prices checked against DataFast's pricing page on November 3, 2026.

### Does DataFast have a free plan?

No, DataFast has no free plan: only a 14-day trial, 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 DataFast does not?

invisit includes data stored in the EU, heatmaps, web vitals, short links, on-page feedback, and free plan; DataFast does not, as of November 3, 2026.

### When should I choose DataFast over invisit?

DataFast suits you better than invisit when one of these is true. You want revenue, MRR, LTV and churn split by channel, campaign and visitor, and can pass a visitor id into your checkout. You sell through Shopify or WooCommerce, or want Meta Ads ROAS and Search Console keywords with revenue estimates. You want X and Reddit mentions on your chart, phone apps, weekly email reports, or a React Native SDK. You are leaving Plausible and want to bring your history with you. You run one site at 2M to 10M events a month, where DataFast Starter ($89 to $169) costs less.

### When should I choose invisit over DataFast?

invisit suits you better than DataFast when one of these is true. You want revenue from Stripe, Paddle, Polar, Lemon Squeezy, Creem or Dodo Payments beside traffic, with no code in your checkout. You want analytics without cookies by default, and data stored in Germany. You run several sites or work as a team: paid plans have unlimited sites, and team members come with every plan. You want a free plan, heatmaps, web vitals, short links or traffic alerts to Slack and Discord. You want your data kept forever, and crawler reads that are never billed.

### Does DataFast use cookies?

Yes, by default. As of November 2026, DataFast's standard script.js sets a first-party datafast_visitor_id cookie that lasts a year, plus a 30-minute session cookie, and DataFast's GDPR guide says you may need a cookie banner for it. An optional cookieless script uses a hash that rotates about every 24 hours instead, with less complete revenue attribution. invisit sets no cookies and tells visitors apart with a hash that rotates daily.

### Is DataFast GDPR compliant?

DataFast says it is built so you can use it in line with GDPR and publishes a DPA. As of November 2026 that DPA states most of DataFast's infrastructure is outside the EU, including the United States, relies on Standard Contractual Clauses where relevant, and is governed by Singapore law. Its default script may need a cookie banner. invisit stores analytics data in Falkenstein, Germany, sets no cookies, and has a DPA at invisit.dev/legal/dpa.

### How does DataFast attribute revenue to traffic sources?

DataFast connects to Stripe, Lemon Squeezy, Polar, Paddle, Shopify or WooCommerce, then matches each payment to a visitor. With a checkout API you pass the datafast_visitor_id and datafast_session_id cookies as checkout metadata; with payment links the success URL carries the session or checkout id; otherwise you call window.datafast('payment', { email }). invisit reads payments, refunds and fees from the provider with no checkout code and charts them beside traffic.

### What happens if I go over my DataFast event limit?

As of November 2026, DataFast emails you at 75% of your plan, keeps recording every event past 100%, and locks the dashboard until you upgrade to a plan that covers that month's usage. A 'Pause tracking at limit' setting drops new events instead. invisit warns at 80%, records the whole first month over, and pauses new events only in a second month over in a row.

### Can I export my data from DataFast?

Through its API and CLI. DataFast's DPA says personal data is available via the API and that DataFast does not provide consolidated archive exports or raw event logs, so you export aggregates such as daily visitors and revenue. DataFast's terms say tracking continues for 30 days after you cancel and the data is then deleted, so export first. invisit cannot import that history.

### Does DataFast track AI crawlers?

Yes. Since July 2026 DataFast records AI assistant, search and training crawler requests through a server-side package, @datafast/ai-crawl. As of November 2026 each account includes 100,000 accepted requests per billing cycle, and more costs $9 a month per million. invisit records search and AI crawler reads server-side with @invisitdev/server and never bills them.

## Sources

Read on 2026-11-03. Corrections: help@invisit.dev

- https://datafa.st/#pricing
- https://datafa.st/docs/gdpr-cookieless-tracking
- https://datafa.st/dpa
- https://datafa.st/js/script.js
- https://datafa.st/docs/managed-proxy
- https://www.npmjs.com/package/datafast
- https://datafa.st/docs/import-from-plausible
- https://datafa.st/changelog/real-time-map
- https://datafa.st/docs/custom-goals
- https://datafa.st/docs/conversion-funnels
- https://datafa.st/changelog/goal-tracking
- https://datafa.st/changelog/new-returning-visitors
- https://datafa.st/changelog
- https://datafa.st/changelog/channel-filters
- https://datafa.st/docs/bot-traffic-tracking
- https://datafa.st/docs/revenue-attribution-guide
- https://datafa.st/docs/api/account/websites/update
- https://datafa.st/changelog/email-reports
- https://datafa.st/changelog/public-dashboard
- https://datafa.st/docs/api
- https://datafa.st/docs/mcp-introduction