on 28 May 2025 02:43 PM
Since version 122, by default, Chromium blocks third party cookies. If a site needs these to run as expected, they will need to be enabled for the Browser Monitor.
The site to be tested does not load as expected with third party cookies blocked. This might be shown in the screenshots, like below, or the page may just not load as expected.
There are 2 options for this:
This setting is persisted.
chrome://settings/cookies
The following Chrome startup parameter makes Chrome allow 3rd party cookies for all websites by disabling the Chrome feature that blocks 3rd party cookies:
--disable-features=TrackingProtection3pcd
No changes are required, as the TrackingProtection3pcd
feature will be disabled by default.
Note: if the private synthetic location configuration/ monitor configuration has previously been updated, as descibed in the 'Prior to Cluster version 315' section, then the lines added will need to be removed/ updated to allow the new feature list to be used.
If this does not resolve the issue, please open a support ticket and provide
More articles can be found on the Synthetic Troubleshooting Map
Confirm the current list of disabled features
--disable-features=
and copy the whole value. For example in Cluster version 313 it'sand you would copy
,TrackingProtection3pcd
to the end of the list of values. For exampleUpdate list of disabled features
This feature can be disabled for all monitors running on the ActiveGate, or for a single monitor.
Note: These changes persist on update, so if new features are disabled by default, you may need to update your snippet.
To affect all monitors running on an ActiveGate
user.properties
fileC:\\ProgramData\\dynatrace\\synthetic\\config\\user.properties
on Windows/var/lib/dynatrace/synthetic/config/user.properties
on Linux--disable-features
snippet created earlier aftercom.ruxit.vuc.poolConfig.playerConfig.additionalStartupParams=--disable-features
. For exampleTo affect a single monitor