forked from prebid/prebid.github.io
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* initial commit for sustainability * lint * split portal by type * re-titled * feedback * Update sustainability-portal.md * Update statement-on-sustainability.md * Update statement-on-sustainability.md * Update statement-on-sustainability.md --------- Co-authored-by: Stephen Johnston <[email protected]>
- Loading branch information
Showing
6 changed files
with
352 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
--- | ||
layout: page_v2 | ||
title: Prebid Statement on Sustainability | ||
description: Prebid Statement on Sustainability | ||
sidebarType: 0 | ||
--- | ||
|
||
# Prebid Statement on Sustainability | ||
|
||
Digital advertising plays a vital role in the modern economy, connecting businesses with audiences worldwide. However, this connection comes with an environmental cost - from the energy consumed by ad servers to the computational resources required for real-time bidding. As our industry continues to grow, so does our responsibility to address its environmental impact. | ||
|
||
Sustainability in advertising technology isn't just about reducing carbon emissions - it's about creating more efficient systems that benefit both the environment and business operations. This involves examining everything from how we handle bid requests to how we optimize our server infrastructure. While the challenges are complex, they also present opportunities for innovation and collaboration across the digital advertising ecosystem. | ||
|
||
## No Standard Currently | ||
|
||
In the absence of standardized sustainability metrics and protocols, conducting transactions through OpenRTB and similar programmatic systems presents significant challenges. The decentralized nature of programmatic advertising, where multiple parties interact through complex bid streams, makes it particularly difficult to track, measure, and optimize for environmental impact. Currently, there exists no industry standard definition of sustainability. | ||
|
||
This lack of standards means each participant in the supply chain - from publishers to SSPs, DSPs, and advertisers - defines and measures sustainability differently. This fragmentation creates obstacles when attempting to make informed decisions about sustainable advertising practices. For instance, one platform might focus on reducing server calls, while another prioritizes energy-efficient data centers, making it challenging to compare and evaluate partners effectively. | ||
|
||
## The Industry Will Evolve | ||
|
||
The current OpenRTB specification, while robust for traditional trading parameters, lacks standardized fields or mechanisms for communicating sustainability-related information between parties. This absence of common sustainability signals means that even environmentally conscious organizations struggle to automate and scale their green advertising initiatives within existing programmatic frameworks. | ||
|
||
As the digital advertising industry evolves toward more transparent and eco-friendly practices, we expect buying platforms to adopt various methodologies that will continue to evolve. In this context, Prebid.org is positioned to play an essential role in supporting the ecosystem's transition to more sustainable practices. Initially, our focus is on providing comprehensive documentation and guidance to help organizations navigate and implement emerging sustainability approaches. | ||
|
||
## Prebid Will Evolve Too | ||
|
||
This educational and supportive role will naturally evolve as industry standards take shape. When concrete sustainability standards emerge, Prebid.org will expand its involvement to include developing and maintaining specific technical implementations, adapting its open-source solutions to support standardized sustainability measures across the programmatic landscape. | ||
|
||
To begin this journey, we're proud to introduce the Prebid.org [Sustainability Portal](/support/sustainability-portal.html). This resource serves as a crucial first step - a central hub where members of the advertising ecosystem can access information about configuration best practices, monitoring approaches, and optimization techniques. The portal is designed to help organizations start taking meaningful action today while preparing for the standardized sustainability frameworks of tomorrow. | ||
|
||
The Sustainability Portal represents our commitment to supporting the ecosystem's environmental initiatives, providing practical guidance that organizations can implement now, while remaining flexible enough to adapt as industry standards develop and mature. | ||
|
||
## Related Reading | ||
|
||
- [Prebid Sustainability Portal](/support/sustainability-portal.html) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
--- | ||
layout: page_v2 | ||
title: Analytics Sustainability Best Practices | ||
description: Analytics Sustainability Best Practices | ||
sidebarType: 7 | ||
--- | ||
|
||
# Analytics Sustainability Best Practices | ||
{:.no_toc} | ||
|
||
- TOC | ||
{:toc} | ||
|
||
## Overview | ||
|
||
This page collects recommendations for analytics providers interested in exploring ways to save carbon emissions while preserving revenue. See the [Susta | ||
inability Portal](/support/sustainability-portal.html) for more background. | ||
|
||
## Tip 1: Connection reuse | ||
|
||
Much like bidders, analytics adapters should reuse connections as much as possible. Enabling HTTP2/3 and bundling of events can be impactful. | ||
|
||
More importantly, analytics events should be buffered and sent as a group where possible. For example, don't send separate payloads for the auction event, the bid response event, the bid won event, etc. Combine them into one payload. | ||
|
||
## Tip 2: Reduce sent payloads | ||
|
||
Send only the data that you need and can process. Avoid sending long data fields that are potentially duplicate or not needed. | ||
|
||
Specific examples: | ||
|
||
- Don't send the TCF or GPP strings if you're not parsing them. Consider sending just the privacy flags needed. | ||
- Don't send User Agent strings in the payload when they can be obtained from the HTTP header. | ||
|
||
## Tip: 3 Reduce response payloads | ||
|
||
Do not send unnecessarily verbose responses. An empty 204 response is all that is usually necessary. If you have a need for more verbose responses then consider compression. | ||
|
||
## Further Reading | ||
|
||
- [Prebid Statement on Sustainability](/overview/statement-on-sustainability.html) | ||
- [Prebid Sustainability Portal](/support/sustainability-portal.html) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,47 @@ | ||
--- | ||
layout: page_v2 | ||
title: Bidder Sustainability Best Practices | ||
description: Bidder Sustainability Best Practices | ||
sidebarType: 7 | ||
--- | ||
|
||
# Bidder Sustainability Best Practices | ||
{:.no_toc} | ||
|
||
- TOC | ||
{:toc} | ||
|
||
## Overview | ||
|
||
This page collects recommendations for Prebid bidders (SSPs, DSPs, etc.) interested in exploring ways to save carbon emissions while preserving revenue. See the [Sustainability Portal](/support/sustainability-portal.html) for more background. | ||
|
||
## Tip 1: Use HTTP2/3 | ||
|
||
Update your endpoints to support HTTP 2 and HTTP 3. This helps because optimizing connection reuse is beneficial. The later protocols limit client side and transport resource usage and are expected to generally improve performance. | ||
|
||
## Tip 2: Reduce payloads | ||
|
||
Determine if extraneous JSON or other payload is being delivered to your endpoint. | ||
|
||
## Tip 3: Enable compression | ||
|
||
Once the required payload is determined, make sure compression is enabled on your endpoint to make the response smaller over the wire. | ||
|
||
## Tip 4: Reduce your adapter size | ||
|
||
Remove or consolidate duplicate code and consider using [the ORTB library](https://github.com/prebid/Prebid.js/blob/master/libraries/ortbConverter/README.md) if your bidder endpoint is oRTB compatible. The [Rix Bidder](https://github.com/prebid/Prebid.js/blob/master/modules/rixengineBidAdapter.js) is an example of using library and shared functions to reduce code size. | ||
|
||
## Tip 5: Combine requests | ||
|
||
Whenever possible send as many bid requests in the same network request as possible. Prebid.js supports this by default with multiple impression and multiple mediatype support. | ||
|
||
For example, if your endpoint currently requires separate requests for each adunit or for each mediatype, you should plan to upgrade to be able to handle richer scenarios. | ||
|
||
## Tip 6: Reduce response payloads | ||
|
||
Do not send unnecessarily verbose responses. For a 'no bid', many analytics adapters would like to receive a "no bid reason", but other than that, the response should be small. If you have a need for more verbose responses then consider compression. | ||
|
||
## Further Reading | ||
|
||
- [Prebid Statement on Sustainability](/overview/statement-on-sustainability.html) | ||
- [Prebid Sustainability Portal](/support/sustainability-portal.html) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
--- | ||
layout: page_v2 | ||
title: Sustainability Portal | ||
description: Sustainability Portal | ||
sidebarType: 7 | ||
--- | ||
|
||
# Sustainability Portal | ||
{:.no_toc} | ||
|
||
- TOC | ||
{:toc} | ||
|
||
## Overview | ||
|
||
The digital advertising industry's environmental impact continues to grow alongside its expanding role in the global economy. To address this challenge, Prebid.org established a Supply Chain & Sustainability Taskforce. | ||
|
||
As the industry works toward defining sustainability standards, this taskforce serves as a central resource for documentation and best practices, helping organizations align their operations with broader sustainability goals. This initiative reflects Prebid's commitment to promoting environmental responsibility while maintaining the transparency and efficiency of the digital advertising supply chain. | ||
|
||
This portal organizes existing Prebid documentation through the lens of sustainability, providing practical guidance for both Publishers and Tech Partners. The content is structured into two main sections, each further categorized by Prebid software components (such as Prebid.js and Prebid Server) and conceptual areas (including Analytics and Bidders). This organization allows stakeholders to easily access relevant information for their specific needs while working toward more sustainable advertising practices. | ||
|
||
Many of the best practices boil down to a simple philosophy: | ||
|
||
{: .alert.alert-success :} | ||
Good housekeeping is good for sustainability. | ||
|
||
A fair amount of value can be obtained from: | ||
|
||
- Retaining only the bidders, modules, and identity providers that are providing value, removing those that do not. | ||
- Upgrading Prebid more often to receive efficiency-related updates. | ||
|
||
## Best Practices | ||
|
||
- [Publisher Sustainability Best Practices](/support/sustainability-publishers.html) | ||
- [Bid Adapter Sustainability Best Practices](/support/sustainability-bidders.html) | ||
- [Analytics Adapter Sustainability Best Practices](/support/sustainability-analytics.html) | ||
|
||
## Further Reading | ||
|
||
- [Prebid Statement on Sustainability](/overview/statement-on-sustainability.html) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,155 @@ | ||
--- | ||
layout: page_v2 | ||
title: Publisher Sustainability Best Practices | ||
description: Publisher Sustainability Best Practices | ||
sidebarType: 7 | ||
--- | ||
|
||
# Publisher Sustainability Best Practices | ||
{:.no_toc} | ||
|
||
- TOC | ||
{:toc} | ||
|
||
## Overview | ||
|
||
This page collects recommendations for Publishers interested in exploring ways to save carbon emissions while preserving revenue. See the [Sustainability Portal](/support/sustainability-portal.html) for more background. | ||
|
||
Regardless of the Prebid implementation, publishers seeking to improve sustainability and supply chain stance should focus on the following major areas: | ||
|
||
1. Work with Demand Partners that align with your sustainability goals | ||
2. Monitor behavior to ensure those goals are met and to also discover areas of optimization particularly related to Geo and Device participation | ||
3. Configure Prebid products with the minimum bidders and setting which meet your sustainability goals | ||
|
||
## General Advice | ||
|
||
### Tip 1: Choose bidders that meet your requirements | ||
|
||
When choosing bidders consider your internal requirements for HTTP2 support, adapter size, bid response time, response size, cookie loads and more. | ||
|
||
The docs at [https://docs.prebid.org/dev-docs/bidders.html](/dev-docs/bidders.html) contain information related to bidder feature support. | ||
|
||
Questions to ask bidders before enabling them: | ||
|
||
1. What is your average server response rate and latency? | ||
1. Do you filter out consistently slow/non-responsive demand sources to reduce unnecessary server load and energy consumption? | ||
1. Do you have any capability to measure and report the carbon footprint of individual demand source activities (e.g. computational resources used per bid request)? | ||
1. What optimization strategies do you employ with your demand sources to reduce overall infrastructure demands, such as implementing intelligent throttling, bid caching, or selective bidder calls based on performance? | ||
|
||
## Prebid.js | ||
|
||
This is advice specific to Prebid.js. | ||
|
||
### Tip 2: Reduce build size | ||
|
||
Only build prebid with the bidders, modules and features that you intend to use. | ||
|
||
The on-site builder is available at [https://docs.prebid.org/download.html](/download.html) and instructions for building manually are in the Github repo [https://github.com/prebid/Prebid.js/blob/master/README.md\#Build](https://github.com/prebid/Prebid.js/blob/master/README.md#Build). Building manually the JavaScript object name to be defined, but is otherwise the same. | ||
|
||
### Tip 3: Monitor bid performance with client-side analytics | ||
|
||
Major areas to consider here are bid rates and participation which indicates whether the bid is meaningful. Fruitful areas to investigate first are geographic and currency support for the bidder. Consider delivering different script configurations based on Geo and Currency or using Header Bidding management providers which provide this service. | ||
|
||
Configure an analytics provider that can track the related areas of interest from the building and monitoring section. | ||
|
||
- [Analytics Adapters](/overview/analytics.html) | ||
- [Building your own analytics adapter](/dev-docs/integrate-with-the-prebid-analytics-api.html) | ||
|
||
### Tip 4: Dynamically determine which bidders to use based on analytics | ||
|
||
Prebid.js AdUnits can be configured to call different sets of bidders and modules in different geographic areas and for different devices. Ideally, this also implies different builds for each of these combinations. If this capability is not available in-house, consider a [managed service](https://prebid.org/managed-services/) that provides automatic performance-based reconfiguration of your Prebid.js configuration. | ||
|
||
For example, instead of running a global Prebid.js build, consider creating separate builds for North America, Europe, APAC, or other regions important to your business. Each of those builds would be tailored to have the relevant bidders and modules. | ||
|
||
### Tip 5: Use Professor Prebid | ||
|
||
[Professor Prebid](/tools/professor-prebid.html) is a Chrome browser extension that provides setup validation, performance analysis, debugging and education about the live page behavior. Professor Prebid provides a wealth of information including: | ||
|
||
1. Adunits | ||
2. Bids | ||
3. Timeline | ||
4. Config | ||
5. User ID | ||
6. User Sync | ||
7. Version Information | ||
8. More... | ||
|
||
It's a great diagnostic tool, but is limited to the current page you are viewing, so you'll still need an analytics adapter to provide comprehensive reports. | ||
|
||
- [Professor Prebid User Guide](/tools/professor-prebid.html) | ||
- [Chrome Plugin](https://chromewebstore.google.com/detail/professor-prebid/kdnllijdimhbledmfdbljampcdphcbdc?pli=1) | ||
|
||
### Tip 6: Use Other Debug Tools | ||
|
||
Use the [Prebid.js debugging module](/dev-docs/modules/debugging.html) to see other available data including bidder debug and the ability to inject configuration, intercept bids and mock responses. | ||
|
||
### Tip 7: Check client-side syncing configuration | ||
|
||
Most bidders want to perform cookie syncing, which can impact page performance, and doesn't always even help monetization on all browsers. Evaluate your [cookie sync config](/dev-docs/publisher-api-reference/setConfig.html\#setConfig-Configure-User-Syncing) for each bidder to ensure it meets your requirements. | ||
|
||
For example, you may consider: | ||
|
||
- Whether it makes sense to turn off syncing in certain browsers. | ||
- Limit certain bidders to pixel syncs which are lower impact than iframe syncs. | ||
|
||
You can consider using [Professor Prebid's Usersync Info](/tools/professor-prebid.html#user-sync-network-inspector) tool to investigate server-side syncs. | ||
|
||
## Prebid Server | ||
|
||
Ask your Prebid Server provider to provide guidance on how the sustainability profile of their global datacenters and traffic routing technology. | ||
|
||
Ideally, your provider can handle user traffic in datacenters that are local to the user. e.g. North American user requests are processed in a North American datacenter. | ||
|
||
Also, confirm that they regularly update Prebid Server to get the latest features. | ||
|
||
### Tip 8: Monitor bid performance with server-side analytics | ||
|
||
Watching bidder performance by geo, device, and channel can help you decide how to set up the adunits. Channel is "Prebid.js", "SDK", "AMP", etc -- any traffic source supported by Prebid Server. Ask your Prebid Server provider which analytics systems they can support. | ||
|
||
### Tip 9: Determine whether it makes sense to run Prebid.js bidders server-side | ||
|
||
If you're using Prebid.js, we recommend use of the [Server-to-Server Testing Module](/dev-docs/modules/s2sTesting.html) to determine which bidders can be run on the server side. | ||
|
||
If your Prebid Server provider has energy-efficient datacenters, then it may make sense to explore running as many bidders as possible server-side. This can help you focus traffic to network connections powered by more sustainable energy sources than what end-users may be consuming. | ||
|
||
### Tip 10: Disable bidders by datacenter | ||
|
||
Ask your Prebid Server provider whether they're utilizing bidder self-declared "Geographic Scope". | ||
Several bidders have declared the regions in which they do business, so utilizing this information | ||
can help everyone save money and carbon emissions. | ||
|
||
GeoScope examples | ||
|
||
- [Global](https://github.com/prebid/prebid-server/blob/master/static/bidder-info/adf.yaml) | ||
- [US & CAN](https://github.com/prebid/prebid-server/blob/master/static/bidder-info/imds.yaml) | ||
|
||
### Tip 11: Optimize server-side syncing | ||
|
||
Ask your Prebid Server provider to confirm how they've set up cookie-syncing and whether they support setting: | ||
|
||
- account-specific sync priority | ||
- account-specific sync limits | ||
- cooperative syncing | ||
|
||
See the relevant documentation for [PBS-Java](https://github.com/prebid/prebid-server-java/blob/master/docs/application-settings.md) and [PBS-Go](https://github.com/prebid/prebid-server/blob/master/config/usersync.go). | ||
|
||
You can consider using [Professor Prebid's Usersync Info](/tools/professor-prebid.html#user-sync-network-inspector) tool to investigate server-side syncs. | ||
|
||
## Identity Modules | ||
|
||
### Tip 12: Minimize the number of Extended IDs | ||
|
||
Some Extended IDs (aka EIDs) are still experimental. The Prebid community tests some EIDs, but conclusions are often difficult to draw. Until we have more conclusive evidence on which EIDs are the most helpful for monetization, we encourage publishers to continue their own tests, which often means testing a dozen or more EIDs. You should monitor and reconfigure as value is proven (or not) with your properties. | ||
|
||
See the [Prebid Identity Overview](/identity/prebid-identity.html) | ||
|
||
## Prebid Mobile | ||
|
||
Prebid Mobile uses Prebid Server, so the recommendations above are relevant. | ||
|
||
There are no recommendations specific to Prebid SDK at this time. | ||
|
||
## Further Reading | ||
|
||
- [Prebid Statement on Sustainability](/overview/statement-on-sustainability.html) | ||
- [Prebid Sustainability Portal](/support/sustainability-portal.html) |