Visitor analytics
What Floot's built-in tracker records, where to see it, and how it handles cookie consent.
Every published Floot app counts its visitors with Floot's built-in tracker. There is nothing to set up, and it sets no cookies.
What it records
For each page view: the path, the referrer, the browser's user agent and language, and a country worked out from the visitor's time zone — never the query string, the part after #, or the IP address — plus a random session id that lasts 30 minutes. Your app can record events of its own too; ask your assistant for them.
Where to see it
Open your project on floot.com and go to Services → Analytics for page views, traffic sources, countries, devices, and trends. The analytics dashboard requires a paid plan.
Cookies and consent
The tracker never sets a cookie. By default it keeps the session id in the browser's local storage, which EU and UK privacy rules treat like a cookie, so visitors there have to agree before it is stored. There are three modes. Ask your assistant to switch, and the change takes effect on your next publish:
| Mode | What it does | Consent banner needed |
|---|---|---|
| storage (default) | Keeps the session id in local storage | Yes, for visitors in the EU and UK |
| memory | Keeps the session id in memory only, so nothing is stored on the device. A reload counts as a new session | No |
| off | Sends nothing | No |
You can also keep storage and add a consent banner: ask your assistant for one that covers Floot analytics. The banner tells the tracker what the visitor chose, nothing is stored until they accept, and their choice is remembered on later visits. Analytics you add yourself, such as Google Analytics, need their own consent handling.
How long it is kept
Raw page-view events are kept for 12 months. The totals built from them are kept after that.