Download websites that use eSputnik

eSputnik belongs to a category that says more about a business than most of the stack does. Nobody installs a marketing automation platform to make a page render. A site carries the tag because somebody behind it is running campaigns, which means lists, segments, abandoned-cart triggers, push notifications and messenger sends that all need a tracker on the storefront to know what the visitor did. The script is the visible end of a marketing operation.

Which platform a merchant chose is a commercial signal in its own right. eSputnik launched in 2012 and built its business on multi-channel sending for online retail, competing with the large international suites rather than with a plugin. A shop that picked a regional vendor is usually optimising for local billing, local support, local messenger channels and a price point the global platforms do not reach. Merchants of that profile behave differently from merchants on an enterprise suite, and they buy differently too.

The platform is Proprietary, which for a researcher is a convenience. There is no free self-hosted edition to confuse the picture, so a detection means a live account with a vendor relationship behind it rather than a copy of some open-source library a developer left in the page.

As of October 2026 the Customer data platform footprint we publish for this platform covers 5,485 sites. A per-domain lookup tells you what one shop uses today. A downloadable list is what you need when the question is a population question: who the current customers are, what else runs on those sites, which carts and payment providers the platform is paired with, and which shops appear or disappear between two exports. Competing vendors use a file like that for displacement targeting, agencies use it to size a service line, and integration builders use it to decide whether a connector is worth writing.

The usual caveat applies. We see the platform when a site loads something identifiable from it, so an account that only sends email and never places a tracker on the storefront can stay invisible to a crawler. Treat the count as a floor for the deployed base rather than as a customer total, and remember that a tag left in a template can outlive the account that put it there.