Phasing out of 3rd party cookies impact on RUM

Platform Real User Monitoring
1

Hi,

With respect to Google phasing out 3rd parties cookies, how would this impact Dynatrace RUM?

Understand from the documentation that that the following cookies are  all first-party cookies:

Cookie Structure Expires Max size Purpose

dtCookie1v4 session state:
v_4_key1_value1_key2_value2_keyN_valueNPossible keys include:
  • srv
  • sn
  • mvisitor
  • msn
  • perc
  • ol
  • mul
  • app:
v4 example:
v_4_srv_7_sn_4D3133F359A76AB05AAF39691696858A		SessionNo set limitation, but usually less than 100 BTracks a visit across multiple requests.
dtLatCSession5 BMeasures server latency for performance monitoring.
dtPC$_veSession58 BRequired to identify proper endpoints for beacon transmission; includes session ID for correlation.
dtSaSessionMax number of characters in the URLServes as an intermediate storage for page-spanning actions. This cookie is used to save user action names, such as Click on Login, across different pages. This is required because page loads result in JavaScript code restart, so all contextual information must be stored in cookies.
dtValidationCookieThe dTValidationCookieValue string.Deleted after a few milliseconds; no expiry date setLength of dTValidationCookieValue string, that is 23Used to determine the top-level domain.
dtDisabledSession4 BDetermines if the RUM JavaScript should be deactivated due to cost and traffic control or overload prevention.
rxVisitorSession or permanent245 BContains the visitor ID to correlate sessions.
rxvt|Session27 BSpecifies the session timeout.

But how are these cookies being injected such that they are first party cookies?

  • Sever-side injection or domain matching?

In other post, one of the replies stated that “actually dtCookie is injected on server-side and its injection is unrelated to the presence of the RUM script”.

If so are the other cookies injected on server-side too?

Based on another comment is seems to suggest that if the RUM script is not loaded, then only dtCookie is injected. This also suggest that the other cookies are injected by the RUM script - would this make them 3rd party cookies?

And also does this server-side injection require OneAgent? If i am using agentless monitoring, are dtCookie still injected on server-side?

Sorry for the list of questions, & thanks in advance.

2

look at the below portion in the beginning of the file `ruxitagentjs_xxxxxxxxxxxxxxxx.js` `.concat(“__dtCookie”,“=”)` then it’s looks injected in the client side

/*
 Copyright and licenses see https://www.dynatrace.com/company/trust-center/customers/reports/ */
(function(){function Ga(){document.cookie=""<strong>.concat("__dTCookie","=")</strong>.concat("1",";SameSite=Lax");var Pa=-1!==document.cookie.indexOf("__dTCookie");document.cookie="".concat("__dTCookie","=").concat("1","; expires=Thu, 01-Jan-1970 00:00:01 GMT");

I wish this help you.

3

Thanks for the response, i see so dtCookie is client side?

Even so, it is still 1st party cookie right? hence Dynatrace RUM is not affected in anyway by Google phasing out on 3rd party cookies?

Thanks.

4

it depends on type of injection, if you’re using RUM auto-injection mostly it wouldn’t affected by Google because ruxitagent uses the same domain name of your web app and send data back to the same Origin, otherwise if you using manual injection or your app data will be sent using CORS which means you’ll using different domain for specific activegate then it’s mostly would be affected by Google.

in this case you’ve to check the rules and policies of Google

5

Just to clarify further by RUM auto-injection you are referring to OneAgent and by manual injection you are referring to agentless monitoring?

Thanks.

6

yes exactly I’m referring to agentless monitoring when mentioned manual injection, but take in consideration regardless what you’re using for injection (auto or manual) the origin of the ruxitagent.js is it using the same domain different domain this is the main idea.

I hope this notes be useful for you.