Prebid docs - browse
Prebid/Settings/Prebid bid caching: when to use it
SETTING

Prebid bid caching: when to use it

Bid caching lets Prebid consider a bid from an earlier auction on the same page view, instead of using only the bids that just returned.

Plain English

Since Prebid.js 2.0, useBidCache defaults to false. Turning it on does not skip the next call to the bidder. Prebid still requests fresh bids. When those return, or the timeout hits, it also looks at bids kept from earlier auctions on that ad unit.

Prebid's FAQ limits that reuse: the same ad unit, the same page view, the same user, and only until the bid's time-to-live or until the bid is displayed. The cache is in the browser. A page load drops it. A cached bid is discarded once its TTL is up or its status is targetingSet or rendered. It can win only if its CPM beats the new bids.

The cases Prebid names are auto-refresh, infinite scroll that recreates the same ad unit, and galleries. Each adapter sets its own TTL.

How it shows up in pbjs

The switch is one flag. A bidCacheFilterFunction can refuse some cached bids - Prebid's example excludes video. That filter is only consulted for cached bids, not for bids from the current auction.

pbjs.setConfig({ useBidCache: true });

When it helps, when it hurts

Helps

On a refresh or a second auction of the same unit, a bid that is still inside its TTL can cover a thin response. The bidder was still asked. The cache is a candidate, not a substitute.

Hurts

A high cached bid can beat a lower fresh one and then expire before the ad renders. Video is the case Prebid calls out for a filter. Keeping every expired bid in memory for the life of a long single-page session is a different setting (minBidCacheTTL) and is not this switch. Across a real navigation, there is nothing to reuse.

What bidtune tests here

Autopilot can turn useBidCache on for optimized traffic. The page script calls pbjs.setConfig({ useBidCache: true }) when that test is active. The holdback does not get the flag, even if the same config object mentions it.
The test does not change a bidder's TTL, and it does not install a cache filter. Whether reuse earns more than always taking the fresh auction is the question the traffic has to answer. Refresh is the usual place the question shows up.
The 10% holdback keeps your current configuration. A test runs on 30% of optimized traffic, for at least 72 hours and 2,000 sessions in each arm, and no longer than 14 days. bidtune keeps the change only after the capped session read is better at two daily checks.
How bidtune tests itTHE RULES
A test takes 30% of optimized traffic
Judged against its own control. The 10% holdback never changes.
10% holdback60% control30% test
sessions per arm2,000minimum runtime72hdecides onrev / session