How to Tell If a Website Uses Contentsquare

Contentsquare is an enterprise digital-experience analytics platform — the heavyweight cousin of tools like Hotjar and FullStory, used by large retail, finance and travel brands. It absorbed ClickTale and, more recently, Heap. To detect it, look for the t.contentsquare.net/uxa script or the global _uxa array. Here is the full detection guide and why the find matters.

What is Contentsquare?

Contentsquare is a premium experience-analytics suite that captures every interaction on a site and turns it into journey analysis, zone-based heatmaps, frustration scoring and revenue attribution. It targets large enterprises with dedicated experience-analytics, UX and conversion teams, and it competes at the top of the market against Adobe and Glassbox. Through acquisitions it now also encompasses ClickTale (session replay) and Heap (product analytics), so its footprint spans several analytics disciplines.

Because Contentsquare is expensive and team-intensive to run, detecting it is a strong enterprise signal: you are almost always looking at a major brand with significant digital revenue and budget.

How Contentsquare loads and sends data

A Contentsquare install defines a global _uxa array (a command queue, conceptually like GA's dataLayer or Matomo's _paq) and loads its UXA library from t.contentsquare.net/uxa/<id>.js. The library reads the queued commands and streams captured interaction data to *.contentsquare.net endpoints (with some legacy deployments still touching ClickTale hosts) throughout the session.

Visitor and session state live in first-party cookies prefixed _cs_ — _cs_id (visitor), _cs_s (session) and _cs_c (consent). The t.contentsquare.net UXA script and the _uxa queue are the cleanest signals.

How to tell if a website uses Contentsquare

1. View the page source. Search for contentsquare, _uxa or uxa. You will find the _uxa array definition and the t.contentsquare.net/uxa/<id>.js script reference.

2. Check the Network tab. Filter for contentsquare. You will see the UXA script load from t.contentsquare.net and streamed data to *.contentsquare.net. The ongoing requests are characteristic of an experience-capture tool.

3. Use the console. Type _uxa and press Enter. If Contentsquare is present you get an array back. Some deployments also expose CS_ globals.

4. Inspect cookies. Look for _cs_id, _cs_s and _cs_c. The _cs_ prefix is distinctive.

5. Note the tag/site ID. The numeric ID in the uxa/<id>.js path identifies the Contentsquare project.

What the Contentsquare signals look like

GET https://t.contentsquare.net/uxa/12345.js
window._uxa = [ ["trackPageview", ...], ... ]
Cookie: _cs_id = "..."
Cookie: _cs_s  = "..."

The combination of the t.contentsquare.net/uxa script, the _uxa array and the _cs_ cookies is conclusive.

Contentsquare versus similar tools — avoiding false positives

Within experience analytics, match the exact fingerprint. Contentsquare uses t.contentsquare.net and _uxa; FullStory uses edge.fullstory.com and FS; Hotjar uses static.hotjar.com and hj; Glassbox and Quantum Metric have their own hosts. Because Contentsquare acquired Heap, you may see Heap (heapanalytics.com, heap global) on the same property — note both. And since Contentsquare is enterprise software usually deployed through a tag manager, the UXA script may appear only after the tag manager runs, so check the live page rather than the static source.

How reliable is each Contentsquare signal?

The t.contentsquare.net/uxa/<id>.js request is definitive, as is active streaming to *.contentsquare.net. The _uxa array is strong, though, like any queue global, confirm it alongside the script or cookies. The _cs_ cookies are reliable corroboration. A legacy ClickTale reference without modern Contentsquare traffic is the weakest signal and may indicate an old, migrated implementation. Prefer the UXA script and the _cs_ cookies.

What a Contentsquare install reveals about an organisation

Contentsquare is enterprise-grade and priced accordingly, so its presence almost always means a large organisation with real digital revenue — major ecommerce, banking, insurance, travel and telecoms brands are typical. It signals a dedicated experience-analytics, UX or CRO team and a culture of optimising the customer journey at scale. For enterprise sellers, that is a high-value qualifying signal: budget, a relevant team, and a demonstrated belief in experience analytics. For agencies, a Contentsquare deployment can flag specialist implementation, analysis or integration work.

Contentsquare in a modern enterprise stack

Contentsquare rarely stands alone. Expect it alongside an enterprise analytics platform (Adobe Analytics or GA4 360), a tag manager (Tealium, Adobe Launch or GTM), a consent-management platform, and — given the acquisition — possibly Heap. The combination paints a picture of a sophisticated, well-resourced digital organisation. For an auditor, record the tag ID, whether Heap coexists, which enterprise analytics platform is present, and the consent setup; those facts both size the account and reveal how its experience-analytics practice is structured.

A quick Contentsquare detection checklist

• Filter the Network tab for contentsquare; the t.contentsquare.net/uxa/<id>.js load is conclusive.
• Search the source for _uxa and the UXA script reference.
• Type _uxa in the console and confirm an array is returned.
• Check cookies for _cs_id, _cs_s and _cs_c.
• Look for Heap (heap global) on the same property, given the acquisition.
• Confirm the UXA script loads, not just a tag-manager reference.

Privacy, masking and consent with Contentsquare

As enterprise experience analytics, Contentsquare captures interaction data at scale, so privacy governance is a serious part of any deployment — and a revealing thing to audit. Contentsquare supports masking and exclusion of sensitive elements, and enterprise customers typically run it behind a consent-management platform and a tag manager that enforces consent mode. When you inspect a Contentsquare site, check the sequence: the consent banner, the CMP, the tag manager, then the t.contentsquare.net UXA script. A compliant enterprise deployment will hold the UXA tag until analytics consent is granted; if you see it stream to *.contentsquare.net regardless of choice, that is a notable compliance finding for a brand that almost certainly has a legal obligation to get it right.

For detection, the consequence is the same as for any consent-gated tool: on a strict deployment the UXA script may not load until you accept analytics cookies, so accept and reload before concluding it is absent. Because Contentsquare is enterprise software, it is also more likely than SMB tools to use server-side or first-party-proxied delivery, so be ready to rely on the _uxa queue and the _cs_ cookies if the obvious t.contentsquare.net host is masked behind a custom domain.

A quick Contentsquare confirmation walkthrough

Open the site with developer tools on the Network panel and clear the cookie banner. Filter for contentsquare and reload: the t.contentsquare.net/uxa/<id>.js load is your primary signal, with streamed data to *.contentsquare.net confirming capture. Switch to the Console and type _uxa — a returned array confirms the command queue is present. Then open the Application panel and look for _cs_id, _cs_s and _cs_c cookies. Note the tag ID from the UXA path, and check separately for Heap (heap global), since Contentsquare now owns it and the two sometimes appear together.

When finding Contentsquare matters most

Contentsquare is one of the strongest enterprise signals you can find: it rarely appears outside large retail, finance, travel, telecoms and media brands with real digital revenue and dedicated experience teams. For enterprise sellers, that means a qualified account with budget, a relevant buying centre, and a demonstrated belief in experience analytics — you are not starting from zero on why it matters. For agencies and consultancies, a Contentsquare deployment flags specialist implementation, tagging and analysis work, a high-value and sticky service line. And for competitive intelligence, knowing a rival runs Contentsquare tells you they can quantify journey friction and revenue impact at a level most mid-market competitors cannot match.

How Contentsquare compares to Hotjar and the enterprise field

Contentsquare sits at the top of the experience-analytics market, so comparing it to mid-market tools clarifies what a find means. Hotjar and Microsoft Clarity are accessible, largely self-serve tools aimed at individual teams optimising specific pages; Clarity is free, Hotjar is freemium. Contentsquare operates in a different tier entirely: enterprise pricing, professional-services-led onboarding, and capabilities those tools do not match — journey analysis across millions of sessions, zone-based revenue attribution, automated friction scoring, and integrations with the wider martech stack. Its closest peers are Adobe (Analytics plus Customer Journey Analytics), Glassbox and Quantum Metric, not Hotjar.

That tier difference is the intelligence. Where a Hotjar or Clarity install can belong to any team with a credit card or none, a Contentsquare deployment almost always means a large brand with significant digital revenue, a dedicated experience-analytics function, and a procurement-driven buying process. Through its acquisitions of ClickTale and Heap, Contentsquare may also appear alongside those tools, signalling an even broader analytics investment. For enterprise sellers, recognising Contentsquare rather than mistaking it for a generic heatmap tool fundamentally changes the account's qualification and the size of the opportunity; for agencies, it points to specialist, high-value work that mid-market tools never generate.

Detecting Contentsquare at scale

One page is a quick console check. To find enterprise sites running Contentsquare across a list, automate it. StackOptic detects Contentsquare and thousands of other technologies from a real browser, including tag-manager-injected deployments. See how to find out what analytics a website uses and the Contentsquare profile for more.