Track visitor analytics

How Quackback counts portal and widget visitors without cookies, what the Visitors dashboard shows, and how visitor privacy is protected.

JM
James Morton
Written By James MortonLast updated about 2 hours ago

Visitor analytics shows how many people look at your portal and widget, not only how many sign up. It counts pageviews without cookies, third-party trackers, or stored personal data, and it's always on. This article explains what's counted, how, and how visitor privacy is protected.

Where to see it

Open Analytics from the admin sidebar and choose Visitors. You'll see:

  • Visitors, pageviews, and visits for the selected period, with the change from the previous period
  • a daily chart of the metric you select
  • Top pages, Sources, Countries, Devices, Browsers, and Operating systems

Use the filter menu to show All surfaces, Portal only, or Widget only, and the period picker to choose 7, 30, or 90 days, or 12 months.

How tracking works

Pageviews are recorded on your portal and, once the widget is installed, on the pages of your own site or app. In single-page apps, client-side route changes count as pageviews too. Repeat views of the same URL in a row are counted once.

No cookie is set. A visitor is counted using a hash of a daily random value, the site origin, the IP address, and the browser's user agent. The daily value rotates every day and is discarded after 48 hours. Raw IP addresses and user agents are never stored.

This means a "visitor" is roughly one person on one day. It can't be used to follow someone across days or devices.

Repeat visitors in the widget

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. The value is random and isn't derived from the visitor's identity. If the visitor later starts a conversation, Quackback links that device to them, which lets workflows react to the pages they visit. If storage is blocked (private browsing or browser settings), the widget falls back to the daily count.

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

Privacy

  • Opt-out signals are respected. If a visitor's browser sends Do Not Track or Global Privacy Control, the widget sends no pageview at all.
  • First party only. Pageviews go straight to your own Quackback workspace, never to a third-party analytics vendor.

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

Was this helpful?

Your feedback shapes what we write next.