Skip to content
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

Triplelift: Adding support for video.plcmt #11554

Closed
wants to merge 0 commits into from

Conversation

patrickloughrey
Copy link
Contributor

Type of change

  • Feature

Description of change

Adding support for video.plcmt if the publisher doesn't explicitly set it

@@ -241,6 +241,9 @@ function _getORTBVideo(bidRequest) {
if (!video.placement) {
video.placement = 1;
}
if (!video.plcmt) {
video.plcmt = 1;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fowler446 can you comment here? Generally video.context instream does not map to plcmt = 1

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image (8)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is direct from IAB so I think we have instream plcmt correct. But like I mentioned below, if the publisher sets this, we don't meddle with it.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're gonna get in trouble here from ttd. They were very adamant no one does this. Prebid instream context basically just means preroll, there is no easy way for you to infer if plcmt should be 1 or 2

@@ -249,6 +252,9 @@ function _getORTBVideo(bidRequest) {
logMessage(`video.placement value of ${video.placement} is invalid for outstream context. Setting placement to 3`)
video.placement = 3
}
if (!video.plcmt) {
video.plcmt = 4;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

prebid already has logic in place doing something similar

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

to support plcmt, pick up what you find in the request, this logic to infer it is not necessary. That's true for the old value as well.

Copy link
Contributor Author

@patrickloughrey patrickloughrey May 23, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in current versions? or in the upcoming v9? Because currently if video.placement isn't set, it will not be added to the bid request

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

since #10438

Copy link
Contributor Author

@patrickloughrey patrickloughrey May 28, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the info, I reviewed it. After reviewing the logic in src/video.js, it seems like our logic is slightly redundant for outstream but not for instream and not for legacy placement values (which triplelift still wants to ingest).

Both checks in our adapter are secondary checks and are irrelevant if the publisher does the right thing:
https://github.com/prebid/Prebid.js/blob/master/modules/tripleliftBidAdapter.js#L232

We just want to ensure that we are still receiving both new and legacy placement values if not set by the publisher which I understand is covered in video.js but only for the outstream plcmt value scenario.

Copy link
Collaborator

@patmmccann patmmccann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please fix incorrect plcmt interference

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants