Integrate DoubleVerify Support into TS #56

Description

Determine the Trusted Server integration contract for DoubleVerify and implement the agreed path. The original issue had only a title; its discussion records a plan to follow up with the vendor, but does not specify a product, endpoint, credentials, or which traffic should be evaluated. Those choices must be made before code changes are scoped.

Proposed scope

• Confirm the vendor contact and document the supported use case, required request/response data, authentication, and decision point in the ad-serving flow.
• Identify which Trusted Server serving paths can supply that data and how failures, latency, and consent should be handled.
• Implement only the agreed integration surface, with configuration, observable outcomes, and operator instructions.

Done when

• The vendor/product contract and Trusted Server behavior are recorded in a reviewable integration spec, including failure and privacy handling.
• The agreed path works in a representative end-to-end test or vendor sandbox, with success and failure cases covered.
• Deployment configuration and operational limits are documented, or the issue is closed with the reason integration is out of scope.

Related

The May 2026 issue comment records vendor follow-up; it is not evidence that an integration contract was agreed.