-
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
Audigent RTD configurable per-bidder segment mappings #5903
Conversation
@anthonylauzon I don't see the unit test file for this module at all (audigentRtdProvider_spec.js). Make sure unit tests are added and you have at least 80% coverage. To generate and view the code coverage reports: gulp test-coverage
gulp view-coverage |
@anthonylauzon , I don't see docs PR here, you should open a PR against https://github.com/prebid/prebid.github.io, describing additional params you introduced in this PR. From what I see you're missing docs entry for this module altogether, please take a look at this page on how to add an appropriate docs file. |
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'm not looking at the code but have a question and comments about the docs.
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.
Getting close. (!)
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.
Approving the documentation and examples. Thanks. Will assign someone else for a secondary code review.
This PR is slightly below 80% code coverage. Also, I am not receiving audience segments on the example page, it would be helpful to use a test id here that returns a mock response 100% of the time, is that possible? |
i've added a test id to the integration example that retrieves test segments from our backend |
LGTM |
LGTM |
* configurable per bidder segment mappings, optional segment caching, documentation update * rubicon->appnexus in docs * apply fpd convention, remove publisher defined mappers, add unit tests, fixes * segment mapping arr->dict * add fpd data to bids * update audigent tests * openrtb fpd data descriptions, update docs, more tests * update docs, update integration example * integration update * documentation table update * add examples of adding and overriding segment mappers * fix documentation * add contact verbiage * requestParams object type * brand rtd provider * update appnexus segment function * support numerical segments for appnexus * no default appnexus segments * update url * update gpt example * conditionally set bid segments for generic * fixes for integration example * update integration example * add appnexus handler override
Type of change
Description of change
This PR adds configurable per-bidder segment mapping capabilities for Audigent's RTD provider. It relieves bid adapter maintainers from having to modify their bid adapters in order to make them compatible with our real-time data module's segments.
Relevant previous pull requests:
#4834
#5777