Programmatic Advertising & AdTech Architecture

What programmatic advertising does

Programmatic advertising automates the process of making advertising inventory available, evaluating opportunities and selecting ads. A single page view can involve a publisher, ad server, supply-side platform, exchange, demand-side platform and advertiser systems, all communicating within a very small time budget.

Publisher and ad inventory

The publisher owns the site or application where an ad can appear. An ad slot has context such as size, placement, page or app information and sometimes consent or audience signals. The publisher's monetization setup determines which demand sources are allowed to compete.

SSP and exchange

A supply-side platform helps publishers package and expose inventory to demand. An exchange provides auction infrastructure connecting supply and demand. In practice product boundaries can overlap, so it is more useful to understand the role each component plays in the request path than to assume every company maps to one category.

DSP and advertiser

A demand-side platform evaluates bid opportunities on behalf of advertisers or buyers. It considers campaign targeting, budget, pacing, creative eligibility and bidding logic. If the opportunity matches, the DSP returns a bid response containing price and creative-related information.

The auction lifecycle

When an impression opportunity becomes available, information is transformed into a bid request and sent to eligible buyers. Responses arrive under strict timeouts. The auction compares valid bids according to the publisher's rules. The winning demand is then passed into the ad-serving and rendering path. A bid win therefore does not automatically mean a rendered impression; additional steps still have to succeed.

OpenRTB

OpenRTB provides a common protocol for bid requests and responses. Important fields describe the impression, site or app, device, user or privacy context, auction rules and supply-chain information. Troubleshooting requires looking at the actual payload rather than assuming that a configured field is being transmitted correctly.

Why reporting differs

Publisher and buyer systems often count at different points. One system may count an auction, another a served creative and another a rendered impression. Time zones, invalid traffic filtering, retries, caching and late events can also create discrepancies. Teams should first align metric definitions and timestamps before treating every difference as a defect.

Transparency files

Mechanisms such as ads.txt, sellers.json and the SupplyChain object help buyers understand authorized selling relationships. They do not replace technical integration testing; a valid authorization file cannot fix malformed bid requests, timeouts or creative-rendering failures.

Practical troubleshooting sequence

• Confirm the ad opportunity is created.
• Verify the expected demand partner receives a request.
• Inspect required OpenRTB fields and privacy signals.
• Check timeout and no-bid reasons.
• Confirm the winning response reaches the ad server.
• Verify creative rendering and impression tracking.
• Compare reporting using the same metric definition and time window.

Thinking in stages makes complex AdTech incidents much easier to isolate.