Foundations

L1-L24 modules

Start here. Build the mental model of the ad-serving stack, see why the old waterfall under-monetized, and understand what header bidding actually changed. Everything else in the curriculum assumes this foundation.

What do L1–L5 mean?depth, beginner → expert

Each module carries a depth band. A range like L3–L4 means it spans two.

Foundations: Vocabulary and the big picture. No prior ad-tech assumed.
Practitioner: The hands-on basics you use day to day.
Intermediate: Real configuration and the trade-offs behind it.
Advanced: Optimization, edge cases, and running at scale.
Expert: Architecture and deep specialization.

L1A1The ad-serving stack and where header bidding sits
Objectives
- Identify the actors: publisher, SSP/exchange, DSP, ad server, DMP/CDP.
- Trace one impression from page request to rendered creative.
- Define CPM, eCPM, fill rate, impression, and win rate.
Key concepts
Publisher ad server (GAM as the dominant primary ad server)SSP vs DSPThe bid request / bid response round-tripDemand side vs supply side
Assessment
Label a blank impression-flow diagram, answer multiple-choice on actor roles, and define eight glossary terms.
Read the lesson →
ANALYZE
Open a Bidcliq Academy audit and identify which actors appear in the publisher ads.txt.
Run it live →
L1A2The waterfall and its problems
Prereqs: A1
Objectives
- Explain sequential / daisy-chain mediation.
- Articulate why the waterfall under-monetizes: passback latency, priority not price, no true competition, and "first acceptable bid" is not the highest bid.
Key concepts
Passback tagsPrice priority vs partner priorityLatency cascadeOpacity of demand
Assessment
Given a four-tier waterfall with stated CPMs and fill rates, compute realized revenue and identify the unmonetized bids the waterfall left on the table.
Read the lesson →
DEBUG
Proposed "waterfall regret" simulator: run the same demand as a waterfall vs as an auction and compare realized eCPM.
L2A3Header bidding vs waterfall vs unified auction
Prereqs: A2
Objectives
- Define header bidding as a pre-auction held in the page header before the ad-server call.
- Contrast it with the open-auction-only waterfall and with Dynamic Allocation.
- Explain why header bidding exists: to let multiple demand sources compete simultaneously on price for the same impression.
Key concepts
Parallel (not sequential) auctionThe wrapperThe ad-server translation layer (key-values)"Unified auction" as the conceptual end-state
Assessment
Write a short essay on why header bidding emerged and what advantage it neutralized, plus a compare-table fill-in.
Read the lesson →
ANALYZE
The SSP count in any Bidcliq Academy audit is the number of header-bidding demand partners a publisher has wired in. Correlate it with the quantity axis.
Run it live →
L2A4Client-side vs server-side vs hybrid
Prereqs: A3
Objectives
- Define where the auction runs: browser vs server.
- State the trade-off: client-side gives better cookie match, transparency, and control; server-side gives lower browser latency and more bidders but weaker match rates.
- Define hybrid.
Key concepts
Browser connection limitsPage weightCookie-match advantage of client-sideThe latency-vs-match trade
Assessment
Complete a decision-matrix exercise for three publisher profiles.
Read the lesson →
LEARN
Sets up Track B (client-side) and Track E (server-side).
DEBUG
Proposed connection-saturation simulator (revisited in F1).

Track quiz

Complete this track

Answer 4 of 5 correctly

Five questions drawn from this track. Get 4 right to mark the whole track done.

1.What did header bidding change versus the traditional waterfall?
2.What does an SSP (supply-side platform) do?
3.In the old waterfall, demand partners were called…
4.In client-side Prebid, where does the header-bidding auction run?
5.A DSP (demand-side platform) primarily serves…

0/5 answered