-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Ozone Project Bid Adapter: Support for auctionId and transactionId when a publisher opts in #12267
Conversation
Your adapter is generally too complicated :) it can be dramatically simplified with modern tools I see you are taking the full ortb object now, which might make @justadreamer pr no longer needed |
@@ -891,7 +894,9 @@ export const spec = { | |||
params: bid.params, | |||
price: bid.price, | |||
transactionId: bid.transactionId, | |||
ttl: bid.ttl | |||
ttl: bid.ttl, | |||
ortb2: deepAccess(bid, 'ortb2'), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're going to end up with enormous redundancy within your payload
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is purely for logging purposes as opposed to payload that is sent.
Holding merge for @AskRupert-DM responses, thanks |
updated device object values to come from ortb.device
have added the change to the device object per @justadreamer pr @patmmccann - Some of the complication that you mention is for logging/debugging purposes which is useful for our technical account management teams, and some of it is down to the way in which it’s grown over time, which in our next version I can certainly look at refactoring. |
Thanks! |
Type of change
Description of change
added support for auctionId and transactionId where a publisher has opted in for these values to be set.