Shed more
light on your
traffic.

No. Lumastat sets no cookies and collects no personally identifiable information, so there is no legal trigger for a GDPR or ePrivacy consent banner. You get full behavioural analytics on your pages with zero consent overhead.

Yes — by structural design, not by configuration. Lumastat never stores personal data. IP addresses are hashed daily and cannot be reversed. Sessions are not linked across days, devices, or pages in any way that constitutes personal data processing under GDPR Article 4. Infrastructure runs inside the EEA. No Data Processing Agreement is required.

Lumastat collects page-level behavioural signals: scroll depth, click coordinates, active time on page, navigation path within a session, UTM parameters from the URL, and device category (desktop / mobile / tablet). It does not collect names, email addresses, raw IP addresses, device fingerprints, or any data that could identify a specific person.

Instead of setting a cookie to follow a user across visits, Lumastat analyses each page visit independently. Behavioural signals — scroll depth, click positions, active engagement time — are aggregated server-side and attached to the page URL rather than to any individual. Every metric is page-scoped, not person-scoped.

For page-level insights — heatmaps, scroll depth, exit patterns, funnel drop-offs — cookieless analytics is highly accurate and often more complete than cookie-based tools, because it is not skewed by visitors who declined the consent banner. The trade-off is that individual user journeys across multiple sessions cannot be traced. For landing pages and content sites this is rarely a limitation.

Frustration signals are behavioural patterns that indicate a visitor encountered something broken, confusing, or misleading. Rage clicks are rapid repeated clicks on an element that does not respond. Dead clicks are clicks on non-interactive elements that visually imply they are clickable. Both are automatically detected by Lumastat and highlight UI problems that raw visitor counts would never surface.

Scroll depth measures how far down a page a visitor scrolled before leaving, expressed as a percentage of total page height. When correlated with exit rate, it tells you whether visitors leave because they never found the information they were looking for (low scroll depth) or because nothing on the page convinced them after reading it (high scroll depth, high exit). The two causes require completely different fixes.

A heatmap overlays a screenshot of your page with colour-coded zones showing where visitors clicked, moved, or tapped — warmer colours indicate higher activity. Heatmaps make it immediately visible which sections attract attention, which calls-to-action receive clicks, and which content is completely ignored. Lumastat generates heatmaps from aggregated click coordinates, without cookies and without a consent banner.

Session funnels show the sequence of pages visited within a single browsing window and reveal where visitors exit the site. For multi-step flows — product page → cart → checkout — funnels pinpoint the exact step causing the most drop-off, so you know where to focus optimisation effort instead of guessing.

UTM parameters are tags appended to URLs in marketing campaigns (e.g. ?utm_source=newsletter&utm_medium=email). Lumastat reads these from the URL on arrival and associates the session's behavioural data — scroll depth, clicks, engagement time, exit point — with that specific campaign source. You can see which channels send visitors who genuinely engage versus those who bounce within seconds.

Yes. A server-side module analyses request patterns, timing, and behavioural signals to separate human visits from automated traffic — search engine crawlers, scraper bots, AI training agents, and uptime monitors. Bot visits are excluded from all analytics metrics by default, so heatmaps and engagement numbers reflect genuine human behaviour only.

Lumastat is designed to be adblocker-resistant because all data collection happens server-side. There is no third-party tracking script loaded from an external domain that ad blockers routinely intercept. The result is a more complete picture of visitor behaviour than tools that depend on client-side JavaScript which can be silently blocked.

Google Analytics (GA4) tracks individuals across sessions using cookies and device IDs, requires a GDPR consent banner, routes data through Google's US-based advertising infrastructure, and is designed for audience segmentation and attribution modelling. Lumastat tracks behaviour per page without cookies, stores no personal data, keeps data inside the EEA, and is focused on answering why visitors leave a specific page rather than who they are.

Hotjar collects session recordings and heatmaps using cookies and requires user consent under GDPR and ePrivacy. It is a powerful UX research tool aimed at product and design teams. Lumastat covers similar visual analytics — heatmaps, scroll depth, click patterns — without cookies or a consent banner, and adds UTM attribution, bot filtering, and frustration signals. It is oriented towards marketers and website owners who need conversion insight without a compliance layer.

Lumastat is built for pages where a single visit determines whether a visitor converts: product pages, sales landing pages, blog posts, e-commerce category and product detail pages, and marketing microsites. It is not designed for tracking authenticated user workflows inside SaaS dashboards or complex web applications, where a different class of analytics tool is more appropriate.

All data is processed and stored on infrastructure hosted within the European Economic Area (EEA). Data never leaves EU jurisdiction, which means Lumastat's data handling complies with GDPR Chapter V requirements on international transfers by default — without needing Standard Contractual Clauses or other transfer mechanisms.