Download websites that use Permutive

About Permutive

Audience data platforms sit at the point where a publisher decides whether to hand its readers to somebody else's targeting stack or to build the segments itself. Permutive represents the second answer. A publisher installing it is choosing to treat its own audience data as an asset it sells directly, rather than as raw material collected by intermediaries in exchange for demand.

Permutive is filed under Advertising, comes from Permutive, has been in the market since 2014 and reaches the page as JavaScript under a Proprietary licence. The delivery model explains what an install actually implies. A behavioural data layer running on every article page is only worth operating where there are enough page views for segments to be statistically meaningful and enough direct advertiser relationships to sell those segments into. Publishers with a small audience and a purely programmatic monetisation model have no use for the machinery.

Presence is therefore a fair proxy for a particular kind of media business: substantial traffic, an ad operations team, direct sales conversations with agencies and brands, and an active position on how targeting should work as third party identifiers become less reliable. Agencies planning campaigns without those identifiers need to know which publishers can offer first party segments. Competing data platforms need to know which properties are already committed. Privacy researchers auditing what actually executes on news sites need the same list from the opposite direction. None of those questions is about a single domain.

As of October 2026 we detect Permutive on 62 sites, and the number needs framing. Customers here are media groups rather than individual pages, so one commercial relationship can cover many domains or a single domain carrying enormous traffic, and the site count says nothing about reach. Detection has a specific weakness on this category too: scripts of this type are frequently loaded only after a consent decision, and a crawler that does not accept a consent prompt will never see the tag fire. The count is the subset visible without consent, which for a privacy oriented tool is an understatement by design.

The list earns its place by answering the population question. Checking one publisher confirms one relationship. The export shows how many publishers in a market have taken this route, which consent platforms and ad servers appear alongside it, how the group is distributed across countries and suffixes, and whether it grew or shrank since the last snapshot. That is a picture of an industry changing its data strategy, and it cannot be assembled one lookup at a time.