Fix guides · UX & conversion

How to fix “Uses third-party cookies”

Embedded services that set cookies from their own domain may stop working when browsers or visitors block them. How to find which ones, and what to do about each.

Time to fix
30–60 minutes
Skill needed
Developer
Who notices
Visitors whose browsers block third-party cookies

Why it matters

A third-party cookie is set by a different domain than the one in the address bar, usually by an embed, widget, ad or tracking script.

Safari and Firefox restrict them by default, and Chrome blocks them in Incognito mode or when visitors choose to. Anything that depends on them (a chat widget remembering a conversation, an embedded login, ad measurement) may quietly fail for those visitors.

“Third-party cookies may be blocked by browser restrictions, user settings, developer flags, or enterprise policy. You need to provide a great experience for all your users, whether or not third-party cookies are available.”

Privacy Sandbox: Prepare for third-party cookie restrictions

Before you start

  • Your report lists each cookie and the domain that set it. Most belong to services you've added: ads, analytics, social embeds, video players, chat and reviews.
  • For each service: do you still use it? Does the vendor offer a version that doesn't need third-party cookies? Test your key flows with third-party cookies blocked.
  • This is also a privacy question: third-party cookies used for tracking usually need consent under laws such as the GDPR.

Fix it on your platform

Shopify

  1. Check which apps and sales channels set the listed cookies. Remove apps you don't need, and ask the rest about their plans for cookie restrictions.

WordPress

  1. Check which plugins and embeds set the listed cookies. Remove what you don't use, and check plugin settings for a privacy-friendly mode (many video embeds offer a no-cookie option).

Webflow

  1. Review scripts and embeds in your custom code; each listed domain belongs to one of them. Remove what you don't need.

Wix

  1. Review apps and marketing integrations (and Custom Code), and remove those you don't need.

Squarespace

  1. Review code injection, embeds and extensions, and remove those you don't need.

Next.js

  1. Review third-party scripts loaded with next/script or in components. If you embed your own service on another domain, use partitioned cookies (CHIPS) or the Storage Access API.
Partitioned cookie (CHIPS)
Set-Cookie: session=abc; Secure; SameSite=None; Path=/; Partitioned

Any other site

  1. Remove services you don't need. For your own cross-site embeds, use partitioned cookies (CHIPS) or ask for storage access with the Storage Access API.

Check that it's fixed

  • In Chrome DevTools → Application → Cookies, check which domains set cookies on your page.
  • Re-run your StudioLNC audit: fewer third-party cookies should be listed.

Find every issue like this on your site

Free audit of performance, accessibility, SEO and security, with fixes for your platform.