Última actualización: Lunes 31 de marzo de 2025
Revisa el estado de la plataforma de Chrome, los recursos y los cronogramas de lanzamiento de funciones.
Cada una de las propuestas de Privacy Sandbox se encuentra en diferentes etapas del proceso de desarrollo. Dentro de cada propuesta, hay funciones individuales que tienen una disponibilidad esperada diferente.
Para revisar la información más reciente sobre cualquier propuesta o API, visita la documentación de descripción general correspondiente y la hoja de ruta de Privacy Sandbox.
Servicio de agregación
| Proposal | Status |
|---|---|
| Cross Cloud Privacy Budget Service
Explainer |
Available |
| Aggregation Service support for Amazon Web Services (AWS) across Attribution Reporting API, Private Aggregation API
Explainer |
Available |
| Aggregation Service support for Google Cloud across Attribution Reporting API, Private Aggregation API Explainer |
Available |
| Aggregation Service site enrollment and multi-origin aggregation. Site enrollment includes mapping of a site to cloud accounts (AWS, or GCP). To aggregate multiple origins, they must be of the same site.
FAQs on GitHub Site aggregation API documentation |
Available |
| The Aggregation Service's epsilon value will be kept as a range of up to 64, to facilitate experimentation and feedback on different parameters.
Submit ARA epsilon feedback. Submit PAA epsilon feedback. |
Available. We will provide advanced notice to the ecosystem before the epsilon range values are updated. |
| More flexible contribution filtering for Aggregation Service queries
Explainer |
Available |
| Process for budget recovery post-disasters (errors, misconfigurations, and so on)
Explainer |
Available Mechanism to review the percentage of shared IDs recovered by an ad tech using budget recovery and suspend future recoveries for excessive recoveries planned for H1 2025 |
| Accenture operating as one of the Coordinators on AWS
Developer Blog |
Available |
| Independent party operating as one of the Coordinators on Google Cloud
Developer blog |
Available |
| Aggregation Service support for Aggregate Debug Reporting on Attribution Reporting API
Explainer |
Available |
| Cross-cloud cryptographic key services
Explainer |
Expected in H1 2025 |
Informes de atribución
- The Attribution Reporting proposal is now moving to general availability. Raise questions and follow discussion.
- Discuss industry use cases in the Improving Web Advertising Business Group.
- Blink status
- Attribution Reporting Chrome platform status: Specific to this API on Chrome.
- Ads API Chrome platform status: A collection of APIs to facilitate advertising: Protected Audience API, Topics, Fenced Frames and Attribution Reporting.
You can keep track of the API changes.
| Proposal | Status |
|---|---|
| Conversion journey: app-to-web Web explainer and Android explainer Mailing list announcement |
Available in Chrome and Android for origin trial |
| Conversion journey: cross-device Explainer |
This proposal has been archived. There are no current plans for implementation. |
| Preventing invalid aggregatable reports using report verification Explainer |
This proposal has been archived. We have implemented trigger_context_id for this use case instead. |
| Default allowlist for the Attribution Reporting API Permissions-Policy will remain * Mailing list announcement |
Available in Chrome in Q1 2023 |
| Configurable event-Level reporting epsilon GitHub issue |
Available in Chrome in Q4 2023 |
| Padding for aggregatable reports payload Updated explainer |
Available in Chrome in Q4 2023 |
| Flexible event-Level Flexible event-level configurations explainer |
Available in Chrome in Q4 2023
The ability to customize the number of attribution reports and the number/length of reporting windows. Available in Chrome in Q1 2024 The ability to customize the number of bits of trigger data. |
| Support for Attribution Reporting verbose debugging reports not dependent on third-party cookies Explainer |
Available in Chrome in Q3 2024 |
| Support for Attribution Reporting API and Aggregation Service for Google Cloud Attribution Reporting API Explainer Aggregation Service Explainer |
Available in Chrome in H2 2023 |
| Flexible contribution filtering Explainer |
Available in Chrome in Q3 2024 |
| Pre-attribution filtering: attribution scopes Explainer |
Available in Chrome in Q4 2024 |
Mitigaciones del seguimiento por rebote
- The Bounce tracking mitigations proposal has been implemented for testing in Chrome. If you try this out and have any feedback, we'd love to hear it.
- Chrome platform status.
CHIPS
- Compatible de forma predeterminada en Chrome 114 y versiones posteriores.
- Hay una prueba de origen, ya completada, disponible de la versión 100 a la 116 de Chrome.
- Consulta los artículos Intención de experimentar y Intención de envío.
API de Federated Credential Management (FedCM)
- Chrome Platform Status
- FedCM shipped in Chrome 108.
- The FedCM proposal is open for public discussion.
- FedCM isn't supported in other browsers yet.
- Mozilla is implementing a prototype for Firefox and Apple has expressed general support and interest in working together on the FedCM proposal.
Marcos vallados
- La propuesta Marcos protegidos ahora está disponible de forma general.
- Estado de la plataforma Chrome
| Propuesta | Estado |
|---|---|
| Explicación de los cambios en la API web para pasar de urn a config |
Disponible en Chrome en el primer trimestre de 2023. |
| Macros de creatividad en marcos delimitados para informes de anuncios (FFAR) Problema de GitHub |
Disponible en Chrome en el tercer trimestre de 2023. |
| Enviar píxeles contadores automáticos una vez Problema de GitHub |
Disponible en Chrome en el tercer trimestre de 2023. |
| Configs de marcos con cercado serializable Error de GitHub |
Disponible en Chrome en el tercer trimestre de 2023. |
| Opción de formato adicional para las macros de tamaño de anuncios de Protected Audience Problema de GitHub |
Disponible en Chrome en el cuarto trimestre de 2023. |
| Los píxeles contadores automáticos se envían a todas las URLs registradas. Problema de GitHub | Problema de GitHub |
Disponible en Chrome en el cuarto trimestre de 2023. |
| Habilitar la salida de los grupos de intereses de anuncios de los iframes de Urn y los marcos de componentes de anuncios
Problema de GitHub |
Disponible en Chrome en el 1ᵉʳ trimestre de 2024 |
| Se agregó reserved.top_navigation_start/commit. Error de GitHub, Error de GitHub |
Disponible en Chrome en el 1ᵉʳ trimestre de 2024 |
| No inhabilites la configuración de cookies en ReportEvent hasta 3PCD
Problema de GitHub |
Disponible en Chrome en el 1ᵉʳ trimestre de 2024 |
| Se agregó compatibilidad con píxeles contadores automáticos en submarcos de origen cruzado.
Problema de GitHub |
Disponible en Chrome en el 1ᵉʳ trimestre de 2024 |
Permite que los subframes de origen cruzado envíen píxeles contadores reportEvent()
Problema de GitHub |
Disponible en Chrome en el segundo trimestre de 2024 |
Encabezado Referer en píxeles contadores
Error de GitHub |
Disponible en Chrome en el primer trimestre de 2025 |
| Compatibilidad automática con datos de píxeles contadores de origen cruzado
Problema de GitHub |
Se espera que esté disponible en Chrome en el 2º trimestre de 2025 |
Protección de IP
- The IP Protection proposal has entered public discussion.
- This proposal has not been implemented in any browser.
API de Private Aggregation
- The Private Aggregation API is now moving to general availability.
- New function names
- The
contributeToHistogram()function is available in Chrome Canary, Dev, Beta, and Stable M115+ - The
contributeToHistogramOnEvent()function is available in Chrome Canary, Dev, Beta, and Stable M115+
- The
- Legacy function names
- The following function names will be deprecated in M115
- See the Chrome platform status page page to see the API's current stage.
| Proposal | Status |
|---|---|
| Prevent invalid Private Aggregation API reports with report verification for Shared Storage Explainer |
Available in Chrome |
| Private Aggregation debug mode availability dependent on 3PC eligibility GitHub issue |
Available in Chrome M119 |
| Reducing report delay Explainer |
Available in Chrome M119 |
| Private Aggregation contribution timeout for Shared Storage Explainer |
Available in M119 |
| Support for Private Aggregation API and Aggregation Service for Google Cloud Explainer |
Available in Chrome M121 |
| Padding for aggregatable report payloads Explainer |
Available in Chrome M119 |
| Private Aggregation debug mode available for auctionReportBuyers reporting Explainer |
Available in Chrome M123 |
| Filtering ID support Explainer |
Available in Chrome M128 |
| Client-side contribution merging Explainer |
Available in Chrome M129 |
| Per-context contribution limits Explainer |
Expected in Q1 2025 |
| Named privacy budgets that pre-allocate privacy budget for different measurement use cases Explainer |
Expected in Q2 2025 |
| Aggregate error reporting that debugs implementation issues without relying on third-party cookies Explainer |
Expected in Q2 2025 |
Tokens de estado privado
- Estado de la plataforma Chrome.
- En prueba de origen Chrome 84 a 101: ahora cerrado.
- Demostración
- Integración de las Herramientas para desarrolladores de Chrome.
Protected Audience
Descendiente de TURTLEDOVE. Anteriormente, se llamaba FLEDGE. Consulta también el Estado de las funciones pendientes de la API de Protected Audience para obtener más información.
- La propuesta de la API de Protected Audience ahora cambiará a disponibilidad general. Formula preguntas y sigue la conversación.
- El estado de las funciones pendientes de la API de Protected Audience detalla los cambios y las mejoras en la API y las funciones de la API de Protected Audience.
- Estado de la luz intermitente
- Estado de la plataforma de Chrome de la API de Protected Audience: Específico de la API de Protected Audience en Chrome
- Estado de la plataforma de Chrome de la API de Ads: Es un conjunto de APIs para facilitar la publicidad, como la API de Protected Audience, los temas, los marcos protegidos y los informes de atribución.
Para recibir notificaciones sobre cambios de estado en la API, únete a la lista de distribución para desarrolladores.
| Proposal | Status |
|---|---|
| Buyer Reporting ID for Custom Breakdowns Github Issue |
Available in Chrome in Q3 2023 |
| Currency for Highest and bid Highest Other Scoring Bid Github Issue |
Available in Chrome in Q3 2023 |
| Macro Support for Third-party Ad Trackers (3PAT) Github Issue |
Available in Chrome in Q3 2023 |
| Support for Negative Interest Group Targeting Github Issue |
Available in Chrome in Q4 2023 |
| Secure Propagation of Auction Signals without WebBundles Github Issue |
Available in Chrome in Q4 2023 |
| Bulk Interest Group Deletion Github Issue |
Available in Chrome in Q4 2023 |
| Increase Interest Group Cap from 1K to 2K Github Issue |
Available in Chrome in Q4 2023 |
| Support for Bidding and Auction Beta 1 Explainer |
Available in Chrome (via Origin Trial) in Q4 2023 |
| Request for Ad Slot size as an additional Buyer Trusted Signal GitHub issue |
Available in Chrome in Q1 2024 |
| directFromSellerSignals to use LIFO ordering | Available in Chrome in Q1 2024 |
| Negative Targeting to work with iFrame Loads | Available in Chrome in Q1 2024 |
| Allow Updating IG userBiddingSignals | Available in Chrome in Q1 2024 |
| Allow Updating IG executionMode | Available in Chrome in Q1 2024 |
| Include Chrome-facilitated Testing Label in Trusted Server Requests
GitHub issue |
Available in Chrome in Q2 2024 |
Downsampled forDebuggingOnly() labels
GitHub issue |
Available in Chrome in Q2 2024 |
| Prevent Overly Large Trusted Bidding Signal URLs
GitHub issue |
Available in Chrome in Q2 2024 |
| Increase Ad Component Max Count from 20 to 40
GitHub issue |
Available in Chrome in Q2 2024 |
deprecatedReplaceInURN() for multi-seller auctions
GitHub issue |
Available in Chrome in Q2 2024 |
Allow generateBid() to return multiple bids
GitHub issue |
Available in Chrome in Q2 2024 |
| Key/Value Service update for interest group
GitHub issue |
Available in Chrome in Q2 2024 |
| K-anonymity will be enforced on 20% of the unlabeled traffic outside of the Chrome-facilitated testing
Explainer |
Available in Chrome in Q2 2024 |
| Real-Time Monitoring API to get auction data to buyers and sellers as quickly as possible (e.g. < 10 mins) to support monitoring and alerting | Available in Chrome in Q3 2024 |
| Deals support through reporting ID enhancements
GitHub issue |
Available in Chrome in Q4 2024 |
| Additional bids auction nonce hardening GitHub issue |
Available in Chrome in Q1 2025 |
| Creative scanning with BYOS/V1 trusted scoring GitHub issue |
Expected in Chrome in Q2 2025 |
Conjuntos de sitios web relacionados (anteriormente, Conjuntos propios)
- Related Website Sets has now moved to general availability in Chrome.
- The first origin trial ran from Chrome 89 to 93.
- Chrome Platform Status.
- Blink status.
- Chromium Projects
- Related Website Sets submission guidelines
Almacenamiento compartido
- La API de Shared Storage ahora pasó a la disponibilidad general.
- Hay una demostración en vivo disponible, al igual que las pruebas:
- La puerta de salida de selección de URL está disponible para pruebas locales desde Chrome M105 y versiones posteriores.
- La puerta de salida de agregación privada está disponible para pruebas locales desde Chrome M107 y versiones posteriores.
- La medición con la API de Private Agregación ahora está disponible de manera general.
- Estado de la plataforma de Chrome
| Proposal | Status |
|---|---|
| Allow writing from response headers Explainer GitHub Issue |
Available in M124. Can be manually enabled in M119-M123 |
| Debugging Shared Storage worklets with DevTools Section |
Available in M120 |
| Update Shared Storage data storage limit to 5MB Explainer |
Available in M124 |
createWorklet() to create cross-origin worklets without an iframe |
Available in M125 |
Allow cross-origin script in addModule(), and align createWorklet() to match the behavior |
Available in M130 |
| Allow Shared Storage worklet to read interest groups Explainer |
Available in M134 |
Custom data origin support in createWorklet()Explainer |
Available in M135 |
| Debugging Shared Storage worklets with DevTools Explainer GitHub issue |
Expected in Q2 2025 |
API de Storage Access
- Storage Access API supported by default from Chrome 119 an higher.
- Chrome Platform Status.
- Blink status.
API de Topics
- The Topics API is now in general availability.
- To provide your feedback on the Topics API, create an Issue on the Topics explainer or participate in discussions in the Improving Web Advertising Business Group. The explainer has a number of open questions that still require further definition.
- Topics API latest updates details changes and enhancements to the Topics API and implementations.
- Topics Chrome platform status: Specific to the Topics API on Chrome.
- Ads API Chrome platform status: A collection of APIs to facilitate advertising: Protected Audience API, Topics, Fenced Frames and Attribution Reporting.
| Feature | Status |
|---|---|
| Improved taxonomy for Topics (latest note) | Available in Chrome in M119 |
| Updated top topics selection algorithm | Available in Chrome in M120 |
Reducción de usuario-agente y sugerencias de cliente (UA-CH)
Limita los datos del navegador compartidos de forma pasiva para reducir el volumen de información sensible que genera huellas digitales.
- Origin trial Chrome 95 to 103, ended March 7, 2023.
- Deprecation trial Chrome 103 to Chrome 116, ended September 23, 2023.
- Chrome DevTools integration
- Review the UA-CH Chrome platform status
User-Agent Client Hints API documentation is available on MDN.
Propuestas cerradas
FLoC
Se reemplazó por la API de Topics.
- Estado de la plataforma de Chrome.
- Se cerró la prueba de origen inicial. Consulta Intent to Experiment para obtener actualizaciones.
- Estado de Blink:
- La propuesta de API se estaba analizando con el WICG y los grupos de interés.
- GitHub: Consulta las incidencias para ver preguntas y debates sobre la API.
Más información
Blink, Chromium y Chrome
- ¿Qué son los canales de versiones de Chrome?
- Programa de lanzamientos de Chrome
- Proceso para lanzar funciones nuevas en Chromium
- Intent to explain: Demystifying the Blink shipping process
- blink-dev: Estado de la implementación y análisis de las funciones de Blink, el motor de renderización que usa Chromium
- Búsqueda de código de Chromium
- ¿Qué son las funciones experimentales de Chrome?