
How-to · Published October 21, 2026
How to set up events and revenue tracking in DataFast
Practical DataFast setup for web analytics goals and payment-linked revenue attribution — including cookieless mode trade-offs for indie SaaS.
Updated
Quick answer
Quick answer
DataFast covers lightweight web analytics plus optional payment attribution (e.g. Stripe). Set up the site script first, define goals/funnels you need, then connect payments and pass visitor/session ids into checkout metadata so revenue ties back to channels.
Install the script first
Add DataFast via snippet, npm, or the CMS path that matches your stack. Confirm pageviews and referrers before you chase revenue joins.
Choose default vs cookieless deliberately — cookieless can ease consent friction but changes identity. We recorded both installs: default and cookieless.
Goals and funnels
Define goals for the marketing actions that matter (pricing click, signup). Keep the list short. DataFast is closer to web analytics than full product analytics — see DataFast vs PostHog if you need deep in-app events.
Connect revenue attribution
For Stripe-style flows: connect the provider, then pass DataFast visitor/session identifiers into checkout or payment metadata so paid conversions inherit channel and referrer context.
QA with a test payment and confirm the sale appears with traffic source attached. Missing metadata is the usual failure mode.
When DataFast is the wrong event tool
If your primary need is feature flags, session replay, or complex product funnels, instrument PostHog (or similar) in the app and keep DataFast for marketing + revenue questions — or pick one stack consciously.
Compare cost and fit with Plausible vs DataFast and the pricing calculator.