You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The goal is to eventually move everything to ORTB, so that's what we recommend for new implementations. There are a number of adapters that do native ORTB, but all of them get it "for free" through the ortbConverter library. For example:
From what I can tell Smilewanted does not talk ORTB - so you may need to do more legwork in the adapter. See also this discussion about the gaps between legacy and ORTB:
Type of issue
Question
Description
Hi, I'm from Smilewanted and we have several questions about adding the Native Support to our Adapter.
The documentation here https://docs.prebid.org/prebid/native-implementation.html suggests to pass a Native OpenRTB 1.2 bidrequest in mediatypes.native.ortb, but every other adapters use the legacy version https://docs.prebid.org/prebid/native-implementation-legacy.html or convert the ortb request in legacy via the
convertOrtbRequestToProprietaryNative
function innative.js
.Is there any reason not to use the ortb method rather than the legacy method?
Is the documentation for the ortb method too recent?
What is the recommended way to implement Native in Adapters ?
The text was updated successfully, but these errors were encountered: