Cookieless mode

Use cookieless mode when you want analytics without storing anything on your visitors' devices: no cookies, no local storage, no session storage.

Switch to the cookieless script

1. Copy the cookieless snippet

   Open Website settings › Tracking. The Cookieless mode card has the snippet with your website ID:

   HTMLCopy

   <script defer data-website-id="YOUR_SITE_ID" src="https://revfaro.com/js/script.cookieless.js"></script>

2. Replace the standard script

   Put it where the standard script.js tag was, in the <head> of every page. Use one of the two scripts on a page, never both.

3. Keep your goals and identify calls

   data-rf-goal attributes, window.revfaro('goal', …) and window.revfaro('identify', …) work exactly the same. Nothing else changes in your code.

Use the cookieless npm entry

For an npm installation, import init from revfaro/cookieless instead of revfaro. Your goal and identify methods stay the same. Use one tracking mode per page and remove an existing hosted script when switching to npm.

How does Revfaro count visitors without cookies?

For each event, Revfaro computes a hash of your website ID, the visitor's IP address and their browser (user agent), using a random key that is replaced every day (UTC) and then deleted. The same person on the same day produces the same hash, so their pages and visits belong together. The IP address and user agent are not stored, and the same person can't be linked across days or across your websites.

What still works

• Visitors, page views, visits (30 minutes without activity end a visit), sources, campaigns and locations
• Goals, funnels, outbound links and the live view
• Identified users with identify
• Revenue matched on the same day by the return page (?session_id=, ?payment_id=, ?checkout_id=, ?order_identifier=), an identified email or checkout timing

What to keep in mind

• Returning visitors aren't recognized. Someone who comes back on another day counts as a new visitor, so there are no returning-visitor numbers.
• Revenue is credited to the same day only. A tweet clicked on Monday doesn't get credit for a purchase on Wednesday.
• Shared connections can merge. People on the same IP address with the same browser version, such as an office network, can count as one visitor that day.
• No visitor ID for your checkout. Checkout links aren't tagged, window.revfaro.attribution() returns an empty object, and your server can't send a visitor ID to the Payments API or the Goals API. Set up the return page of your payment provider (step 3 of each provider guide) and call identify so payments still find their visitor.

Site on a shared host?

Without cookies, the script guesses your root domain from the page's address (example.com for blog.example.com), to tell your own links from outbound clicks. On a shared host such as name.vercel.app or name.netlify.app that guess is too wide, so tell the script your domain:

<script defer data-website-id="YOUR_SITE_ID" data-domain="name.vercel.app" src="https://revfaro.com/js/script.cookieless.js"></script>

Serve it from your own domain

To get past ad blockers, point a rewrite at /js/script.cookieless.js; the card's Serving the script from your own domain section has the code. Your proxy must pass on the visitor's IP address, which cookieless mode relies on; see how the proxy works.