[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
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.

Sign up for GitHub

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

Jump to bottom

Ability to request multiple ads on a single ad request #9115

Closed
jasti opened this issue May 3, 2017 · 3 comments
Closed

Ability to request multiple ads on a single ad request #9115

jasti opened this issue May 3, 2017 · 3 comments
Assignees
@keithwrightbos
Labels
Type: Feature Request WG: monetization
Milestone
Prioritized FRs

Comments

@jasti
Copy link
Contributor
jasti commented May 3, 2017

At the moment all amp-ad implementations are only able to make a single ad request per ad slot. Larger publishers often like to correlate ad slots for ad roadblocks or competitive exclusions. This feature request is to allow a way for ad networks to do that.
@jasti jasti added this to the Prioritized FRs milestone May 3, 2017
@dpetrieldn
Copy link

Hi @jasti , in terms of comparing this behaviour to an existing GPT implementation, would this just be keeping the correlator the same for each request, running with Single Request Architecture (SRA), or a mixture of both?

Thanks

@jasti
Copy link
Contributor Author
jasti commented May 3, 2017

@dpetrieldn , @keithwrightbos will be posting an ITI on this in the next week or two with details.
This will be only for the 'Fast Fetch' flow - so it will be an implementation similar to GPT but will not use the underlying GPT.js library.

@keithwrightbos keithwrightbos mentioned this issue May 10, 2017
Merged
@keithwrightbos keithwrightbos mentioned this issue May 25, 2017
Merged
@keithwrightbos
Copy link
Contributor

beta now available for SRA. Note the backend code does not yet support per creative AMP creative validation meaning AMP creatives do not get preferential render (but do render correctly within xdomain frame).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@keithwrightbos keithwrightbos

Labels
Type: Feature Request WG: monetization
Projects
None yet
Milestone
Prioritized FRs
Development

No branches or pull requests
3 participants
@keithwrightbos @jasti @dpetrieldn