Skip to content

Track visitor analytics

Know how many people are looking at your portal and widget, not only who signs up. Visitor analytics tracks pageviews without cookies or stored personal data. It is always on.

Overview

A Visitors section appears in Analytics (Admin → Analytics), alongside Overview, Feedback, Changelog, and Users, showing pageview volume and visitor trends over time.

How tracking works

The widget's pageview beacon fires on load and on every in-app navigation, including client-side route changes in single-page apps. Repeat views of the same URL in a row are deduplicated.

No cookie is set. The daily visitor count is computed server-side as a hash of the day's salt, your site's origin, IP address, and user agent. That hash rotates automatically every day and expires from cache after 48 hours. Raw IP addresses and user agents are never stored.

This means a "visitor" in the dashboard represents a rough daily session, not a person you can track across days or devices.

Repeat visitors

To recognize the same visitor across days, the widget stores a random device ID in your site's localStorage under the key quackback:device-id. It is a random value, not derived from the visitor's identity. When a visitor later starts a conversation, Quackback links the device to them, which powers page-visit workflow triggers. If storage is blocked (private browsing, browser settings), the widget falls back to the cookieless daily count.

If your site's consent policy covers localStorage, list this key alongside your other first-party storage.

Privacy

Visitor tracking respects both major browser opt-out signals. If a visitor's browser sends Do Not Track or Global Privacy Control, Quackback skips the beacon entirely rather than tracking a stripped-down version. Tracking is also first-party only - the beacon posts directly to your own Quackback instance, never to a third-party analytics vendor.

See Manage privacy and data handling for how Quackback handles data across the whole product.

Next steps