Question about reading outputs from CLI Tool vs Chrome Extension

[zinkohlaing]

Hi,

Technically this might not be a bug, but I am very keen to understand the differences between the output from CLI versus Chrome Extension.

Also, I would appreciate if you can provide the best practices for conducting the cookie audit using Chrome extension.

I am going to this URL for example: https://adviser.tal.com.au/

I am using a Chrome Canary, with everything (history, cookies) cleared, and opened the site for the first time. I just opened the page without doing any interaction.

PSAT extension gives me this result:

And I use CLI tool to run audit on the same page and got this result:

I understand that there might be some difference, but shouldn't that be similar at least? How can I explain the differences if I am to do an audit of entire site using CLI tool?

Thank you!

[milindmore22]

Hello @zinkohlaing

Thanks for reaching out to us, We noticed in your screenshots that Chrome DevTools Protocol (CDP) might not be enabled for the PSAT extension.

PSAT relies on CDP for in-depth analysis of your site, You can enable CDP from the extension settings or directly from the PSAT popup, as explained on our wiki page. An inactive CDP could be why you’re seeing a significant difference between the extension’s and CLI’s cookie analysis.

It’s important to note that there can still be some discrepancies between the CLI and extension, and the reasons for this are detailed on our wiki page as well.

Here are some best practices for conducting a cookie audit using the PSAT Chrome extension:

Compare Site Behavior with and Without Third-Party Cookies:

• Enable and disable third-party cookies in your browser settings.
• Use the PSAT extension to analyze cookies on your site in both scenarios.
• Look for any changes in functionality, especially features that rely on third-party cookies (e.g., social media logins, ad targeting, analytics).

Simulate User Flows and Check Functionality:

• Identify key user flows on your site, such as login, checkout, and content sharing.
• Use the PSAT extension to analyze cookies involved in these user flows.
• Manually test these functionalities to see if they are impacted by cookie blocking.

Explore Alternatives for Impacted Features:

• If user flows are broken due to blocked third-party cookies, research alternative solutions, Explore alternative to migrate from third-party cookies

For future references if you have any further questions related to PSAT please contact us on support forums