OpenX is a programmatic advertising technology company.
Websites Using OpenX
What Is OpenX?
OpenX is a programmatic advertising exchange and supply-side platform (SSP) that connects website and app publishers to a marketplace of advertisers and demand-side platforms bidding for their ad inventory. In plain terms, when a page has an empty ad slot, OpenX is one of the systems that can run a real-time auction to fill that slot with the highest-paying ad, then return it to the page for display. It operates squarely on the sell side of the ad-tech ecosystem, working on behalf of publishers to maximize the revenue they earn from each impression.
OpenX is one of the longer-established independent ad exchanges on the open web. It is widely recognized as a major SSP that participates in real-time bidding (RTB), supports the industry-standard OpenRTB protocol, and integrates with header-bidding frameworks like Prebid. Rather than serving a single advertiser, OpenX aggregates demand from many buyers and competes that demand against other exchanges to lift the price a publisher receives for an impression.
It is important to be precise about what OpenX is and is not. OpenX is not an ad network you join to show generic banners, and it is not a tag you paste in to start earning the way a self-service publisher product works. It is exchange and SSP infrastructure that publishers and their monetization partners wire into a broader ad stack, typically alongside an ad server such as Google Ad Manager and a header-bidding wrapper. Because of that, OpenX is frequently loaded indirectly rather than through a single obvious script, which shapes how you detect it.
OpenX sits within a layered supply chain. A publisher decides which slots to monetize, a wrapper such as Prebid solicits bids from several SSPs at once, OpenX runs its slice of the auction by reaching out to its connected buyers, and the ad server picks the overall winner. The visible creative a visitor finally sees may be served from a completely different domain even though OpenX supplied the winning bid, which is exactly why ad-tech detection has to look at the auction plumbing and not just the rendered ad.
How OpenX Works
OpenX functions as the publisher-facing auctioneer in the programmatic chain. When a page loads an ad slot that OpenX is configured to monetize, a bid request describing that slot, its size, the page context, and available audience signals (subject to consent) is sent to OpenX. OpenX then runs or participates in a real-time auction, soliciting bids from connected demand-side platforms and advertisers, and returns its best bid back up the chain.
The protocol underneath this is OpenRTB, the IAB Tech Lab standard for real-time bidding. OpenRTB defines the structured bid request and bid response format that lets an exchange like OpenX talk to dozens of buyers in a consistent way. Each bid response carries a price and the creative (or a pointer to it), and the auction logic compares those prices to decide a winner.
In a modern setup, OpenX is most often invoked through header bidding. A wrapper such as Prebid.js fires near the top of the page, asks OpenX and several other SSPs for bids simultaneously, waits a configured timeout, and then passes the best bids into the publisher's ad server. The ad server (commonly Google Ad Manager) compares those header-bidding bids against its own demand and any direct-sold campaigns, and the overall winner is rendered into the slot. OpenX also supports server-side header bidding through Prebid Server, where the auction happens on a server rather than in the browser to reduce page weight and latency.
A few mechanics shape how OpenX behaves and, by extension, how you detect it. First, the request flow is often invisible in the page's static HTML because the wrapper injects the OpenX bidder adapter dynamically at runtime. Second, OpenX relies on identity and consent signals, so the cookies and parameters it sends vary by region and the visitor's consent choices. Third, on server-side setups the browser may never contact an OpenX domain directly at all, because the bid request originates from Prebid Server, which makes detection from the client side harder. Finally, OpenX maintains an entry in publishers' ads.txt and sellers.json files, the IAB transparency standards that declare which sellers are authorized to sell a site's inventory, and those declarations are one of the most reliable OpenX fingerprints available.
The supply-chain transparency layer deserves emphasis. The ads.txt file at the root of a publisher's domain lists the advertising systems authorized to sell that site's inventory, each with a seller account ID and a relationship type. Because OpenX-monetized sites declare OpenX in ads.txt, that file is a durable, server-readable signal that survives even when the runtime auction is hard to observe in the browser.
How to Tell if a Website Uses OpenX
OpenX can be genuinely tricky to confirm because it is so often loaded indirectly through a header-bidding wrapper or invoked server-side. The most dependable approach combines several signals rather than relying on a single tag. Here are the concrete checks, and where the evidence is only suggestive, treat it as such rather than proof.
Check ads.txt (the strongest, easiest signal). Visit https://example.com/ads.txt in a browser or run curl -s https://example.com/ads.txt | grep -i openx. Publishers that sell inventory through OpenX list a line referencing openx.com with a seller account ID and a DIRECT or RESELLER designation. Because ads.txt lives at a predictable path and is plain text, it is the most reliable server-readable OpenX fingerprint, and it is exactly the kind of file a server-side analyzer can fetch directly.
View Source and search for OpenX strings. Open the page source and search for openx. You may find references to OpenX domains such as openx.net or a Prebid bidder configuration naming openx as a bidder with a delDomain or unit parameter. Note that with many header-bidding setups the bidder config is injected by JavaScript and will not appear in the raw HTML, so absence here does not rule OpenX out.
DevTools Network panel. Reload the page with the Network tab open and filter for openx. If OpenX is bidding client-side, you will see bid requests to OpenX domains (for example, hosts under openx.net) firing as the auction runs. Ad-fetch and impression activity may appear as you scroll, because many slots lazy-load. On server-side header bidding you may see no OpenX requests at all even though OpenX is a bidder, which is a key caveat.
DevTools Console (Prebid inspection). On sites using Prebid.js, type pbjs.getBidResponses() or pbjs.bidderSettings in the console. If OpenX is configured, it will appear among the bidders. This is one of the more direct runtime confirmations that OpenX is part of the auction, when Prebid is present and exposed.
sellers.json cross-reference. OpenX publishes a sellers.json file declaring the sellers it represents. Cross-referencing the seller ID found in a site's ads.txt against OpenX's sellers.json confirms the relationship, which is useful for supply-chain verification.
Wappalyzer and BuiltWith. Both detection tools can flag OpenX under advertising when its scripts or identifiers are present, and BuiltWith can show historical usage. They are a fast confirmation, though they may miss server-side-only integrations for the same reason the Network panel does.
| Method | What to do | What OpenX reveals |
|---|---|---|
| ads.txt | Fetch /ads.txt and grep for openx | An authorized openx.com seller line with account ID (strongest signal) |
| View Source | Search page source for openx | Prebid bidder config or OpenX domain references (often injected, may be absent) |
| DevTools Network | Filter requests for openx | Client-side bid requests to OpenX domains (absent on server-side bidding) |
| DevTools Console | pbjs.getBidResponses() | OpenX listed among Prebid bidders when Prebid is present |
| Wappalyzer/BuiltWith | Run on the live page/domain | OpenX flagged under advertising; historical usage |
Because much ad-tech is loaded indirectly, the honest conclusion is that confirming OpenX often means triangulating: an openx.com line in ads.txt, an OpenX bidder in the Prebid config, and matching seller IDs in sellers.json together make a confident verdict, whereas any one alone may be circumstantial. For the broader methodology, see our guides on how to find out what technology a website uses and how to find out what analytics a website uses. A server-side scan that fetches ads.txt and the raw HTML is particularly well suited to surfacing these transparency-file signals without browser noise.
Key Features
- Programmatic exchange and SSP. A two-sided marketplace that auctions publisher inventory to many connected buyers in real time.
- OpenRTB support. Full participation in the industry-standard real-time bidding protocol for consistent buyer integration.
- Header-bidding integration. Works as a bidder inside Prebid.js and supports server-side bidding via Prebid Server.
- Identity and audience tooling. Support for industry identity solutions and audience signals, subject to consent frameworks.
- Supply-chain transparency. Participation in IAB
ads.txt,app-ads.txt,sellers.json, and SupplyChain Object standards. - Brand safety and quality controls. Filtering and verification integrations aimed at protecting both publishers and buyers.
- Multi-format and multi-channel. Display, video, mobile app, and connected TV inventory across web and apps.
Pros and Cons
Pros
- Adds genuine auction competition that can lift the price a publisher earns per impression.
- An independent exchange, offering demand diversification beyond a single vendor's stack.
- Strong adoption of transparency standards, which aids supply-chain verification and trust.
- Flexible deployment through client-side and server-side header bidding.
Cons
- Complex to configure and optimize; typically requires monetization expertise or an ad-ops partner.
- Loaded indirectly, which makes it hard to detect and to attribute revenue precisely.
- Adds another bidder to the auction, which can increase page weight or latency if not tuned.
- Revenue and fill depend heavily on demand, consent state, and the surrounding stack.
OpenX vs Alternatives
OpenX competes with other supply-side platforms and exchanges, and increasingly is compared against server-side and Google's own stack. The table clarifies where it fits.
| Platform | Type | Standout strength | Typical adopter |
|---|---|---|---|
| OpenX | Independent exchange / SSP | Independent demand, strong transparency standards | Publishers diversifying demand via header bidding |
| Google Ad Manager / AdX | Ad server + exchange | Scale and integration with Google demand | Large publishers centralized on Google's stack |
| PubMatic | Sell-side platform | Publisher-focused SSP with omnichannel reach | Publishers wanting an independent SSP partner |
| Magnite | Independent SSP | Large independent exchange, strong in CTV/video | Publishers prioritizing video and connected TV |
| Amazon Publisher Services | Cloud-based exchange | Amazon demand and server-side connections | Publishers seeking unique Amazon demand |
If you suspect a different sell-side partner, the same detection techniques apply; compare OpenX with a publisher-focused alternative like PubMatic, or look at the open-source wrapper that often invokes these exchanges in Prebid.
Use Cases
OpenX is used by publishers who want to maximize programmatic revenue by adding independent exchange demand to their auction. A mid-sized news site running header bidding might include OpenX as one of several SSPs so that more buyers compete for each impression, lifting the clearing price. Larger publishers use OpenX alongside their primary ad server to diversify demand beyond a single vendor and to access buyers who prefer transacting through OpenX.
It also fits app publishers monetizing mobile inventory through app-ads.txt-declared OpenX seats, and video or connected-TV publishers tapping OpenX's multi-format demand. For supply-chain and ad-ops teams, OpenX's adoption of ads.txt, sellers.json, and the SupplyChain Object makes it a verifiable, transparent partner, which matters for combating fraud and reselling abuse.
From a competitive-intelligence and lead-generation standpoint, detecting OpenX in a site's ads.txt is a meaningful technographic signal. It indicates a publisher that monetizes programmatically, runs header bidding, and is sophisticated enough to manage multiple SSP relationships. For ad-tech vendors, agencies, and analysts, that profile helps qualify prospects and map the competitive landscape of who sells inventory through which exchanges. Reading these signals automatically across thousands of domains, rather than inspecting each ads.txt by hand, is precisely where technology detection earns its keep, as our primer on using tech-stack data to qualify leads explains.
Frequently Asked Questions
Is OpenX an ad network or an exchange?
OpenX is an exchange and supply-side platform, not a simple ad network. A network typically aggregates inventory and sells it on advertisers' behalf, whereas OpenX runs a real-time auction that connects publisher inventory to many demand sources at once using the OpenRTB protocol. Publishers usually plug OpenX into a header-bidding wrapper and an ad server rather than joining it like a self-service product.
Why can't I see OpenX in a site's page source?
Because OpenX is frequently loaded indirectly. A header-bidding wrapper like Prebid.js often injects the OpenX bidder adapter at runtime, so it may not appear in the raw HTML. On server-side header bidding, the bid request originates from a server rather than the browser, so you may see no OpenX network calls at all. The most reliable check in those cases is the site's ads.txt file, which declares OpenX as an authorized seller.
What does an OpenX line in ads.txt mean?
An ads.txt line referencing openx.com with a seller account ID and a DIRECT or RESELLER tag declares that OpenX is authorized to sell that publisher's inventory. DIRECT means the publisher controls the OpenX account directly; RESELLER means an authorized intermediary resells through OpenX. Cross-referencing the account ID against OpenX's sellers.json confirms the relationship and is a standard supply-chain verification step.
Does OpenX use cookies to track users?
OpenX, like other programmatic exchanges, has historically used cookies for identity and frequency capping, but its behavior depends heavily on the visitor's region, consent state, and the identity solutions in play. With privacy regulations and the decline of third-party cookies, exchanges increasingly rely on consent-gated and first-party or alternative identity signals. What you observe in practice varies, so treat any cookie-based detection as region- and consent-dependent.
How is OpenX different from Google Ad Manager?
Google Ad Manager is primarily an ad server (with its own exchange, AdX) that publishers use to manage and serve all their demand, while OpenX is an independent exchange and SSP that competes as one source of demand within that auction. Many publishers run both: Google Ad Manager as the decisioning ad server and OpenX as one of several header-bidding partners feeding competitive bids into it.
Want to identify OpenX and the rest of a site's ad-tech stack automatically? Run any URL through StackOptic at https://stackoptic.com.