Download websites that use GrowingIO

About GrowingIO

An analytics vendor is one of the few procurement decisions a company publishes by accident. The contract is private and the invoice is private, but the tag loads in the browser of every visitor, and each page view quietly names the company chosen to receive the behavioural data.

GrowingIO belongs to the Analytics category, dates in our record to 2015, and is delivered as JavaScript running in the visitor's browser under a Proprietary license. Products in this space compete on how little manual instrumentation a customer has to write, because the real cost of analytics is rarely the subscription and almost always the engineering time spent tagging events. A team that has adopted a platform of this kind has usually sunk a year of that work into it, which is why analytics choices change slowly and why a snapshot of them stays accurate longer than most stack facts.

Version data points the same way as the delivery model. Our record holds a single release line, 2.1, across every site where a version is visible at all, and a population that uniform is not a population of independent installs. The vendor ships one build to everyone. Site owners neither choose a release nor fall behind on one, so version is useless as a segmentation axis for this product, unlike a self-hosted tool where version spread maps directly onto operator behaviour.

Detection has a specific weakness worth stating plainly. Analytics tags are increasingly loaded through a tag manager, or proxied through a first-party endpoint on the customer's own domain to survive tracker blocking, and both arrangements hide the vendor's script address from a fingerprint that looks for exactly that address. As of October 2026 we see the tag on 6 sites, and the real deployment count is higher by a margin nobody can quantify. The direction of the error is at least known, which is more than can be said for most estimates of software adoption.

Who wants the list is no mystery. Competing analytics vendors build displacement campaigns from exactly this kind of set, agencies use it to size a market before entering it, and privacy researchers use it to trace which third parties receive event data from which sites and under which jurisdiction. A per-domain lookup answers a question about one site, and that is the wrong shape for all three jobs. The dataset inverts the lookup and hands over the population, which is the only form in which those questions can be asked at all.