Google confirmed last week that third-party cookie deprecation will begin in Chrome in January 2024, affecting 1% of Chrome users. One percent is the number you need to understand precisely, because it is not small. One percent of Chrome’s approximately 3 billion global users is roughly 30 million people whose third-party cookies will stop functioning in Chrome as of Q1 2024. These 30 million users will become the first live cohort against which the advertising industry can measure real cookie deprecation impact in Chrome — the measurement environment the industry has spent four years preparing for and has never actually had.

The 1% deployment is explicitly framed as a testing and measurement phase. Google has communicated to publishers and adtech vendors that this cohort’s purpose is to generate real-world data on Privacy Sandbox API performance, advertising effectiveness under deprecation, and infrastructure readiness across the publisher and adtech ecosystem. The 1% cohort gives Google — and the industry — the data needed to calibrate the full deprecation schedule. It is also the moment where every advertiser and publisher should be treating their analytics infrastructure as a measurement instrument, not a reporting tool.

What “1% of Chrome Users” Actually Means for Traffic Analysis

The 1% cohort will be distributed globally across Chrome browser installations. The distribution is not geographically concentrated — it is a random sample of Chrome users at the browser level, not a regional rollout. This means the 1% affected users will appear in your analytics as a small but statistically meaningful segment of your normal Chrome traffic.

The immediate practical implication is that your standard analytics reports will not flag the affected cohort as a distinct segment by default. A Chrome user in the 1% cohort looks identical in your web analytics to a Chrome user outside the cohort. The measurement challenge is detecting the behavioral signal — changes in attribution, audience matching rates, conversion tracking completeness — that reveals the cohort’s cookie-free experience, even though the cohort is not labeled.

The most reliable detection method is comparing conversion rates and attribution completeness across Chrome versus Safari/Firefox traffic. Safari has been effectively cookieless for programmatic purposes since ITP 2.0 in 2019. Firefox has been cookieless for programmatic since Enhanced Tracking Protection in 2022. Your current Safari and Firefox conversion rates and attribution data already represent your “cookieless baseline” — the performance you achieve in browser environments where third-party cookies are blocked. When the 1% Chrome cohort behaves similarly to your existing Safari and Firefox traffic, you have your first Chrome-specific cookie deprecation signal.

What to Track in GA4 During the 1% Phase

Google Analytics 4’s browser dimension segmentation is the starting point for building your cookie dependency measurement framework. Establish these baseline measurements before January so you have pre-deprecation benchmarks.

Session-level attribution completeness by browser: compare the percentage of sessions with a known source/medium attribution in Chrome versus Safari versus Firefox. If Safari sessions have significantly higher “direct/none” attribution than Chrome sessions, that gap reflects the attribution loss from third-party cookie blocking. When the 1% Chrome cohort shows the same pattern, you have cookie attribution dependency confirmed.

Conversion rate by browser: segment your GA4 conversion events by browser and compare Chrome, Safari, Firefox, and other browsers. A systematic gap between Chrome conversion rates and cookieless browser conversion rates is either a genuine audience quality difference (Chrome users may differ from Safari users in your specific audience) or an attribution gap that under-counts conversions in cookieless browsers. Separating these requires analysis beyond simple rate comparison.

GA4’s Exploration reports allow you to build custom browser-segmented analyses that are not available in standard GA4 reports. Building these exploration templates now means you can apply them to January data immediately rather than building the analysis under time pressure.

Audience list size trends by browser: GA4 and Google Ads audience lists that are populated from site visits will show size reduction for the 1% cookieless Chrome cohort because remarketing audience building depends on first-party cookies (which are not affected by third-party cookie deprecation in Chrome) but third-party audience syncing and cross-site identity resolution does depend on third-party cookies. Tracking audience list composition changes over January will provide early signal on audience pool impact.

What to Track in Your DSP

Your demand-side platform is where the identity resolution and audience matching impact will be most visible. Three specific metrics to track from January.

Match rates for custom audience segments: if you upload a customer email list as a custom audience for retargeting, the match rate — the percentage of uploaded users your DSP can identify and serve ads to — will decrease for the 1% Chrome cohort as cookie-based cross-site identity resolution is removed. Your DSP should report audience match rates; track the Chrome-versus-other-browser split on match rates monthly starting in January.

Third-party audience segment coverage: segments you buy from third-party data providers through your DSP are built and maintained using third-party cookie syncing. As the 1% Chrome cohort stops syncing, third-party segment coverage on those users will decline. Coverage reports — what percentage of your target audience a given third-party segment reaches — will show the first Chrome-specific coverage erosion in Q1 2024.

CPM and win rate trends by browser context: in programmatic environments that pass browser context in bid request signals, you may begin to see CPM premium compression for the 1% cookieless Chrome cohort as demand bidding algorithms deprioritize impressions with no third-party audience signal. This is a secondary effect that will be small in the 1% phase but will scale proportionally with deprecation expansion.

What to Track in Your SSP and Publisher Analytics

Publishers using SSP dashboards should track fill rate and CPM trends segmented by browser context. SSP fill rates for cookieless browsers (Safari, Firefox) are already lower than Chrome in most publisher environments. Adding Chrome cookieless segment tracking in January will reveal whether the SSP behavioral pattern for the 1% Chrome cohort matches the existing cookieless browser pattern.

Prebid.org’s user ID modules documentation provides technical guidance on configuring first-party identity solutions that provide audience signals even in the Chrome 1% cohort. Publishers who have implemented UID 2.0, ID5, or LiveRamp ATS will see smaller fill rate and CPM impacts than those relying exclusively on third-party cookie-based identity, because authenticated first-party IDs pass through in bid requests regardless of third-party cookie status.

The Privacy Sandbox Attribution Reporting API should be instrumented and reporting by January for publishers and advertisers who have not already set up the integration. The API provides aggregated conversion reporting for the 1% cookieless Chrome cohort that will not be measured through standard pixel-based attribution. Without Attribution Reporting API instrumentation, the 1% cohort’s conversions will simply be unmeasured rather than appearing in alternative reporting — creating an apparent conversion rate decline that is an attribution gap, not a genuine performance drop.

The Strategic Framing for Q1 2024

The January 1% deployment is the beginning of the Chrome cookie deprecation that the industry has been anticipating for four years. The gap between the 1% phase and full deprecation — expected later in 2024, pending CMA review and Privacy Sandbox readiness assessment — will be determined in part by what the 1% measurement data reveals about ecosystem readiness.

If the 1% cohort data shows that Privacy Sandbox APIs are adequately compensating for cookie loss, Google will have evidence to support an accelerated full deprecation timeline. If the data shows significant performance gaps that Privacy Sandbox is not adequately filling, Google has the CMA-enforced requirement to not deprecate cookies until the alternative infrastructure is sufficient — and the data will justify schedule extension.

Either outcome is worth knowing. The industry has been operating on speculation and test environment data. Starting in January, real Chrome users experiencing real cookie deprecation will generate real measurement data. Build your tracking infrastructure to capture it.

FAQ

Will the 1% Chrome cookie deprecation cohort affect my advertising campaigns immediately in January? Yes, but the impact will be proportional to the 1% cohort size — small but measurable. You will begin to see the cookie deprecation signal in attribution reports, audience match rates, and SSP fill rates for the affected cohort. The impact magnitude in January will be 1% of your Chrome traffic; tracking it carefully provides the measurement baseline for understanding full-scale deprecation impact.

How do I identify which of my website visitors are in the 1% cookieless Chrome cohort? You cannot directly identify individual users in the affected cohort — that information is not exposed to publishers or advertisers. You can identify the cohort’s aggregate signal by comparing browser-segmented analytics between Chrome and your existing cookieless browsers (Safari, Firefox), and by monitoring the specific metrics that third-party cookie loss affects: attribution completeness, audience match rates, and SSP fill rates.

Should I implement Privacy Sandbox Attribution Reporting API now? Yes. The Attribution Reporting API provides conversion data for users whose third-party cookies are deprecated — without it, conversions from the 1% cohort simply do not appear in standard pixel-based attribution. Implementing the API now, before January, ensures you have conversion coverage for the affected cohort from the start of deprecation rather than having to retroactively reconstruct the measurement gap.

What first-party identity solutions help maintain advertising effectiveness for the cookie-deprecated cohort? Email-based universal IDs — Unified ID 2.0, ID5, LiveRamp RampID — provide deterministic user identity in bid requests without relying on third-party cookies. These require publisher implementation of the identity solution and user consent to provide email-based identification. For the 1% Chrome cohort, these solutions maintain audience targeting and frequency capping capabilities that third-party cookie deprecation removes.