Determining Native Video Support After Switching to openRTB Protocol
41 views
Skip to first unread message
陈秀
Feb 26, 2025, 3:19:44 AM
Feb 26
to Authorized Buyers API Forum
After switching to the openRTB protocol, how can we determine whether native video types are supported?
We have found that there is almost no native video traffic in the received requests.
Authorized Buyers API Forum Advisor
Feb 26, 2025, 1:17:39 PM
Feb 26
to chenann2...@gmail.com, google-doubleclick-a...@googlegroups.com
Hello,
Similar to Google's RTB protocol, our OpenRTB implementation indicates when video is expected for a native ad opportunity in the bid request. This information is found in the BidRequest.imp.native.{request/request_native}.assets field–note that the path and representation of NativeRequest differs depending on the format you have selected for OpenRTB (i.e. JSON or Protobuf). So in order to identify cases where the ad opportunity is for a native video creative, you need to determine whether a video asset is included in the NativeRequest .
That said, assuming that you are checking for video assets and are finding that the number of native video impressions has decreased, that wouldn't be expected behavior. We haven't noticed such a difference reported by other customers thus far. Other factors could potentially explain the difference, such as changes in targeting–e.g. even changes not directly related to format can potentially impact the amount of times a particular format appears in bid requests. As a hypothetical, if your geographic targeting changed to a region where less ad opportunities happen to exist for a particular format, that could lower the number of bid requests you see for that format.
If you don't think this is related to targeting or a misunderstanding of the native request, we could take a closer look. We would need more information about the specifics of your account though, and this public support forum is not an ideal place to share that information. I'd recommend contacting our support alias ( adxbuyera...@google.com ) for a private discussion if you want us to investigate further. As a starting point, it would be helpful to have the account ID that you're noticing this behavior for.
Thanks,
Similar to Google's RTB protocol, our OpenRTB implementation indicates when video is expected for a native ad opportunity in the bid request. This information is found in the BidRequest.imp.native.{request/request_native}.assets field–note that the path and representation of NativeRequest differs depending on the format you have selected for OpenRTB (i.e. JSON or Protobuf). So in order to identify cases where the ad opportunity is for a native video creative, you need to determine whether a video asset is included in the NativeRequest .
That said, assuming that you are checking for video assets and are finding that the number of native video impressions has decreased, that wouldn't be expected behavior. We haven't noticed such a difference reported by other customers thus far. Other factors could potentially explain the difference, such as changes in targeting–e.g. even changes not directly related to format can potentially impact the amount of times a particular format appears in bid requests. As a hypothetical, if your geographic targeting changed to a region where less ad opportunities happen to exist for a particular format, that could lower the number of bid requests you see for that format.
If you don't think this is related to targeting or a misunderstanding of the native request, we could take a closer look. We would need more information about the specifics of your account though, and this public support forum is not an ideal place to share that information. I'd recommend contacting our support alias ( adxbuyera...@google.com ) for a private discussion if you want us to investigate further. As a starting point, it would be helpful to have the account ID that you're noticing this behavior for.
Thanks,
Mark Saniscalchi
Authorized Buyers API Team
Feedback
How was our support today?
[2025-02-26 18:17:35Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vH40A:ref" (ADR-00289870)
Reply all
Reply to author
Forward
Search
Clear search
Close search
Google apps
Main menu
