Skip to content

Q: Why browsingTopics: true by default on all outgoing bidder requests? #11148

@orazumov-zeta

Description

@orazumov-zeta

Type of issue

Question

Description

Why browsingTopics: true by default on outgoing bidder requests? (sources)
Related PR: Core: enable Sec-Browsing-Topics header on outgoing bidder requests #10340

image

Not all bidders support this. As a result, in Chrome console, I see numerous errors of the type 'Attestation check for Topics on URL failed.' There is an option 'topicsHeader' to control this. Perhaps it would be better to have browsingTopics enabled not by default, but only when this option is explicitly specified?

Steps to reproduce

Open the Chrome browser console on any page where Prebid.js is running with configured bidders that do not support browsingTopics (for example, appnexus, mediafuse, sovrn, minutemedia, etc.). You will see errors Attestation check for Topics on URL failed.

image

Test page

Here you can see such error: https://www.bmwblog.com/2024/02/26/how-a-bmw-7-series-turned-from-city-cruiser-to-off-road-adventurer/

Expected results

Actual results

Platform details

Prebid.js 8.35
Chrome 121.0.6167.184 (Official Build) (arm64)

Other information

Core: enable Sec-Browsing-Topics header on outgoing bidder requests

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions