Docs

How to add fivebar to a site, what it counts, and how to read what it counted.

Installing

Getting started Add a site to fivebar, put its script tag in the head of every page, and check that visits are being counted.
- Installation checker
Coding assistants Instructions for an AI coding assistant, such as Claude Code, Cursor or Copilot, to add fivebar to a site: the tag, where it goes, the attributes and events worth adding, and how to check it works.
Platforms Where the fivebar tag goes on WordPress, Shopify, Webflow, Squarespace, Wix, Next.js, Astro, Vite, Nuxt, SvelteKit, Hugo and other static site generators, and in Google Tag Manager, Adobe, Tealium, Matomo, Piwik PRO, Cloudflare Zaraz and other tag managers.
Proxying Serve the fivebar script and send its counts from your own domain, through Cloudflare, Vercel, Netlify, CloudFront, nginx or Caddy, so content blockers that know fiveb.ar let it through.
Script attributes Every attribute the fivebar script tag reads: data-domain, data-status, data-path, data-search, data-search-results, data-property-<name>, data-links, data-local and data-api.
Single-page apps How fivebar counts the pages of an app that changes its address without loading a page: history.pushState, the back and forward buttons, the back/forward cache, and where each page came from.

Custom events Send an event from a page with tally(), or from anything clicked with a data-tally attribute, with data of its own: the call, the queue, names and limits.
Goals Counting what visitors do as well as what they read: events sent from a page, pages that mark a visit done, and the conversions each one makes.
Outbound links and downloads The clicks fivebar counts with nothing to set up: links to other sites, and links to files, and which files count as downloads.
- Download extensions
Custom properties Label a page’s views with what the page knows about itself, such as its author, language or type, and see each property as a pane of its own.
Site search See what visitors search your site for, from the address of its search pages or from the tag, how often each term was searched, and which searches found nothing.
Error pages How fivebar tells a page answered with an error, such as a 404, from any other: the Errors page, and the data-status attribute Safari needs.
A/B tests Label each variant of a test with a custom property, then compare their conversion rates, bounce rates, speed and errors, for one change or several at once.

Metrics What each figure on the dashboard counts: pageviews, visits, visitors, bounce rate, visit duration, who is on the site now, pages, the chart, the hours and the change from the period before.
Date ranges Choosing the period the dashboard shows: the ranges on offer, a number of days, custom dates, the arrows to the period before and after, and writing a range in the address.
Panes Each pane on the dashboard and what it lists, where a visitor’s country, network, device, browser and system come from, and the full view each pane opens, with search, paging and a trend for every row.
Filters Narrow the whole dashboard to one page, source, channel, country, browser, goal or any other value, combine up to six filters, and what each figure counts under one.
Sources and campaigns Where visits come from: sources and referrers, the channels they make up, the utm_ tags on your links, and how fivebar names them.
Page speed How fast pages load for your visitors: TTFB, FCP, LCP, INP, CLS and page load time, at the 75th percentile, and which browsers report each.
Engagement How long each page was on screen and how far down it was read: time on page, scroll depth, and the graph that puts the two together.
Bots What fivebar takes for a bot, and the Bots page where they show: crawlers, automated browsers, link previews, monitors, programs and visits from hosting networks, left out of every other figure.

Sites Adding a site, the list of your sites and switching between them, and each site’s settings: its tracking code, time zone, group, public stats, email reports, goals, site search, excluded traffic, and deleting it.
Email reports Have a site’s stats emailed to you each week, each month or both: what the report holds, when it comes, who gets it, and turning it off.
Public stats Let anyone see a site’s dashboard and read its stats without signing in: where to turn it on, the address to share, what stays private, and turning it off again.
Excluding traffic Leaving visits out of a site’s counts by where they come from: an IP address or a range of them, a network, or a country. Bots are kept apart on every site already.
Your account Signing in with a link emailed to you, signing out, your account’s settings: the time zone new sites start in, the day your weeks start on, your connected apps and your API tokens, and having your account deleted.

Connecting apps Connect Claude, ChatGPT, Gemini, an editor, a command line agent or any other app that speaks MCP to your fivebar stats, see what it can read, and disconnect it.
Stats API Read a site’s stats as JSON: its figures over a range, each pane in full and how many are on it now, with who it answers, API tokens for scripts, the parameters each takes, what each returns and examples.

Our bot fivebar fetches two things from other people’s sites: the icon a browser shows in its tab, and a home page someone asks the installation checker about. What it asks for, how often, and how to refuse it.
Brand How to write fivebar’s name, its logo to download as SVG or PNG, and the colours and type its pages are drawn in.
Privacy What fivebar keeps about the visitors to the sites it counts, the people who hold an account and those who join the beta: what, where, for how long, and who else handles it.