Attestation check for Topics on https://pagead2.googlesyndication.com/ failed.

Hi @chargeup

I understand that you deactivated all plugins already, except for WooCommerce and Google Listings & Ads and still having the issue, is this correct?

If yes, will you please share a copy of your site’s System Status Report so that we can better understand your site’s current environment? Here’s how to get them:

• System Status Report: navigate to WooCommerce → Status → select Get system report and then Download for support. This will download a TXT file which has the contents of the SSR to share with us.
• Fatal Error log: Share a copy of any fatal error log found under WooCommerce → Status → Logs.

Also, kindly check if there are any errors or disapproval in your Google Merchant Center account that could be causing this issue. If you find any, resolving these may help.

EDIT: I figured it out. it has to do something with chrome privacy settings. If you go to Privacy and security > Ad privacy > and disable Ad topics the error goes away. not sure why it’s happening but seems to be a problem with google or something i am not sure.

I’m getting the same thing on my website since a day ago and I see some other websites are having the same issue. Not sure what this error even means

• This reply was modified 1 year, 5 months ago by guevara93.
• This reply was modified 1 year, 5 months ago by guevara93.
• This reply was modified 1 year, 5 months ago by guevara93.

Hi @guevara93

Thanks for sharing this with us! As you’ve mentioned, adjusting the Chrome privacy settings seems to resolve the issue. This is because the settings you’ve adjusted pertain to how Chrome interacts with Google’s ad services. By disabling Ad Topics, you’re likely limiting the data that’s being sent to Google, which, in turn, may resolve the conflict causing the error.

However, it’s important to note that this solution may not work for everyone, as it depends on individual browser settings and other factors. If other users are experiencing this issue, they may need to adjust their own browser settings, or it could be an indication of a broader issue with Google’s services, which Google support might help them with. @chargeup could you try this, please?

This temporarily fixes the issue. However, I’m using default Chrome settings (as I’m sure most other users are). This wasn’t an issue until one of the latest Chrome updates I’m assuming which is now conflicting with your plugin.

Speaking out loud. Don’t you think it is a better option to fix whatever is causing the issue within your plugin as opposed to assuming a user knows how to dig through Chrome settings to turn off a setting that is default within Chrome?

Seems that there is an issue with how the plugin is now interacting within Chrome.

This error message happens without using this plugin and without using WordPress (using Google’s given JavaScript embed for things like Google campaigns and conversions or using Google Tag Manager using official Google tags). This is currently the only public page I could find on the Internet mentioning this specific error. It seems like this started showing up with Chrome 118. (I was the only person in the office without the issue using Chrome 117 and then I started seeing the same error message after I updated.)

Google Ads chat support kept giving us canned, non-answers about this particular topic (we were trying to report it or get passed to the appropriate channel) — it seems like a Chrome change (as guevara93 mentions) and I assume Google Ads devs haven’t caught up because we’re also not blocking anything with those Chrome privacy settings and/or using default Chrome settings, but everyone in the office and our clients see this error on most of the sites (not all) that have Google Ads campaigns running.

I was hoping Google Ads support could tell us if there was a new setting, that I couldn’t find, that we needed to set on the campaigns but we weren’t able to reach anyone with useful information.

Hey @swizzlestick,

Can you let us know if you tried the fix mentioned above? If so and it doesn’t work, please create a new topic so we can assist you directly.

Thanks!

Hi Sean,

I don’t really need help. I just wanted to mention that it seemed like it was a Chrome 118 issue/change and not directly related to this plugin. Someone on Stack Overflow came up with a better solution (that works for us): https://stackoverflow.com/questions/77303375/chrome-browser-error-attestation-check-for-topics-on-https-pagead2-googlesynd

The person running the website can set a header: “Permissions-Policy: browsing-topics=()” which should fix the issue for everyone without needing to instruct individual users to change Chrome browser settings.

Hey @swizzlestick,

Cool, thanks for sharing that solution! I’ll bounce this to our dev team as well.

Much appreciated!