Frequently Asked Questions

Everything about FrictaSolv — detection, pricing, privacy, and comparisons.

What FrictaSolv detects

What does FrictaSolv detect?
FrictaSolv automatically detects rage clicks, dead clicks, failed API calls (4xx/5xx errors), JavaScript errors, and page load issues. It helps teams identify broken or confusing UI elements and prioritize fixes based on user frustration — without session recordings or manual tagging.
What is a rage click?
A rage click is when a user clicks the same element 5 or more times within 2 seconds. It reliably indicates that something is not responding — a broken button, a form that didn't submit, or an element with a lost event listener.
What is a dead click?
A dead click is a click on an element that produces no response — no navigation, no state change, no visual feedback. Common causes include non-interactive elements styled as buttons, misaligned hit targets on mobile, and event listeners removed by re-renders.
What is a Friction Score?
A Friction Score is a 0–100 number assigned to each user session based on detected frustration signals. Higher = more broken. Failed API calls and rage clicks contribute the most. Sort sessions by score descending to find your most broken user experiences instantly.
Does FrictaSolv detect errors from third-party APIs?
Yes. FrictaSolv intercepts all Fetch and XMLHttpRequest calls regardless of destination. CORS failures, CDN errors, payment gateway timeouts, and analytics service failures are all captured — many of which never appear in server-side tools like Sentry.

Getting started

How do I get started?
Sign up for a free account, copy your API key, and add one script tag to your site — or install via Google Tag Manager in 2 minutes with no code deploy. Data starts appearing in your dashboard immediately.
Do I need to tag individual elements?
No. FrictaSolv monitors all click events using event delegation on the document root. No CSS selectors to configure, no elements to instrument, no code changes required beyond the initial script tag.
Can I install without a code deploy?
Yes. Install via Google Tag Manager — add a Custom HTML tag with the FrictaSolv script and publish. No engineering ticket needed. Takes under 5 minutes and works on any site with GTM.
Will it slow down my site?
No. The SDK (solv.js) is under 4 KB, loads asynchronously after your page renders, and uses passive event listeners. It adds zero perceptible latency to rendering or user interactions.

Pricing and plans

Is there a free plan?
Yes. The free plan includes rage click detection, dead click tracking, failed API call logging, JavaScript error capture, and a real-time dashboard — no credit card required. Up to 500 events/month.
What is included in paid plans?
Starter ($99/month) adds Slack and Teams alerts, CSV export, per-page thresholds, and up to 5 team members. Pro ($299/month) adds real-time spike alerts, console error correlation, advanced filtering, unlimited team members, and 90-day data retention.
Can I cancel anytime?
Yes. No contracts, no cancellation fees. Downgrade to free or cancel from your account settings at any time. Data retained for 30 days after cancellation.

Privacy and data

Does FrictaSolv record user sessions?
No. FrictaSolv detects frustration signals without storing any video or screenshots of user sessions. No session recordings, no screen captures, no PII from visual data.
What data does FrictaSolv collect?
FrictaSolv logs: page URL, event type (rage click / dead click / failed request / JS error), CSS selector of affected element, HTTP status code and truncated URL for API failures, and page load time. It never reads request or response bodies, cookies, or authentication tokens.
Is FrictaSolv GDPR compliant?
FrictaSolv is designed to be GDPR-compatible. No session recordings, no PII in logged data, no cross-site tracking, and data isolated per organization. See the Privacy Policy for full details.

Comparisons

How is FrictaSolv different from Hotjar?
Hotjar is built for UX research — session recordings, heatmaps, and user surveys. FrictaSolv is built for monitoring — catching broken sessions in real time. No recordings, no PII risk, sub-4 KB script vs Hotjar's ~50 KB. FrictaSolv also detects failed API calls and dead clicks, which Hotjar doesn't.
How is FrictaSolv different from Sentry?
Sentry monitors backend and application errors — server exceptions, database failures, release spikes. FrictaSolv monitors what users experience in the browser — including CORS failures, third-party API timeouts, rage clicks, and dead clicks that never appear in Sentry. Most teams use both.
Is FrictaSolv for developers or product teams?
Both. Developers get exact API URLs, HTTP status codes, and JS error stack traces. Product teams get Friction Scores and page-level summaries they can act on without reading code. The dashboard is designed to bridge both perspectives.

Still have questions?

We respond to every email within one business day.

solutions@frictasolv.com →