Experimental: This is an experimental technology
Check the Browser compatibility table carefully before using this in production.
Non-standard: This feature is not standardized. We do not recommend using non-standard features in production, as they have limited browser support, and may change or be removed. However, they can be a suitable alternative in specific cases where no standard option exists.
Warning: This feature is currently opposed by two browser vendors. See the Standards positions section for details of opposition.
Note: An Enrollment process is required to use this feature in your applications.
The HTTP Sec-Browsing-Topics request header sends the selected topics for the current user along with the associated request, which are used by an ad tech platform to choose a personalized ad to display.
If the calling site does not have the Topics API included in a successful privacy sandbox enrollment process, attempting to create or modify Sec-Browsing-Topics fails silently, and any existing Sec-Browsing-Topics header is deleted.
See Using the Topics API for more details.
SyntaxSec-Browsing-Topics: <array-of-observed-topics>
A JSON object representing an array of up to three objects representing the current user's selected topics for the last three epochs. Each object contains the following properties:
configVersion
A string identifying the algorithm (other than the model part) used to calculate the topic.
modelVersion
A string representing the model used to classify a string (such as a web page's hostname) into topic IDs.
taxonomyVersion
A string representing the taxonomy version used.
topic
A number representing the ID of the topic, which can be used by the browser to retrieve the topic from the taxonomy (see an example taxonomy of interests).
version
The configVersion, modelVersion, and taxonomyVersion, concatenated with colons (:) between each.
The exact property values may vary by browser implementation. An example header from Chrome might look as follows:
Sec-Browsing-Topics: [{configVersion: "chrome.1", modelVersion: "1", taxonomyVersion: "1", topic: 43, version: "chrome.1:1:1"}]
This feature is not part of an official standard, although it is specified in the Topics API Unofficial Proposal Draft.
Browser compatibility See alsoRetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4