How to Tell If a Website Uses Inspectlet

Inspectlet is a long-running session-recording and heatmap tool, used to watch real user sessions and visualise clicks, scrolling and attention to optimise conversion. Because it loads a distinctive script and uses a clear command array, detecting it is straightforward: look for cdn.inspectlet.com/inspectlet.js and the global __insp array. This guide covers every reliable signal, the recording model behind them, the other session-replay tools to distinguish it from, and what Inspectlet usage tells you about the team and how much it invests in conversion optimisation. Because Inspectlet is one of the more affordable, longer-established replay tools, recognising it also hints at a pragmatic, cost-conscious CRO approach rather than an enterprise one.

What is Inspectlet?

Inspectlet is a qualitative analytics tool in the session-replay and heatmap category (alongside Hotjar, FullStory, Lucky Orange, Crazy Egg and Microsoft Clarity). It records individual user sessions as replayable videos, builds heatmaps (click, scroll and attention maps), provides form analytics (where users abandon forms) and funnels. Its purpose is conversion-rate optimisation (CRO) and UX research — letting teams watch what real users actually do, find friction, and improve the experience. It is used by marketing, product and CRO teams across many kinds of sites.

For detection, the key context is that Inspectlet signals a team investing in qualitative UX and conversion optimisation — studying session-level behaviour rather than just aggregate metrics. Finding it tells you someone is actively watching replays and heatmaps to improve the site. Because Inspectlet loads from cdn.inspectlet.com and uses the __insp command array (with the website ID), it is easy to confirm, and the wid identifies the account. Its presence marks a CRO/UX-conscious operation, much like the other session-replay tools but with Inspectlet's specific fingerprint.

How Inspectlet loads and records

An Inspectlet install uses the global window.__insp command array, pushing the website ID with __insp.push(['wid', 1234567]) and other commands, and sets a __inspld flag once the library loads. It loads the recorder from cdn.inspectlet.com/inspectlet.js (the snippet typically constructs this URL dynamically). Once running, it records the session — serialising the DOM and user interactions — and streams the data to hn.inspectlet.com (its capture/host endpoint) continuously, as is characteristic of a replay tool.

The wid identifies the Inspectlet account, and the cdn.inspectlet.com/hn.inspectlet.com domains are the load and capture endpoints. So an Inspectlet site shows the __insp array (with wid), the cdn.inspectlet.com/inspectlet.js script, the __inspld flag, and hn.inspectlet.com streaming. Knowing these — the __insp array and wid, the cdn.inspectlet.com script, and the hn.inspectlet.com traffic — makes detection quick and account-identifiable.

How to tell if a website uses Inspectlet

Confirm at least one strong signal.

1. Check the Network tab. Filter for inspectlet. The cdn.inspectlet.com/inspectlet.js script and streaming to hn.inspectlet.com confirm Inspectlet.

2. Use the console. Type __insp and press Enter. A returned array (with a wid) confirms Inspectlet; __inspld indicates the library loaded.

3. View the source. Search for inspectlet or __insp. The __insp.push(['wid', ...]) configuration and the script construction are usually visible.

4. Read the wid. The website ID pushed onto __insp identifies the Inspectlet account.

5. Note the streaming. Continuous data to hn.inspectlet.com reflects active session recording.

What the Inspectlet signals look like

window.__insp = window.__insp || [];
__insp.push(['wid', 1234567]);
(function(){ … var x=document.createElement('script'); x.src='//cdn.inspectlet.com/inspectlet.js?wid=1234567&...'; … })();
window.__inspld = 1;
POST https://hn.inspectlet.com/...   (streamed session data)

The __insp array with a wid, the cdn.inspectlet.com/inspectlet.js script, and hn.inspectlet.com streaming are conclusive.

Inspectlet versus other replay tools — avoiding false positives

Match the domain and global to keep session-replay tools distinct. Inspectlet uses cdn.inspectlet.com/hn.inspectlet.com and the __insp array; Hotjar uses static.hotjar.com and hj/_hjSettings; FullStory uses edge.fullstory.com and FS; Lucky Orange uses tools.luckyorange.com and __lo_site_id; Microsoft Clarity uses clarity.ms and clarity; Smartlook uses web-sdk.smartlook.com. The __insp array and inspectlet.com domains are unique to Inspectlet. As with all replay tools, the continuous capture traffic is normal, and Inspectlet can be loaded via a tag manager, so check the live page. Privacy considerations (input masking, consent gating) apply as they do to all session recorders.

How reliable is each Inspectlet signal?

The __insp array with a wid and the cdn.inspectlet.com/inspectlet.js script are definitive, as is streaming to hn.inspectlet.com. The __inspld flag corroborates. The wid identifies the account. The weakest situation is consent-gated recording that loads only after opt-in, so accept cookies and re-check if needed. As a rule, the __insp array or the cdn.inspectlet.com script settles it, and the wid identifies the account.

What Inspectlet usage reveals about a site

Finding Inspectlet signals a team investing in qualitative UX and conversion optimisation — watching session replays, heatmaps and form analytics to find and fix friction. Its presence tells you someone (marketing, product or a CRO specialist) actively studies how real users behave on the site, a sign of optimisation maturity beyond aggregate analytics. The form-analytics feature, if in use, indicates attention to form conversion specifically. If you sell CRO, UX research, analytics or optimisation tooling, an Inspectlet site marks a buyer who already values qualitative insight. As with other replay tools, privacy handling (masking, consent) is worth checking, and the wid lets you tie the recording to the account. Inspectlet's presence places the site in the CRO/UX-conscious segment, alongside (or instead of) tools like Hotjar.

What finding Inspectlet means for sales, agencies and competitive research

For sales and prospecting, Inspectlet marks a CRO/UX-conscious team that studies session-level behaviour — a fit for CRO, UX research, optimisation and analytics tools.

For agencies and consultants, finding Inspectlet tells you the client values qualitative insight, so engagements can build on session and heatmap data to drive conversion improvements, form optimisation, or UX research.

For competitive and market research, Inspectlet (versus Hotjar, Clarity or none) reveals a competitor's qualitative-analytics choice and that they study session behaviour, useful when benchmarking optimisation maturity.

Inspectlet in the wider stack

Inspectlet sits in the qualitative-analytics layer. It complements rather than replaces quantitative tools, so it typically accompanies general analytics (GA4) and possibly a product-analytics tool, plus A/B testing (since CRO teams test and watch), forms, and conversion tooling. Privacy-conscious deployments pair it with field masking and a consent-management platform. For an auditor, the valuable details are the wid, whether form analytics is in use, the privacy/consent setup, and which quantitative analytics and testing tools accompany it; together these reveal a CRO/UX-focused team and how it blends qualitative and quantitative optimisation. It is worth placing Inspectlet in the broader session-replay landscape, because the specific tool a team chooses is itself informative. Inspectlet is one of the longer-established, more affordable options, so its presence often points to a pragmatic, cost-conscious team — or one that adopted session replay years ago and stuck with it — rather than the enterprise profile implied by FullStory or Contentsquare, or the free-and-ubiquitous profile of Microsoft Clarity. Reading which replay tool a site runs, and how prominently it appears, therefore tells you not just that the team optimises conversion but roughly how much it invests in doing so, which sharpens any pitch built around CRO or UX research.

A quick Inspectlet confirmation walkthrough

Open the site with developer tools on the Network panel and filter for inspectlet — the cdn.inspectlet.com/inspectlet.js script and streaming to hn.inspectlet.com confirm it. In the console, type __insp to confirm the array and read the wid; check __inspld. View the source for the __insp.push(['wid', ...]) configuration. If recording is consent-gated, accept cookies and re-check. The __insp array or the cdn.inspectlet.com script confirms Inspectlet.

A quick Inspectlet detection checklist

• Filter the Network tab for inspectlet; the cdn.inspectlet.com/inspectlet.js script and hn.inspectlet.com streaming are conclusive.
• Type __insp in the console; a returned array with a wid confirms it (__inspld flags loaded).
• View source for the __insp.push(['wid', ...]) configuration.
• Read the wid to identify the account.
• Re-check after accepting cookies if recording is consent-gated.
• Distinguish Inspectlet (__insp, inspectlet.com) from Hotjar, FullStory, Clarity and Lucky Orange.

Detecting Inspectlet at scale

Checking one site is quick, but mapping session-replay-tool adoption across many domains — to find CRO/UX-conscious teams — calls for automation. StackOptic detects Inspectlet and thousands of other technologies from a real browser, reading the script, global and capture traffic. Mapping which replay tool each site in a market runs — Inspectlet versus Hotjar, Clarity, FullStory or none — quickly segments a sector by how much its teams invest in qualitative conversion research. For related reading, see our guide to finding out what analytics a website uses and the full Inspectlet technology profile.