← Plugin catalog
Data & Analytics

ConvRadar: CRO for GA4 & GTM

Pika Ivan v1.1.4

Fix your GA4 conversion leaks

Create a free account to save this plugin.

From the developer

Not specified in the available declarations: capabilities, limitations, pricing & account requirements.

Onboarding example

Run a full conversion audit of my store or lead-gen site
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 20, 2026. Package observed Nov 20, 2026.

View package source →

Description

From the marketplace listing

Find out why your site doesn't convert and what to fix first. ConvRadar connects to your Google Analytics 4 (GA4) and turns your data into a ranked list of fixes: where visitors drop off, what each leak costs you, and the change to make on the page. Connect GA4 in about a minute. ConvRadar loads 90 days of your history, and the first answer arrives in 2 to 3 minutes, with no setup. Ask in plain words: why did sales drop last week, which landing pages lose leads, does mobile convert worse than desktop. Each answer gives the numbers, the likely cause and what to change, checked against 184 conversion rate optimization (CRO) hypotheses from published research. Ask for a full audit and get one HTML report for your store or lead-gen site: the funnel by device and landing page, what each leak costs, and the fixes in order. For a SaaS or B2B service, the page audit takes your product or pricing page, follows it to the signup or checkout form, and returns the fixes with mockups. Conversion (CRO): - Get a conversion audit of your store or lead-gen site, with the fixes ranked by what they cost you - Find why sales or leads dropped: on which step, device, page or traffic source - See which landing pages and channels bring visitors who don't buy - Compare mobile and desktop, paid and organic, with a significance test, so you don't chase noise - See which products lose sales, and at which step: view, add to cart or checkout - Clean your numbers: find bot, spam and internal traffic, and the GA4 filters that remove it - Spot sudden drops in sales, leads or conversion rate, and what changed in your traffic - Audit one SaaS or B2B page: product, pricing, plan or subscription - Learn what customers in your category complain about online, and whether your page answers it - Check a page for load speed and mobile UX problems - Benchmark your conversion rate and AOV against your industry - Get a tracking plan: the GA4 events to add or fix, ranked - Log the changes you ship and measure whether they actually helped Google Tag Manager (GTM): Missing an event in GA4? Say what to track in one sentence: clicks on a button, WhatsApp or phone links, a form, a Google Ads conversion. - ConvRadar reads your live GTM container and GA4, and tells you what is already tracked - It drafts the tags and creates them as a version in its own workspace; nothing goes live until you click Publish - After Publish, it confirms in GA4 realtime that the event arrives, and any change can be rolled back Works with any site on GA4: Shopify and WooCommerce stores, SaaS products, lead-generation and service sites. ConvRadar reads only aggregated GA4 metrics of the property you connect. It never reads user-level data or your ChatGPT conversations. Changes to Tag Manager or GA4 need a separate Google consent that you can pause or remove at any time.

Language: English · Automatically detected from descriptions.

What changed

· 5 observations

Capabilities & instructions

Supporting files updated; open the comparison for details. Skill instructions changed from “(ConvRadar, 7 quota calls total; browser reads do not count) Follow `references/data.md`. Period: 90 days ending `data_complete_to`. Keep the entire...” to “(ConvRadar) Follow `references/data.md`. Period: 90 days ending...

View comparison →
Capabilities & instructions

Supporting files updated; open the comparison for details. Skill instructions changed from “(about 25) for a verified full audit; any further call only to settle a finding you are about to write, and no more than 45 in total. A tracking diagnostic...” to “for a verified full audit, then any further call that settles...

View comparison →
Pricing references

Plugin name changed from “ConvRadar: CRO for GA4” to “ConvRadar: CRO for GA4 & GTM”. Full description changed from “ConvRadar finds where your site loses conversions and ranks what to fix first. Connect your Google Analytics 4 property and ask for an audit. ConvRadar reads...” to “Find out why your site doesn't...

View comparison →

Technical updates · 1

Package or technical metadata updated

View technical comparison →

· 3 observations

Pricing references

Is v2 template added: “false”. App-6a006bea18648191a3a8512c25d445ba updated; open the comparison for details. Convradar updated; open the comparison for details. Full description changed from “2-5 ranked findings, each matched against a curated library of 184 CRO hypotheses across 43 categories, built from published...

View comparison →
Pricing references

App-6a006bea18648191a3a8512c25d445ba updated; open the comparison for details. Convradar updated; open the comparison for details. Full description changed from “2-5 ranked findings, each matched against a curated library of 184 CRO hypotheses across 43 categories, built from published conversion research. What...

View comparison →

Technical updates · 1

Package or technical metadata updated

View technical comparison →

Similar plugins

Finding similar plugins… Results will appear here automatically.

Browse plugins →

Keywords

Files & skills

File archives

Plugin package19 files · 230 KBBrowse files →
Skill instructions
convradar-ecom-leadgen-audit13.9 KB

View saved version →

---
name: convradar-ecom-leadgen-audit
description: Use when a user asks for a full conversion or CRO audit of an ecommerce store or a lead-generation site that sells services and collects enquiries, quotes, bookings or calls. Uses ConvRadar GA4 data, live pages and public research to deliver an actionable HTML report. Typical requests include "audit my store", "what should we fix to get more leads", "аудит магазина" and "полный аудит лидогенерации". Do not use for SaaS or software products, even when their primary conversion is a demo or contact form; a separate SaaS audit skill handles those. Do not use for a one-page review, a single main problem or a drop on named dates.
---

# ConvRadar: E-commerce and lead generation conversion audit

Scope: ecommerce stores and service businesses whose site generates leads. Do not use this skill for SaaS or other software products, even if a demo, trial, contact or quote form is their main measured conversion. A separate SaaS audit skill covers that business model. Goal: one HTML report a business owner can act on the same week. It says what the site converts, where visitors are lost and why, what that costs, what to fix first, and what is fine and should be left alone.

Before the first call, read `references/data.md` and `references/resume.md`. After the free `cr_get_account_info` identifies the business model, read `references/leadgen.md` or `references/ecom.md`, plus `references/pages.md` and `references/writing.md`. Build the file from `assets/report-template.html`.

## 0. Which audit

Call `cr_get_account_info` (free). Use `business_model`:
- First check whether the business sells software or a SaaS subscription. If so, stop this skill even when `business_model` says `lead_generation` or the site has a demo form. Use the separate SaaS audit skill when available; otherwise explain that this audit does not cover SaaS.
- `lead_generation`, or a site whose conversion is a form, a booking request, a call or a quote: follow `references/leadgen.md`.
- `ecommerce`: follow `references/ecom.md`.
- Anything else (media, content, apps without a store or service lead flow): explain that this audit covers ecommerce stores and service lead-generation sites. Do not produce an unrelated whole-site audit under this skill.

If `website_url` is another domain than the one the user named, say the data is for `website_url` and ask which site to audit. Stop. A subdomain of the named domain (app., shop., book.) is the same site; audit both hosts and say which pages sit on which.

Window: the 90 days ending `data_complete_to`. Pass `date_from` and `date_to` to every dated call.

Before any paid call, create the audit checkpoint described in `references/resume.md`. The core calls remain the full audit route; Free users may hit their weekly allowance and receive the evidence-backed partial result described under Limits. Do not silently reduce the audit to fit a plan.

## 1. Trust the data before using it

Run the checks in `data.md` → "Trust checks" before any analysis:
- What the counted conversion event really is. Read the page where it fires (thank-you page, booking step, form). If it fires before the real conversion (a booking started, a button click), say what it measures and look for an outcome event that can be validated. If its volume is far below a confirmation signal or known purchases, investigate the mismatch; do not substitute another event solely because its count looks plausible.
- Unqualified traffic: a device, source or country with 15% or more of sessions and engagement under half the site's average, or a conversion rate near zero against the rest; also several small sources of that kind that together pass 5%. Report the numbers with and without it and use the qualified figure from then on. Do not trust a "clean" verdict from a tool over these numbers.
- Out-of-market traffic: countries the business cannot serve. Show the conversion rate on the market it serves.
- More than one conversion 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 8 — file references are metadata, not package contents.

saas-page-audit8.3 KB

View saved version →

---
name: saas-page-audit
description: Use when a user gives a SaaS product, pricing, hosting plan, subscription or B2B service page URL and asks for a conversion audit, why it does not convert, or specific fixes (including "аудит страницы тарифов"). Produces one HTML report using the page, its signup or checkout, connected ConvRadar GA4 when available, buyer questions and competitor pages. Not for store cart products, whole-site audits or date-specific metric drops.
---

# ConvRadar: SaaS and service page audit

Goal: one HTML report about one page that a founder can act on the same day. It says where visitors stop, which statements on the page and at the next step contradict each other, what buyers ask that the page does not answer, what to change first (with mockups), and what that is worth.

Read `references/checks.md`, `references/data.md` and `references/writing.md` before the first call. Build the file from `assets/report-template.html`.

## 0. What you need

- The page URL. If the user gave none, ask for it and stop.
- ConvRadar connected to the same site. Unless the user forbids quota use, call `cr_get_account_info` once; it consumes a daily MCP call. If `website_url` is another domain, say the page has no GA4 data in ConvRadar, run steps 2 to 6, and write section 01 from the user's numbers only. If the user forbids quota use, make zero ConvRadar calls, including account info, data description and page capture. Use previously supplied data with its dates and provenance; otherwise write a page-only audit without GA4 numbers.
- Optional, never wait for them: heatmap numbers (scroll reach by page depth, clicks on the decision block), next-step counts if the checkout or signup is not in GA4, past tests on this page. Use them when the user gave them. If they cover another period than ConvRadar, section 01 uses the user's numbers and the ConvRadar window goes to the footer.

## 1. Page numbers (ConvRadar)

Follow `references/data.md`. Period: 90 days ending `data_complete_to`. There is no call count to stay under: do not stop early or skip a check to save calls. Stop calling only when a tool result has `status` `weekly_limit` or `rate_limited`; the remaining-call counts in `meta.quota` and `user_notice` are not a reason to stop. Read the page itself with the browser. You need: visits that started on the page by source and by device, conversion, form and next-step events in those visits, page views of the page and of its next step, and a mobile speed check.

## 1b. Where the loss is

Before any page check, locate the loss only from counts joined to the same visits or users and the same page variant. Pricing-page landings, site-wide next-step views and site-wide success events are three different populations; their ratios do not measure pass-through or completion. A shared next step can still supply a separate, clearly labelled site-wide diagnostic, but its totals cannot be attributed to this page.
- Joined counts show a larger loss at the next step on 30+ visits: the H1 and section 01 name that step with its cohort rate; sections 02 and 04 run checks 2 to 6 and the form check there. Mockups show the next step now beside proposed.
- Counts cannot be joined: audit the page and its linked next step, choose emphasis from directly observed friction, and state that the larger loss cannot be located quantitatively. Do not say the page passes visitors on or the next step completes normally from aggregate page-view ratios.
- Joined counts show both steps work: say so with their cohort numbers and keep only problems supported by checks 2 to 6.

## 2. Read the page and its next step

Fetch the full HTML of the page with the browser or web fetch. Use `cr_capture_via_web_fetch` when the browser or web fetch cannot read the page; prices that scripts change after load need the browser. Read all text, including tables, tabs, accordions, FAQ, footnotes and the comparison table. Then open every main call to action and read where it leads: che

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 5 — file references are metadata, not package contents.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
Pika Ivan
Keywords
See keywords

Package observed Nov 20, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 20, 2026 · 14:34 UTC
Latest observed change
Nov 19, 2026 · 06:09 UTC
Collection status
Collected

plugin_asdk_app_6a006bea18648191a3a8512c25d445ba

Download plugin data (JSON)

Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.