Dailymotion Bid Adaptor: get iabcats from ortb2.site.content.data #17
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kvnsw
force-pushed
the
dailymotion_iabcat_from_contentdata
branch
from
25e88f2 to
b399158
Compare
modules/dailymotionBidAdapter.js
Outdated
| // See https://docs.prebid.org/features/firstPartyData.html#segments-and-taxonomy | ||
| .filter(data => data?.ext?.segtax === 4) | ||
| .map(data => (Array.isArray(data?.segment) ? data.segment : []).map(seg => seg.id)) | ||
| .flat(1), |
There was a problem hiding this comment.
Is it possible to have the same segment id between the data ?
If it's the case, the final array could contains several times the same value/id.
modules/dailymotionBidAdapter.js
Outdated
| // See https://docs.prebid.org/features/firstPartyData.html#segments-and-taxonomy | ||
| .filter(data => [5, 6, 7].includes(data?.ext?.segtax)) | ||
| .map(data => (Array.isArray(data?.segment) ? data.segment : []).map(seg => seg.id)) | ||
| .flat(1), |
kvnsw
force-pushed
the
dailymotion_iabcat_from_contentdata
branch
2 times, most recently
from
557619d to
f95ef52
Compare
kvnsw
force-pushed
the
dailymotion_iabcat_from_contentdata
branch
from
f95ef52 to
20e8c8d
Compare
kvnsw
force-pushed
the
dailymotion_iabcat_from_contentdata
branch
from
20e8c8d to
4627162
Compare
jeremy-le-dev
approved these changes
Apr 18, 2024
kvnsw
pushed a commit
that referenced
this pull request
Jul 9, 2024
…rebid#11775) * Azerion Edge RTD Module: Initial release ### Type of change [x] Feature: New RTD Submodule ### Description of change Adds new Azerion Edge RTD module. Maintainer: azerion.com Contact: @garciapuig @mserrate @gguridi * Azerion Edge RTD Module: Initial release. Typo * AzerionEdge RTD Module: Documentation: Required parameters Type of change: Documentation/Feature Description of change: Specifying new required parameters on documentation. Updating examples. * AzerionEdge RTD Module: Compatible with GDPR/USP Privacy Modules (#14) - Added GDPR validation. - We validate against ImproveDigital vendor ID consent and several purposes. - We don't load edge script, nor process the existing data, if consent wasn't given. - Adding support for USP consent. * AzerionEdgeRTDModule: Passing the consent to the script execution (#17) Adding GVL ID to the module configuration Passing the consent to the script execution instead of handling it in prebid (#16) --------- Co-authored-by: Gorka Guridi <gorka.guridi@azerion.com> --------- Co-authored-by: Gorka Guridi <gorka.guridi@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.