Search
Enter at least two characters without personal information.

    LibraryArticles & FAQ Your projectRequest a quote
    LanguageEN
    Practical guides

    Test journeys with third-party cookies blocked

    A visitor can express a choice in the website while their browser still blocks third-party storage. Separate the website choice from the browser’s technical capability: both need testing.

    Go to the method

    Tablet and laptop showing two interface states
    AI-generated illustration

    Identify a dependency on another site

    An embedded player, booking tool or login journey may use cookies in a third-party context. MDN’s documentation explains these contexts. Record the component, provider and action that depends on stored state. A different hostname alone does not fully describe how the component works.

    Describe the required outcome: identifying someone, retaining a basket, selecting a slot or playing a video. Note the embedding point and fallback when the relevant state is inaccessible. A displayed page does not establish successful task completion.

    Repeat a matrix of conditions

    Prepare fresh sessions with third-party storage allowed and blocked, then vary the website’s consent choice. Test browsers used by the audience. Retain version, setting, date and initial state; private browsing and cookie blocking are not necessarily equivalent.

    Check starting, progression, confirmation and recovery after refresh. For bookings, distinguish a displayed calendar from an actual confirmation. For login, test return from the provider and session continuity. Use test accounts and operations without placing real orders merely to assess an interface.

    • No previous state.
    • Third-party storage blocked.
    • Website choice and browser setting recorded.

    Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

    Separate cookie scope, transport and access
    Situation or settingWhat it meansUseful check
    SecureLimits cookie transmission to secure connections, subject to local-environment rules.Does not replace server permissions or other session protections.
    HttpOnlyPrevents access through the document’s usual JavaScript interfaces.The cookie can still accompany a request; this setting does not prevent every attack.
    SameSiteControls circumstances of cross-site transmission.Test navigation, embedded flows and provider callbacks in target browsers.

    Understand the limits of technical options

    The Storage Access API lets embedded content request relevant storage access in supporting browsers. It does not grant universal automatic access. Handle denial, missing support and required interaction where applicable.

    Partitioned storage isolates state by site context; it is not a universal mechanism for sharing login across all sites. Do not replace a blocked cookie with hidden collection. Technical permission and purpose assessment remain separate: a browser grant does not replace a required website choice.

    Provide a useful way forward

    When an embedded component cannot work, offer a clear action: open the provider’s page where appropriate, request a slot through another channel or read a transcript. Identify the destination and implications. The fallback should preserve information needed for the task.

    Test returning to the website, cancellation, errors and repeated clicks. A new window should not trap users or lose their entered information. When booking leaves the website, explain where confirmation occurs; an enquiry received through your form does not guarantee availability.

    Track announcements without treating them as universal rules

    In its 17 October 2025 announcement, Google announced retirement of several Privacy Sandbox technologies including Topics and Protected Audience, while maintaining Chrome’s approach to third-party cookie choice. Avoid assuming a universal removal date or depending on an API announced for retirement. Inspect the current browser and intended API.

    Link findings to the consent review, third-party resource review and pre-publication checks. Retest fixes with the same initial state. Dated observations can be revisited when providers or browsers change.

    Distinguish a blocked cookie, incorrect scope and a session error.

    Synthetic case: a session disappears after returning from another website. Inspect test cookie attributes and compare navigation contexts without arbitrarily removing Secure, HttpOnly or SameSite. Document expected paths and lifetime. Technical attributes establish neither required consent nor overall compliance of the processing.

    • The intended journey works with retained protections; refusal and expired sessions offer a clear recovery path.
    • MDN Set-Cookie

      Reference for server-created cookies and their scope, lifetime and protection attributes.

    Content updated on

    Acceptance matrix to adapt to your project

    These proposed checks use synthetic cases. Decide the required behaviour with the team, record the result and assign unresolved gaps before release.

    Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

    Test cases, expected outcomes and useful evidence
    CaseExpected outcomeEvidence to retain
    A calendar appears but slot selection fails with third-party storage blocked.The failure is detected and a fallback explains how to request a slot.Browser configuration, selected synthetic slot, observed failure and working alternative route.
    Login returns from the provider but no session persists.The journey reports the problem without declaring false success.Test return, refresh and an authenticated action.
    An embedded player does not load.The page retains essential information and a usable alternative.Block storage or the provider in the test environment.

    Frequently asked questions

    How can you isolate an issue involving third-party storage?

    Repeat the same task in a session with a known state, then compare with third-party storage blocked. Record browser, version, previous sign-in and settings without publishing account data. If results differ, inspect the affected component before changing the entire site. Record banner choices and browser policy separately.

    What should you test before offering a link to the provider?

    Check the destination, explain the context change and provide a way back. Repeat the task signed in and signed out, then verify the final request state. A separate tab can change storage access, but does not guarantee transfer of every detail or confirmation of the operation.

    Do all browsers apply the same policy?

    No. Record browser, version, setting and initial state. One configuration’s result does not establish behaviour in others.