Yes, Google uses third-party cookies to support building cross-site profiles of users. This is an opt-in feature via GA admin, where the settings for the property require "Advertising Features" to be enabled.
This can also be controlled on tracker- and tag-level on the site itself.
What you're misunderstanding is that google-analytics.com doesn't leverage this behavior. The third-party cookies are written on doubleclick.net, to which GA's analytics.js library sends a payload of data if advertising features have been enabled.
So everything I wrote in the article stands. google-analytics.com is not being used for cross-site tracking. Any third-party cookies written on that domain are not involved in either first-party tracking by analytics.js, or the audience building efforts by doubleclick.net.
Your insults are completely unnecessary, especially when they're based on a complete misunderstanding of how Google's advertising and analytics stack works.
This can also be controlled on tracker- and tag-level on the site itself.
What you're misunderstanding is that google-analytics.com doesn't leverage this behavior. The third-party cookies are written on doubleclick.net, to which GA's analytics.js library sends a payload of data if advertising features have been enabled.
So everything I wrote in the article stands. google-analytics.com is not being used for cross-site tracking. Any third-party cookies written on that domain are not involved in either first-party tracking by analytics.js, or the audience building efforts by doubleclick.net.
Your insults are completely unnecessary, especially when they're based on a complete misunderstanding of how Google's advertising and analytics stack works.