Skip to content
DataVisitors

Two ways in. One project. Plain ways out.

A browser tracker for website activity, an HTTP API for everything a browser never sees, and scoped keys to read the aggregates back.

How activity reaches one project and how its aggregates leave it

Collect

  • Browser tracker page views · SPA · outbound · downloads
  • HTTP API server events · jobs · webhooks
  • CSV import Plausible · DataVisitors · generic

Store & scope

acme-store one project · its own keys
  • sg2_ingest_•••• collect only
  • sg2_read_•••• report reads
  • sg2_admin_•••• management

Read

  • Dashboard & share links aggregates only
  • Query API · CSV export your own tools
  • Alert webhooks your endpoint

Websites & web apps

Supported

Browser tracker

Page views, single-page navigation, outbound links, file downloads, tagged custom events and engagement. Click and form capture stay off until you configure them.

Code 
<!-- DataVisitors --><script defer  src="https://api.datavisitors.com/assets/sg.js"  data-key="YOUR-INSTALL-KEY"></script>
  • Starts stateless — no cookie on a visitor
  • Set allowed origins before the first event
  • Onboarding shows the first-event status
Read the browser tracker guide

Servers, jobs & webhooks

Supported

HTTP API

Anything that can make a request can send an event: your backend, a scheduled job, a webhook from your payment provider. Record a renewal or refund the browser never saw.

Code 
curl -X POST https://api.datavisitors.com/api/event \  -H "Authorization: Bearer YOUR-INGEST-KEY" \  -H "Content-Type: application/json" \  -d '{"events":[{"event_name":"subscription_renewed", …}]}'# every field an event needs is in the manual
  • One source for page views — don't double-send
  • The same API reads aggregates back out
  • Scoped keys: collect, read, manage
Read the HTTP API guide

No client libraries are published today.

None is published on a package registry. The HTTP API is the supported server path — a plain request. If a library is published, this page will list it with its registry.

Move your history

Bring the totals. Not a fiction of the past.

Import Plausible, DataVisitors or generic CSV exports for aggregate traffic reporting. An import cannot create sessions, journeys or retention the source file never contained — and new activity still needs the tracker or the API.

Today a CSV file is imported on request — there is no upload in the app. Once Google is connected, a project's settings can request a Google Analytics 4 history import.

Read the import guide
What an import gives you CSV import Tracker / API
Daily visitors and page views Yes Yes
Top pages Yes Yes
Sources and countries No Yes
Goals on custom events No Yes
Sessions and individual journeys No Yes
Retention cohorts No Yes

Custom events from Starter, retention cohorts from Growth. Compare plans

Accounts open by invitation

See your traffic honestly. Join the waitlist.

Join the waitlist Explore the demo

One address to join · One mail to confirm it · We write when a seat opens