Life cycle of DtCookie

[service_apms]

Hello guys,

I'm having a problem with one of my clients.

The issue is that the UEM was enabled on one of the system profiles which caused a http 406 problem accessing one of the applications.

We understood that the issue came from the fact that Dtcookie contains the character "|"

We disable the UEM but the dtcookie is still generated.
What is the lifecycle of the dtcookie?

Did anyone experience the same thing before.
Thank you.

[Dallas · Accepted solution]

Hello,

Here is a documentation link for the Dynatrace cookies:

https://www.dynatrace.com/support/help/how-to-use-dynatrace/data-privacy-and-security/data-privacy/c...

It says that the Dtcookie is set to expire at the end of a session, but if you are seeing other functionality it may be a good idea to open a support ticket.

If you are still seeing the cookie even after disabling RUM I would suggest erasing your browser cookies and starting fresh if possible.

Thanks

-Dallas

[service_apms]

Thank you for your answer i will provide this information and see where it'll get us.

[GR]

Hi 

We are facing same issue with the dtCookie. The RUM script which sets the Dynatrace cookies are set even when RUM script is not injected. We have categorized Dynatrace cookies under performance and analytics. When the user is not consent to collect performance and analytics cookie we don't load the RUM script. Which will not create any Dynatrace related cookies. But in our case dtCookie is getting created even when performance consent is not accepted by the customer. Could you please help us understand what is the expiry of dtCookie and why is it set when RUM script is not injected. 

[Julius_Loman · Accepted solution]

@GR  actually dtCookie is injected on server-side and its injection is unrelated to the presence of the RUM script. Whenever a server resource is accessed and passes the RUM filters (browser, IP exclusions, etc) and there is a RUM web application defined, you will receive a Set-Cookie response header.

[GR]

@Julius_Loman Thanks for your reply Julius,

When you say the cookies are unrelated to presence of RUM script. All the other Dynatrace cookies are also same? Eg: dtLatC, dtPC, dtSa, dtValidationCookie ...

To control these Dynatrace cookies we are not loading the RUM script when user switches off the performance toggle in consent banner. In this scenario, apart from dtcookie none of the above mentioned cookies are created. But some one accepts the performance toggle in consent banner, we load the RUM script which is creating all dynatrace cookies. But always the dtcookie is uncontrollable and it gets created by default. Is there any way to control it from not getting created by default please.

[GR]

Thanks for the explanation Julius. We are now trying to “do not inject” policy on the Default Application (My Web Application ).