Skip to content

feat: add marketplaceExperimentVariant to sponsored listings auction#202

Open
agustinespildora wants to merge 2 commits into
mainfrom
feat/agus/auctions-marketplace-experiment-variant
Open

feat: add marketplaceExperimentVariant to sponsored listings auction#202
agustinespildora wants to merge 2 commits into
mainfrom
feat/agus/auctions-marketplace-experiment-variant

Conversation

@agustinespildora

@agustinespildora agustinespildora commented Jun 18, 2026

Copy link
Copy Markdown

Summary

  • Documents the optional marketplaceExperimentVariant field (type: string, maxLength: 10) on the Sponsored Listings auction request (SponsoredListingsAuction) for POST /v2/auctions. The Auction Engine already accepts, validates (max 10 chars) and records this field in auction reporting (resolved_auction_bids and auction_report); it was simply undocumented in the public spec.
  • Added with a disclaimer: by default it does not change auction behavior — it is recorded so clients can run their own A/B experiments and slice ad metrics (impressions, clicks, purchases) by variant.
  • Scoped to Sponsored Listings only (not banners), as requested.
  • Drops a redundant minimum: 0 on Products.qualityScores.items (keeps exclusiveMinimum: 0) so the recommended-strict redocly rule no-mixed-number-range-constraints passes. exclusiveMinimum: 0 already encodes the "greater than 0" constraint and matches the existing QualityScore component and price field conventions.

Test Plan

  • redocly lint --extends recommended-strict topsort-api-v2.yml — valid, 0 errors
  • prettier --check . — passes
  • yamllint topsort-api-v2.yml — passes
  • typos — passes

Document the optional marketplaceExperimentVariant field (max 10 chars) on
the SponsoredListingsAuction request. The engine already accepts, validates
and records it in auction reporting (resolved_auction_bids and auction_report);
this exposes it in the public docs with a disclaimer so clients can tag and
analyze their own experiments.

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
@agustinespildora agustinespildora requested a review from a team as a code owner June 18, 2026 16:22
Products.qualityScores items declared both exclusiveMinimum: 0 and
minimum: 0, which redocly's recommended-strict no-mixed-number-range-constraints
rule rejects. exclusiveMinimum: 0 already encodes the "greater than 0"
constraint and matches the QualityScore component and price field conventions.

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
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.

1 participant