# Phasing out of 3rd party cookies impact on RUM

**URL:** <https://community.dynatrace.com/t/phasing-out-of-3rd-party-cookies-impact-on-rum/43534>\
**Category:** Real User Monitoring\
**Tags:** real-user-monitoring-classic\
**Created:** [January 10, 2024, 2:39am UTC](https://community.dynatrace.com/t/phasing-out-of-3rd-party-cookies-impact-on-rum/43534 "2024-01-10T02:39:52Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Weilin1](https://avatars.discourse-cdn.com/v4/letter/w/5f8ce5/32.png) [@Weilin1](https://community.dynatrace.com/u/Weilin1)\
**Post date:** [January 10, 2024, 2:39am UTC](https://community.dynatrace.com/t/phasing-out-of-3rd-party-cookies-impact-on-rum/43534/1 "2024-01-10T02:39:52Z")

</div>

Hi,

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

Understand from the [documentation](https://docs.dynatrace.com/docs/manage/data-privacy-and-security/data-privacy/cookies#dynatrace-cookies) that that the following cookies are&nbsp;&nbsp;all first-party cookies:

Cookie Structure Expires Max size Purpose

| dtCookie[1](#fn-1-1-def) | v4 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 | Session | No set limitation, but usually less than 100 B | Tracks a visit across multiple requests. |
| dtLatC | | Session | 5 B | Measures server latency for performance monitoring. |
| dtPC | $\_ve | Session | 58 B | Required to identify proper endpoints for beacon transmission; includes session ID for correlation. |
| dtSa | | Session | Max number of characters in the URL | Serves 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. |
| dtValidationCookie | The dTValidationCookieValue string. | Deleted after a few milliseconds; no expiry date set | Length of dTValidationCookieValue string, that is 23 | Used to determine the top-level domain. |
| dtDisabled | | Session | 4 B | Determines if the RUM JavaScript should be deactivated due to cost and traffic control or overload prevention. |
| rxVisitor | | Session or permanent[2](#fn-1-2-def) | 45 B | Contains the visitor ID to correlate sessions. |
| rxvt | | | Session | 27 B | Specifies 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](https://community.dynatrace.com/topic/121587), 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.

---

<div class="post-metadata">

**Author:** ![MostafaHussein](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/mostafahussein/32/2785_2.png) [@MostafaHussein](https://community.dynatrace.com/u/MostafaHussein)\
**Post date:** [January 10, 2024, 6:53am UTC](https://community.dynatrace.com/t/phasing-out-of-3rd-party-cookies-impact-on-rum/43534/2 "2024-01-10T06:53:42Z")

</div>

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

```auto
/*
 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.

---

<div class="post-metadata">

**Author:** ![Weilin1](https://avatars.discourse-cdn.com/v4/letter/w/5f8ce5/32.png) [@Weilin1](https://community.dynatrace.com/u/Weilin1)\
**Post date:** [January 10, 2024, 8:16am UTC](https://community.dynatrace.com/t/phasing-out-of-3rd-party-cookies-impact-on-rum/43534/3 "2024-01-10T08:16:33Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![MostafaHussein](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/mostafahussein/32/2785_2.png) [@MostafaHussein](https://community.dynatrace.com/u/MostafaHussein)\
**Post date:** [January 11, 2024, 5:37am UTC](https://community.dynatrace.com/t/phasing-out-of-3rd-party-cookies-impact-on-rum/43534/4 "2024-01-11T05:37:58Z")

</div>

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&nbsp;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

---

<div class="post-metadata">

**Author:** ![Weilin1](https://avatars.discourse-cdn.com/v4/letter/w/5f8ce5/32.png) [@Weilin1](https://community.dynatrace.com/u/Weilin1)\
**Post date:** [January 11, 2024, 7:04am UTC](https://community.dynatrace.com/t/phasing-out-of-3rd-party-cookies-impact-on-rum/43534/5 "2024-01-11T07:04:22Z")

</div>

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

Thanks.

---

<div class="post-metadata">

**Author:** ![MostafaHussein](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/mostafahussein/32/2785_2.png) [@MostafaHussein](https://community.dynatrace.com/u/MostafaHussein)\
**Post date:** [January 11, 2024, 10:01am UTC](https://community.dynatrace.com/t/phasing-out-of-3rd-party-cookies-impact-on-rum/43534/6 "2024-01-11T10:01:31Z")

</div>

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.
