-
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
Added new types of traffic Colossus SSP adapter #2281
Conversation
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.
Hello @HuddledMasses ,
If you are planning to support video & native, the colossus SSP bidder spec should include
supportedMediaTypes: ['banner', 'video', 'native'],
(below aliases
or anywhere in the spec is fine). See this note in the docs for more info on supporting video & native (if you haven't already).
Additionally, can you please also remove the changes to the package-lock.json
file from this PR? Thanks!
Hi @jsnellbaker |
Hi @HuddledMasses I'm a bit confused, you are planning to support banner, video and native - right? If so, the docs PR only included the banner support. Shouldn't it also note the video & native support? Also, did you have the chance to look at the recommendations for this PR? Thanks. |
We updated pull request. |
Hi @HuddledMasses , thanks for submitting the update. I was trying to test the adapter with the test params included in the PR (for the video ad unit?), but the adapter code wasn't accepting the bid response. It seems like a banner type unit came back instead of a video type. Further the bid was rejected because it didn't contain a Can you take a look at the test param information/bid response? Also, if you're going to now support additional ad unit types, I'd like to test each type (banner, video, native) to ensure they're all working successfully with your updated adapter. If you can provide test param info for each ad type, I'd greatly appreciate it. For reference here is a copy of the bid response I received: |
Hi @jsnellbaker |
Hi @HuddledMasses, I tested out each of the ad units; see details/feedback below:
When we're receiving a native bid response, certain properties of the native bid response need to be defined in the The following page has a sample markup for the Can you take a look and make the changes? I was using the |
Hi @jsnellbaker |
Hi @HuddledMasses thanks for submitting the changes. Unfortunately, it doesn't seem like the native bid response is being accepted by the internal validation. The issue seems to boil down to where the native information (clickurl, image object) is being stored. It's currently being added to the bid overall, instead into a As an example, this is the current appearance of the bid response object as populated from the adapter:
It should ideally store the native related information like this:
Can you try to make the necessary changes? Please let me know if you have any questions. |
Hi @jsnellbaker |
Hi @HuddledMasses, Thanks again for making the changes. I tested the native ad unit and found it was structured properly and passing the internal checks. However, ad unit wasn't rendering on the test page. While looking over the browser console, I noticed the This is normally used to help render banner and video ads and is invoked from the prebid creative template. The native creative template is different (as it has to handle different creative assets). The following page gives an outline of what the native creative code looks like: http://prebid.org/adops/setting-up-prebid-native-in-dfp.html Can you take a look over this page and try to make the needed changes? I believe we should be good to merge after this is addressed. Thanks! |
@jsnellbaker |
@HuddledMasses There should be a creative in your ad server that would return a 'prebid' creative. Normally this creative is a set of JavaScript that makes the call the Maybe one of the traffickers or adops people on your end may be able to help point you to the area where the changes need to be made? If it will help, below is a link to a more parent-level page on the different ways to setup prebid creatives: |
@jsnellbaker |
@HuddledMasses I'm sorry about the confusion on the last point in this PR. I conferred with a colleague and got this straightened out. It seems everything is fine at this point. I'm going to merge in this PR. |
* add video&native traffic colossus ssp * Native obj validation * Native obj validation #2 * Added size field in requests * fixed test
Team, can you please let us know why Colossus adapter has not been listed here? http://prebid.org/dev-docs/bidders.html#bidders-with-video-and-native-demand |
To have the bidder appear on that table, you'd need to submit a PR to the Prebid Docs repo (located here) to update this file: Just need to add the following variables to the top section (where the other variables are located):
|
Hi @jsnellbaker Please take a look. Thanks! |
Type of change
Description of change
Added new types of traffic Colossus SSP adapter.