Your conversion analyst in ChatGPT and Claude: here's how to use it.
Ask in plain English. ConvRadar pulls your GA4, finds where the funnel leaks, matches the finding against a verified hypothesis library, opens your actual page to confirm, and tells you the next thing to ship. Diagnose → match → verify → act + measure.
Type one slash-command, get a structured answer.
These are the fastest path to value. Each one orchestrates the right tools in the right order so you don't have to learn the API. Use them as defaults; ask follow-up questions in chat.
Want to know exactly what each one runs, in what order, and what comes back? The instrument documentation covers all fourteen, with a real session against a demo dataset on every page.
/full_audit≈ 5–8 minComplete CRO audit on the connected property
- Pulls overview metrics, scans for anomalies, and diagnoses the biggest funnel drop.
- Matches the finding against the hypothesis library and verifies the top candidate on your actual page.
- Returns three prioritised findings + the single next thing to ship.
/weekly_checkup≤ 2 minWeek-over-week health check
- Headline WoW deltas: sessions, conversion rate, revenue, AOV.
- Anomaly scan over the last 7 days; flags statistically-significant breaks.
- Status of in-flight hypotheses + verdicts on changes you shipped recently.
/diagnose_drop≈ 2 minFocused diagnosis when one metric drops
- Splits the drop across device / source / country / landing page.
- Surfaces the top 3 contributors with confidence intervals.
- Suggests candidate hypotheses without auto-running verification — fast and cheap.
/suggest_next_test≈ 1 minPick the next A/B test by leverage
- Reads your confirmed-but-unshipped hypotheses + recent change journal.
- Frames the highest-leverage one through the A/B test design playbook.
- Hands you a primary metric, MDE, sample size, and a ramp plan.
Or just ask in your own words.
ConvRadar maps your question to the right tools — you don't need to know the names. Pick a row that matches what you want to learn and ask it in ChatGPT or Claude.
AHow am I doing?
Status, trends, benchmarks. Use these as a baseline before drilling deeper.
Show me a 28-day overview with revenue, conversion rate, and AOV vs the previous period.
Headline KPIs with prior-period deltas.How does my conversion rate compare to industry benchmarks for my vertical?
CR / AOV / bounce vs benchmark band, calibrated to your vertical.Where is most of my traffic coming from this month?
Top sources/mediums by sessions and revenue.How does mobile conversion compare to desktop?
Side-by-side segment comparison with deltas.
BWhy did X happen?
Diagnostics — the part that makes ConvRadar more than a dashboard.
Why did conversions drop last week?
Anomaly detection + segment breakdown of the drop.Where is my checkout funnel leaking the most revenue?
Step-by-step funnel with leak ranking and dollar value.Did my paid traffic quality change recently?
Source-share shifts + per-source spike/drop detection.Which products are dragging the catalogue conversion rate down?
Per-SKU classification (underperforming / watchlist / healthy) with broken funnel step.
CWhat should I do?
Recommendations + verification + measurement loop.
What should I A/B test next on my product page?
Pulls confirmed hypotheses; frames the test (metric, MDE, sample).Show me hypotheses for checkout friction in subscription e-commerce.
Browse the verified hypothesis library by category + vertical.I shipped a price-display change on Apr 18 — did it work?
Logs the change, runs pre/post z-test 14 days later.Verify this hypothesis on my actual product page.
ConvRadar fetches the page, extracts observables, returns a calibrated verdict.
Diagnose, match, verify, then act.
This is the loop that separates ConvRadar from chatting with a raw analytics dump. The product enforces it; you skip steps only when you want to.
Diagnose
ConvRadar pulls the right slice of GA4 — funnel, segments, traffic mix — and surfaces where the loss concentrates. Statistical, not vibes-based.
Match
The finding gets matched against a library of 126 verified hypotheses across 21 categories and 11 verticals. You see what's likely, ranked.
Verify
ConvRadar fetches your actual page (or asks for a screenshot), extracts observables, and returns a calibrated verdict — matches: yes / partial / no.
Act + measure
When you ship the fix, log the change. Two weeks later, ConvRadar runs a pre/post z-test on the metric you targeted and tells you whether it moved.
25 tools across three tiers.
You almost never need to know these by name — Claude picks the right one from your question. But if you're evaluating ConvRadar for a team or running it for a client, here's the full surface.
Show all 25 tools9 read · 8 diagnostic · 8 hypothesis & verification
Tier 1 — Read your data (9)
- Account info
- Connected GA4 property name, currency, timezone, and the data window we have on file.
- Overview metrics
- Headline KPIs (sessions, conversion rate, revenue, AOV) with prior-period deltas.
- Funnel
- Step-by-step e-commerce funnel with conversion rate per step and the biggest leak ranked.
- Traffic breakdown
- Top traffic sources by (source, medium) with sessions, revenue, conversion rate.
- Landing pages
- Top landing pages with engagement, bounce, duration, purchases, and revenue.
- Device breakdown
- Mobile / desktop / tablet session share with conversion rate and revenue split.
- Geo breakdown
- Top countries by sessions or revenue, with per-country conversion rate.
- Product performance
- Top products by revenue/views/purchases, with cart-to-view and purchase-to-view rates.
- Compare segments
- Side-by-side segment comparison (device, source, country, new vs returning) with deltas.
Tier 2 — Diagnostics (8)
- Find conversion anomalies
- Statistically-significant spikes and drops in daily metrics (28-day rolling baseline, weekly seasonality).
- Diagnose funnel drop
- Segment-level leak analysis split across device, source, country, and landing page.
- Compare to benchmark
- Headline metrics vs industry benchmark band — calibrated to your vertical.
- Detect traffic-quality change
- Flags shifts in source share and per-source spikes or drops over a window.
- Assess traffic quality
- Quantifies analytics noise (referral spam, internal, datacenter, low-quality paid) and estimates distortion.
- Product analysis
- Pre-computed per-SKU diagnosis (underperforming / watchlist / healthy) with the broken funnel step.
- Describe data
- Metadata: which fact tables, dimensions, metrics, and events are queryable, plus the date window.
- Query metrics
- Flexible ad-hoc aggregation over GA4 fact tables with dimensions, metrics, and filters.
Tier 3 — Hypotheses & verification (8)
- List hypotheses
- Browse the verified hypothesis library — paginated index by category and vertical.
- Get hypothesis
- Full hypothesis content by ID — description, expected impact, suggested test, evidence basis.
- Capture page
- Server-side fetch of a URL; ConvRadar reads the live HTML to verify a hypothesis.
- Record verification
- Submit observables from the captured page; runs the matcher and returns a verdict.
- Mark hypothesis status
- Move hypotheses through surfaced → testing → confirmed / rejected / dismissed / archived.
- Save AI-suggested
- Persist a Claude-generated hypothesis when the library has no good match.
- Log change
- Record a deployed change (copy / design / pricing / flow / experiment) for impact tracking.
- Verify change impact
- Two-proportion z-test on pre/post metrics — did your change actually move the number.
Five tips that pay back fast.
- Be specific about the time window."Last 28 days", "this quarter", "Apr 1 to today" — ConvRadar defaults to 30d if you don't say.
- Mention the segment you care about.Mobile, paid search, returning users, a specific country. Diagnoses get sharper when scoped.
- Use a slash-command when in doubt.
/full_auditis the right default for "something is off, find what."/weekly_checkupfor routine Mondays. - Ask Claude to verify on your real page.Once a hypothesis is proposed, say "verify on my actual product page". ConvRadar will fetch the page and return a verdict — not a guess.
- Log every change, then check back.After you ship a fix, ask "log this change against hypothesis X". Two weeks later, run
/weekly_checkupand ConvRadar will report the pre/post verdict.
What ConvRadar doesn't do.
Honesty saves trust. These limits are intentional — most of them are about staying out of your users' private data and out of your platform settings.
- No live or real-time queries.GA4 itself has a ~24-hour data delay. You're seeing yesterday and back.
- No user-level data.Aggregated rows only. No emails, no IDs, no individual session traces.
- No competitor data, no Ads, no Search Console.GA4 only. We don't connect to BigQuery exports, paid platforms, or third-party tools.
- No autonomous actions.ConvRadar recommends. You decide and ship. Nothing changes in your GA4 or your site without you doing it yourself.
Plug ConvRadar into your AI in five minutes.
Click-by-click, with screenshots. In ChatGPT it is the official ConvRadar plugin: open it, click Connect, sign in with Google. In Claude you sign up first, then one click adds the connector. The seven questions it answers in ChatGPT, with the prompts to paste.
- 1Create a ConvRadar accountGo to convradar.com/connect and continue with Google, or use your email for a one-click sign-in link. Free plan, no card.

- 2Connect GA4 read-onlyAllow read-only access to Google Analytics and pick your property. ConvRadar loads the last 90 days in the background.
- 3Click Add to ClaudeYour ConvRadar page lists one-click buttons per client. Add to Claude opens claude.ai with the connector already filled in: name ConvRadar, URL https://mcp.convradar.com/mcp. Click Continue, then sign in with the same account when Claude asks.

- 4Ask in any chatOpen a new chat and ask “Use ConvRadar to show my funnel for the last 30 days.”

- 1Open the ConvRadar plugin in ChatGPTConvRadar is an official plugin in ChatGPT’s plugin directory and works on any ChatGPT plan. Open ConvRadar in ChatGPT, or open Plugins in the ChatGPT sidebar and search ConvRadar. Click Connect.

- 2Sign in with Google and pick your GA4 propertyChatGPT opens ConvRadar in a new window. Continue with the Google account that can see your GA4 property; a ConvRadar account is created on the Free plan, no card. Allow read-only GA4 access and pick the property ChatGPT should read.

- 3Click Return to ChatGPTThe last ConvRadar screen shows your property and one button, Return to ChatGPT (it reads Approve if you already had a ConvRadar account). ChatGPT takes over and the plugin is installed. Your last 90 days of GA4 load in the background; questions about recent days work within minutes.
- 4Type @, pick ConvRadar, askIn any chat type @ConvRadar, pick ConvRadar: CRO for GA4 and ask “Where am I losing conversions?”

- 5Read the answerChatGPT calls ConvRadar's tools and answers from your own GA4 numbers: the leaking step, the segment behind it, and whether the drop is real or tracking noise. Below, the same question on our demo store.

Troubleshooting
ChatGPT doesn't use ConvRadar when I ask▾
It says my data is still loading▾
It reads the wrong GA4 property▾
Claude says “Couldn’t reach the MCP server”▾
My sign-in email didn't arrive▾
I want to revoke access▾
OpenAI and Anthropic change these screens often. If a screenshot here doesn’t match what you see, tell us at /contacts. Captured on October 5, 2026.
Already have an account? Open your connector page →
Got it? Time to plug in your GA4.
Free plan, no card. Paid plans from $5.99 when you need more.