-
Notifications
You must be signed in to change notification settings - Fork 227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
prev_wins and PLTD #151
Comments
michaelkleber
pushed a commit
that referenced
this issue
Sep 9, 2021
* Clarifying product-level specification. Adresses issues: #150, #151, #160. * Better description of trustedBiddingSignalsKeys. * Drop the idea of shallow merge in daily updates At the same time, let's keep `ads` and `adComponents` as separate fields, so as to maintain some flexibility in daily updates of ads. * Drop the clarification on prevWins
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The specification of
generate_bid
introduces a field named prev_wins:I was wondering, how would that signal be constructed in case of multi-product ads? (Section 3.4, "Ads Composed of Multiple Pieces")
It would be great to obtain information about specific products that were displayed to the user, for example:
The text was updated successfully, but these errors were encountered: