Added adapter for Conversant Media #708
Conversation
| responseNurl = conversantBid.nurl || ''; | ||
|
|
||
| // Our bid! | ||
| bid = bidfactory.createBid(1); |
There was a problem hiding this comment.
pass the bid object as 2nd argument to sync bid request and response IDs. See #509
| } else { | ||
| //0 price bid | ||
| //indicate that there is no bid for this placement | ||
| bid = bidfactory.createBid(2); |
There was a problem hiding this comment.
pass the bid object as 2nd argument to sync bid request and response IDs. See #509
|
@msahagu2 |
|
|
||
| 'site': { | ||
| 'id': siteId, | ||
| 'mobile': document.querySelector('meta[name="viewport"][content*="width=device-width"]') !== null ? 1 : 0, |
There was a problem hiding this comment.
is the presence of this meta tag a reliable way to detect mobile clients? Our responsive site at washingtonian.com includes this meta tag for everyone.
There was a problem hiding this comment.
The mobile field is there to determine if the site's layout can be optimized when on mobile clients. Not necessarily that they are mobile
There was a problem hiding this comment.
I see, thank you @msahagu2! 👍
| n = navigator; | ||
|
|
||
| // production endpoint | ||
| var conversantUrl = '//media.msg.dotomi.com/s2s/header?callback=$$PREBID_GLOBAL$$.conversantResponse'; |
There was a problem hiding this comment.
@msahagu2 can you request an Access-Control-Allow-Origin: * header for this endpoint?
There was a problem hiding this comment.
Do you know what ad sizes are requested? We're currently working on a fix for the headers of our 204 responses
There was a problem hiding this comment.
I am told by T. Rex at Conversant that the site_id numeric value must be passed as a string (buh?) so can you catch this case in the adapter @msahagu2
Type of change
Description of change
Added adapter for Conversant Media