Connect website activity and server events.

The browser tracker supports page views, single-page navigation, outbound links, file downloads, tagged custom events, and engagement. Optional click and form capture require explicit configuration.

Create a project, add the snippet, set the allowed origins, and check that your first event arrives. Review the tracker options and privacy settings before collection.

The HTTP API takes an event from anything that can make a request: your backend, a scheduled job, a webhook from your payment provider. Use it for what a browser never sees — a renewal, a refund, a purchase confirmed after the visitor left.

The same API reads aggregates back out, so your own tools and the dashboard answer from one source.

DataVisitors does not publish client libraries today. Source for several languages lives in the repository. These packages are not currently available from a package registry.

The HTTP API is the supported server path, and it is a plain request. When libraries are published, they will be listed here with their registries.

Export CSV reports or use the aggregate query API. Management keys and OAuth applications provide controlled automation where supported. Alert webhooks can notify your own endpoint.

These are APIs and webhooks. DataVisitors does not claim a native connector for every tool that can receive them.

Import supported Plausible, DataVisitors, or generic CSV exports. Historical imports support aggregate traffic reporting. They do not create original sessions, individual journeys, or retention history that the source file never contained.

Read the import guide before migration. The browser and API collection paths still need configuration for new activity.