First/Third Party Cookie

  • Is it safe to assume that, since the gtag.js is local, that also the cookie will be local; in other words: making the former third party cookie a first party cookie?

    Best

    Marc

    • This topic was modified 11 months, 2 weeks ago by jansass GmbH.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    Since GA4 the cookie is always first-party to be more GDPR compliant.

    Thread Starter jansass GmbH

    (@mcian)

    Thats exactly what it though, so there is no real need to user measurement protocol (with all the disadvantages in caching, …), right?

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    The Measurement Protocol is something completely different. MP allows for server-side sending of tracking data, as opposed to client-side, which is what the gtag.js file provides.

    Server-side sending of tracking data remains the most GDPR/privacy friendly approach, when done properly, because it allows you to filter any information that can be used for fingerprinting, before sending it to Google Analytics 4.

    First party cookie does not equal GDPR-compliance at all, it just doesn’t allow for cross-domain tracking. Which is why I said “more compliant”. It doesn’t automatically make your site GDPR compliant.

    An example, that’s why CAOS Pro takes a hybrid approach and leverages the features of the new GA4 JS library (it being a first party cookie, real time tracking, consent mode framework, etc.) but still sends the tracking data server-side.

    Hope this answers your questions!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘First/Third Party Cookie’ is closed to new replies.