Your data is yours. A one-time export is available on every plan, and the file never carries branding rows or footers. Chart-image export is not available.
Request an export
An analyst or an administrator can export every event of a project as a gzip CSV file.
- Open the project's Settings page and its Data & privacy tab, then choose Request an export.
- Enter the range under From and To. The days are whole days in the project's timezone.
- Select Request export.
When it is ready
The service's worker produces the file. The person who requested the export receives a mail with the download link, usually within ten minutes. Every member of the project can download the file from the Files list while they are signed in. A file stays for 7 days. After that, the row shows expired and the link stops working.
What the file contains
The file has one row for each event. The columns are the event's own fields: the event name, the time, the visitor and session identifiers, the page, the referrer, the campaign fields, the country, the region, the device, the browser, the operating system, the locale, the consent state, the SDK, the custom properties, the scroll depth, the engaged time and the click position. The file never contains the city, the retention period, or an internal identifier.
An export has a row cap of 1,000,000 rows. A range that is too large fails with a message that names the cap. Choose a shorter range.
The one-time export is available on every plan.
Monthly export
An administrator on the Business plan can turn on Monthly export. On the first day of each month, DataVisitors exports the previous month and sends the link to every administrator and owner. A plan that no longer includes the feature stops the schedule. The switch stays as you set it, and an upgrade resumes it.
Exports and privacy
The file carries the first-party visitor and session identifiers — random values that mean something inside this project and nothing outside it. It never carries a raw IP address, because the analytics store never held one, and never a city, a retention period or an internal identifier.
Under the Strict regime a visitor's identifier is a daily value, so two rows from the same person on different days cannot be joined from the file alone.