Download websites that use Rakuten

About Rakuten

A retailer does not choose Rakuten the way it chooses a shopping cart or a payment gateway. The script arrives on a site because a commercial relationship already exists behind it, usually a marketplace listing, an affiliate partnership, a cashback arrangement or a loyalty integration. What the code does technically is modest. What the code says about the business running the site is not.

Rakuten operates the ecosystem behind the tag, and the pieces of it reach back to 1997. Over that span the same corporate group accumulated a marketplace, a cashback business, media properties and an advertising network, and several of them ship client side code of their own. A researcher who sees the Affiliate programs classification on this page should read it as a centre of gravity rather than a boundary, because a single site may carry the tag for reasons that have little to do with selling goods through the marketplace itself.

As of October 2026 we detect Rakuten on 1,177 sites. The delivery mechanism is JavaScript executed in the visitor's browser, which is what makes detection possible at all and also what limits it. Tags injected through a tag manager, loaded conditionally by consent tooling, or moved behind a server side collector will be missed by a crawl that fetches a page once and never clicks. Regional storefronts on separate domains fragment the picture further. The count is best read as a floor for visible participation rather than as a census of every business holding a contract.

One further caution matters before the data is used. The corporate group also operates a separate advertising and affiliate network that we track under its own entry, and the two leave different fingerprints for different reasons. Treating every detection of the group's code as one population will double count sites that carry both, and will blur the distinction between a merchant selling through the marketplace and a publisher earning commission on links. Keeping the two entries separate is the whole point of listing them separately.

The reason to want the whole list rather than a lookup on one domain is that a single positive result tells you almost nothing on its own. A channel manager wants to know which competitors already sit inside the same affiliate and marketplace ecosystem. An agency wants a prospect list of retailers who have proven they will integrate a partner tag at all. A payments or logistics vendor wants the subset that overlaps with its own footprint. Every one of those is a set operation, and set operations need the set. The downloadable file gives each detected domain with the rest of its detected stack alongside it, so the partnership question can be crossed against platform, country and technology in one pass instead of thousands of individual checks.