Report views
See how often a report is opened, from Halo Data, public links and embeds, each day, and which pages, sites, countries and devices its readers come from. Nobody can be traced.
A report's Views show how often it's opened. Open a report, then Views from its … menu.
What it shows
Pick a period, from the last 7 days to the last 12 months.
| Part | What it says |
|---|---|
| Views, In Halo Data, From links, In embeds | How many times it was opened, and through what. A signed embed counts as an embed |
| Each day | Views a day, with embeds stacked apart from Halo Data and links |
| Pages it opened on | The page readers landed on: the first page, or the one a filtered link names |
| Sites that sent readers | The sites readers came from when they followed a link or saw an embed: your website, a newsletter's, a partner's |
| Countries and Devices | Where readers were, and whether on a phone, tablet or desktop |
How views are counted
Once a reader an hour. Reloading, or opening it again soon after, isn't another view. In Halo Data a reader is a member; on a link or an embed, Halo tells readers apart for that hour only.
Published reports. In Halo Data, opening the published report counts. Editing a draft, and viewing as someone else, don't.
People, not robots. Search engines, link previews and Halo's own PDF and email renderer aren't counted.
Days are in UTC.
Views are kept for 13 months, so a month compares with the same month a year before.
Privacy
Views are counts. For a public link or an embed, Halo keeps the report, the day, how it was opened, the page, the site that sent the reader (its name only, never the address of the page), the country and the kind of device. It keeps no IP address, cookie or identifier with them, so a view can't be traced back to a reader, and readers see no consent banner on Halo's account. Halo Data views are counted the same way: the count doesn't say which member opened it.
Halo activity in Halo Data
To build your own reports on how Halo is used, keep Halo activity in Halo Data. In Settings, open Halo activity, pick a workspace and choose Connect. You need See the audit log and Manage connections, as Owners and Admins have.
Halo keeps a connection like any other there, refreshed every six hours, with the last 13 months a day at a time:
| Table | A row is |
|---|---|
report_views | A report's views on a day, by where they came from (Halo Data, Public link, Embed, Signed embed), the page, the site that sent readers, the country and the device |
dataset_queries | A dataset's queries on a day, by where they were asked from (data, report, embed, api, ai, system), how many failed, and how long they took on average |
member_activity | How many things a member did on a day, as the audit log counts them. A member without a name shows as "Member" and the end of their id, never their email |
The days of dataset_queries and member_activity are your organization's, in its time zone. If the tables stop refreshing, whoever can turn them on and off hears why. Halo Data's page for the connection says Halo activity keeps it, with a way back to its settings, and doesn't let anyone change its tables by hand.
Make datasets, charts and reports on them as on any source. What each person reads follows what they can open:
A report's views, only if they can open the report.
A dataset's queries, only if they can open the dataset.
Other members' activity, only if they can see the members list. Otherwise, their own.
That holds in every dataset over these tables, whichever fields it has. Whatever could read around it needs See the audit log: samples of the tables, the values in their catalog, custom SQL, SQL fields, and a dataset on another connection that joins them. An overlay can't join them at all, since its copy reaches everyone who opens it. A public link to a report built on them shows none of it.
Halo's audit log separately records that a report was opened, for security, with its own retention and the access rules of the audit log.