How to Tell If a Website Uses Kissmetrics

Kissmetrics is a person-based product and marketing analytics tool — one that ties every event to an individual across sessions and devices, rather than counting anonymous pageviews. Because it uses a distinctive command array and sets recognisable cookies, detecting it is straightforward: type _kmq into the console and look for km_ cookies. This guide covers every reliable signal, the person-based model behind them, the look-alikes to rule out, and what Kissmetrics usage tells you about the team and its business model. Because its person-based model ties events to identified individuals, recognising it also signals a site with known, logged-in users or captured leads rather than anonymous traffic.

What is Kissmetrics?

Kissmetrics is an analytics platform built around a person-based data model. Where general analytics focuses on sessions and pageviews, Kissmetrics focuses on individuals: it associates events with a specific person (identified by email or a user ID) and follows that person across visits and devices, enabling funnel, cohort and retention analysis at the individual level. It is aimed at SaaS and ecommerce/marketing teams that want to understand how specific users move through a funnel or product over time — who converted, who churned, and what they did. It competes conceptually with product-analytics tools (Amplitude, Mixpanel) but with a strong marketing-funnel and person-identity emphasis.

For detection, the key context is that Kissmetrics signals a team focused on person-level funnel and retention analytics — a SaaS or marketing operation that thinks in terms of identified users and their journeys, not anonymous traffic. Finding it tells you the team instruments events and identifies people to analyse behaviour over time. Because Kissmetrics uses the _kmq command array, loads from kissmetrics.io/kissmetrics.com, and sets km_ cookies, it is easy to confirm. Its presence marks a person-analytics-minded team.

How Kissmetrics loads and tracks

A Kissmetrics install uses the global window._kmq command array, pushing commands such as _kmq.push(['record', 'Viewed Pricing']) (events), _kmq.push(['identify', '[email protected]']) (tying events to a person), and _kmq.push(['set', {...}]) (properties). It loads its library and sends tracking via kissmetrics.io/kissmetrics.com (historically i.kissmetrics.com/scripts.kissmetrics.io, with tracking to trk.kissmetrics.io/trc.kissmetrics.com), and exposes a KM object. To maintain person-level identity across sessions, it sets first-party cookies prefixed km_ — km_ai (anonymous identity), km_uq (unsent event queue), km_lv (last visit) and km_vs (visit state).

So a Kissmetrics site shows the _kmq array, the kissmetrics.io/kissmetrics.com scripts/tracking, the KM object, and the km_ cookies. The identify calls (tying events to emails/IDs) are the behavioural signature of its person-based model. Knowing these — the _kmq array, the kissmetrics domains, the KM object, and the km_ cookies — makes detection reliable.

How to tell if a website uses Kissmetrics

Confirm at least one strong signal.

1. Use the console. Type _kmq and press Enter. A returned array confirms Kissmetrics; the KM object may also be present.

2. Check the Network tab. Filter for kissmetrics. Scripts and tracking on kissmetrics.io/kissmetrics.com confirm Kissmetrics.

3. Inspect cookies. Look for km_ai, km_uq, km_lv and km_vs cookies.

4. View the source. Search for kissmetrics or _kmq. The _kmq.push([...]) event and identify calls are usually visible.

5. Note identify calls. _kmq.push(['identify', ...]) tying events to a person is characteristic of Kissmetrics's person-based model.

What the Kissmetrics signals look like

var _kmq = _kmq || [];
_kmq.push(['record', 'Viewed Pricing']);
_kmq.push(['identify', '[email protected]']);
(function(){ … load from kissmetrics.io / kissmetrics.com … })();
Cookies: km_ai, km_uq, km_lv, km_vs

The _kmq array, the kissmetrics domain scripts/tracking, and the km_ cookies are conclusive.

Kissmetrics versus other analytics — avoiding false positives

Match the global and domains to keep analytics tools distinct. Kissmetrics uses _kmq, the kissmetrics domains and km_ cookies; Mixpanel uses cdn.mxpnl.com and a mixpanel global; Amplitude uses cdn.amplitude.com and an amplitude global; Heap uses heapanalytics.com and a heap global. The _kmq array and km_ cookies are unique to Kissmetrics. Like those product-analytics tools, Kissmetrics is person/event-based (not pageview-based), so it usually accompanies a general analytics tool (GA4) rather than replacing it. The identify calls and person-level cookies are Kissmetrics's distinctive person-based signature.

How reliable is each Kissmetrics signal?

The _kmq array and the km_ cookies are definitive, as are scripts/tracking on the kissmetrics domains. The KM object corroborates. The identify calls confirm the person-based model. The weakest situation is a site loading Kissmetrics via a tag manager or CDP, so check the live page — but the _kmq array and km_ cookies are present regardless. As a rule, the _kmq array or the km_ cookies settle it.

What Kissmetrics usage reveals about a team

Finding Kissmetrics signals a team focused on person-level funnel, cohort and retention analytics — a SaaS or marketing operation that thinks in terms of identified users and their journeys over time. Its person-based model and identify calls tell you the team ties behaviour to specific people (by email or ID), a more sophisticated, marketing-and-product-funnel approach than anonymous pageview analytics. If you sell product, marketing, data, or analytics tooling, a Kissmetrics site marks a team that already instruments events and analyses individual behaviour — a data-aware buyer. The presence of identify calls indicates the site has known/logged-in users (or captures emails), common in SaaS and lead-gen. As with other event-based tools, Kissmetrics usually coexists with GA4 (general analytics) rather than replacing it, so its presence adds the person-level dimension to the site's measurement.

What finding Kissmetrics means for sales, agencies and competitive research

For sales and prospecting, Kissmetrics marks a person-analytics-focused SaaS or marketing team — a fit for product, marketing, data and analytics tools. The identify usage signals a site with known users or captured leads.

For agencies and consultants, finding Kissmetrics tells you the client analyses individual funnels and retention, so engagements can focus on funnel optimisation, cohort analysis, or improving the person-level data model.

For competitive and market research, Kissmetrics (versus pageview analytics) reveals a competitor's person-based measurement approach and focus on funnels and retention, useful when benchmarking analytical maturity.

Kissmetrics in the wider stack

Kissmetrics sits in the person-analytics layer. It accompanies a general analytics tool (GA4) for traffic, often a CRM or marketing-automation platform (since person-level data ties to known contacts), and on SaaS the product application. It may be fed by a CDP. For an auditor, the valuable details are whether identify calls indicate known users, the events recorded, and the surrounding analytics, CRM and CDP tools; together these reveal a person-focused, funnel-and-retention-minded team and how it measures individual behaviour. The identify calls deserve particular attention, because they are the clearest expression of Kissmetrics's person-based philosophy and a useful signal in their own right: a site that ties events to email addresses or user IDs is one with known, logged-in users or captured leads — a SaaS product, a lead-generation funnel, or a membership site — rather than an anonymous content destination. So beyond confirming the tool, observing whether and how a site uses identify tells you something concrete about its business model and how directly it connects on-site behaviour to real, contactable people, which is exactly the context that makes the detection useful for sales, product or competitive analysis.

A quick Kissmetrics confirmation walkthrough

Open the site with developer tools on the Console panel and type _kmq — a returned array confirms Kissmetrics. Switch to the Network tab, filter for kissmetrics, and confirm scripts/tracking on kissmetrics.io/kissmetrics.com. Open the Application panel and look for km_ai, km_uq, km_lv and km_vs cookies. View the source for _kmq.push([...]) event and identify calls. The _kmq array or the km_ cookies confirm Kissmetrics.

A quick Kissmetrics detection checklist

• Type _kmq in the console; a returned array is conclusive.
• Filter the Network tab for kissmetrics; scripts/tracking on the kissmetrics domains confirm it.
• Check cookies for km_ai, km_uq, km_lv, km_vs.
• View source for _kmq.push(['record'/'identify', ...]) calls.
• Note identify calls indicating the person-based model.
• Distinguish Kissmetrics (_kmq, km_) from Mixpanel, Amplitude and Heap.

Detecting Kissmetrics at scale

Checking one site is quick, but mapping person-analytics adoption across many domains — to find funnel-and-retention-focused teams — calls for automation. StackOptic detects Kissmetrics and thousands of other technologies from a real browser, reading the global, domains and cookies. Because Kissmetrics ties events to identified people, finding it across a list reliably surfaces sites with logged-in users or captured leads — SaaS products and lead funnels rather than anonymous content destinations. For related reading, see our guide to finding out what analytics a website uses and the full Kissmetrics technology profile.