Prebid 7: an upgrade checklist
If you are still on 6.x, this is the path I would take to get current without breaking yield.
Prebid 7 is not a dramatic release, which is exactly why so many publishers have not bothered to upgrade. They should — the boring releases are often the ones worth chasing.
Do not skip straight to latest
Go from 6.x to 7.0, then 7.0 to 7.4. The staged path surfaces adapter breakage one layer at a time instead of dumping every incompatibility on you at once.
The floor module is the prize
The rewritten dynamic floor module is the single best reason to upgrade. Publishers paying a third party for dynamic floors today can, in many cases, do the same job inside Prebid with logic they can actually read.
If you can read your own floor logic, you can defend your own revenue. If you cannot, you are renting both.
The checklist
Before you ship the upgrade to production:
- Pin every adapter version and test them against 7.4 in staging.
- Diff your config — several deprecated options were removed.
- Run the new build in shadow mode and compare auction outcomes for a week.
- Watch latency, not just revenue, during the comparison window.
The rollout
Flip a small traffic percentage first. A staged rollout turns a scary migration into a measured one, and gives you a clean rollback if a bidder misbehaves. None of this is exciting work. All of it is the difference between an upgrade and an incident.