Find it via Blocking controls > Content > All sites > Manage Ad Serving. The default setting is "Allowed".

Hello,

This won't change anything.

Browsers / Extension which are blocking third party cookies, are also blocking adsbygoogle.js .

In my opinion, this is just another trick from Google/Adsense regarding GDRP / ePrivacy Directive (cookie law). If their cookies are first party, then they can claim they are not liable, and that it's your fault, for not obtaining the explicit consent of visitors, because this is a script, running on your page, which is creating a cookie attached to your domain.

edit: didn't you notice how, since some weeks, a lot more sites are now showing a modal message box, before injecting ads?

Is g injecting the first party cookie on your site? Just curious how all this stuff works.

Hello,

There are two ways to set (and read) a cookie.

- The server can set the cookie in the sever headers.

- A cookie can also be set in javascript.

In both cases, the cookie can only be attached to the domain name of the page.

So, if a piece of javascript is running on your page, it can set and access cookies attached to your domain name.

Part of Adsense 's javascript code is running on your page. So this piece of code, can also write/read cookies from your domain (first party cookie). Another part of the Adsense's javascript is executed within an iframe from a Google's domain. This other piece of code, can only write cookies attache to Google's domain (third party).

Indirectly related, this is the same method exploited for XSS hacks.

Thanks for clarifying something I thought:

js is required.

If you don't have/use it, no "first party". :)