Download websites that use Qubit

About Qubit

The vendor recorded against this entry is not the name in the script. Qubit was built and sold as an independent personalisation product and is now owned by Coveo, which is the ordinary end state for a mature experimentation vendor and a detail with real consequences for anyone reading the detection. A tag from an acquired product on a live site usually means one of two situations, a customer still under contract on the original platform, or a deployment that nobody has revisited since the acquisition closed.

Either situation is commercially legible. Personalisation and experimentation tools are among the harder pieces of a marketing stack to remove, because the rules, audiences and running tests are embedded in campaign operations rather than in the codebase. A retailer or travel brand that has invested in behavioural targeting does not migrate on a whim, so accounts detected on the platform are simultaneously sticky and, at a moment of ownership change, contestable. Competitors in the personalisation market and consultancies selling migration work are the obvious audiences for the list.

The technical shape of the deployment explains what we can and cannot see. The product runs as JavaScript loaded into the page, because the whole point is to modify what a visitor is shown before or during render, and code that manipulates the visible page has to reach the browser. Browser-side delivery is what makes fingerprinting possible at all. Products delivered server-side or through an edge worker leave no comparable trace, which is worth remembering when comparing this category across vendors.

Qubit has been in the market since 2010 and is sold on Proprietary terms, so every detection corresponds to a paid arrangement rather than a library someone dropped in. A paid arrangement is a stronger signal than an open source dependency, because it implies a budget holder, a contract and a renewal conversation.

As of October 2026 we detect it on 2 sites. A count that small should be read as a floor rather than as a market position. Enterprise personalisation is routinely deployed through a tag manager, behind consent gating that suppresses the script for an unconsented visitor, or through a first-party subdomain that disguises the vendor endpoint, and any of those will hide a live customer from source-level detection. Our figure counts the deployments visible in page source when we crawled.

A per-domain lookup tells you whether one brand you already suspected is running the platform. The downloadable list gives you the detected population in one file, joined to country, top-level domain and the rest of each site's stack, which is what you need in order to size a migration opportunity rather than to confirm a hunch.