Download websites that use Nosto

About Nosto

A personalization service is not something a small shop installs on a whim. Nosto is sold as a A/B Testing layer for online retail, covering behavioural tracking, product recommendations, on-site campaigns and segmented messaging, and priced against the revenue it is meant to lift. Finding the tag on a domain therefore says something about the store underneath. Someone judged the catalogue large enough and the traffic valuable enough to pay for recommendations, and someone had the engineering time to place a tag across product pages.

Hosted services are often assumed to run one version everywhere, and version data says otherwise. We record 56 distinct release strings across the installed base, and 7.6.1 is a commonly recorded one. Fragmentation of that kind is normal for a script that ships in stages, gets pinned inside a theme, or is deployed through a tag manager and then left alone after launch. Release strings matter commercially, because a merchant several releases behind is a different conversation from one running a current build.

Detection is based on the tag present in the page, which means the finding describes the storefront rather than the back office. A merchant can run the service on some templates and not others, load it only for returning visitors, or hold it inside an experiment that serves a fraction of traffic. A crawl of a few pages will not see any of that. The count should be read as sites where the tag was visible when we looked, not as a customer register.

The vendor, Nosto, has sold into this market since 2011, long enough that the footprint mixes early adopters with recent arrivals. The product is Commercial, so each detection stands for a paying relationship rather than a free install, and the domains carrying it cluster in retail verticals where a recommendation engine can pay for itself. As of October 2026 the tag is visible on 599 sites.

A per-domain lookup answers a support question. A downloadable list answers a market question: which merchants run personalization at all, which commerce platforms they run it on top of, which releases they are pinned to, and which comparable stores run nothing of the kind. Competing vendors use the population to size a market and to find stores worth approaching. Integrators use it to find merchants already committed to a tag-driven stack. Analysts use it to watch adoption move between snapshots rather than to confirm a single site.