Download websites that use Linx Impulse

About Linx Impulse

Product search boxes and recommendation carousels are the parts of an online store that shoppers never read as separate software, which is exactly why detecting them is worth the effort. Linx Impulse lives in that layer. Our index files it under Personalisation and records it as JavaScript running in the shopper's browser, bought by the retailer and dropped into a storefront that keeps its own branding throughout.

The supplier on record is Linx (StoneCo) and the product is Proprietary, so every install is a paid relationship rather than a download. The entry dates from 2010, and the reference site we hold sits under a Brazilian domain, which is consistent with a retail technology business selling into that market. Where a corporate group is registered is not something a page fingerprint can establish, so the domain is the evidence and anything beyond it is inference.

Commercially, a dedicated search and personalisation layer is a qualifier rather than a curiosity. A retailer buys one after concluding that native storefront search is losing sales, and the decision usually travels with a large catalogue, a merchandising team and a budget line for conversion work. For a competing vendor that marks a replacement target with a contract somewhere behind it. For an integrator it marks a store already comfortable paying for third party ecommerce software.

As of October 2026 we record Linx Impulse on 1 site, and the number is a floor rather than a measurement. Personalisation scripts are frequently loaded through a tag manager, proxied behind the retailer's own domain, or rendered server side before the page is delivered, and each of those hides the vendor from a crawler reading finished HTML. Category listings and checkout paths, where this kind of software does most of its work, are also parts of a store that a crawl often never reaches.

A per-domain lookup answers whether one store runs this software today. The downloadable dataset answers the inverse, which is which stores across an entire crawl run it, what platform they sit on and which countries and top level domains they cluster in. The inverse is the question you cannot brute force, because answering it by lookup requires the list you were trying to build.