Guide · Data & API

Data exports & API

Your analytics data is yours: one-click CSV downloads in the dashboard, a ready-made GDPR Art. 30 record, and a cookieless REST API for BI tools and scheduled jobs.

Exports in the dashboard

Traffic CSV Every plan

Aggregate daily counters per site: visits, visitors, identified visits, bounced visits, average dwell and the top country, city, browser, OS, device, page and source per day.

Companies CSV Pro

The identified-company table with network, location, source, sessions, engagement and score — the same rows the Companies tab shows.

ROPA export (Art. 30) Every plan

A ready-made Record of Processing Activities for this analytics module, generated from your actual configuration and operator details. Download it from the Overview tab ("Download ROPA") and attach it to your GDPR documentation.

Filtered company CSV Pro

The Companies table exports exactly what is on screen — filters included — and the export runs in your browser, so no data leaves the dashboard.

Find the per-site download links under Settings → Data exports.

The export API (v1)

The API is cookieless by design: it authenticates with a bearer key, never reads a session cookie and never sets one. Create keys in Settings → API access — you can hold up to 10 active keys per account, each with a label, and each key is shown only once at creation.

Authentication

Authorization: Bearer vk_… (preferred) X-Api-Key: vk_… (for hosts that strip Authorization)

Endpoint

GET https://visitora.eu/api/v1/export.php?dataset=traffic&site=SITE-ID&from=2026-11-01&to=2026-11-17&format=csv
ParameterRequiredValues
datasetno (default traffic)traffic — aggregate daily counts, every plan · visitors — identified-company rows, requires identification (Pro)
siteyesYour site ID, as shown in Settings → Websites
from, tonoYYYY-MM-DD (UTC days). Defaults: full stored history for traffic, last 30 days for visitors
formatno (default json)json or csv

Examples

Last 30 days of aggregate traffic as JSON:

curl -H "Authorization: Bearer vk_your_key_here" \ "https://visitora.eu/api/v1/export.php?dataset=traffic&site=my-site"

Identified companies for a quarter as CSV:

curl -H "Authorization: Bearer vk_your_key_here" \ "https://visitora.eu/api/v1/export.php?dataset=visitors&site=my-site&from=2026-07-01&to=2026-09-30&format=csv" \ -o companies.csv

Traffic JSON shape

{ "ok": true, "dataset": "traffic", "site": "my-site", "range": { "from": "2026-11-01", "to": "2026-11-17" }, "totals": { "visits": 0, "visitors": 0, "identified": 0 }, "rows": [ { "date": "2026-11-01", "visits": 120, "visitors": 84, "identified": 3, "bounced": 41, "dwell_avg_s": 47, "top_country": "AT", … } ] }

Good to know

Frequently asked questions

What is the difference between dashboard exports and the API?

They read the same data. Dashboard exports (Settings → Data exports) are one-click CSV downloads using your sign-in session; the API (Settings → API access) issues bearer keys so scripts, BI tools and cron jobs can pull the same datasets without a session.

Who can use the export API?

Any account. The traffic dataset (aggregate daily counts) works on every plan. The visitors dataset (identified-company rows) requires a plan with identification — Pro, or a team share covered by the owner's Pro subscription.

Are API keys linked to my user or to a website?

Keys belong to your user account. Each request names the site explicitly with the site parameter; you can export any site you own or that is shared with you, within your role.

Why do visitors exports stop at 50,000 rows?

Company exports are capped at 50,000 rows per request. Use from/to windows to page through longer histories — the limit applies per request, not per range.

Is the traffic dataset personal data?

No. It contains aggregate daily counters only (counts per day and top values per category), consistent with GDPR Recital 26. The visitors dataset contains company-level rows and requires the identification plan level.

My request returns 401 — what now?

The key is missing, invalid or revoked. Create a fresh key in Settings → API access and send it as Authorization: Bearer vk_… (or X-Api-Key: vk_… on hosts that strip the Authorization header).