Browse Analytics

Visits explore

The Visits explore has one row for every visit, as it arrived. What it counts, what to know when reading it, and every dimension and metric in it.

The Visits explore has one row for every visit with at least one page view. A visit ends after 30 idle minutes and is shared across tabs, so reading in two tabs is one visit.

Use it for traffic, engagement and conversion by channel, campaign, landing page, audience and device. It is the explore behind most of the ready-made dashboards.

Good to know

Everything is as the visit arrived. Channel, Source and Campaign are those of its first page view and never change, so a visit that arrived directly is Direct, whatever brought the visitor before.
A conversion counts under the visit it happened in. The credit a conversion gives earlier visits is in the Campaigns and Attribution explores, never here, so no rate here divides credited conversions by visits.
A conversion is macro or micro. Macro is a purchase; micro is a lead, a demo request, a newsletter signup or a trial start. Conversion rate counts both, and Purchase rate and Micro conversion rate split it.
Purchases and leads come from page types: a visit that reaches an Order confirmation page made a purchase, and one that reaches a Form confirmation page a lead. Demo requests, newsletter signups and trial starts come from the click types of the forms sent.
Revenue adds up Order value on Order confirmation pages, each order once, or the value of the Shopify order Kontala's pixel reported. It is empty, not zero, where nothing says what an order came to.
A visitor is a device until Kontala resolves devices to people. Safari clears the device cookie after 7 days without a visit, so Users reads high there.
Country, device, browser and similar dimensions are read from the visit's first page view, while Organisation and Company domain say who the visit was.
Days here are UTC days. The Trends explore uses your organisation's time zone, so a day's count can differ between the two.

Used on dashboards

Charts on these dashboards are built on the Visits explore:

Acquisition: where do people come from?: Channels, Campaigns & spend and Landing pages
Engagement: Do they stick?: Engagement and Coming back
Conversion: do they do the thing?: Conversion, Who converts, Funnels, Micro vs macro and Time to convert
Audience: who are they?: Audience, Location, Technology, New vs returning, Identified and Organisations
Product and app usage: Usage, Friction and Speed

Dimensions

The Visits explore has 74 dimensions.

When

Dimension	Type	Description
Visit start	Timestamp	When the visit began: its first page view. Time intervals: Raw, Hour, Day, Week, Month, Quarter, Year, Hour of day (number), Day of the week (index), Day of the week (name).

How it arrived

Dimension	Type	Description
Channel	String	How the visit arrived, from its first page view: the click id, the campaign medium and the referring domain, in that order of trust, by the rules of Channel in the page view explore. It never changes afterwards, so a visit that arrived directly is Direct, whatever brought the visitor before or during it. The Campaigns explore credits a direct visit's conversion to an earlier visit, or to a campaign that reached the visitor mid-visit; this explore counts every visit as it arrived.
Mid-visit campaign touches	Number	How many campaigns reached the visitor after the visit began: later page views of the visit that arrived from outside the site with a campaign tag or an ad's click id the visit had not had, such as a retargeting ad opened in a new tab. The visit keeps the channel it arrived by; the Campaigns and Attribution explores credit conversions to these touches too.
Source	String	Where the visit came from: the campaign source its link carried, else the ad network its click id names, else a search engine's name, such as google, else the referring domain, such as facebook.com, else (direct). (not set) is a campaign link that named a medium and no source.
Medium	String	How the visit came: the campaign medium its link carried, else cpc for an ad network's click id, organic for a search engine and for Google's free listings, referral for any other site and for Meta's own links, and (none) for a visit with no referrer. (not set) is a campaign link that named a source and no medium, as ChatGPT's do.
Source / medium	String	Source and medium together, such as google / organic, facebook / paid_social or (direct) / (none).
Campaign	String	The campaign named on the link the visit arrived by. Empty for a visit whose link named none.
Campaign ID	String	The ad platform's campaign id the link the visit arrived by carried as utm_id, which a spend file names too and which survives the campaign being renamed. Empty for a visit whose link carried none.
Term	String	The paid keyword of the campaign the visit arrived by, where the network writes one.
Content	String	The creative or placement variant of the campaign the visit arrived by.
Click ID source	String	Which click identifier the visit's first page carried, such as gclid. A click id names a network, not a payment: Channel says whether the visit was paid.

Where it landed

Dimension	Type	Description
Landing page	String	The path the visit began on.
Landing hostname	String	The hostname the visit began on, for a property that spans more than one website.
Landing page type	String	What kind of page the visit began on, as Page type reads it in the page view explore: the type the site declared, the page type rules confirmed in Kontala, or the page type model where the property lets it answer. Unclassified when none says.

The visitor

Dimension	Type	Description
Visitor	String	Whether this was the device's first visit. Each device has one first visit, in the channel it first arrived by, so first visits add up across channels. Bounded by the device cookie's life, which Safari cuts to 7 days.
Visit number	Number	Which visit of this device this is: 1 for its first. Bounded by the 400 days Kontala keeps and by the device cookie's life, which Safari cuts to 7 days.
Visit number band	String	Which visit of its device this is, in five bands: 1st, 2nd, 3rd-4th, 5th-9th, and 10th or later. Bounded by the 400 days Kontala keeps and by the device cookie, which Safari clears after 7 days, so a returning Safari visitor reads 1st visit again each week.

Who it was

Dimension	Type	Description
Signed in	Boolean	Whether anything in the visit named a signed-in user: the site's own identify call, a login Kontala captured, or an analytics tool's identify call. False is the normal state on a public page. A login names who tried, so a failed one counts too.
Sign-in state	String	Signed in: the visit named a user. Signed out: it named none, but its device signed in on an earlier visit. Signs in later: its device signs in only on a later visit. Anonymous: its device never signed in within the 400 days Kontala keeps. Bounded by the device cookie, which Safari clears after 7 days, so there a device's sign-ins are forgotten after a week.

What happened in it

Dimension	Type	Description
Engaged	Boolean	Whether the visit did more than glance: two or more page views, or a conversion. GA4 also counts ten seconds of visible time, which Kontala does not measure yet.
Converted	Boolean	Whether the visit converted: a purchase, a lead, a demo request, a newsletter signup or a trial start.
Purchased	Boolean	Whether the visit reached a page whose page type is Order confirmation: the site's own declaration, a Shopify store's thank-you page as Kontala's Shopify pixel declares it, a page type rule confirmed in Kontala, or the page type model.
Lead	Boolean	Whether the visit reached a page whose page type is Form confirmation.
Demo request	Boolean	Whether the visit sent a form whose Click type is Request demo: declared on the page with data-ac-event, typed by a click type rule confirmed in Kontala, or by the click type model. A click that sent no form, such as the link to the form, is not one. Read on properties that capture clicks.
Newsletter signup	Boolean	Whether the visit sent a form whose Click type is Newsletter signup. A click that sent no form is not one. Read on properties that capture clicks.
Trial start	Boolean	Whether the visit sent a form whose Click type is Start trial. A click that sent no form, such as a Start free trial link to the sign-up page, is not one. Read on properties that capture clicks.
Micro-converted	Boolean	Whether the visit made a micro conversion: a lead, a demo request, a newsletter signup or a trial start. A purchase is the macro conversion.
Conversion kind	String	The visit's biggest conversion where it made several: Purchase, then Trial start, Demo request, Newsletter signup and Lead. Empty for a visit that did not convert.
Micro conversion	String	The visit's micro conversion, the most telling where it made several: Trial start, then Demo request, then Newsletter signup, then Lead. Empty for a visit with none.
Furthest sign-up step	String	How far the visit went down the sign-up funnel, in order: it landed, then saw a Pricing page, then started a sign-up (reached a Form page, or clicked Sign up, Start trial, Request demo or Begin application), then completed it (reached a Form confirmation page, or sent a form typed Sign up, Start trial, Request demo or Submit application). A step taken before the one it follows does not count.
Furthest purchase step	String	How far the visit went down the purchase funnel, in order: it landed, then viewed a Product detail page, then added to cart (clicked Add to cart or reached a Cart page), then began checkout (reached a Checkout page or clicked Begin checkout), then reached an Order confirmation page. A step taken before the one it follows does not count.
Pages in visit	Number	How many page views the visit had, in every tab.
Visit depth	String	How many page views the visit had, in five bands: 1 page, 2 pages, 3-4, 5-9 and 10 or more.

How long it took

Dimension	Type	Description
First conversion	Boolean	Whether this was the device's first visit with a conversion. Bounded by the device cookie's life, which Safari cuts to 7 days.
Days to convert	Number	On the device's first converting visit, the days from the start of its first visit to the conversion, at a fraction of a day; empty on every other visit. Bounded by the device cookie's life, which Safari cuts to 7 days.
Time to convert	String	On the device's first converting visit, how long after its first visit it converted, in five bands: 0 days (under a day, the first visit itself included), 1-2 days, 3-6 days, 7-29 days and 30 days or more. Empty on every other visit.
Visits to convert	String	On the device's first converting visit, how many visits it took, that one included, in five bands: 1 visit, 2, 3-4, 5-9 and 10 or more. Empty on every other visit.
First purchase	Boolean	Whether this was the device's first visit with a purchase.
Days to first purchase	Number	On the device's first visit with a purchase, the days from the start of its first visit to the purchase; empty on every other visit.
Purchased since	Boolean	Whether the device has made a purchase in this visit or a later one, so far: a recent visit has had less time to.
Days to next purchase	Number	Days from this visit's start to the device's first purchase in this visit or a later one; empty where none has followed yet.

Whether it came back

Dimension	Type	Description
Days to next visit	Number	Days from this visit's start to the start of the same device's next visit; empty where none has followed yet. A visit ends after 30 idle minutes, so a return later the same day counts, at a fraction of a day. Bounded by the device cookie's life, which Safari cuts to 7 days.

The features it used

Dimension	Type	Description
Features used	Number	How many different features the visit used: page types it viewed and click types it clicked.
Feature path	String	The features the visit used, in order, a repeat of the one before taken as one step: its first four, then how many more. (no typed step) where none of its pages or clicks had a type.
Typed page or click	Boolean	Whether the visit viewed a page or clicked something Kontala gives a type: how much of a visit the Product and app usage dashboard can see.

What it met

Dimension	Type	Description
Friction measured	Boolean	Whether the visit was measured for speed and friction: its property captures friction and the visitor consented. Every friction rate is over measured visits.
Frustrated	Boolean	Whether the visit met an error click, a rage click, a dead click or a quick back. Empty for a visit that was not measured.
Friction met	String	The most telling friction the visit met: an error click before a rage click, before a dead click, before a quick back, else None. Empty for a visit that was not measured.
Had a JavaScript error	Boolean	Whether the page threw an uncaught error or left a promise's rejection unhandled during the visit, with a click or without. Empty for a visit that was not measured.
Landing page LCP rating	String	How fast the visit's landing page showed its largest text or image, rated as web.dev rates it: Good at 2.5 seconds or less, Poor over 4. Empty where it was not measured.

Page

Dimension	Type	Description
Referring domain	String	The registrable domain (eTLD+1) of the referrer, so www.google.co.uk and news.google.co.uk are one source and m., l. and lm.facebook.com are one source. Null where there is no public suffix to find, which is how localhost and a bare IP read - Referrer host still carries those.

Geo

Dimension	Type	Description
Country	String	The visitor's country as a two-letter code, such as GB, from their IP address. IP Geolocation by DB-IP (https://db-ip.com/), CC-BY 4.0. A dashboard showing this must display that attribution.
Country name	String	The country's name in English, as the Unicode CLDR gives it, read from Country's code; a code CLDR does not name reads as itself. IP Geolocation by DB-IP (https://db-ip.com/), CC-BY 4.0. A dashboard showing this must display that attribution.
Continent	String	One of seven continents, read from Country by the UN's regions: North America includes Central America and the Caribbean. Russia is Europe; Turkey, Cyprus, Georgia, Armenia and Azerbaijan are Asia, as the UN files them. IP Geolocation by DB-IP (https://db-ip.com/), CC-BY 4.0. A dashboard showing this must display that attribution.
Region	String	The visitor's region, such as a state or county, from their IP address. IP Geolocation by DB-IP (https://db-ip.com/), CC-BY 4.0. A dashboard showing this must display that attribution.
City	String	IP Geolocation by DB-IP (https://db-ip.com/), CC-BY 4.0. A dashboard showing this must display that attribution.

Browser environment

Dimension	Type	Description
Language	String	The browser's language as it reports it, such as en-GB. Language code and Language name group its variants.
Language code	String	The language alone, such as en for en-GB, en-US and en-GB-oxendict alike. Empty where the browser reports no language code.
Language name	String	The language's name in English, as the Unicode CLDR gives it, read from Language code: English for en-GB, en-US and en alike, Chinese for zh-Hans-CN. A code CLDR does not name reads as itself; empty where the browser reports no language code.
Device class	String	Bucketed from window width, not from the User-Agent. A narrow desktop window reads as mobile, which is the honest answer for a layout question; Device type answers the hardware one.

Browser, operating system and device

Dimension	Type	Description
Device type	String	Desktop, mobile, tablet or smart tv, from the User-Agent header, and unknown where it names no platform: the hardware, where Device class is the layout the window's width gives. A tablet asking for desktop sites, as Safari on iPad does by default, reads as desktop.
Browser	String	The browser, from the User-Agent header. A browser built on Chromium that does not name itself there, such as Brave, Arc or a desktop app, reads as Chrome. A page opened inside an app reads as the app where it names itself, such as Instagram or the Google app, and as In-app browser where it does not. An app's own screens, from Kontala's SDK, read as App.
Browser version	String	The browser and its major version, such as Chrome 131 or Safari 18. Empty for an in-app browser, whose numbers are the app's rather than the browser's, for an app's own screens, whose version is App version's, for DuckDuckGo, whose User-Agent carries no version of its own, and for Other.
Operating system	String	The operating system, from the User-Agent header; iOS includes iPadOS. There is no version beside it, because browsers freeze theirs: Windows 11 reports Windows 10 and every Mac reports macOS 10.15. An iPad asking for desktop sites, as Safari on iPad does by default, reads as macOS, and many Android tablets read as Linux the same way.

Data source and quality

Dimension	Type	Description
Site	String	The property the event was sent to, read from the key it was sent with.
Allowed origin	Boolean	Whether the page's origin is one its property allows. False marks a development server, a staging copy or another site carrying the snippet, so filter on true for real traffic. A property that lists no allowed origins allows every one.

First touch

Dimension	Type	Description
First-touch channel	String	The channel of this device's first visit, read as Channel reads a visit: how the visitor first arrived, whichever visit this is. Empty for a device with no page view.

Signed-in user

Dimension	Type	Description
Organisation	String	Application organisation id. The account-level rollup key: the primary B2B question is which ORGANISATIONS adopt a feature, not which people. Null before sign-in.
Company domain	String	The company a signed-in user's id names when the id is an email address: the registrable domain after its @, so acme.co.uk for jane@eng.acme.co.uk. Empty for an id that is no address and for a mailbox anyone can open, such as gmail.com, from Kontala's list of free providers; a provider not on it reads as a company, and so does a mistyped domain, since a login names what was typed.

An app

Dimension	Type	Description
Platform	String	Web, iOS, Android or App web view: whether the row came from a website, through Kontala's tag or the Events API, from an app on Kontala's SDK, or from a page of a website an app showed in a WebView it attached to Kontala, whose rows are the app's visitor and visit. iOS includes iPadOS.
OS version	String	An app's operating system and its version, such as iOS 18.1 or Android 14, as the device reports it. Empty on the web, whose browsers freeze the version they write.
App version	String	The app's version, such as 3.2.0, as the store shows it. Empty on the web.
App build	String	The app's build number, which tells two builds of one version apart. Empty on the web.
Device model	String	The device an app runs on, by its machine identifier, such as iPhone16,1 or Pixel 8. Empty on the web.

Metrics

The Visits explore has 99 metrics.

Main metrics

Metric	Calculation	Description
Visits	Count	Visits with at least one page view. A visit ends after 30 idle minutes and is shared across tabs, so reading in two tabs is one visit. Bot traffic and visits without consent are left out.
Users	Count distinct	Distinct visitors: today each is a device, from the first-party device cookie. Optimistic on Safari, which clears that cookie after 7 days, so a returning visitor there counts again each week.
First-time visitors	Count	Visits that were their device's first. Each new device counts once, in the channel of its first visit, so channel rows add up to the total. The page view explore's New visitors counts a device on every row of its first day, so the two can differ.
First-time share	Ratio (%)	The share of visits that were their device's first.
Returning visits	Count	Visits that were not their device's first.
Returning share	Ratio (%)	The share of visits that were not their device's first. Low on Safari, which clears the device cookie after 7 days, so a visitor returning after that counts as new.
Returning visitors	Count distinct	Distinct visitors with a visit that was not their first: today each is a device. A visitor whose first visit was in range and who came back counts here and among First-time visitors, so the two can add up to more than Users. A lower bound: Safari clears the device cookie after 7 days.
Visits per visitor	Ratio	Visits per visitor, today per device. Low on Safari, which clears the device cookie after 7 days, so one person there can count as several devices.
Engaged visits	Count	Visits with two or more page views, or a conversion.
Engagement rate	Ratio (%)	The share of visits that were engaged. GA4's bounce rate is its complement.
Pages per visit	Average	Page views per visit, in every tab.
Avg. visit duration (s)	Average	Seconds from a visit's first page view to its last, averaged over visits; a one-page visit counts as 0, since nothing measures its time.
Conversions	Sum	Purchases, leads, demo requests, newsletter signups and trial starts, under the channel of the visit they happened in, each kind once a visit: a visit reaching an Order confirmation page is a purchase, one reaching a Form confirmation page a lead, and a form sent as a Request demo, Newsletter signup or Start trial click one of those. Zero where no page or form has a type yet.
Converting visits	Count	Visits with a purchase, a lead, a demo request, a newsletter signup or a trial start.
Visits with a mid-visit campaign	Count	Visits a campaign reached after they began, such as a retargeting ad opened in a new tab, which the Campaigns and Attribution explores credit as touchpoints of their own.
Conversion rate	Ratio (%)	The share of visits that converted, macro or micro: a purchase, a lead, a demo request, a newsletter signup or a trial start. GA4 calls it the session key event rate.
Converting users	Count distinct	Distinct visitors with at least one converting visit: today each is a device.
User conversion rate	Ratio (%)	The share of users with a converting visit: GA4's user key event rate. A visitor who converts on a later visit counts once here and lowers the visit rate. Optimistic on Safari, which clears the device cookie after 7 days.
Purchase rate	Ratio (%)	The share of visits with a purchase: the macro conversion rate.
Micro-converting visits	Count	Visits with a lead, a demo request, a newsletter signup or a trial start.
Micro conversion rate	Ratio (%)	The share of visits with a micro conversion: a lead, a demo request, a newsletter signup or a trial start.
Purchases	Count	Visits that reached an Order confirmation page.
Leads	Count	Visits that reached a Form confirmation page.
Demo requests	Count	Visits that sent a form typed Request demo.
Newsletter signups	Count	Visits that sent a form typed Newsletter signup.
Trial starts	Count	Visits that sent a form typed Start trial.
Sign-up funnel: saw pricing	Count	Visits that viewed a Pricing page.
Sign-up funnel: started	Count	Visits that started a sign-up after viewing a Pricing page: reached a Form page, or clicked Sign up, Start trial, Request demo or Begin application.
Sign-up funnel: completed	Count	Visits that completed a sign-up after starting one: reached a Form confirmation page, or sent a form typed Sign up, Start trial, Request demo or Submit application.
Sign-up funnel: saw pricing (%)	Ratio (%)	The share of visits that viewed a Pricing page.
Sign-up funnel: started (%)	Ratio (%)	The share of visits that saw pricing and then started a sign-up.
Sign-up funnel: completed (%)	Ratio (%)	The share of visits that started a sign-up and then completed it.
Purchase funnel: viewed a product	Count	Visits that viewed a Product detail page.
Purchase funnel: added to cart	Count	Visits that added to cart after viewing a product: clicked Add to cart, or reached a Cart page.
Purchase funnel: began checkout	Count	Visits that began checkout after adding to cart: reached a Checkout page, or clicked Begin checkout.
Purchase funnel: purchased	Count	Visits that reached an Order confirmation page after beginning checkout.
Purchase funnel: viewed a product (%)	Ratio (%)	The share of visits that viewed a Product detail page.
Purchase funnel: added to cart (%)	Ratio (%)	The share of visits that viewed a product and then added to cart.
Purchase funnel: began checkout (%)	Ratio (%)	The share of visits that added to cart and then began checkout.
Purchase funnel: purchased (%)	Ratio (%)	The share of visits that began checkout and then reached an Order confirmation page.
First conversions	Count	Devices' first converting visits.
Converted on the first visit	Count	First conversions made on the device's first visit.
Converted on the first visit (%)	Ratio (%)	The share of first conversions made on the device's first visit.
Converted within 7 days	Count	First conversions made within 7 days of the device's first visit.
Converted within 7 days (%)	Ratio (%)	The share of first conversions made within 7 days of the device's first visit.
Median days to convert	Median	How many days after its first visit a device typically first converted, over first conversions. Short on Safari, which clears the device cookie after 7 days.
Median visits to convert	Median	How many visits a device typically took to first convert, that visit included, over first conversions.
First purchases	Count	Devices' first visits with a purchase.
Median days to first purchase	Median	How many days after its first visit a device typically first purchased, over first purchases.
Median visits to first purchase	Median	How many visits a device typically took to first purchase, that visit included, over first purchases.
Micro conversions followed by a purchase	Count	Visits with a micro conversion whose device has purchased since, in that visit or a later one.
Micro to purchase rate	Ratio (%)	The share of visits with a micro conversion whose device has purchased since, so far: a recent visit has had less time to.
Median days from micro conversion to purchase	Median	How many days after a micro conversion its device typically purchased, over those that have.
Orders	Sum	The orders Revenue adds up: each once, by Order transaction ID where that is labelled, by its own id for a Shopify order Kontala's Shopify pixel reported, and else once for each Order confirmation page view, counted in the first visit that reached it, and only where a value was read.
Revenue	Sum	The standard field Order value on Order confirmation pages, or a Shopify order's value as Kontala's Shopify pixel reported it, in the site's own currency, under the visit the order happened in: each order once, by Order transaction ID where that is labelled and by its own id for a Shopify order, so a reloaded confirmation page, in this visit or a later one, is not counted again. Empty, not zero, where neither says what an order came to.
Revenue per visit	Ratio	Revenue over every visit, converting or not.
Average order value	Ratio	Revenue per order.
Avg. landing scroll depth (%)	Average	How far down the page they landed on visitors got, averaged over the visits that measured it. Empty where the property does not capture scroll.
Back within 7 days	Count	First visits at least 7 days old whose device made another visit within 7 days of it.
7-day return rate	Ratio (%)	The share of first visits whose device came back within 7 days, over the first visits at least 7 days old. A visit ends after 30 idle minutes, so coming back later the same day counts. Empty while no first visit is 7 days old.
Back within 30 days	Count	First visits at least 30 days old whose device made another visit within 30 days of it.
30-day return rate	Ratio (%)	The share of first visits whose device came back within 30 days, over the first visits at least 30 days old. Low on Safari, which clears the device cookie after 7 days, so a visitor returning after that counts as a new device. Empty while no first visit is 30 days old.
Median days to return	Median	How many days after a first visit its device typically came back, over the first visits at least 30 days old that came back within 30 days. Empty while none has.

Who they were

Metric	Calculation	Description
Signed-in visits	Count	Visits in which anything named a signed-in user: the site's identify call, a captured login or an analytics tool's identify call.
Signed-in share	Ratio (%)	The share of visits in which anything named a signed-in user.
Signed-in users	Count distinct	Distinct user ids the visits named. They come from the application rather than a cookie, so Safari does not erode them, and the gap to Users is itself a measurement. A visit names its first user, so a second person signing in within one visit is not counted; ids count as sent, so Anna@x and anna@x are two.
Identified visitors	Count distinct	Distinct visitors, today devices, that signed in on some visit within the 400 days Kontala keeps, before, in or after this range, so a past range's count grows as visitors sign in later. Resolved in the warehouse, never written into a row. Bounded by the device cookie, which Safari clears after 7 days.
Identified share	Ratio (%)	The share of visitors that signed in on some visit, before, in or after this range: Identified visitors over Users.
Newly identified visitors	Count distinct	Visitors, today devices, whose first signed-in visit within the 400 days Kontala keeps was in range. A known person on a new browser counts again, and so does a Safari browser after 7 days.
Devices per signed-in user	Ratio	Devices with a signed-in visit per signed-in user: how many browsers a person uses. High on Safari, which clears the device cookie after 7 days, and low where people share a machine.
Active organisations	Count distinct	Distinct organisations the visits named: the org id the site's identify call, a captured login's company field or an analytics tool's group call gives.
New organisations	Count distinct	Organisations whose first visit within the 400 days Kontala keeps was in range, on any site and from any origin, so one first seen on a staging copy is new there, and one unseen for 400 days is new again on its return.
Signed-in users per organisation	Ratio	How many signed-in people each active organisation had, over the visits that named one.
Visits per organisation	Ratio	Visits per active organisation, over the visits that named one.
Converting organisations	Count distinct	Organisations with a visit that converted, macro or micro.
Last visit	Max	When the latest of these visits began.
Companies	Count distinct	Distinct company domains the visits' signed-in users' email addresses name, free mail providers left out.
Countries	Count distinct	Distinct countries the visits began in. IP Geolocation by DB-IP, licensed CC BY 4.0: a chart showing this must display that attribution.

The features it used

Metric	Calculation	Description
Visits with a typed page or click	Count	Visits that viewed a page or clicked something Kontala gives a type.
Visits with a typed page or click	Ratio (%)	The share of visits that viewed a page or clicked something Kontala gives a type: how much of what visitors do the feature figures can see. Confirming page and click types on their pages raises it.
Features per visit	Average	How many different features a visit used, on average.

What it met

Metric	Calculation	Description
Visits measured	Count	Visits measured for speed and friction: on a property that captures friction, with the visitor's consent.
Visits measured	Ratio (%)	The share of visits measured for speed and friction: how much of the traffic the friction figures speak for.
Visits with frustration	Count	Measured visits that met an error click, a rage click, a dead click or a quick back.
Visits with frustration	Ratio (%)	The share of measured visits that met an error click, a rage click, a dead click or a quick back.
Error-free visits	Count	Measured visits in which the page threw no uncaught error and left no promise's rejection unhandled.
Error-free visits	Ratio (%)	The share of measured visits with no JavaScript error, as Sentry's crash-free sessions count a browser's.
Visits with an error click	Count	Measured visits in which an error came within a second of a click.
Error clicks	Ratio (%)	The share of measured visits with an error click.
Visits with a rage click	Count	Measured visits with three clicks or more within a second of each other, in one spot.
Rage clicks	Ratio (%)	The share of measured visits with a rage click.
Visits with a dead click	Count	Measured visits with a click on something that looked clickable that nothing answered within a second.
Dead clicks	Ratio (%)	The share of measured visits with a dead click.
Visits with a quick back	Count	Measured visits in which the visitor went back from a page within 10 seconds.
Quick backs	Ratio (%)	The share of measured visits with a quick back.
Visits with a landing LCP	Count	Visits whose landing page measured its Largest Contentful Paint.
Visits with a slow landing	Count	Visits whose landing page's LCP was poor: over 4 seconds.
Slow landings	Ratio (%)	The share of visits with a measured landing LCP whose landing page took over 4 seconds to show its largest text or image.

Engaged time

Metric	Calculation	Description
Avg. engaged time per visit (s)	Average	Seconds a visit's screens were on show while its app was in the foreground, added up and averaged over the visits that measured it. Empty on the web.

Was this helpful?

Page views

Clicks