consumable: updated yaml config #4139
Conversation
- endpoint-compression: gzip - geoscope: USA, CAN, MEX - target-currency: USD
| redirect: | ||
| url: https://e.serverbid.com/udb/9969/match?gdpr={{gdpr}}&euconsent={{gdpr_consent}}&us_privacy={{us_privacy}}&gpp={{gpp}}&gpp_sid={{gpp_sid}}&redir={{redirect_url}} | ||
| support-cors: false | ||
| target-currency: "USD" |
There was a problem hiding this comment.
This property is not expected by the bidder. What's the purpose of it? Probably some changes to the bidder are required. But it's redundant for now.
There was a problem hiding this comment.
would using meta-info.currency-accepted be the correct one to use? link
There was a problem hiding this comment.
Could you describe what is the purpose of the currency-accepted property? For now the bidder doesn't know about this property so it just ignores the property. I believe it should be a separate PR for the ConsumableBidder to make it utilize the property - and the correct way for the property to be added is within that PR.
There was a problem hiding this comment.
We are reacting to this email sent from the prebid-server project that requests setting currency-accepted. Is this field unsupported by prebid-server-java?
--
Prebid Server adapter community - many of you are in the midst of 2025 planning, and the Prebid Server committee would like everyone to consider their Prebid Server adapter maintenance plans:
OpenRTB 2.6 is no longer new. Bid adapters should be thinking about when they will be able to accept regs.gdpr instead of regs.ext.gdpr, user.eids instead of user.ext.eids, source.chain instead of source.ext.schain, regs.us_privacy instead of regs.ext.us_privacy, and user.consent instead of user.ext.consent.
Think about currency. The bidder YAML files now support a currency-accepted field. If your endpoint only supports a limited set of currencies, please consider setting this field so your endpoint is not called when other currencies are specified.
Think about geographic scope. The bidder YAML files support defining the region that you do business in. Please consider setting this field so your endpoint is not called when you're not likely to bid. It saves everyone operational fees and saves carbon emissions.
Consider emerging formats. Digital Out Of Home is already supported, and Prebid will provide better support for Audio and CTV in 2025. Your support for these channels and formats can be declared in your bidder YAML file.
Please consider gzip compression. This will save both you and the Prebid Server host companies network fees.
Publishers want to use multiformat adunits. For example, they want to be able to run both banner and "standalone video" in the same slot. Many bidders cannot handle an OpenRTB impression containing both banner and video or both banner and native. We ask that everyone work towards having a clear multiformat strategy either pick one or bid on any available. Please don't fail or bid incorrectly.
Publishers are also looking to have a deeper understanding of why a bidder is not bidding on the auctions. Please consider providing better No Bid Reasons in your bid responses.
Finally, and maybe most important in this age, everyone should be thinking about user IDs and first party data. 3rd party cookies are already not supported on many browsers, and they may disappear altogether in 2025. Instead of relying on a vendor-specific buyeruid, everyone should be thinking about support for other IDs like SharedId, UID2, ID5, LiveIntent, etc. Everyone should be looking to utilize Seller-Defined Audiences and other forms of first party data.
thank you, and happy holidays
Bret Gorsline
Chair, Prebid Server Committee
There was a problem hiding this comment.
Looks like this feature is somewhere on the horizon, but at least for now it's not supported for PBS Java, and as I know it's not supported for the PBS Go as well. I believe the best way to increase the priority for that is to communicate it at the Prebid Committee or create a github issue in the https://github.com/prebid/prebid-server/issues.
FYI @Net-burst
…umable/geo-compression-currency
- endpoint-compression: gzip - target-currency: USD
- endpoint-compression: gzip - target-currency: USD
- endpoint-compression: gzip
🔧 Type of changes
✨ What's the context?
🧠 Rationale behind the change
🧪 Test plan
🏎 Quality check