Visits

A visit is one contiguous stretch of activity from a single person. A new visit starts after 30 minutes of inactivity, so the same person coming back later shows up as a separate, later visit. The feed is newest first.

Reading a visit cardLink copied

Each card is one visit. Left to right it tells you who came, how, and what they did.

• Visit number and acquisition source. VISIT 25 is the 25th visit in your selected dates, counted from the oldest. The numbers carry on across pages, so page 2 starts where page 1 stopped. A conversion that arrived without a browser visit (from a webhook, for example) is labelled Conversion instead of a number. The Acquisition source line shows the source and medium that first brought them in (for example ig · social). Direct visits have no acquisition line.
• Who. An avatar plus a name. If you have identified the user (by sending a user ID from your site), you see their real identifier and an Identified badge; otherwise you get a stable anonymous name like "Orange Trout" that stays the same across all of their visits.
• Browser, OS, device. The three small icons. Traffic from an in-app browser (Instagram, for example) shows that app's icon, which is why social visits look the way they do.
• Pageviews and events. The eye pill counts pageviews. Any named event that fired in the visit gets its own pill next to it (for example InitiateCheckout 1), so you can spot the visits where something actually happened.
• Channel. The marketing channel TrueMetriks resolved for the visit (Organic Social, Direct, Paid Search, and so on).
• Entry and exit page. The first page they landed on, an arrow, and the last page they saw. A single path means they only viewed one page.
• When and how long. The start time and the visit duration, with a small info icon next to it. How the duration is measured is explained just below.
• Likely bot tag. A yellow Likely bot tag and a dashed border mark a visit that looks automated. Hover the tag to see which signs the visit showed. See Likely bots.

How visit duration is measuredLink copied

The duration on each card is the longer of two numbers:

• the time between the visit's first and last event, or
• the time its pages were actually on screen, added up across every page of the visit.

The second number is what makes one-page visits readable. Someone who lands on a page, reads it for two minutes and leaves only ever sends one event, so the first number alone reads 0s. Paid landing pages (an ad, one long page, then a checkout on another domain) used to read almost all zeros for exactly that reason. With time on screen counted, that visit now shows about two minutes.

A few rules keep the number honest:

• Only visible time counts. A tab left open in the background, or overnight, adds nothing.
• Each page view counts at most 30 minutes of on-screen time.
• A visit never reads shorter than it used to. Time on screen only fills in what the events could not see.
• No install change is needed. The TrueMetriks tracker already on your site picked it up automatically.
• It applies from 2026-09-26 onward. Visits before that date keep their old duration.

Some visits still read 0s. That means the visitor left within about 5 seconds, or their browser did not report the time (some in-app browsers close the page without warning). Hover the info icon next to any duration and it says exactly that.

The same duration feeds the Visit duration card on the Main page, the average on a person's profile, the visit lists on goals and funnels, and the weekly email and PDF reports.

Your numbersLink copied

The row above the list totals your selected dates and filters.

Unique Users counts the distinct people who visited.

Visits counts every visit. One person can visit more than once, so this number can be higher than Unique Users.

Pageviews counts every page loaded across those visits.

When some visits look like bots, a yellow line under each number says how many of them are included, for example "incl. 4 likely bots".

Likely botsLink copied

Some visits come from software, not people: email security scanners that open links, uptime checkers, and scrapers that run a real browser. They pass ordinary bot filters because they look like a normal browser, so TrueMetriks marks them instead.

A visit is marked as a likely bot when at least two of these signs show up together:

• Server network. It came from a data-centre company (Google Cloud, Amazon AWS, Microsoft Azure and similar), not a home or mobile connection.
• No sign of a person. No mouse, touch, key or scroll input on any page.
• Burst. It arrived in the same second as two or more other new visitors on the same page.

A visit with a click, a form, an event, a purchase or a known person is never marked. A real person on a VPN still scrolls and clicks, so they stay counted.

When the dates you picked contain likely bots, a yellow banner on the Main and Visits pages says how many. Why? lists the signs and the networks they came from. The Hide likely bots switch removes them from every number on those two pages and adds a "Likely bots: hidden" chip to the filter bar; remove the chip to show them again. The choice is remembered for each site, and the × on the banner shrinks it to a slim line.

Nothing is deleted. Likely bots stay in your data, and the marks only change your dashboard: events sent to Facebook, Google and TikTok are not affected. The Block bot traffic setting is separate: it blocks bots that announce themselves before they are ever counted.

PagesLink copied

The list shows 10 visits per page, newest first. The line at the bottom says which visits you are looking at, for example "Showing 1-10 of 38 visits". Use the page numbers, Previous and Next to move through the list.

Visits per page sets how many cards each page shows: 5, 10, 20, 50, 100, or a custom number from 1 to 500. The choice is remembered for each site.

To narrow the list, use the Filter button and the date range at the top. They scope the feed by any property (country, channel, UTM, page, event name, and more), exactly like the rest of the dashboard.

Opening a visitLink copied

Click any card to expand it in place. You get two tabs and a shortcut to the person's full history.

TimelineLink copied

The Timeline is the play-by-play: every event in the visit, in order, numbered down the page. Each pageview shows the URL (the query string, including UTMs and click IDs, is greyed after it) and the time spent on that page before the next pageview. Custom events, outbound clicks, button clicks, copies, form submits, input changes, and errors all appear inline where they happened.

The pills at the top filter the timeline by event type. Each one carries a count, so Pageview 3 means three pageviews in this visit; click a type to show or hide it. Long visits load in batches with a Load More button, and the footer keeps a running Showing X of Y events.

The per-page duration is measured to the next pageview, not the next event, so a custom event firing a split second after the page loads never makes a page look like it lasted zero seconds. The last page of a visit has no next pageview, which is why the visit's own duration on the card (with time on screen counted) can be longer than the timeline's per-page times added up.

Visit infoLink copied

The Visit info tab is the reference card for the visit, in three columns:

• User Information - user ID, language, and resolved country, region, and city.
• Device Information - device type, browser and version, OS and version, screen size, and IP.
• Source Information - channel, referrer, and entry page.

View UserLink copied

View User jumps from this single visit to that person's complete profile: every visit they have ever made, stitched together. It is the bridge from "what happened in this visit" to "who is this person and what is their whole journey." See Users for that view.