Dashboard
Data export
Download the page views and custom events of a site as a CSV file, and know exactly what the file holds and what it leaves out.
This page shows how to take the data of a site out of Clear Saga as a file you can open in a spreadsheet or load into another tool, and what you will and will not find in that file.
Download a file #
There is one export, and it is in the settings of each site.
- Open the site and go to Settings, Data.
- In the "Export CSV" card, pick how far back the file should go.
- Click Download CSV.
The file downloads straight to your device. Nothing is sent by email and nothing is stored anywhere else.
You can pick the last 7, 30 or 90 days, or All time. A period is counted in days in the time zone of the site and ends at the moment you click. "All time" starts on the day of the first visit the site still has stored.
Owners and Admins of the workspace can export. A Viewer cannot, and neither can a visitor of a shared dashboard or of the public demo.
What the file holds #
The file has one row for every stored page view and every stored custom event, oldest first. It is not a summary: totals such as visitors or bounce rate are not in it, and you work them out yourself if you need them.
These are the columns, in order:
| Column | What it holds |
|---|---|
timestamp |
When it happened, in UTC, with milliseconds. |
type |
pageview or event. |
name |
The name of the custom event. Empty for a page view. |
path |
The path of the page, never with a query string. |
hostname |
The hostname of the page. |
referrer |
The site the visit came from, on every row of that visit. Empty when there is none. |
country |
A two-letter country code. Empty when it is not known. |
device |
desktop, mobile or tablet. |
browser |
The browser family. |
os |
The operating system family. |
utm_source, utm_medium, utm_campaign, utm_term, utm_content |
The campaign tags of the visit. Empty unless campaign capture was on. See campaigns. |
props |
The properties of a custom event, as a JSON object. Empty when there are none. |
The file is comma separated, has a header row and is encoded as UTF-8, so a spreadsheet opens it as it is. A cell that a spreadsheet would run as a formula is written so that it is shown as plain text.
What the file never holds #
Rows are single page views and events, but no row can be tied to a person. That is also true for a site with Remember returning visitors on: the file carries no visitor key.
- No visitor or session identifiers. You cannot group rows by visitor or rebuild one person's path through your site.
- No IP addresses and no user agent strings. IP addresses are not stored in the first place.
- No query strings, and no regions or cities. The country is the finest location in the file.
Some kinds of data are not part of the export at all: visits to missing pages (404), performance samples, orders and the requests that were filtered out as bots.
The size estimate #
Before you download, the card tells you about how many rows the file will have and what it will be called. The estimate updates when you pick another period. If a period has no events, the card says that the file would hold only its header row.
The file is named after the domain of the site, the period and the date of the download, so files from different sites and days do not overwrite each other.
There is no cap on the number of rows. The file is sent to your browser in pieces as it is read, so a large export simply takes longer. If something fails on the way, your browser reports a failed download. It does not save a short file that looks complete.
What limits an export is how long data is kept: page views and events are stored for 3 years, so "All time" reaches back that far at most. Statistics that were deleted with "Reset statistics" are gone from the export too. See managing a site.
While the dashboards are locked #
The export stays open while the dashboards of a workspace are locked, for example after a trial ended without a plan. The Settings of a site stay reachable then, and so does the Data tab. Your data is never held back. Plans, usage and limits explains when a workspace is locked.
Deleting a site deletes everything collected for it, for good. If you may need the data later, export it first.
Exports and programs #
An API token cannot export a CSV file. The export is a download for a signed-in person, on purpose.
A program or an AI agent reads the same data through the API instead, as JSON: totals, breakdowns and the activity log, with the same filters the dashboard has. Connect an AI agent explains how to create a token. The list of what a token can never do is in the API reference.
An export is always started by hand. There are no scheduled exports and no automatic delivery to a data warehouse.
Bringing data in #
The same Data tab has an "Import history" section that lists the tools an import is planned for. Importers are not built: nothing can be imported from another analytics tool today. See what works today.
Next: Managing a site, Connect an AI agent, Privacy: cookieless by default