Chrome’s proposed cookie-choice experience did not become the promised prompt

Google’s July 2024 proposal described a new Chrome choice experience. Its April 2025 update said a new standalone third-party-cookie prompt would not roll out. The later statement superseded that milestone. Proposal; Follow-up decision.

Keep the browser decision in its lane

The change concerns Chrome’s treatment of third-party-cookie choice. It does not establish that all users accept cookies, that every browser behaves the same way or that app-level attribution restrictions disappeared. A mobile-game web shop can encounter several measurement environments in one acquisition journey.

Our recommendation is to revisit plans that were tied specifically to the proposed prompt. Separate those dependencies from work that remains useful under existing consent, browser and app conditions. Do not cancel an entire measurement programme because one projected platform event changed.

Replace the forecast with observed conditions

For a concrete campaign, identify the landing environment, consent state and attribution path. Test the intended route and record which events can actually be connected. A policy announcement is not evidence that the studio’s implementation captures them correctly.

The supplied timeline preserves the original certainty as a proposal and the later provider decision as a change in plan. It does not certify subsequent API availability; those technologies need their own status checks. That separation gives the archive a cleaner history and gives operators a more precise list of assumptions to revisit.

Inspect the evidence

Download the announcement-to-outcome evidence timeline. The extraction separates documented facts from our analysis and unknowns.

Further reading in the existing archive: Privacy Sandbox Alternatives Now That Chrome Cookies Stay; The Web Shop Attribution Blind Spot Nobody Budgets For. These links provide background; this check does not independently verify their full contents.

Frequently asked questions

What happened next, and what should UA change after: Chrome’s proposed cookie-choice experience did not become the promised prompt?

Update plans that depended on the proposed standalone prompt, and keep the change inside Chrome’s third-party-cookie lane. Google’s July 2024 proposal described a new browser-wide choice experience; its April 2025 update said a new standalone third-party-cookie prompt would not roll out, superseding that milestone. The decision does not establish that all users accept cookies, that every browser behaves the same way, or that app-level attribution restrictions disappeared — a mobile-game web shop can still encounter several measurement environments in one journey. Revisit dependencies tied specifically to the proposed prompt; keep work that remains useful under existing consent, browser and app conditions. Do not cancel an entire measurement programme because one projected platform event changed. For a concrete campaign, identify the landing environment, consent state and attribution path, test the intended route, and record which events can actually be connected. Preserve the original certainty as a proposal and the later provider decision as a change in plan; subsequent APIs need their own status checks.