Skip to content
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

Feature Request - add support video assets in Prebid Native #10275

Open
jsnellbaker opened this issue Jul 24, 2023 · 1 comment
Open

Feature Request - add support video assets in Prebid Native #10275

jsnellbaker opened this issue Jul 24, 2023 · 1 comment

Comments

@jsnellbaker
Copy link
Collaborator

Type of issue

Feature Request

Description

As a follow-up to a comment made in another issue (#10249 (comment)), I'm creating this feature request to add support for video assets in Prebid.js Native.

The video asset could be integrated for both the 'legacy' native approach and for the ORTB native approach that are still currently supported in Prebid.js; additionally the conversion functions that exist in the native.js could be updated to support forward and backward conversions for this video field.

As an example , the request and the response could look like the following:

legacy request (in adUnit):

native: {
  video: {
    required: true|false,
    maxduration: 60,
    minduration: 5,
    mimes: ['...']
    protocols: [1,2,3,...]
  }
}

legacy response:

bid.native.video = '...'  // URL to vast XML

ORTB request:

native: {
  ortb: {
    assets: [{
      id: 0,
      required: true|false,
      video: {
        maxduration: 60,
        minduration: 5,
        mimes: ['...']
        protocols: [1,2,3,...]
      }
    }]
  }
}

ORTB response:

native: {
  ortb: {
    assets: [{
      id: 0,
      video: {
        vasttag: '...'  // URL to vast XML
      }
    }]
  }
}

To note - I'm suggesting the support for legacy since it seems that some people might already be trying to use it, despite it not necessarily being documented on prebid.org, since someone added it to our adapter for example (#9396).

@lcorrigall
Copy link

We'll raise this with the Publishers PMC to get feedback on how we should prioritize this.

@lcorrigall lcorrigall moved this from Triage to Needs Req in Prebid.js Tactical Issues table Jul 31, 2023
@patmmccann patmmccann moved this from Needs Req to Ready for Dev in Prebid.js Tactical Issues table Aug 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Ready for Dev
Development

No branches or pull requests

3 participants