Download websites that use Segment Consent Manager

A consent banner is the only part of a privacy programme a crawler can see. Contracts, retention schedules and processing agreements leave no trace in a page, while the small dialog asking a visitor what may be tracked sits right there in the markup. Segment Consent Manager is one implementation of that dialog, built to switch analytics destinations on and off according to what a visitor allowed. Our index files it under Privacy / Consent, credits Twilio, records a MIT license, dates it to 2018 and lists JavaScript as the implementation language.

An open license changes what a detection means. Because the component is MIT licensed, it gets copied into a site's own build rather than loaded from a vendor endpoint, so a match implies no contract, no invoice and no ongoing relationship with anyone. Whoever deployed it took a piece of source code and made it their own problem, which describes a very different buyer from a company paying a managed consent platform every month.

Version data shows what that ownership looks like in practice. Our records carry 5.3.0 for it, out of 11 distinct version strings seen across the detected sites. A spread of that size on a component with one narrow job tells a familiar story, which is that a consent dialog gets installed once, pinned to whatever release was current, and left alone for as long as it keeps rendering. Anyone assessing whether deployed consent tooling still reflects current privacy expectations should treat pinned versions as the norm rather than the exception.

Ownership of the name is worth a line too. The product carries the Segment name while Twilio is recorded as the owner, which is the shape an acquisition leaves in an index. In practice the component is coupled to a specific analytics pipeline, so finding it on a site says as much about the data collection stack underneath as it does about the site's approach to consent.

As of October 2026 the fingerprint matches on 60 sites, and the figure should be read as a floor. Self hosted code can be renamed, bundled, minified into a larger file or forked outright, and any of those steps can remove the signature we look for.

One limit deserves stating plainly. Finding a consent component in a page proves an attempt was made, not that the gating behaves correctly, and the difference is where most privacy findings actually live. A dialog can render while trackers fire before a choice is recorded, or destinations can stay connected despite a refusal, and none of that is visible to a fingerprint that only sees the component is present. Detection scopes an audit and never replaces it.

The people who want this list are researchers measuring what privacy tooling actually ships rather than what policies claim, and vendors of managed consent platforms looking for sites running a component they maintain themselves. A per-domain lookup serves neither, because both questions are about a population. The downloadable set gives every matched domain with the rest of the detected stack in the same row, which is how a self hosted consent component becomes a segment you can reason about.