Connect your website to the questions behind each visit
Use the DataVisitors browser tracker for traffic, engagement, and conversion events. It works with standard websites and applications that change pages without a reload.
Before the first event
A project and an install key
Created in the app, one project per site
Allowed origins
The domains permitted to send
Your privacy settings
Choose them before the first event
Start with the visit
Which sources bring the visits that finish something.
See which sources bring visitors to your website. Compare landing pages, campaigns and the goals those visits complete.
For a SaaS website, start with the pricing page and a completed signup. Compare the goals that each traffic source completes.
Sources · last 30 days
goal: signup completed
| Source | Visitors | Signups | Rate |
|---|---|---|---|
| Search — googletop landing /pricing | 8,412 | 286 | 3.4% |
| Directtop landing / | 5,190 | 171 | 3.3% |
| Newsletter — septembertop landing /pricing | 1,204 | 98 | 8.1% |
| Referral — news.exampletop landing / | 3,880 | 41 | 1.1% |
| Social — linkedintop landing /features | 962 | 19 | 2.0% |
A goal shows traffic quality. In this sample, the newsletter has the highest signup rate.
Choose what you collect
A few useful events beat a mass of detail.
The browser integration supports page views, outbound links, downloads, tagged custom events and engagement. Optional click and form capture need explicit configuration.
-
Page views
Pages a visitor opens, with the referrer and campaign that brought them.
-
Engagement
The time a visitor actively used a page. An idle tab does not count.
-
Outbound links
A click that leaves your site, recorded with its destination.
-
File downloads
A PDF, a price list or an installer, counted where it was offered.
-
Tagged custom events
Your names for important actions, such as a trial start or a plan selection.
Off until you turn it on
Configure these two collectors before they record events.
-
Click capture
Select the elements that you want to measure.
-
Form capture
Measure form submissions. Keep form answers out of event properties.
Keep passwords, form answers and other sensitive values out of event properties.
Connect and confirm
Four steps, and then a number you can trust.
Check the project's first-event status. Verify one goal before you build a report on it.
-
Create a project and an install key
Use one project per website. The key sends events and reads nothing.
-
Add the snippet to your website
The app supplies it with your key. Put it in the head of every page.
-
Set origins and privacy first
Name the permitted domains. Choose your privacy settings before the first event.
-
Watch the first event arrive
Check the project status. Verify one goal before you use its results.
One source per page view
Count each visit once.
The browser tracker observes supported history changes in single-page applications. It already counts those page views.
Do not also send a server page view for the same visit. Choose one source for page views.
Browser
The tracker already sees this
- A page opened, including supported route changes
- The time a visitor actively used a page
- An outbound link or a file download
- A custom event you tagged in the page
Server · jobs · webhooks
Send this to the HTTP API
- A subscription renewal your billing system confirmed
- A background job that finished after the visit
- A purchase confirmed after the visitor closed the tab
- An event with the same permitted visitor identity