Footfall documentation (public knowledge base)
Getting started
- Install Footfall from the Atlassian Marketplace. Counting starts right away; there is nothing to add to pages.
- A Confluence admin opens Confluence administration > Apps > Footfall page analytics and picks the privacy mode, who sees counts and names, report viewer groups and how long to keep history. The defaults: names recorded but shown only to Confluence admins, counts visible to everyone who can see the page, history kept for 2 years.
- Open any page and click Views in the byline.
The Views dialog
- Views, unique viewers and last viewed for the last 7, 30 or 90 days, 12 months, or all history, and a chart (per day up to 3 months, per week up to about a year, then per month).
- Who viewed (named mode, for people allowed to see names): each person, their views, when they last viewed and which page version they saw.
- Viewers CSV / Views CSV for page editors and report viewers.
- Views from anonymous visitors and from people who opted out are counted without a name.
- Every day is a UTC calendar day.
Space reports
Space admins (and report viewers) open Page analytics in the space sidebar.
- Most viewed: pages and blog posts with views, unique viewers and last view in the range.
- Not viewed lately: every page nobody opened in the chosen time (30 days to 2 years), with when it was last updated and by whom. Until Footfall has been installed for that long, the list means "not viewed since counting started", and the report says so.
- Export CSV: every page in the space with views, unique viewers, last viewed, last updated and a link.
- Reports list only pages you can see. Spaces with more than 2,000 pages cover the 2,000 least recently updated.
Site report
Confluence admins and report viewers open Apps > Footfall page analytics: views, unique viewers and pages viewed per space, any space's report by key, and the least recently updated pages across the site with their last view.
Privacy
- Aggregate only: Footfall counts views and unique viewers but never stores who viewed. It keeps a salted hash per person per month and deletes each month's salt when the month ends, so stored records can't be linked back to anyone. Switching converts names already stored. It can't be undone, and unique viewers across several months become an estimate.
- Don't link my views to me: anyone can turn this on in the Views dialog or in Apps > Footfall page analytics. Their name is never stored again and is removed from views already stored. Admins choose whether their views still count without a name (default) or don't count at all.
- Leave people out: don't count views by a page's creator, or never count chosen people.
- History: kept for 90 days, 6 months, 1, 2 or 3 years, then deleted automatically.
- Delete all view data: in settings, after typing DELETE ALL VIEW DATA. Counting restarts.
Who sees what
| Counts and trend | Who viewed | Space report | Site report | Settings | |
|---|---|---|---|---|---|
| Anyone who can see the page | Yes, unless the admin limits it | No | No | No | No |
| Page editors | Yes, unless limited to report viewers | If the admin turns it on | No | No | No |
| Space admins | Like any reader or editor | No | Their space | No | No |
| Report viewer groups | Yes | Yes (named mode) | Every space they can see | Yes | No |
| Confluence admins | Yes | Yes (named mode) | Every space they can see | Yes | Yes |
Licensing
Paid through Atlassian, from the first user, with Atlassian's 30-day free trial. If the subscription lapses, Footfall keeps counting (so there's no gap when you renew) and every privacy control keeps working; reports pause until it is renewed.
Data
Footfall runs entirely on Atlassian Forge. It stores page ids, space keys, days, counts, version numbers and (named mode only) Atlassian account ids in your site's Forge storage. It does not store page titles or content and sends nothing outside Atlassian. See the privacy policy for details.