-
Notifications
You must be signed in to change notification settings - Fork 768
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
Alkimi: Add imp extension support #4213
base: master
Are you sure you want to change the base?
Conversation
# Conflicts: # adapters/alkimi/alkimi_test.go
# Conflicts: # adapters/alkimi/alkimi_test.go
merge master
merge master
Code coverage summaryNote:
alkimiRefer here for heat map coverage report
|
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.
Please use the jsonutil
package to marshal/unmarshal data everywhere. PBS is in the process of removing standard json, which is slow and makes more memory allocations compared to jsonutil
@pm-jaydeep-mohite can you please review? |
temp := extObj{AlkimiBidderExt: extImpAlkimi} | ||
temp.AlkimiBidderExt.AdUnitCode = imp.ID | ||
temp := extImpAlkimi | ||
temp.AdUnitCode = imp.ID |
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.
Is imp.ID required to be part of impression extension as this is standard ORTB parameter ?
Usually bidder specific custom parameters are added in impression extension.
When bidder receive request, imp.ID can be used as AdUnitCode
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.
Yes, it's required for bidder.
But this is not related to this PR, in this PR we've added support of any parameters in imp.ext map.
Code coverage summaryNote:
alkimiRefer here for heat map coverage report
|
Added bidder extension as new feature.