Skip to content

New PBS-Java module: optable-targeting #5931

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

Open
wants to merge 15 commits into
base: master
Choose a base branch
from

Conversation

zapo
Copy link
Contributor

@zapo zapo commented Mar 7, 2025

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

  • new PBS-Java module

📋 Checklist

Copy link

netlify bot commented Mar 7, 2025

Deploy Preview for prebid-docs-preview ready!

Name Link
🔨 Latest commit bd3f157
🔍 Latest deploy log https://app.netlify.com/sites/prebid-docs-preview/deploys/6800fafba4e6000008afa8f2
😎 Deploy Preview https://deploy-preview-5931--prebid-docs-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@zapo zapo marked this pull request as ready for review March 7, 2025 16:56
…ds -> user.eids (as server converts user.ext.eids to user.eids according to OpenRTB 2.6)
Copy link
Contributor

@bretg bretg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@justadreamer
Copy link
Contributor

Hi @bretg, thank you for the review! We'll work on addressing these design issues.

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

Successfully merging this pull request may close these issues.

5 participants