How to Tell If a Website Uses Clicky Analytics

Clicky (made by Roxr Software) is a long-established real-time web analytics tool known for showing individual visitors and their actions live as they happen. To tell whether a site uses it, the fastest checks are to look for a script from static.getclicky.com and a hit to in.getclicky.com/in.php, or to read the clicky_site_ids global. This guide covers every reliable signal and what the find means.

What is Clicky?

Clicky is an independent analytics platform that has been running since the mid-2000s, with a distinctive focus on real-time, per-visitor reporting. Where Google Analytics emphasises aggregate trends, Clicky lets you watch individual visitor sessions unfold live — the pages they view, the actions they take, where they came from — and layers on heatmaps, uptime monitoring and goal tracking. It positions itself as detailed, granular and privacy-respecting (it supports anonymised tracking and can run without cookies in a restricted mode).

Its accessible pricing and real-time depth have long made it popular with bloggers, independent publishers, small businesses and hobbyist site owners who enjoy watching their traffic in real time. Detecting Clicky therefore often points to a hands-on owner who cares about individual visitor behaviour rather than just monthly totals. Clicky has also remained deliberately independent and stable over nearly two decades, which is part of its appeal to owners who distrust the churn and complexity of larger platforms. It supports privacy-friendly options such as IP anonymisation and a cookie-free mode, so on some sites you will find it configured to track without persistent identifiers — a configuration detail worth checking, because it changes which signals you can rely on.

How Clicky loads and sends data

A Clicky install defines a global clicky_site_ids array holding the numeric site ID, then loads the tracking script from static.getclicky.com/js (sometimes referenced as getclicky.com). When a page loads, the script sends a hit to in.getclicky.com/in.php carrying the site_id and details of the page view. For custom interactions it exposes a global clicky object with methods like clicky.log() and clicky.goal().

Returning visitors are identified with a _jsuid cookie (and Clicky may set additional state cookies). The static.getclicky.com script, the in.getclicky.com/in.php beacon and the clicky_site_ids array are the cleanest, most reliable signals.

How to tell if a website uses Clicky

1. View the page source. Search for getclicky, clicky_site_ids or clicky. You will find the clicky_site_ids array definition and the static.getclicky.com script reference.

2. Check the Network tab. Filter for getclicky. You will see the tracking script load from static.getclicky.com and a hit to in.getclicky.com/in.php?site_id=.... That in.php beacon is the definitive recording request.

3. Use the console. Type clicky_site_ids to read the site ID array, and clicky to inspect the tracking object. Both confirm the install.

4. Inspect cookies. Look for the _jsuid cookie (and other clicky-related cookies).

5. Note the site ID. The numeric site_id in the clicky_site_ids array and the in.php request identifies the Clicky account.

What the Clicky signals look like

var clicky_site_ids = clicky_site_ids || []; clicky_site_ids.push(12345);
GET https://static.getclicky.com/js
GET https://in.getclicky.com/in.php?site_id=12345&type=pageview&href=/pricing&...
Cookie: _jsuid = "..."

The combination of the static.getclicky.com script, the in.getclicky.com/in.php beacon and the clicky_site_ids array is conclusive.

Clicky versus similar tools — avoiding false positives

Clicky's real-time, independent positioning puts it near tools like StatCounter, Matomo and the privacy-first set, but its fingerprint is distinct: getclicky.com hosts and the clicky_site_ids global are unique to it. Do not confuse the generic clicky object name with unrelated click-tracking scripts — confirm with the getclicky.com host. Clicky can be deployed via a CMS plugin (it has popular WordPress integrations) or a tag manager, so the script may load slightly later; check the live page. Its older snippets vary in form, but the clicky_site_ids array and the in.php beacon are consistent across versions.

How reliable is each Clicky signal?

The in.getclicky.com/in.php beacon is definitive — it is the hit being recorded. The clicky_site_ids array and the static.getclicky.com script are equally strong and reveal the site ID. The _jsuid cookie is reliable corroboration. The generic clicky global is supportive but should be paired with a getclicky.com host to rule out unrelated scripts. As ever, the live beacon or the site-ID array settles it.

What a Clicky install reveals about a company

Clicky's audience skews toward independent site owners, bloggers, publishers and small businesses who value detailed, real-time visibility into their traffic at an affordable price. Finding it suggests a hands-on owner who likes to watch individual visitor behaviour and react quickly, rather than a large team relying on aggregate dashboards. It also signals a degree of independence from the Google ecosystem, which can correlate with a broader preference for lean, self-directed tooling. If you sell to independent publishers or small businesses, a Clicky install marks an engaged, analytics-curious owner who already invests in understanding their audience.

Clicky in a small-publisher stack

Clicky commonly appears within a lightweight publisher or small-business stack: a WordPress or static site, perhaps a newsletter tool, modest advertising, and Clicky for real-time stats — sometimes alongside Google Analytics as a more enjoyable day-to-day dashboard. Because Clicky offers uptime monitoring and goals, it may be doing more than analytics on the site. For an auditor, record the site ID, the host CMS, whether GA also runs, and whether Clicky's heatmap or uptime features appear to be in use; together these describe a hands-on, real-time-oriented owner and the kind of complementary tools they are likely to value.

A quick Clicky confirmation walkthrough

Open the site with developer tools on the Network panel, filter for getclicky and reload. The hit to in.getclicky.com/in.php with a site_id is your conclusive signal, and the static.getclicky.com script confirms the library. Switch to the Console and type clicky_site_ids to read the numeric site ID, then clicky to inspect the tracking object. Check the Application panel for the _jsuid cookie. In under two minutes you have confirmed Clicky and captured the site ID, which is useful when profiling a network of sites that may share an account.

A quick Clicky detection checklist

• Filter the Network tab for getclicky; the in.getclicky.com/in.php hit is conclusive.
• Search the source for clicky_site_ids and the static.getclicky.com script.
• Read clicky_site_ids in the console for the site ID; inspect the clicky object.
• Check cookies for _jsuid.
• Confirm the getclicky.com host to avoid confusing the generic clicky name.
• Note the site ID to identify the account.

Why detecting Clicky matters across teams

For sales and prospecting, a Clicky install points to an engaged, hands-on site owner — typically a blogger, publisher or small business that enjoys watching its traffic in real time. That profile is receptive to tools and services that promise more visibility or easier wins: SEO products, content tools, ad-management services and analytics upgrades all land well with an owner who already checks their stats daily. Because Clicky is inexpensive, it also signals price sensitivity, so value-led positioning works better than enterprise pricing.

For agencies and consultants, finding Clicky tells you the client cares about individual visitor behaviour and real-time feedback, so you can frame work around responsiveness — live campaign monitoring, rapid content iteration, conversion tweaks they can watch take effect. It can also flag a site that has outgrown a hobbyist tool and would benefit from a more structured analytics and reporting setup, which is a natural upgrade conversation.

For competitive research, spotting Clicky on a rival's site suggests a lean, independent operator paying close attention to its audience rather than a large team buried in dashboards. And for migration or modernisation work, Clicky's presence — especially with a visible counter — can date a site and hint at where a refresh would add value. In each case, the real-time, per-visitor nature of Clicky tells you something specific about how the owner relates to their traffic, which is more actionable than simply noting "they have analytics".

Detecting Clicky at scale

One page is a quick console check. To scan a list of sites for Clicky, automate it. StackOptic detects Clicky and thousands of other technologies from a real browser, catching plugin- and tag-manager-injected installs. This is especially useful when profiling a network of blogs or small-business sites that might share a single Clicky account, since the site IDs let you spot common ownership. Tracking the results over time also reveals when a site upgrades from Clicky to a heavier analytics platform — a growth signal worth acting on, because it often coincides with a budget increase and a willingness to invest in new tooling. See how to find out what analytics a website uses and the Clicky profile for more.