We have three monitors and all have custom user agent string (starting with <var>Synthetic*). However, intermittenly we do see blocking happening from DataDome.
Located the <request.> request in desktop Chrome, It's sent by the Navigator.sendBeacon() API which bypassed the normal code path for sending requests, which is probably why Chrome fails to set a user-agent for it or record it in HAR. The request is typically sent after the page finished loading but before the browser is closed, which explains why it's present only on some monitor runs.
Dsabled in Aug 18 25 HotFix and later.