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

stroeerCoreBidAdapter - possibility to split bid request by adtype #12357

Open
vlyby-nadja opened this issue Oct 23, 2024 · 5 comments
Open

stroeerCoreBidAdapter - possibility to split bid request by adtype #12357

vlyby-nadja opened this issue Oct 23, 2024 · 5 comments

Comments

@vlyby-nadja
Copy link

Type of issue

Feature request

Description

Using the stroeerCoreBidAdapter for video and banner bid requests at the same time result in only one bidRequest for both adTypes.
Here an example:
image

A publisher recognized issue on connected DSPs within the StröerSSP and asked to split the bidRequest to have them seperated by adType. Otherwise some DSPs did not bid on video, but for banner only.
We reworked a possible solution for the bidder on our own and running it since more than one year, but it would be better to have an official solution.

Steps to reproduce

Using banner and video adUnit at the same time on one page.

Test page

Expected results

Separated bidRequests for each adType.

Actual results

Only one bidRequest is generated for both adType (see in description above).

Platform details

Prebid 8.37.0, but within version 9.16.0 the request url is still generated in the same way.

Other information

@dgirardi
Copy link
Collaborator

This needs to be addressed by the SSP (@philipwatson ?). If you have a business relationship with them you're probably better able than we are to bring this to their attention. Multiple formats in the same request is not necessarily a problem, especially on the client side.

@patmmccann
Copy link
Collaborator

patmmccann commented Nov 4, 2024

Please see https://docs.prebid.org/dev-docs/adunit-reference.html#twin-adunit-codes for a publisher side solution. The ideal solution would be for the SSP to handle splitting requests on their side for the DSPs incapable of handling multiformat. As this number should be going to zero over time, a client side solution seems less than ideal.

@vlyby-nadja
Copy link
Author

Thanks @patmmccann, this is clear and already in use.
The main "issue" is, the standard behaviour of the bidder will run only one bidRequest regardless of whether the request contain banner and video adunit at the same time.
We reworked the bidder in our local fork somehow similar to Rubicon bidder, which uses config option "singleRequest", to split the bidRequests by adType. But this is not a common solution and could cause issues in the furture when the bidder get updated on this.

That's why we asked for an offical way either by the bidder itself or the SSP directly.

@philipwatson Do you have any recommendation on that?

@philipwatson
Copy link
Contributor

Hi @vlyby-nadja

We do have a split config on the server-side that we can enable for a DSP - it turns every impression into its own separate request. Do you know the DSPs? If so, let us know and we'll look into it.

Unfortunately, we don't have a config that enables split by ad type (format). But is something we can easily support in the prebid.js bidder. I'll propose the idea to my PM.

@vlyby-nadja
Copy link
Author

Hi @philipwatson,
unfortunately, we don't now the exact infected DSPs. It was only described as "some DPSs", including the one from Ströer.
We act as an technical provider and multiple publishers can use our service, including your bidder. I assume, that all of them could have different DSPs in the background.
So from my perspective a general solution would be better in that case.

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

No branches or pull requests

4 participants