You visit a webpage. An ad appears. It feels instantaneous.

But behind that blink-of-an-eye moment, a complex journey unfolds. Multiple systems communicate, auctions run, and decisions are made—all in under 100 milliseconds. The process involves publishers, ad exchanges, supply-side platforms (SSPs), demand-side platforms (DSPs), and advertisers, each playing a specific role in delivering that ad to your screen.

This guide breaks down exactly what happens between an ad request and an ad appearing—step by step.

Key Takeaways

• The entire ad request-to-delivery process takes under 100 milliseconds.
• OpenRTB is the standard protocol that enables different ad tech systems to communicate.
• SSPs connect publishers to exchanges; DSPs connect advertisers to exchanges.
• Header bidding lets multiple demand sources bid simultaneously, creating competition.
• Win and loss notifications help advertisers optimise future bidding strategies.

The 100-Millisecond Journey: Step by Step

What follows is the typical path an ad request takes in a programmatic environment—from the moment a user loads a page to the moment an ad appears. The specific order can vary slightly depending on the technology stack and whether header bidding is involved.

1. A User Visits a Webpage

The journey begins when a user navigates to a publisher's website. The page starts loading, and the browser begins rendering the content. As part of this process, the page's ad tags are triggered.

The ad tags are JavaScript snippets placed by the publisher or their ad server. When the browser loads the page, these tags execute and initiate the ad request sequence. For header bidding setups, this happens via a header bidding wrapper like Prebid.js, which orchestrates the entire process.

2. The Ad Request Is Created

The ad tag generates an ad request—a message containing everything the system needs to know to find the right ad for this specific impression.

The request includes site or app information—name, domain, category, and content details like genre, keywords, and content rating. It contains device information—type, operating system, IP address, and identifier for advertising. User data is included—anonymised identifiers, consented data, and universal IDs like UID2 or RampID. Impression details describe ad size, format, and the minimum price required (floor). The supply chain shows the path from the original media owner to the final buyer.

All of this information is packaged using the OpenRTB protocol—the standard language of ad tech. The request is formatted in JSON, making it readable and interpretable by all participants in the ecosystem.

Neuromarketing insight: the more detailed the ad request, the more confident advertisers can be in targeting the right user. Confidence triggers higher bids because advertisers perceive lower risk and higher relevance. This is why publishers who provide clear content and audience signals consistently earn more.

3. The SSP Sends the Request to the Exchange

The ad request is sent to a supply-side platform (SSP). The SSP's job is to help publishers sell their inventory efficiently across multiple exchanges. In a header bidding setup, the request is sent to multiple SSPs simultaneously.

The SSP applies its own business logic and data insights, then forwards the request to an ad exchange. Often, the SSP and ad exchange are the same organisation.

The exchange is the marketplace where publishers and advertisers meet. It is the engine that powers the real-time auction.

4. The Exchange Runs the Auction

The exchange receives the request and broadcasts it to multiple demand-side platforms (DSPs) that represent advertisers. This is where the real-time auction begins.

Each DSP evaluates the request against its advertisers' campaigns. It checks whether the impression matches targeting criteria—geography, device, content relevance, audience segments, and campaign goals. The DSP's algorithms determine the value of the impression and generate a bid.

This entire evaluation happens in milliseconds. The DSP must decide whether to bid and at what price before the auction times out.

The exchange then determines the winner. In a first-price auction, the highest bid wins and the winning bidder pays their bid amount. Other auction types exist, but first-price is becoming the industry standard for transparency.

5. The Winning Ad Is Returned

The exchange sends the winning bid back to the SSP, which passes it back to the publisher's ad server. The response includes the winning bid price, the ad creative, or a URL where the creative can be retrieved.

If the winning bid did not include the creative directly, the publisher's ad server retrieves it from the advertiser's ad server. The ad server makes the final decision, which may also consider direct sold campaigns that take priority over programmatic winners.

The selected ad is then sent to the browser for rendering.

6. The Ad Is Rendered to the User

The ad creative appears on the page. The user sees the ad—often without any awareness of the complex auction that just occurred. This is the only part of the process the user experiences directly.

Rendering itself involves painting the creative on the screen, whether it is a display banner, video, native ad, or another format. However, rendering does not always mean viewability—the user may not actually see the ad depending on placement and scrolling behaviour.

7. Performance Is Tracked and Verified

After the ad is delivered, multiple systems collect data. Beacons fire, notifying participants that the ad rendered and transactions should be recorded.

Win notifications confirm the auction win to the winning bidder. The system notifies the winner through a win notification URL (NURL), which includes the clearing price and settlement details. Loss notifications inform losing bidders why they did not win, helping them optimise future bidding strategies. The loss reasons follow standardised codes, like budget depleted or targeting mismatch.

Billing notices indicate that spending should be applied, informing the advertiser that an impression has been served and billed. This enables the advertiser to manage campaign delivery and budget pacing.

8. Records Are Reconciled

The journey does not end with the ad render. Both selling platforms and buying platforms log impressions, fees, clearing prices, billable prices, and telemetry in ledger systems.

Most companies conduct monthly reconciliation, matching numbers between systems and managing any discrepancies. This ensures accurate billing and payment for all parties involved.

The Role of Header Bidding

While the process described above works in any programmatic environment, header bidding has become the preferred approach for many publishers.

In traditional waterfall setups, demand sources were called one at a time in a fixed order. Header bidding sends requests to multiple demand sources simultaneously. This creates a more competitive, transparent auction where all bidders compete on equal footing.

The result is higher CPMs, better fill rates, and greater control for publishers.

The process happens in two phases. In the pre-bid phase, the header bidding script sends bid requests to demand sources, collects bids, and runs an auction to determine the highest bid. In the post-bid phase, the winning bid is sent to the ad server, which updates analytics and displays the ad.

Industry Insight: The OpenRTB Protocol

At the heart of this entire process is OpenRTB, the industry standard maintained by the Interactive Advertising Bureau (IAB).

OpenRTB defines the communication protocols between advertising buyers and sellers in programmatic ecosystems. It provides a standardised way to express advertising-related information, allowing media owners, marketers, and others in the programmatic supply chain to communicate during an auction.

Without OpenRTB, every system would need custom integrations with every other system. The protocol enables interoperability at scale, making the 100-millisecond journey possible.

The 2026 Programmatic Auction Definitions document from IAB Tech Lab continues to build on this foundation, establishing standardised vocabulary and technical explanations for how digital advertising auctions operate. It defines 12 critical roles and a 12-step workflow that includes inventory setup, bid solicitation, auction execution, and transaction recording.

The 100-millisecond journey from ad request to ad appearing is a testament to the complexity and efficiency of modern ad tech. Adstork handles this entire process through a unified header bidding platform, connecting your inventory to multiple premium demand sources simultaneously. Every step—from the moment a user visits your site to the moment an ad renders—happens with transparency and speed. Sign up for a free Adstork publisher account and see how efficient ad delivery can transform your revenue.

Comparison Table: The Ad Request Journey at a Glance

A quick reference guide to the 8-step journey from ad request to ad appearing.

Future Outlook: The Evolution of Ad Delivery

The ad request-to-delivery process continues to evolve. Several trends are shaping how ads will be served in the coming years.

AI-powered optimisation is becoming more sophisticated. Machine learning models analyse thousands of signals in milliseconds, predicting which advertisers will perform best on which inventory and adjusting bids in real time.

Server-side header bidding is reducing latency. Moving the auction from the browser to the server improves page speed and reduces timeout rates, allowing more bidders to participate without performance penalties.

Unified measurement is becoming the standard. The industry is moving toward consistent vocabulary and technical explanations for how digital advertising auctions operate, enabling better optimisation for all participants.

Privacy-first signals are replacing cookies. The ad request will increasingly rely on first-party data and contextual signals, rather than third-party identifiers. Publishers who provide clear, consensual audience signals will command higher bids.

The 100-millisecond journey will only get faster and smarter. Publishers who understand the process and optimise for it will capture more value from every impression.

The journey from ad request to ad appearing is a complex, lightning-fast process involving multiple systems, real-time auctions, and thousands of data points—all in under 100 milliseconds.

Understanding this journey helps you appreciate the technology that powers your revenue. Every step—from the initial request to the final render—is designed to maximise the value of your inventory while delivering a seamless user experience.

The right ad network handles this entire process for you, connecting your inventory to premium demand sources through header bidding, running transparent auctions, and delivering the highest-paying ads to your users. Adstork does all of this through a unified platform, with instant approval and no minimum traffic requirements. Sign up for a free Adstork publisher account and see how efficient ad delivery can transform your revenue.

Your immediate action plan: Review your current ad setup. Are you using header bidding or waterfall? Can you see win and loss data from your demand sources? If your network is not providing transparency into the ad delivery process, consider testing one that does. Adstork's reporting shows you exactly what is happening at each step of the journey.

FAQs

How long does it take for an ad request to become an ad on the page? The entire process from ad request to ad delivery typically takes under 100 milliseconds. This includes sending the request, running the auction, selecting the winner, and rendering the ad.

What is OpenRTB and why does it matter? OpenRTB is the industry standard protocol that enables different ad tech systems to communicate during an auction. It standardises how ad requests and responses are formatted, allowing publishers, exchanges, SSPs, and DSPs to work together seamlessly.

What is the difference between an SSP and a DSP? An SSP (supply-side platform) helps publishers sell their inventory across multiple exchanges. A DSP (demand-side platform) helps advertisers buy inventory across multiple exchanges. The exchange sits between them, running the auction that brings buyers and sellers together.

What happens if no one bids on my inventory? If no advertiser bids or no bid meets your floor price, the request goes unfilled. Many networks use waterfall or passback chains to capture revenue from secondary demand sources.

What are win and loss notifications? Win notifications confirm an auction win to the winning bidder, including the clearing price. Loss notifications inform losing bidders why they did not win, helping them optimise future bidding strategies.

How does header bidding fit into this process? Header bidding sends ad requests to multiple demand sources simultaneously, rather than sequentially. This creates more competition and transparency, often resulting in higher CPMs and better fill rates for publishers.