Where the Chrome third-party cookie story stands now
Chrome has been signaling a "phased deprecation of third-party cookies" since 2020. The schedule has been pushed multiple times, but the direction is consistent:
- 2020: Deprecation plan announced
- 2022: First delay
- 2023: Second delay
- 2024: Shifted from "full deprecation" to "user choice" (announced July 2024)
- 2025: Expanded test environment, Privacy Sandbox API standardization
The key shift: not "full deprecation," but "users can opt out." Even so, from an advertiser's perspective, cookie-based tracking is steadily losing reliability.
How Meta is affected
Meta Pixel on Chrome runs in a third-party cookie context. When cookies are blocked or restricted:
- User IDs are lost → Meta can't match logged-in users
- Retargeting audiences shrink (without cookies, "site visitor" tracking fails)
- Conversion tracking accuracy drops
Safari (iOS) already blocks third-party cookies fully. If Chrome moves in the same direction, effective Pixel tracking could fall below 50%.
Source: Meta Business Help — About Advanced Matching for web
What Privacy Sandbox is
Chrome's proposed standard to replace third-party cookies. Key APIs:
- Topics API: The browser infers user interest topics on-device. Topic-level ad targeting without cross-site identification
- Protected Audience API (formerly FLEDGE): Retargeting runs inside the browser. User data doesn't leave to servers
- Attribution Reporting API: Conversion reports only in aggregate form
Meta is rolling out partial Privacy Sandbox support. Full integration, however, will take time.
What Meta is doing
1. Conversions API (CAPI) — server-to-server signals that don't depend on cookies
2. Advanced Matching — login-based matching reduces cookie dependency
3. Domain Verification — if your domain is verified with Meta, some signals pass through even without cookies
4. Aggregated Event Measurement — the iOS-era tooling is being extended to Chrome
So what should you do?
Right now:
- Implement CAPI — don't rely on Pixel alone; add server signals. Shopify and WooCommerce have one-click CAPI Gateway setup
- Domain Verification — verify your domain in Meta Business Suite
- Turn on Advanced Matching — enable hashed matching on the Pixel
- Strengthen first-party data — newsletters and sign-ups to build your own customer database. Without cookies, you can still run ads via Customer Lists
Mid-term (6–12 months):
- Shorten attribution windows — 7-day click by default. The 28-day window has low credibility already
- Brand Lift Study — measure incremental impact empirically
- Consider a CDP (Customer Data Platform) — for accounts spending $10K+ per month
Long-term (1–2 years):
- First-party ID partnerships — monitor industry standards like UID 2.0, Prebid
- Direct Privacy Sandbox integration — requires developer resources
- MMM (Marketing Mix Modeling) — aggregate-based budget allocation
Advertiser response by scenario
Small ecommerce ($1K/month):
- CAPI Gateway (Shopify) + Advanced Matching
- Can be done in 30 days
- Cost: essentially free
Mid-sized brand ($10K/month):
- Everything above + first-party database build (newsletters, etc.)
- Evaluate GA4 server-side integration
- 3–6 month project
Large advertiser ($100K/month+):
- CDP rollout + unified measurement
- Regular MMM and Lift Studies
- 12+ month project
One thing to keep in mind
The "Chrome isn't killing cookies anymore" headline has circulated, but cookie-based tracking reliability is already declining. Whether or not cookies are deprecated, the move toward first-party + server signal infrastructure is the constant.
Tracking architecture, CAPI, and measurement strategy are covered in Meta Ads Book 5.