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

pass site.{} into prebid server request #3783

Closed
wants to merge 3 commits into from

Conversation

AntoineJac
Copy link
Contributor

Type of change

  • Feature

Description of change

Some publisher want to pass keywords to prebid server and current code only read pbjs.setConfig(app{}) not pbjs.setConfig(site{})
This code will pass the data in config.site to the prebid server request

Other information

Prebid server is already able to read data passed in $.site.keywords

Antoine Jacquemin (Rubicon) added 3 commits April 26, 2019 11:23
One publisher want to pass keywords to prebid server and current code only read pbjs.setConfig(app{}) not site.
Prebid server is already able to read data passed in $.site.keywords
@bretg
Copy link
Collaborator

bretg commented Apr 26, 2019

Thanks for the PR @AntoineJac, but would like to bring this in line with the design for first party data we finalized in #3687

setConfig({site}) is not currently part of the PBJS externally facing API. IMO, it would be better not to have multiple ways to specify keywords.

Finally, I'm not comfortable that this proposed change has the side-effect of removing site.publisher and site.page if the user doesn't provide them.

So my requested change is to specify keywords in setConfig({context}) rather than setConfig({site})

This change should ideally be packaged with the full implementation of first party data (which is on the Rubicon internal queue), but I gather you have a more immediate need for keywords, so I suppose jumping the gun on this one part of first party data is ok.

On a tangent, why do we accept setConfig({app})?

  • Apps use the SDK, not PBJS
  • This 'feature' isn't documented anywhere

Searched for the history of this feature but it's pretty old -- beyond the refactoring. Anyone recall the use case? If not, I propose removing it. That wouldn't really be a breaking change because it undocumented.

@AntoineJac
Copy link
Contributor Author

@bretg , here the documentation for setConfig({app}):
http://prebid.org/faq/prebid-server-faq.html#how-can-i-use-prebid-server-in-a-mobile-app-post-bid-scenario

This is important to not remove it as I have several clients using it on a postbid environment!

Regarding setConfig({site}) I am ok to wait for the new design for first party data. Thanks

@bretg
Copy link
Collaborator

bretg commented Apr 29, 2019

Good to know. Made a PR to update the post-bid docs. prebid/prebid.github.io#1288

Can we close this PR then?

@bretg bretg self-assigned this Apr 29, 2019
@AntoineJac
Copy link
Contributor Author

Yes perfect thanks @bretg

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

Successfully merging this pull request may close these issues.

None yet

2 participants