> Site index: https://usehardal.com/llms.txt
> Every content route also serves markdown at <url>.md

# Audit Third-Party Cookies in Chrome With PSAT

Use Chrome's Privacy Sandbox Analysis Tool to find third-party cookies, test blocked-cookie behavior, and trace the requests behind a broken user journey.

Source: https://usehardal.com/privacy-sandbox-chrome
Published: 2024-01-10
Updated: 2026-09-14
Author: Berkay Demirbas
Category: Privacy & Cookies

---

Use the Privacy Sandbox Analysis Tool, or PSAT, to see which first-party and third-party cookies a page creates, which requests depend on them, and what breaks when third-party cookies are unavailable. PSAT is a Chrome DevTools extension. It diagnoses browser behavior; it does not make a site private or compliant by itself.

## Install PSAT

Install [PSAT from the Chrome Web Store](https://chromewebstore.google.com/detail/privacy-sandbox-analysis/ehbnpceebmgpanbbfckhoefhdibijkef), open the page you want to test, then open Chrome DevTools. Select the Privacy Sandbox panel.

Google also publishes the [PSAT source and issue tracker](https://github.com/GoogleChromeLabs/ps-analysis-tool).

## Test one user journey at a time

Pick a flow with a measurable outcome, such as:

- landing page to lead submission
- product page to confirmed purchase
- content site to a checkout on another domain
- sign-in followed by an authenticated action

Clear site data or use a fresh browser profile. Record the expected network requests and source-system result before changing cookie settings.

## Read the cookie report

PSAT groups observed cookies by context and shows the requests associated with them. For each third-party cookie, record:

1. The domain that set or read it.
2. The request or script that introduced it.
3. The product owner and business purpose.
4. The user journey that changes when the cookie is blocked.
5. Whether a first-party or server-side design can remove the dependency.

The count alone is not the finding. A cookie used by a required sign-in flow and one left by an unused marketing tag need different fixes.

## Test blocked-cookie behavior

Follow Google's current [third-party cookie debugging guide](https://privacysandbox.google.com/cookies/prepare/debug). Repeat the same journey with the relevant Chrome setting or test mode enabled. Compare:

- console and network errors
- requests that no longer fire
- identifiers or campaign fields that disappear
- the confirmed result in your backend
- events received by analytics and advertising destinations

Do not judge the implementation from a dashboard total alone. Trace one controlled conversion through the browser, collection endpoint, source system, and destination response.

## Decide what moves server-side

Server-side tracking can move eligible destination calls out of the browser and use a first-party collection endpoint. It does not remove the need for consent, data minimization, access controls, or destination review.

Start with events your backend can confirm, such as a paid order or accepted application. Keep a stable event ID, carry consent state, and compare delivery with the source record.

Use the [server-side tracking checklist](https://usehardal.com/server-side-checklist) to plan the migration, or compare the [first-party stack before and after](https://usehardal.com/first-party-stack).
