Publisher Guide: How to activate Protected Audience and Topics on your sites
Stay organized with collections
Save and categorize content based on your preferences.
Publishers have several ways to activate Protected Audience and Topics,
depending on how their ad tech vendors are integrating the technologies.
The following are some of the integration types that are available. Publishers
should verify which implementation types their ad tech partners support.
Enable Protected Audience
Direct
If you run your own ad stack, you can implement the APIs directly. The
Protected Audience API
documentation
explains how.
Ad server
If you work with an ad server that can enable the Protected Audience
API on your behalf, refer to their documentation.
Header Bidding
Prebid: If you work with SSPs using Prebid, see
the
overview
of sequential auction setups. For implementation, you can reference the
Prebid documentation.
You should check with your SSPs for their specific guidance on
integrating through Prebid. Guidance may include a minimum Prebid version
and installation of a
module.
More header bidders may integrate with Protected Audience in the future.
Check the documentation of the header bidding library you use for
implementation.
Enable Topics
Ad Server or SSP
An Ad Server or SSP can request Topics on their publisher partner pages
using
HTTP headers
or
JavaScript
if they have a tag or code on page.
Header Bidding
Prebid: If you work with SSPs using Prebid, there
are a couple of options for how you can enable Topics. You should
check with your SSPs for their specific guidance on integrating through
Prebid.
Using Prebid.js Core: Prebid
has released a feature
in the Prebid
8.9.0+ that
enables Topics to be accessed and included in outgoing bid requests.
Using Topics module: SSPs that participate in Prebid can also
reference the Prebid documentation to learn how to receive Topics using
the
topicsFpdModule.
More header bidders may integrate with Topics in the future. Check the
documentation of the header bidding library you use for implementation.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-11-14 UTC."],[[["Publishers can enable Protected Audience directly via APIs, through their ad server, or using header bidding solutions like Prebid."],["Publishers can enable Topics through their ad server or SSP, by leveraging Prebid's built-in features or dedicated modules, or via Open Bidding integrations."],["It's crucial for publishers to consult their ad tech partners to determine which integration methods are supported and to follow their specific implementation guidance."],["Prebid offers support for both Protected Audience and Topics, with detailed documentation and resources available for publishers and SSPs."],["Header bidding libraries are continuously evolving, and publishers should stay informed about updates and new integrations for Protected Audience and Topics."]]],["Publishers can activate Protected Audience directly via API implementation, through an ad server, or via header bidding platforms like Prebid. For Prebid, publishers should consult their SSPs for integration guidance, referencing Prebid's documentation. Activating Topics can be done through an ad server or SSP using HTTP headers or JavaScript, or via Prebid. Open Bidding also allows SSPs to receive Topics. Publishers must consult their ad tech partners' documentation for specific integration methods.\n"]]
