-
Notifications
You must be signed in to change notification settings - Fork 2.3k
33Across Bid Adapter: Start using ORTB converter + refactoring #13666
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
33Across Bid Adapter: Start using ORTB converter + refactoring #13666
Conversation
Allow video ad pod params
Relocate ext attributes
…rtb2_config_attrs
…fig_attrs 33across adapter allow ortb2 config attrs
|
Tread carefully! This PR adds 1 linter error (possibly disabled through directives):
|
9f7fa26 to
18a012c
Compare
73df9fe to
96e56bc
Compare
| }, | ||
| id: 'r1', | ||
| regs: { | ||
| coppa: 0, |
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.
So where does the coppa value come from in a normal bid-request operation? I don't see it explicitly referenced in the bid adapter implementation. Does it get pulled in with getTTXConfig()?
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.
I think you are looking into a specific commit diff. Final diff doesn't mention coppa on this location since it's no longer referenced from the adapter and it's being picked from the ORTB converter instead.
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.
Ah, OK - I see now. Thanks.
|
LGTM |
Type of change
Description of change
Start using the ORTB converter utility while going through the process of removing attributes that are no longer needed by 33across. Apply some refactoring to existing functionality.