Download websites that use Treasure Data

About Treasure Data

Joining a customer record across a call centre, a loyalty scheme, a mobile app and a store estate is a problem that only appears above a certain size of business, and solving it usually means buying a platform and dropping a small collector script onto the public site. Detecting that collector is how a company's data ambition becomes visible from outside.

Treasure AI has run Treasure Data since 2011 on Proprietary terms, and the vendor address we hold now redirects to a site that carries the platform under the Treasure AI name and describes itself as formerly Treasure Data. A rename of that kind matters if you are tracking roadmaps, support commitments or contract risk rather than adoption alone.

As of October 2026 we detect Treasure Data on 25 sites. The count is small in absolute terms and that is what an enterprise data platform looks like from the outside, where one customer can represent an enormous deployment spread across brand domains that never carry the collector at all.

Presence implies a stack rather than a purchase. A company pulling behavioural data into a warehouse it controls has already built or bought identity resolution, audience export into ad platforms, a tag manager, a consent layer and somebody whose job is keeping the schema coherent. Reading a detected domain as a single-product signal understates it, because the surrounding spend is usually larger than the platform licence itself.

The list therefore reads differently depending on who opens it. Vendors selling adjacent tooling see qualified accounts with budget already allocated. Competing platforms see a switching population. Consultancies see companies that bought the engine and often still need help driving it. Analysts see a proxy for how far serious customer-data infrastructure has spread beyond the handful of industries that adopted it early.

The limits deserve equal space. Detection sees a collector, not a contract, so a proof of concept and a signed enterprise agreement look identical in the markup. We also see web collection only, which means mobile-only and server-side implementations stay invisible, and large data operations are often the ones collecting server-side. Our Customer data platform filing is coarse as well, since page analytics answers what happened during a visit while a customer data platform exists to join that visit to everything else the company knows about the same person.

A per-domain lookup confirms one company. A list answers which companies have made the same commitment, and that is the version of the question that supports a market map, a target account list or a study of how enterprise data tooling spreads.