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

Remove BID_TARGETING_SET as criteria for a "used bid" #4148

Closed
mkendall07 opened this issue Sep 3, 2019 · 7 comments
Closed

Remove BID_TARGETING_SET as criteria for a "used bid" #4148

mkendall07 opened this issue Sep 3, 2019 · 7 comments
Labels

Comments

@mkendall07
Copy link
Member

mkendall07 commented Sep 3, 2019

Type of issue

I2I.

Description

Currently we mark bids as used if they are rendered or set in an auction (BID_TARGETING_SET). This means that we will not be able to use a bid (aka, via bid caching) if it is not ultimately rendered in the 1st auction. code link

This makes bid caching somewhat ineffective in most cases when bid caching is enabled.

We will therefore remove the criteria of BID_TARGETING_SET from a used bid and the bid will only be marked as used if it has been rendered.

Risks:
There is a slight risk of sending the same bid to the ad server multiple times if subsequent ad server calls are made repeatedly in a short period of time (such that the 1st ad call did not have time to renderer before the next ad call is made).
Since this is a bad practice (to rapidly refresh ads) we think the risk is worth the tradeoff.

Open for comments.

@pm-harshad-mane
Copy link
Contributor

Looking at the risk of rendering the same bid twice, can we add a logic to use a bid in one auction only at a given time, maybe something like bid.inUse = true flag.

@mkendall07
Copy link
Member Author

Looking at the risk of rendering the same bid twice, can we add a logic to use a bid in one auction only at a given time, maybe something like bid.inUse = true flag.

That is basically the same thing that BID_TARGETING_SET does. So the question becomes, when does the status change to bid.inUse = false if we don't get a callback that the ad did not render?

@pm-harshad-mane
Copy link
Contributor

Mostly after getting the bids from Prebid, a publisher would call the guaranteed server (say GAM).
If bid from Prebid is rendered then we can know that now we need to unset bid.inUse for other bids in a given auction.
But if a bid from Prebid is not rendered then we do not have a way to know when to unset bid.inUse.
To handle the above scenario, can we add a timeout based logic that assumes the max-time until which the bid will be rendered if it wins. We can keep this timeout fairly big like 3000ms and also let publisher configure it as some pubs may fetch bids from Prebid for lazy-loading ad-slots.

@stale
Copy link

stale bot commented Sep 17, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Sep 17, 2019
@stale stale bot closed this as completed Sep 24, 2019
@mkendall07 mkendall07 reopened this Oct 1, 2019
@stale stale bot removed the stale label Oct 1, 2019
@mkendall07 mkendall07 added feature Pub API Change Publisher Facing API change labels Oct 1, 2019
@madma
Copy link
Contributor

madma commented Oct 8, 2019

Since this is a bad practice (to rapidly refresh ads) we think the risk is worth the tradeoff.

Bad practice but seen quite often in production on publisher sites. Personally, I have seen as bad as 30sec refreshes / re-running of the auction. It would be nice to see support for observables so AJAX requests could be terminated. That or something like others suggested using setTimeout in order to effectively expire a bid if it has not been rendered within a certain amount of time .

@patmmccann
Copy link
Collaborator

pretty sure this is good to close, as it is now changed to rendered

@ChrisHuie
Copy link
Collaborator

Closing because changed to render #6020

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants