3 ms·
It seems certain features are restricted to third-party cookies: https://developers.google.com/analytics/devguides/collection/gtagjs/cookie-usage https://develo
by btdmaster 4y ago
It seems certain features are restricted to third-party cookies: https://developers.google.com/analytics/devguides/collection/gtagjs/cookie-usage https://developers.google.com/analytics/devguides/collection.... In practice though, moving from third-party to first-party is simply a way to reduce the probability that the spyware gets blocked by the user agent.
- jefftk 4y ago> certain features are restricted to third-party cookies You're talking about the https://developers.google.com/analytics/devguides/collection/gtagjs/cookie-usage#google_analytics_for_display_advertisers_-_cookie_usage https://developers.google.com/analytics/devguides/collection... section, right? That's only for sites that are already using third-party cookies for advertising, has to be specifically enabled, and doesn't seem very applicable to our "know how many people visited my website" discussion? But my comment above was too broad, and I've edited it to point here. > moving from third-party to first-party GA, back to the Urchin days, has always been built around first-party cookies though.
- btdmaster 4y ago> https://developers.google.com/analytics/devguides/collection/gtagjs/cookie-usage#google_analytics_for_display_advertisers_-_cookie_usage https://developers.google.com/analytics/devguides/collection... Is that the same as https://support.google.com/analytics/answer/2700409 https://support.google.com/analytics/answer/2700409?
- jefftk 4y agoI think so? It's about linking advertising activity (keyed by third party advertising cookies) with analytics activity (keyed by first party analytics cookies)