Skip to content

uid2-refresh: refresh a stale cached UID2 on pages that never merge a response - #380

Merged
etiennelatendresse-optable merged 5 commits into
masterfrom
uid2-refresh-from-cache
Nov 4, 2026
Merged

etiennelatendresse-optable merged 5 commits into
masterfrom
uid2-refresh-from-cache

Conversation

@etiennelatendresse-optable

@etiennelatendresse-optable etiennelatendresse-optable commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

Why

Without this feature a token past its refresh_from keeps going out to bidders until it hard-expires, visible only as falling match rates. We need to refresh a stale UID2 on every page

What changed

  • A page that serves targeting from cache now refreshes a UID2 that is due, instead of handing bidders an aging token.
  • The refresh finds tokens resolved by either path, targeting or tokenize, so it covers the tokens prebid actually bids with.
  • Nothing is refreshed when there is no cache, no refresh material, or a token that is not yet due, so the common page makes no extra request.

Comment thread lib/addons/uid2-refresh.ts Resolved

@mosherBT mosherBT left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM let's get @jplaroche to give review as well

Comment thread lib/addons/uid2-refresh.ts Resolved
Comment thread lib/addons/uid2-refresh.ts Resolved
@etiennelatendresse-optable
etiennelatendresse-optable merged commit 451c0ec into master Nov 4, 2026
7 checks passed
@etiennelatendresse-optable
etiennelatendresse-optable deleted the uid2-refresh-from-cache branch November 4, 2026 19:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants