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

getAdserverTargeting() does returns empty targeting for adUnit slots #2764

Closed
Saigredan opened this issue Jun 22, 2018 · 10 comments
Closed

getAdserverTargeting() does returns empty targeting for adUnit slots #2764

Saigredan opened this issue Jun 22, 2018 · 10 comments

Comments

@Saigredan
Copy link
Contributor

Saigredan commented Jun 22, 2018

Type of issue

Bug

Description

Since 1.15.0 getAdserverTargeting() or related methods are not returning targeting for adUnit slots

Steps to reproduce

Anywhere after auctionEnd event fire getAdserverTargeting() method.

Expected results

Targeting for specified adUnit slots

Actual results

Empty Taregeting for adUnit slots

Platform details

Prebid 1.15.0

Other information

This change from latest release is probably the source of issue:
c82572e

@Saigredan
Copy link
Contributor Author

Anyone else encounters same problem?

@YOzaz
Copy link

YOzaz commented Jun 22, 2018

@Saigredan just on a matter of interest - where do you use getAdserverTargeting() method call?

@Saigredan
Copy link
Contributor Author

@YOzaz We're using it for some internal communication methods. Usually after auction is finished.

@YOzaz
Copy link

YOzaz commented Jun 22, 2018

@Saigredan the reason behind is here: #2676 and here: #2685.
I'm not 100% sure how this fix "fixes" auction concurrency problem, but @jaiminpanchal27 may have more comments on it?

@Saigredan
Copy link
Contributor Author

@YOzaz well, after rollbacking c82572e commit, all started to work just fine (except thing we noted in other Issue #2752)

I will take a look at issues you attached

@YOzaz
Copy link

YOzaz commented Jun 22, 2018

@Saigredan this commit / bugfix solved concurrent auctions issue, when multiple requests for bids were done at the same time - which is actual in our case e.g., as we're lazy-loading ads.

@Saigredan
Copy link
Contributor Author

@YOzaz I see. I will take a deeper look

@jaiminpanchal27
Copy link
Collaborator

@YOzaz @Saigredan I added c82572e commit, because getAdserverTargeting() was including all bids received to get targeting.

What it should be doing is select bid from bid pool, and apply following filters

  • should be unused bid
  • should not be expired

@harpere
Copy link
Collaborator

harpere commented Jun 22, 2018

@Saigredan can we close this?

@Saigredan
Copy link
Contributor Author

@harpere yes, please :)

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

No branches or pull requests

4 participants