Emit and expose certain attributes from auction in order to create transparency and insight for publishers #198

Description

Publishers need useful, appropriately scoped visibility into auction outcomes. The ticket originally had no description; comments requested requirements and a product spec. Trusted Server now builds auction telemetry rows for summaries, provider calls, and bids, so the remaining work is to specify which attributes publishers should see and how they are exposed rather than assuming no auction data exists.

Proposed scope

• Define the publisher questions to answer and a field matrix covering source, meaning, availability, retention, and privacy constraints for each proposed attribute.
• Compare those requirements with current auction telemetry and identify missing capture, aggregation, and publisher-facing access paths.
• Implement the approved gaps with consistent handling of bid, no-bid, timeout, and failed auctions.

Done when

• A reviewed product spec names the exact publisher-visible fields, their definitions, and access model.
• A publisher can retrieve or view the approved attributes for representative auction outcomes, with tests for missing and sensitive fields.
• Documentation explains interpretation, retention, and known limits; any out-of-scope analytics are split into follow-up work.

Affected area

Auction telemetry, storage, and publisher reporting.