We've observed breakage on chromestatus.com in Firefox related to cookie blocking the datastudio.google.com domain (see Bug 1640425). I did a quick whois search and chromestatus.com seems to be registered and run by Google, so it may make sense to add them as a property under the Google entity.
We've observed breakage on chromestatus.com in Firefox related to cookie blocking the
datastudio.google.comdomain (see Bug 1640425). I did a quick whois search and chromestatus.com seems to be registered and run by Google, so it may make sense to add them as a property under the Google entity.