Learn

← All tracks
E

Server-Side and Advanced Media

L4-L53 modules

Where the auction moves off the page and into formats beyond banner. Prebid Server and its cookie-sync cost, stored requests for app and AMP, video and CTV header bidding, and how deals compete against the open auction.

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

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

L1
Foundations
Vocabulary and the big picture. No prior ad-tech assumed.
L2
Practitioner
The hands-on basics you use day to day.
L3
Intermediate
Real configuration and the trade-offs behind it.
L4
Advanced
Optimization, edge cases, and running at scale.
L5
Expert
Architecture and deep specialization.
  1. L4E1Prebid Server (s2s)

    Prereqs: A4, B4

    Objectives
    • Explain server-to-server: the browser sends one request to Prebid Server, which fans out server-side.
    • State when to use it and the cost: weaker cookie match, so cookie sync is needed.
    • Configure the prebidServer (s2s) adapter and understand the host vs requesting-publisher split.
    Key concepts
    Server-to-server (s2s) fan-outWeaker cookie matchThe prebidServer adapterHost vs requesting-publisher split
    Assessment

    Decide which 4 of 12 bidders to move to s2s and justify the choice.

    Read the lesson →
    PRACTICE

    Proposed s2s config builder.

    DEBUG

    Proposed "bidder gets no user ID server-side because cookie sync never ran" reproduction.

  2. L4-L5E2Cookie sync and stored requests

    Prereqs: E1

    Objectives
    • Explain why server-side bidders’ IDs must be synced (/cookie_sync), including cooperative syncing.
    • Explain stored requests: OpenRTB blocks stored server-side and merged via ortb2Imp, central for mobile-app and AMP.
    Key concepts
    /cookie_sync and cooperative syncingStored requestsortb2Imp mergeMobile-app and AMP delivery
    Assessment

    Trace why a freshly onboarded s2s bidder has a 0% match rate and how cooperative sync resolves it, then design a stored-request layout.

    Read the lesson →
    DEBUG

    Proposed cookie-sync timeline simulator.

  3. L5E3Video, CTV, PMPs, and deals

    Prereqs: B2, E1

    Objectives
    • Explain video header bidding: VAST / VPAID, the video mediaType, instream vs outstream, and why video often runs s2s.
    • Explain CTV: ad pods, SSAI, and app-ads.txt.
    • Define PMPs and deals: deal IDs through Prebid (hb_deal), preferred deals vs private auctions vs programmatic guaranteed, and deal priority vs open-auction bids.
    Key concepts
    VAST / VPAID and the video mediaTypeInstream vs outstreamCTV ad pods and SSAIDeals (hb_deal): preferred, private auction, programmatic guaranteed
    Assessment

    Configure an outstream video ad unit and explain how a $X deal competes against a $Y open-auction bid.

    Read the lesson →
    PRACTICE

    Proposed video and deal-targeting builder.

    ANALYZE

    Run a Bidcliq Academy audit on an app developer domain (app-ads.txt) and read its supply chain.

    Run it live →
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. 1.Moving the auction to Prebid Server (server-side) primarily reduces…

  2. 2.The main trade-off of server-side vs client-side bidding is…

  3. 3.A PMP / deal (e.g. a preferred deal or programmatic guaranteed) is…

  4. 4.Stored requests in Prebid Server are used to…

  5. 5.Video / CTV header bidding differs from banner mainly because it…

0/5 answered
Bidcliq Academy · Track E: Server-Side and Advanced Media