Download websites that use Drip

About Drip

A shop can replace its theme, its payment provider and its agency and still be running the automation sequences it wrote years earlier, because those sequences are what turns a first order into a second one and nobody volunteers to rebuild them. Email outlives every redesign around it.

Drip sits in that durable layer. The Marketing automation category covers tools that watch behaviour on a site and act on it days later, and what a crawler sees is the JavaScript tag that handles the watching part: a page view, a product view, an abandoned cart, an email address matched back to a profile on the vendor's servers. The tag is the visible edge of a system whose interesting half runs somewhere else entirely.

The service is Proprietary and dates from 2013, from the wave of tools built for online stores rather than for publishers or enterprises, and the implication of a match follows from that lineage. A site carrying the tag has usually bought into behaviour triggered messaging rather than a monthly newsletter, which in turn implies a catalogue, repeat purchases and somebody employed to look after a funnel. For a researcher hunting merchants above hobby scale, that tag filters harder than the storefront platform does, because every storefront platform carries a long tail of empty shops.

As of October 2026 we detect Drip on 3 sites, and the installed base is larger than the count. Loading through a tag manager, proxying the script from the merchant's own domain and forwarding events server side all remove the static evidence a crawler depends on, and a tag placed only on checkout pages is invisible to a crawl that stops at the front door. The name is also an ordinary English word, so it is worth being explicit that our figure counts a fingerprint match on the vendor's own script rather than any use of the term.

Email tooling churns faster than the platform underneath it, which is what makes the population interesting over time rather than as a snapshot. Checking one domain answers a sales question about one prospect. The export answers a market question: which stacks the tool coexists with, whether it clusters around a particular storefront or payment processor, and which sites carry it in one month's file and a competitor's tag in the next. Agencies use those transitions for prospecting, vendors read them as win and loss evidence, and neither use is possible from a lookup that only ever sees one domain at a time.