Website analytics is an opt-in module that records anonymous traffic from your foundry site – pageviews, unique visitors, traffic sources, and country-level geography. Enable it under Settings → Analytics.
The admin surface lives at Admin → Analytics. Date range and grouping work the same as on the Dashboard.
How the figures are calculated
A pageview counts every page event from a visitor’s browser, with no deduplication across rapid reloads.
A unique visitor counts distinct anonymous IDs in the range. Once a visitor has accepted cookies their ID is stored in the _fontdue_state cookie and stays the same across pages and return visits. On a site that requires consent, a visitor who hasn’t accepted gets a fresh ID for each page load that is never stored anywhere, so their traffic does reach the unique visitor count – as a brand new visitor every load.11For the portion of traffic that hasn’t accepted, Unique visitors therefore tracks page loads rather than people. Pageviews from client-side route changes within one page load carry no ID at all, so they raise Pageviews without raising Unique visitors.
Webfont requests
The Webfonts section reports how often your hosted webfonts are loaded by the sites that embed them. Unlike the visitor figures above, this data is collected at the edge each time a font file is served, so it’s always available – you don’t need to enable tracking, and it isn’t affected by cookie consent.22Because the counts come from font-file requests rather than a browser script, they cover traffic that website analytics can’t see, such as cached pageviews that still fetch a font.
The summary cards show the total Font requests in the range, the number of Unique domains those requests came from, and the Top family by request volume. A Total font requests chart breaks the same total down over time, and a Top font families table ranks each family by requests alongside how many distinct domains loaded it.
Cookies
Fontdue sets up to two cookies on your site:
_fontdue_state– a signed cookie storing the visitor’s anonymous ID plus any UTM and referrer data captured on first visit. One-year lifetime. Set only when analytics tracking is allowed._fontdue_cc– the consent cookie, written by the consent banner when the visitor chooses Accept all or Necessary only. Stores a comma-separated list of consent categories. One-year lifetime.
If your site doesn’t require cookie consent, _fontdue_state is set on first visit and every pageview is linked. If you do require consent, tracking runs cookieless – pageviews are still recorded, under a throwaway ID that lasts no longer than the page load – until the visitor accepts, at which point _fontdue_state is set and subsequent views are linked to one identity. To enable the consent banner, see Cookie consent. A site can also stay in that cookieless state permanently, with no banner – see Running analytics with no cookies at all.
What’s not tracked
Fontdue’s analytics are deliberately lightweight: no event tracking (clicks, scroll depth, etc.), no session recording, and no identity resolution beyond the anonymous ID. If you need heavier analytics, add a third-party service alongside Fontdue’s – see Gate third-party scripts on consent for how to wire them into the consent banner.