Skip to content

Conversation

@zapo
Copy link
Contributor

@zapo zapo commented Mar 7, 2025

🔧 Type of changes

  • new module

✨ What's the context?

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.

prebid/prebid.github.io#5931

🧪 Test plan

The documentation PR describes how to run a demo and this PR also contains a sample config and sample request to test. The only thing necessary will be the Optable api endpoint URL to add to the sample configuration of the module.

🏎 Quality check

  • Are your changes following our code style guidelines?
  • Are there any breaking changes in your code?
  • Does your test coverage exceed 90%?
  • Are there any erroneous console logs, debuggers or leftover code in your changes?

@zapo zapo marked this pull request as ready for review March 7, 2025 16:56
@osulzhenko osulzhenko requested a review from CTMBNara March 10, 2025 09:36
@softcoder594 softcoder594 force-pushed the optable-targeting-module branch from b2cb2bf to afaae43 Compare March 10, 2025 20:58
@osulzhenko osulzhenko requested a review from And1sS March 18, 2025 10:42
@justadreamer
Copy link
Contributor

Hi guys, @And1sS @CTMBNara, just checking: any ETA to get a review? Thanks.

Copy link
Collaborator

@And1sS And1sS left a comment

Choose a reason for hiding this comment

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

First take ;)

Copy link
Collaborator

Choose a reason for hiding this comment

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

Merge it to your sample config please.

Copy link
Contributor

@softcoder594 softcoder594 Mar 27, 2025

Choose a reason for hiding this comment

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

I can't merge them into one sample config because it contains account settings. I need this change to enable AnalyticsTags.

According to the documentation, account settings should be placed in a separate file: Prebid Server Java - Application Settings.

When I try to move the account settings to the sample config file, the account doesn't work.

@justadreamer
Copy link
Contributor

Hi @And1sS, thanks for the first pass. @softcoder594 has addressed the review comments. Could you please take another look?

@softcoder594 softcoder594 force-pushed the optable-targeting-module branch from ef0f7f2 to 7df560b Compare April 17, 2025 13:00
@justadreamer
Copy link
Contributor

justadreamer commented Apr 17, 2025

Hi guys! 2 new features were added per Bret's suggestion:

  • Optable Targeting API endpoint is now added to the host-level config with tenant and origin parameters at the account-level config
  • Prebid Cache Storage is now used to cache Optable Targeting API results

Would you mind doing another review pass, please?

@zapo zapo requested a review from And1sS April 28, 2025 20:36
@zapo zapo requested review from CTMBNara and softcoder594 June 16, 2025 14:24
@zapo zapo requested a review from CTMBNara June 27, 2025 17:17
@zapo zapo requested a review from CTMBNara July 7, 2025 15:10
@zapo zapo requested a review from CTMBNara July 14, 2025 13:38
@CTMBNara CTMBNara merged commit 3bdbe21 into prebid:master Jul 30, 2025
8 of 9 checks passed
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.

6 participants