There are a variety of legitimate reasons for failures to collect:
Client networks, e.g., low bandwidth, network handovers, dropped connections, and Mobile Carrier TCP idle management
Remote software e.g,. ad blockers, OS/user privacy controls, endpoint client security
Corporate VPNs, e.g., traffic restrictions, content filtering, firewalls
Geographical latency e.g,. round-trip between client->proxy->Feedzai
Infrastructure configuration, e.g., traffic management, TCP management
A number of the above (ad blockers, OS/user privacy controls, content filtering) can be partially mitigated with the implementation of the Digital Trust control flow.
However, across client-side telemetry tools, you can still expect a 1-3% failure rate. This failure rate is in keeping with industry norms.
As part of any risk strategy, we recommend considering the absence of Digital Trust risk assessment as a signal in and of itself. But importantly, this should be considered alongside additional external data points and context(s) to optimize the trade-off between risk and false positives in line with an operational strategy. Here are some considerations of what else to consider when there is no Digital Trust risk assessment available:-
Layered Fraud Controls
-
Refer to other risk systems for real-time insight:
E.g., spending patterns, outbound reputation, etc., all possible via monetary transactional risk analysis systems.
Request additional authentication assurance, e.g., step-up
Fraud loss exposure
-
Risk exposure stances may change:
E.g., time of year, fraud patterns, individual payment amounts, cumulative payment amounts.
Operational Response
Manual review of alerts
Delay in payment processing
-
Restrict user entitlements
E.g., view only, payment limits
If you have noticed an unusual volume of missing sessions, please open a support ticket and include a list of the specific Session IDs that were not found in the Digital Trust console. This will allow our team to investigate why these particular sessions were not captured.