ConvRadar is in open beta — every diagnostic, every tool, completely free while we’re collecting feedback. Sign up with email. No card. No checkout.
ConvRadar reads your GA4 and tells you exactly that — the leak, the cause, and the fix you can ship this week. In plain English. The way a senior analyst would, if you'd hired one.
Open beta — completely free. No card required.
| Metric | This week | Last week | Δ |
|---|---|---|---|
| Sessions | 6,914 | 7,512 | −8.0% |
| Conversions | 51 | 78 | −34.6% |
| Revenue | $6,724 | $9,810 | −31.5% |
| CR | 0.74% | 1.04% | −28.8% |
Where it broke: the drop is concentrated in add_to_cart → begin_checkout (70% → 56%). Traffic mix is steady — this is a checkout-step regression, not an acquisition problem.
Ask me to dig deeper — e.g. "why is checkout dropping?" or "is this device-specific?"
Three steps, and the third one is the whole product. The only thing between you and your first verdict is one hour of data collection — kicked off automatically the moment you connect.
Create an account, connect your GA4 property with one Google OAuth click. Read-only — disconnect anytime.
Paste the ConvRadar connector URL into Claude (web, Desktop, Cowork) or ChatGPT, ping it from Telegram, or just talk to it on the webpage. The MCP tools install themselves — no extension, no install wizard.
Ask Claude, ChatGPT, Telegram, or the webpage chat what's going on. ConvRadar pulls the right slice of GA4, runs the diagnostic, and turns the result into a verdict you can defend.
Simple lookups — sessions, CR, top channels — we hand back as-is. But when you ask why something dropped, the analysis runs as Python and SQL against our own Postgres, not as a guess from the LLM.
Ingested nightly into fact tables. No live API calls, no sampling, no thresholds.
Funnel drops, anomalies, segment attribution — Python and SQL on our server, against a 300+ audit playbook. The verdict is computed before the model sees it.
It receives the finished finding and turns it into the answer. The reasoning happens before the writing.
Read-only OAuth. Every number traces back to the GA4 slice it came from.
Not a sizzle reel. No cuts, no fast-forward — me opening ConvRadar and using it end to end, exactly the way you will.
Same interface you already use to write emails, brainstorm copy, debug code. You ask in plain English, ConvRadar pulls the right slice of GA4, and the answer comes back as a verdict — not another dashboard.
You open the report. Sessions held, conversions slipped, revenue is down — and that's where the help ends. The chart shows you the dip and walks away. You spend the afternoon poking around segments, trying to figure out if it's mobile, the new landing page, the pricing test you shipped last week, or just a noisy Tuesday. By 6pm you have a guess, not an answer. You ship something. You hope.
That's the problem. Not the data. The silence after.
ConvRadar talks back. Connect GA4 once and just ask — in Claude, ChatGPT, Telegram, or the chat right on this page — what's happening. It knows your numbers, knows where to look, and knows what to do next. Like a senior analyst who picks up the phone, except it's completely free during open beta and it's already inside the chat you use anyway.
I've been the top-rated analytics & conversion freelancer on Upwork for five years running. Over the last decade I've run more than 300 audits for e-commerce and SaaS teams — and in the last five years, zero unsuccessful projects. ConvRadar is that playbook, distilled. Every check we run is a check I've run by hand, a hundred times. When you ask — in Claude, ChatGPT, Telegram, or the chat right here — what's wrong, you're getting the same answer I'd give if you'd hired me. At 1% of the price, available the moment you ask.
Ivan Pika — host of the Conversion & Analytics podcast. Every check in ConvRadar is one I've run by hand, a hundred times.
Real questions you've already asked yourself this week. Each one comes back with a verdict, the evidence, and — most importantly — what to actually do next. Not a chart. Not a "directionally interesting" observation. The fix.
Every row is the output of a single question — asked in Claude, ChatGPT, Telegram, or right here in the page chat. Verdict, evidence, recommended action — paste it into a Slack thread and stand behind it.
| Industry | Problem we found | Fix we shipped | Recovered |
|---|---|---|---|
| DTC apparel | Mobile checkout CVR 38% below desktop Leak localised to the address step on iOS | Replaced address autocomplete widget, removed a blocking JS error in the ZIP validator. | +$42,800/mo mobile CVR +51% |
| SaaS | Sign-up to activation drop at the "invite teammate" step Anomaly started the day after a deploy; only affected free plan | Made the invite step skippable; activation recovered within 48 hours. | +27% activation ~$9,100 MRR added |
| Beauty e-com | Paid search CVR collapsed on one campaign Intent mismatch — page promised "gift sets", campaign bid on "refill" | Split the ad group, pointed refill queries at the correct PDP, paused 4 mismatched keywords. | +$18,400/mo paid CAC −23% |
| Marketplace | Top-10 SKU with above-average traffic, below-average CVR Product images missing; variant picker broken on mobile | Re-uploaded photography, rebuilt the variant picker as a native select on mobile. | +$11,600/mo SKU view→cart +64% |
| Subscription | Organic traffic grew 22%, revenue flat New traffic landed on a blog post that didn't link to the offer | Added an inline CTA block and an exit-intent offer; kept the editorial tone. | +$6,900/mo blog→trial +3.1pp |
Numbers rounded. All figures verified before/after with the ConvRadar confidence interval attached.
Five minutes to sign up and connect GA4, one to paste the connector URL into Claude, ChatGPT, or Telegram (or just chat with it right here), an hour for the initial sync — then ask anything. Senior-analyst answers, completely free during open beta, no card required.