Learning Track
OpenRTB Deep Dive
Understand bidstream contracts, decode requests quickly, and spot malformed fields.
Why it matters
OpenRTB is the shared language between DSPs/SSPs. TAMs use it to troubleshoot bids, spot compliance issues, and explain auction outcomes.
What to read
- OpenRTB 2.5 (or 2.6) spec: imp, device, user, regs, source
- IAB Transparency & Consent string mapping to regs/user
- One SSP sample bid request/response JSON
How to practice
- Decode 50 bid requests; annotate each field with meaning and examples.
- Find 10 malformed or missing fields (geo, ua, consent, device ID, imp.media).
- Write a one-page glossary explaining the top 30 fields to a non-engineer.
- Create a “red flags” checklist for malformed bids.
Outputs to keep
- openrtb-glossary.md, issues-log.csv, decoded-bid.json
- Slide with 3 common failure patterns (bad geo, missing consent, wrong device type).
References
- IAB Tech Lab OpenRTB 2.5/2.6 spec
- IAB CCPA/GDPR in bid requests
- Example SSP bid logs (use your sandbox/log exports)