AnalyticScan
KO

Sample result

SaaS GA4 diagnosis

All thirty verdicts and the evidence behind them, without signing in.

Run 2026-09 · over the last 28 days

Three things to look at first

  1. Critical failureCV-02Conversions not collecting
  2. Weakest categoryConversions (key events) — 38%
  3. Quick winCV-03Conversion value collection — Worth 4 points

Data health score

65/ 100

Grade

C

Caution — some key metrics can't be trusted

1 critical failure(s) (CV-02)

Score by category

  • Event collection84
  • Conversions (key events)38
  • Parameters & custom definitions100
  • Property settings50
  • Tagging & data streams60
  • Integrations & governance80

All thirty checks

  • CV-02Conversions not collecting

    A conversion that is registered but never collected reads as zero. You end up switching off a campaign that was selling perfectly well.

    Key events with zero count: purchase, event_1, event_2 — configured but not collecting

    I don't understand what this means

    In plain terms — we check whether an action you've flagged as a conversion is actually being recorded even once. Flagging it is the switch; recording it is a separate thing.

    Terms

    Key event
    — GA4's current name for what used to be called a "conversion": an event you've flagged as a business outcome, which is what ad platforms optimize toward.
    0/7Fail

  • CV-03Conversion value collection

    Without the purchase amount, you cannot judge performance by revenue. ROAS and revenue-by-campaign cannot be calculated at all, so budget gets split on conversion counts alone.

    purchase carries no value/currency at all — ROAS can't be computed

    I don't understand what this means

    In plain terms — we check whether your purchase event carries what it was actually worth — an amount and a currency. Counts alone can't tell you anything about revenue.

    0/4Fail

  • EV-04Event volume anomalies

    An event sitting at zero from some date onward means that period is simply missing. Compare month over month and a campaign looks like it collapsed, when in fact the tag was switched off.

    Events that stopped collecting: page_view, user_engagement, scroll — zero for 7+ recent days

    I don't understand what this means

    In plain terms — we check whether a particular event's daily count suddenly spiked or dropped to zero in the last month. That's usually a broken tag or a deploy nobody noticed.

    0/4Fail

  • ST-01Data retention period

    The default is two months, after which older data is deleted. Year-on-year comparison and seasonal analysis stop being possible at all.

    Event data retention left at the 2-month default — extend to 14 months

    I don't understand what this means

    In plain terms — we check how long GA4 is keeping your raw data. Left at the default (two months), you can't compare this year to last.

    0/4Fail

  • TG-02Dev/staging traffic mixed in

    Test visits from a site still in development mix into your real numbers. Traffic is inflated, and test orders can end up counted as revenue.

    15% non-production host traffic: host_1

    I don't understand what this means

    In plain terms — we check whether test visits from localhost or a staging domain are leaking into your real, production data.

    0/3Fail
Run the same diagnosis on my GA4 — freeAsk about implementation

A real diagnosis of a property the owner runs, anonymised. Property name, hosts, custom event and dimension names and internal filter names were substituted, and the country and time zone removed. The verdicts and the figures are untouched.

← Other verticals

SaaS GA4 diagnosis example | AnalyticScan