How Lynq counts
Every number in the dashboard comes from one definition. This page is the list.
Visitors
A visitor is a number computed when a request arrives, from the visitor’s IP address, browser, the site, and a salt that changes every day. Nothing is stored in the browser to remember them.
Unique visitors for a range counts those numbers once each. Because the salt rotates, the same person is one visitor per day: someone who comes on Monday and Tuesday is two unique visitors over the week. A site that identifies its users counts each identified user once over the whole range.
Sessions
A session is one tab’s visit. It ends after 30 minutes without an event, or 6 hours after it started, whichever is first; the next pageview starts a new one. A tab opened from a link continues the session; a tab opened with target="_blank" starts a new one. An anonymous session never spans midnight UTC, because the visitor number changes then.
Sessions counts them. Pages per session is pageviews divided by sessions. One session, opened as a timeline, is a journey.
Pageviews
One per page load or client-side navigation. A hash-only change is not a pageview.
Bounce rate
A session bounces when it has exactly one pageview, under 10 seconds of engaged time, and no custom event. Bounce rate is bounced sessions divided by sessions. Clicking a tracked button on a landing page is engagement, so it is not a bounce.
Engaged time
The time the page was visible and focused: a tab in the background, a minimised window or a hidden page does not count. It is reported when the page is hidden or left, and summed per session. The Overview’s Engaged time is the average per session.
Time on site, where shown, is the plain span from a session’s first event to its last.
Entry and exit
The entry page is a session’s first pageview, the exit page its last. The source and channel of a session come from the referrer and UTM parameters of that first pageview: Direct, Organic Search, AI, Social, Referral, Email and Paid. The Sources screen ranks sessions by their entry source; the row-level Referrer and Source dimensions on other screens describe each pageview instead.
AI is its own channel rather than part of search, because someone arriving from an answer already has one. It covers ChatGPT, Claude, Perplexity, Gemini, Copilot, Grok, DeepSeek, Poe and You.com. A tagged link naming one of them counts the same way, and UTM parameters still override the referrer.
Attention, read-through and influence
A second reading of the same rows, on the Pages screen’s Attention view. Nothing extra is collected for them.
Attention is the engaged time a page accumulated over the range, added up rather than averaged, and share of attention is a page’s portion of the site’s. It is not the same number as Engaged time, which is an average per session and stays where it is: attention is a total, and it is what ranks pages. A page with fewer visits can hold more of your visitors’ time than the home page, and usually does.
Read-through is the share of a page’s pageviews where the deepest scroll reached 75% of the document and engaged time was at least 10 seconds, the same 10 seconds that decides a bounce. Below 30 pageviews in the range a page shows a dash instead, because the share of a handful of views is noise.
Influence is how much more often your KPI goal is reached by sessions that saw a page than by sessions that did not, as a ratio. 1.5x means those sessions converted half as often again. A page only counts when it was seen before the session converted, which is what stops pages people reach by converting, a dashboard or a thank-you page, from topping the list. Both sides of the comparison need at least 50 sessions, else the page shows a dash. It needs a KPI goal, and it is association rather than cause: a page that appears on the way to a purchase is not necessarily the reason for it.
Conversion
A goal completes when a session has a pageview matching the goal’s path, or a custom event with the goal’s name. Conversion is sessions with at least one completion divided by sessions. On a table such as Pages, the denominator is the sessions that touched that row. See Goals and the KPI.
Web Vitals
Each metric is reported once per page load when the browser finalises it, and the Performance screen shows the 75th percentile over the range, the value Google’s thresholds are defined on. LCP and INP also record the element responsible. When a metric gets worse, the first question is what changed that day; a note pinned at the deploy answers it before you go looking.
What is left out
Known bots and automated browsers are dropped at the collector. Visits from a site’s excluded IP ranges and excluded paths are never stored. Visits on localhost are ignored unless the tag allows them.