Web Analytics
Web Analytics shows how visitors use your website: how many came, where they came from, which pages they looked at, and what they clicked.
It is built from the events that Autocapture sends, so the only setup is turning Autocapture on in the browser SDK. Open it from the Analytics section of the side menu.
- Turn on Autocapture in your website. Until page views arrive, the page shows No page views in this range yet.
- To fill the Clicks card, also turn on clicks with
autocapture: { clicks: true }. See Autocapture.
Pick what to look at
- Environment. Web Analytics shows one Environment at a time. Use the Environment switcher at the top of the page to change it.
- Date range. Choose Today, Yesterday, Last 7 days, Last 30 days or Last 90 days. The Last ranges include today. The default is Last 7 days.
- Refresh. Use the refresh button to load the latest numbers, or turn on auto refresh to reload every 30 seconds.
Days are counted in the time zone of your browser.
Summary
The tiles at the top show the main numbers for the selected range:
| Metric | What it counts |
|---|---|
| Visitors | The number of different visitors, anonymous or signed in, that viewed at least one page. Each visitor is counted once in the range. |
| Page views | The number of $pageview events. |
| Sessions | The number of sessions that started in the range and include at least one page view. A session ends after 30 minutes without activity. |
| Session duration | The average time between the first and the last page event of a session. |
| Bounce rate | The share of sessions that had exactly one page view. |
Each tile also shows the change from the previous period: the range of the same length that comes right before the one you picked. Hover over the change to see the previous value. A lower bounce rate is shown as an improvement.
Trend
The chart shows one number per day. Switch between Visitors, Page views and Sessions. A session is counted on the day it started, so the daily sessions add up to the Sessions total in the summary.
Breakdowns
Each card has tabs, and each tab lists the top 20 values.
| Card | Tabs | What it shows |
|---|---|---|
| Paths | Top pages | Each page with its visitors, views and average time on page. |
| Entry pages | The first page of a session, with the number of sessions. | |
| Exit pages | The last page viewed in a session, with the number of sessions. | |
| Sources | Referrers | The website the visitor came from, by sessions. Visits that did not come from another website are shown as (direct). |
| UTM source, UTM medium, UTM campaign | The campaign tags on the landing page of the session, by sessions. | |
| Devices | Device type, Browser, OS | What visitors use, by sessions. |
| Geography | Countries, Cities | Where visitors are, by sessions. |
| Clicks | Top clicks | The elements visitors click most, with the number of clicks and visitors. |
A few things to know about how the numbers are counted:
- Entry values. Referrer, UTM, device, browser, OS, country and city are taken from the first page view of the session, so a session is counted once in each of them. A value that was not recorded is shown as (none).
- Average time on page comes from the time recorded when a visitor leaves a page.
- Referrers are other websites only. Moving between pages of your own website does not count as a referrer.
- Top clicks groups clicks by what the visitor saw: the element's text, or else its
aria-label, or else itsid(shown with a#), or else its selector. The same label on different kinds of elements is listed separately, and hovering over a row shows the link target for links. Form submits are not included. - Page views with no session, for example ones tracked from a server, count in Visitors, Page views and Top pages. They are not counted in Sessions or in the other breakdowns.
What is left out
Visits from bots and crawlers are left out of every number. DashX recognizes them from the browser's user agent.
Where the data comes from
The browser SDK sends the page, referrer, session and campaign with each event. When DashX receives an event, it adds the browser, operating system and device type from the user agent, and the country and city from the IP address the event was sent from.
Learn more about what the SDK sends, and how to keep personal data out of it, in Autocapture.