EUM browser data is not correlating to the backend application, even when the correlation cookie is coming as a part of the response from the application server.
We see that the cookie information is present in the response and there is no httpOnly flag tagged with the cookie, but the same data is not being sent in the beacons. The guid we see in the beacon is self-generated and not the one sent by the application server. This is causing the correlation to break.
We can see that there are resource files in the page like .png that also have the correlation cookies. These correlation cookies on resource files cause the actual page correlation to break.
The transactions serving the resource files should not be enabled for correlation. Identify the transactions that serves the resource file on the page and disable EUM correlation for those transactions.