DATA-22937: LI analytics adapter

[SuperIzya]

🔧 Type of changes

• new bid adapter
• bid adapter update
• new feature
• new analytics adapter
• new module
• module update
• bugfix
• documentation
• configuration
• dependency update
• tech debt (test coverage, refactorings, etc.)

✨ What's the context?

What's the context for the changes?

🧠 Rationale behind the change

Why did you choose to make these changes? Were there any trade-offs you had to consider?

🔎 New Bid Adapter Checklist

• verify email contact works
• NO fully dynamic hostnames
• geographic host parameters are NOT required
• direct use of HTTP is prohibited - implement an existing Bidder interface that will do all the job
• if the ORTB is just forwarded to the endpoint, use the generic adapter - define the new adapter as the alias of the generic adapter
• cover an adapter configuration with an integration test

🧪 Test plan

How do you know the changes are safe to ship to production?

🏎 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?

[cursor]

This PR is being reviewed by Cursor Bugbot

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[cursor]

Bug: Missing Validation Causes Null Pointer Exceptions

The LiveIntentAnalyticsConfigurationProperties class lacks @NotNull validation on its partnerId and analyticsEndpoint fields, unlike other analytics configurations here. This omission means critical properties can be null, potentially causing NullPointerExceptions when building URIs or using the partnerId in the LiveIntentAnalyticsReporter.

 

[cursor]

Bug: URIBuilder Overwrites Base Path Incorrectly

The URIBuilder.setPath() method replaces the entire path component of the URI. If the analytics endpoint is configured with a base path, this overwrites it when constructing URLs for both auction and notification events, leading to requests sent to incorrect endpoints.

Additional Locations (1)

• src/main/java/org/prebid/server/analytics/reporter/liveintent/LiveIntentAnalyticsReporter.java#L172-L177

 

[cursor]

This PR is being reviewed by Cursor Bugbot

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[cursor]

Bug: URIBuilder Overwrites Path Instead of Appending

URIBuilder.setPath() replaces the entire path component of the URI instead of appending to it. If properties.getAnalyticsEndpoint() contains a path (e.g., "https://api.example.com/v1"), calling setPath("/analytic-events/pbsj-bids") will replace "/v1" with "/analytic-events/pbsj-bids", resulting in "https://api.example.com/analytic-events/pbsj-bids" instead of the likely intended "https://api.example.com/v1/analytic-events/pbsj-bids". The same issue exists in processNotificationEvent at lines 173-178. Consider using appendPath() or constructing the full path by concatenating with the existing path from the base endpoint.