“Yes, Ravelin can still provide useful device-fingerprinting and fraud-detection signals, but its effectiveness can be materially reduced when a large proportion of your customers use privacy-focused browsers and ad blockers.”
“Yes, Ravelin can still provide useful device-fingerprinting and fraud-detection signals, but its effectiveness can be materially reduced when a large proportion of your customers use privacy-focused browsers and ad blockers.”
“Ravelin also uses: - Transaction and payment information. - Customer account and login history. - IP addresses and geographic information. - Behavioural patterns and session activity. - Connections between customer accounts and devices through its graph network. - Historical fraud patterns and machine-learning models.”
“The good news: Ravelin actually provides two solutions: - Custom subdomain: Route Ravelin traffic through your own domain. - Server-side proxy: Route API requests through your infrastructure.”
“I wouldn't dismiss Ravelin because of privacy browsers and ad blockers. It has recognised the problem and provides a technical workaround for an important part of it.”
“Ad blockers can intercept requests to live.ravelin.click.”
“Missing information can negatively affect fraud-detection performance.”
“A custom subdomain can help with requests blocked because of Ravelin's domain reputation, but it cannot restore browser information that the browser deliberately withholds.”
“These are qualitative assessments, not published Ravelin performance benchmarks.”
