Repository navigation

Allow duplicate cookie family names - #4316

Merged

And1sS merged 13 commits into

allow-duplicate-cookie-family-names

Jul 15, 2026

Merged

Allow duplicate cookie family names#4316
And1sS merged 13 commits into
masterfrom
allow-duplicate-cookie-family-names

Commits on Apr 16, 2026
- Update setuid endpoint to accept both bidder names and cookie family names
  Lightwood13
  committed
  310da3f
- Update cookie sync endpoint to return bidder name instead of cookie family name in redirect url
  Lightwood13
  committed
  7ac551f
Commits on Apr 20, 2026
- Update setuid endpoint to accept only bidder name
  Lightwood13
  committed
  522d1c8
Commits on May 7, 2026
- Refactor UsersyncInfoBuilder
  Lightwood13
  committed
  62271c3
- Merge branch 'refs/heads/master' into update-cookie-sync-to-use-bidder-name-instead-of-cookie-family
  Lightwood13
  committed
  bf61d1d
- Updated cookie sync logic to allow duplicate cookie family name if glvid and usersync config are identical
  Lightwood13
  committed
  f36c665
- Test: Allow duplicate cookie family names (#4360)
  
  marki1an
  authored and
  Lightwood13
  committed
  035c00c
Commits on May 11, 2026
- Added validation that bidders provide cookie family name in usersync config
  Lightwood13
  committed
  7eeb5ad
Commits on Jul 14, 2026
- Merge branch 'master' into allow-duplicate-cookie-family-names
  Lightwood13
  committed
  9d38088
Commits on Jul 15, 2026
- Removed validation that vendor id is the same when cookie family name matches
  Lightwood13
  committed
  45c1b7d
- Removed comparison of enabled field from Usersyncer
  Lightwood13
  committed
  38fad50
- Refactored tests
  Lightwood13
  committed
  c4862a5
- Fix functional tests
  osulzhenko
  committed
  f52b215