Skip to main content

General

Profile Analytics

What is counted, what is excluded, and how it stays private

Read
3 min read
Sections
5
Article
12 of 45

What you get

Dashboard → Analytics, filtered by Today, 7 days, 30 days or 90 days. Analytics events are kept for 90 days, so no range reaches further back than that: your public view counter is separate and does count for the lifetime of the profile. Overview shows the last seven days of views and link clicks, with Open analytics for the rest.

  • Views, and Visitors: a person counts once per day, so someone who visits on three days counts three times
  • Link clicks and Click rate
  • A trend chart you can switch between views, link clicks and click rate
  • Top links, with each link's own clicks, unique clicks and click rate
  • Plays, for the links that play in your page
  • Traffic sources: Instagram, TikTok, X, Google, direct, and named referring domains
  • Devices, split into phone, tablet and computer
  • Countries, and Referring sites
  • Campaigns, grouped by the UTM tags on the links you shared
  • A comparison against the previous period, so a number arrives with a direction

Analytics is free. There is no paid tier of it.

What counts as an event

Three things: a profile view, a link click, and a play. A visitor's views of a page count once a day, and a repeat click on the same link within 10 minutes counts once, so a refresh does not inflate your numbers. People on the same internet connection count as one visitor that day. A visitor who opens many different pages within a few seconds is treated as a bot and not counted. A link that plays in the page (YouTube, Spotify, Apple Music or Twitch) records no clicks, because nobody leaves your page to use it. Instead, the first time a visitor presses its player counts as a play, once per visitor every 30 minutes, and Analytics shows plays on their own, so they never change your click rate. What happens inside another company's player cannot be seen from your page.

What is excluded

  • Bots and social-preview crawlers: about fifty user-agent patterns, from Googlebot to Discord's link unfurler to headless Chrome
  • Your own views, unless you turn on My own views at the top of Analytics. When you sign in, your dashboard leaves a note signed by our server in that browser, and our server checks the signature with each view, so a browser cannot simply claim to be you
  • Your live preview in the dashboard, which is never counted at all
  • Duplicates inside a rolling window, and events from a visitor firing far too many too fast

Whenever anything was excluded, a line above Top links says how many events were left out and how many of each kind: duplicate refreshes, bots and previews, and the rest. The point is that your figures are the ones you can act on, not the biggest ones we could show you.

How it stays private

Measurement is server-side and cookieless. Nothing is written to your visitor's device, no cookie, no local storage entry, no identifier.

  • IP addresses are never stored. A visitor is identified by a SHA-256 hash of their IP, user-agent, the profile, today's date and a secret salt, which cannot be reversed, and which changes every day, so it cannot follow anyone across days either
  • The user-agent itself is stored only as a hash; what we keep in readable form is the coarse device type, browser and OS
  • Country and region come from the network edge, not from a lookup service
  • You see totals and trends. There is no per-visitor view, and no way to build one

How a visitor opts out

The privacy notice has Turn off measurement, or Settings with a Measurement switch. Either one stops measurement for that browser immediately, on every noiz.bio page including creator profiles. Privacy choices in the site footer reopens it at any time.

Measurement is opt-out rather than opt-in, and the privacy policy says so in the same words: it stores nothing on the device, hashes the IP before writing it and only ever produces aggregates, so it runs on legitimate interest.

Was this article helpful?

I need more help

Still stuck?

Support reads every message.