New PBS-Java module: optable-targeting #5931
Conversation
✅ Deploy Preview for prebid-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
…ds -> user.eids (as server converts user.ext.eids to user.eids according to OpenRTB 2.6)
bretg
left a comment
bretg
left a comment
There was a problem hiding this comment.
The text is fine - thanks for being thorough. However, I have a problem with the design of this module. I strongly dislike that it slows every auction for a WAN call, and that WAN endpoint is global to the account. This is a recipe for performance problems.
I would like you to consider an alternate configuration design where:
- the host company can link your regional endpoints to their own datacenters. e.g. I want to point to your US endpoint in the US, your EU endpoint in the EU, etc.
- any account-level data is appended to this host-level URL
Further, I'd like to request that you consider making use of the local Prebid Cache to store data for ~24 hours. WAN calls are likely to be much slower than local cache calls.
|
Hi @bretg, thank you for the review! We'll work on addressing these design issues. |
|
Hi guys! |
7 participants
The optable-targeting module enriches an incoming OpenRTB request by adding to the user.ext.eids and user.ext.data objects. Under the hood the module extracts PPIDs (publisher provided IDs) from the incoming request's user.ext.eids, and also if provided sha256-hashed email, sha256-hashed phone, zip or Optable Visitor ID provided correspondingly in the user.ext.optable.email, .phone, .zip, .vid fields. These IDs are sent as input to the Targeting API. The received response data is used to enrich the OpenRTB request and response. Targeting API endpoint is configurable per publisher.
🏷 Type of documentation
📋 Checklist