6 solution docs
DataFast solution docs
Web analytics that tells you which channel made money, not just which one made visits.
Pick DataFast and all 6 land in docs/solutions/datafast/, next to the rules and skills that reference them.
Every DataFast doc in the registry
Tags: ad-blockers · after · analytics · api · checkout · consent · cookies · datafast · debugging · development · dodo-payments · gdpr · goals · lemon-squeezy · localhost · naming · nextjs · pageviews · polar · privacy · revenue-attribution · reverse-proxy · route-handlers · server-side · serverless · stripe
Cookie consent for DataFast in Next.js without breaking attribution
DataFast sets a year-long first-party cookie, which needs opt-in consent in the EU and UK. Gate the script render, the goal queue and the checkout metadata on one flag.
datafast · consent · gdpr · cookies
DataFast shows nothing on localhost? That is on purpose. How to debug it anyway
The script skips localhost, 127.0.0.1, .local hosts, iframes and browsers flagged with datafast_ignore. Turn on data-allow-localhost for a session, check the network tab, then turn it off.
datafast · debugging · localhost · nextjs
DataFast goals versus page views, and when you need neither
Page views are free and automatic. Goals cost events and need a name, a reason and a side of the network. A decision table, the naming rule, and what never to put in a goal.
datafast · analytics · goals · pageviews
Proxy DataFast through your Next.js domain so ad blockers stop eating visits
Blockers match the datafa.st hostname. Serve the script and the events endpoint from your own origin with two route handlers, and forward the visitor's IP.
datafast · analytics · ad-blockers · reverse-proxy
DataFast shows revenue as direct traffic? Pass the visitor id into checkout metadata
DataFast attributes a payment by reading datafast_visitor_id from the checkout's metadata. Read the cookie on the server when you create the Stripe, Polar, Lemon Squeezy or Dodo checkout.
datafast · revenue-attribution · stripe · polar
Server-side DataFast goals from Next.js, and why the Goals API returns 404
Send goals from route handlers and server actions with POST /api/v1/goals, after the response. The visitor id comes from the request cookie, and it must already have a page view.
datafast · goals · server-side · api