Download websites that use Oracle BlueKai

Not every third party on a page is there to render something. Oracle BlueKai belongs to the Segmentation category as a data management platform, and its function is to observe visitors and attach them to audience segments that can be bought and sold elsewhere. A site carrying the tag was not simply running ads, it had joined a pool of audience data that reached well beyond its own domain.

Our records credit the platform to Oracle under a Proprietary licence and date it to 2007, which places the product in the generation of advertising technology built when third party cookies were the default assumption of the web. Regulation and browser policy have moved a long way since, and the hosts that served the collection tag no longer resolve at all. Consent frameworks, tracker blocking and the retirement of cross-site cookies in several browsers all bear directly on a platform of this design, which is why an inventory of who still carries the tag is more interesting now than it was when such tags were unremarkable.

Detection here is inferential and worth stating plainly. The tag is frequently deployed through a tag manager, wrapped in a consent layer, or fired only after a visitor accepts tracking, so a crawler that does not consent may never see the request at all. Our figure counts sites where the fingerprint is visible in the delivered page, which means consent gated deployments are undercounted. Reading the number as a lower bound is the honest interpretation.

As of October 2026 we detect Oracle BlueKai on 475 sites. The audience for a list like that divides cleanly. Privacy researchers and regulators want to know where a given data platform still executes and under which consent regimes. Competing platforms want the accounts. Publishers and advertisers auditing their own supply chains want to discover which of their partners quietly pull in a third party they never contracted with, which is a recurring finding in tag audits and almost never visible from the outside without a population to compare against.

A single domain check answers a compliance question about one property. The dataset answers the population question: which domains carry the tag, under which country top level domains, alongside which other trackers, and how that set moves between exports. Movement over time is the useful axis for a platform of this vintage, because the story is consolidation and decline rather than growth, and decline is only measurable if you can count the same population twice.