-
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
Support DFP Premium Same Ad Unit Multiple Slots #69
Comments
Proposed solution: Instead of using For example:
If 2 prebid ad units for some reason share the same code (DFP slot element ID) in this case, we'll combine the 2 ad units' result bids together. GPT has the function |
👍 this feature request, this is currently a blocking item for us. |
Update: I have been fiddling around with the source code a bit and have been able to get two ads of different sizes using the same slot with the suggested method above.
with adUnits defined:
and
The necessary code change appears to be in prebid.js at
where the adUnitCode is now based on the SlotElementId as suggested, though the GPTAsyncTargeting is still based on the adUnitPath as it was previously. I have added this to a forked PR #77 |
Thanks for the contributing. I will also update the code to reflect a fallback to |
…11.0 to master * commit 'e0e25bc31e66fe7c89003741d654ea6b25fb1a21': Mistype fix. Removed conflict message leftover. Change method names, simplified regex, DOMReady logic introduced. Minor changes in the code. Small changes. Removed adapter. Adding functionality of cookie syncing upon bid request
As a publisher, I would like Prebid.js to support the case where I have one ad unit reused across multiple slots. For example:
(In this case, the same ad unit is served into multiple ad slots)
(In this case, multiple ad units serve into the same ad slot)
We need to come up with an example to support the above cases.
The text was updated successfully, but these errors were encountered: