Shopify is the source of truth — GA4 under-reports 77% of revenue — figures here use Shopify; fix GA4 tagging to restore in-tool tracking.Shopify $3,697 · GA4 $867 (-77%) · consent n/a
1,754 sessions · 35 purchases
GA4 · through Oct 24Shopify · through Nov 10Clarity · through Nov 11
Last 30 days
Bigvita
US · Supplement · 896 mobile sessions
0.83%
mobile conversion · Shopify
GA4 · Funnel
Add to cart3.57%
Checkout start2.01%
Purchase0.33%
Sitewide band 1.5–3.5%
Shopify · Revenue
Orders35
AOV$370
Revenue$3,697
Refunds$0
Real Shopify · 30d
Clarity · Behavior · mobile
Script errors11.8%
Bot traffic16.9%
Pages / session1.42
Dead clicks288
Avg scroll22%
4,620 Clarity sessions
Conversion funnelmobile
No single leak — every step is within its typical range for supplement stores.
896
Session Start
64%
vs 20–45%
576
View Product
6%
vs 5–10%
32
Add to Cart
56%
vs 40–60%
18
Begin Checkout
41%
vs 40–60%
7
Purchase
Low counts — treat as directional.
Percentages are how many carry over to the next step. Ranges are typical for supplement stores.ⓘTypical ranges are Evolut's methodology reference bands (§3.3.2) — category benchmarks for DTC supplement funnels: View→Add to Cart 5–10%, Add to Cart→Checkout 40–60%, Checkout→Purchase 40–60%. Session→View (20–45%) is an internal reference — no established category benchmark exists for that step. A step above its range is fine; only the worst step below its range is the leak.
Recommendationsblockers gate at top · opportunities ranked by ICE
1
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Reported revenue can't be trusted — analytics is undercounting real sales by 78%
All downstream funnel and revenue figures are unreliable until this gap is closed, so every other finding here is provisional.
What's happening

GA4 shows $867 in revenue while Shopify shows $3,877 for the same 30 days — a 78% shortfall.

  • GA4 Revenue$867 vs Shopify $3,877
  • Divergence-78% should be within ±10%

Likely cause Likely a broken/duplicated GA4 purchase event or consent-mode blocking hits; check event firing vs consent banner behavior to distinguish.

Do this — in order
  1. Audit GA4 purchase event in GTM preview mode
    Confirm it fires once per order with correct value/currency parameters.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode and cookie-banner configuration
    Null consentRatePct suggests consent signals may be suppressing GA4 hits entirely.
    ~1 day · analytics · Evolut (analytics)
  3. Reconcile 10 sample orders between GA4 and Shopify
    Pinpoint exactly where GA4 loses the purchase event.
    ~2 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $867 vs Shopify revenue $3,877 (-78% divergence)tracking verdict: RED
2
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Your two revenue systems disagree by 41%, so every funnel number here is suspect
A 41% revenue gap between GA4 and Shopify means funnel retention percentages used for every other finding are unreliable until tracking is fixed.
What's happening

GA4 reports $1,758 vs Shopify's $2,985 in the same 30 days, a 41% gap that invalidates funnel math.

  • GA4 vs Shopify Revenue-41% should be ~0%

Likely cause Likely GA4 purchase event failing to fire on some orders, or consent-mode blocking tags; distinguish by comparing order IDs missing in GA4.

Do this — in order
  1. Compare GA4 purchase hits against Shopify order IDs
    Identify which orders GA4 is missing to isolate the firing issue
    ~2 h · analytics · Evolut (analytics)
  2. Check consent banner impact on purchase tag firing
    Confirm analytics consent isn't silently blocking the purchase event
    ~30 min · analytics · Evolut (analytics)
  3. Add Shopify order webhook as a server-side backup feed
    Removes reliance on client-side GA4 tag for revenue truth
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,758 vs Shopify revenue $2,985GA4 vs Shopify revenue: -41%tracking verdict RED
3
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Reported revenue can't be trusted for any decision
A 77% revenue gap between GA4 and Shopify means every funnel and CR number below is provisional until tracking is fixed.
What's happening

GA4 reports $867 in revenue while Shopify shows $3,697 — a 77% gap signalling broken measurement.

  • GA4 Revenue$867 vs Shopify $3,697
  • Shopify Revenue$3,697 source of truth

Likely cause Likely GA4 purchase events failing to fire/duplicate on some sessions, or consent-mode blocking tags; compare event counts vs Shopify order IDs to isolate which.

Do this — in order
  1. Audit GA4 purchase event firing
    Confirm the event fires exactly once per completed order and matches Shopify order IDs.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode and tag-blocking impact
    Verify whether GA4 tags are blocked pre-consent, undercounting purchases.
    ~2 h · analytics · Evolut (analytics)
  3. Build a daily GA4-vs-Shopify reconciliation check
    Catch future divergence early before it skews CRO decisions.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $867 vs Shopify revenue $3,697 (-77% divergence)tracking verdict: RED
4
Data-supportediSev 4 · blockeriInstrumentianalyticsi
You can't trust your own revenue numbers right now
A 68% gap between GA4 and Shopify revenue means all downstream funnel and CRO conclusions are provisional until measurement is fixed.
What's happening

GA4 reports $1,031 in revenue while Shopify shows $3,175 — a 68% gap invalidating funnel analysis.

  • GA4 vs Shopify Revenue-68% should be near 0%

Likely cause Likely missing/duplicated GA4 purchase events or consent-blocked tracking; check server-side event firing vs consent mode defaults.

Do this — in order
  1. Audit GA4 purchase events against Shopify order webhooks
    Reveals whether events are missing, duplicated, or blocked.
    ~2 h · analytics · Evolut (analytics)
  2. Implement server-side GA4 tagging for Shopify
    Removes reliance on client-side JS that can fail or be blocked by ad blockers.
    ~1 day · analytics · Evolut (analytics)
  3. Check consent mode default settings
    If consent isn't granted by default, GA4 under-reports vs Shopify's native count.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,031 vs Shopify revenue $3,175GA4 vs Shopify revenue: -68%tracking verdict RED
5
Data-supportediSev 4 · blockeriInstrumentianalyticsi
You can't trust the revenue numbers driving every decision
Tracking is RED and revenue is understated by nearly half, so all funnel percentages below are provisional until fixed.
What's happening

GA4 shows $1,271 in revenue while Shopify shows $2,515, a 49% gap that invalidates funnel analysis.

  • GA4 Revenue$1,271 vs Shopify $2,515
  • Revenue Divergence-49% RED verdict threshold

Likely cause Likely a misfiring or duplicated GA4 purchase tag versus Shopify's order record, rather than real refunds; compare tag firing logs to webhook order timestamps.

Do this — in order
  1. Audit GA4 purchase event against Shopify order webhook
    Confirms whether events are missing, duplicated, or blocked by consent mode.
    ~2 h · analytics · Evolut (analytics)
  2. Add Shopify order ID as a dedupe key in GA4
    Prevents double-counting or dropped purchases from refreshes.
    ~2 h · analytics · Evolut (analytics)
  3. Implement server-side purchase tracking
    Captures orders missed by client-side tags due to ad blockers or script errors.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,271 vs Shopify revenue $2,515 (-49% divergence)tracking verdict: RED
6
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue reports can't be trusted for decisions
A 40% revenue gap between GA4 and Shopify means every funnel and revenue number below is unreliable until tracking is fixed.
What's happening

GA4 captures only $1,468 of the $2,456 Shopify reports, a 40% gap, making funnel data unreliable.

  • GA4 vs Shopify Revenue$1,468 vs $2,456 -40% divergence

Likely cause Purchase event likely blocked by a default-denied consent state or a broken GTM trigger; checking consent defaults vs server logs would distinguish them.

Do this — in order
  1. Audit GA4 purchase event firing
    Compare triggered events to confirmed Shopify orders to find where tracking drops
    ~2 h · analytics · Evolut (analytics)
  2. Check consent banner default state
    A default-denied consent state can silently block GA4 purchase events
    ~30 min · analytics · Evolut (analytics)
  3. Add server-side GA4 tagging via Conversions API
    Server-side capture avoids ad-blockers and consent gaps causing dropped events
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,468 vs Shopify revenue $2,456 (-40% divergence)tracking verdict RED
7
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue and funnel numbers can't be trusted for decision-making
All downstream funnel and CR figures are built on GA4 data that undercounts actual Shopify revenue by 43%, so prioritization is unreliable until fixed.
What's happening

GA4 captures only 57% of actual Shopify revenue, making every funnel and conversion number unreliable.

  • GA4 Revenue$1,742 vs Shopify $3,061
  • Shopify Revenue$3,061 source of truth

Likely cause Likely a broken or partially-blocked GA4 purchase tag on the confirmation page, or missing server-side event capture.

Do this — in order
  1. Audit GA4 purchase event firing on order confirmation
    Confirm the purchase event fires for every completed order, not a subset.
    ~2 h · analytics · Evolut (analytics)
  2. Add Shopify server-side conversions feed
    Reduces reliance on client-side tags blocked by ad blockers or consent tools.
    ~1 day · analytics · Evolut (analytics)
  3. Build a daily GA4 vs Shopify revenue reconciliation check
    Catches future divergence before funnel data is trusted again.
    ~2 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,742 vs Shopify revenue $3,061 (-43% divergence)tracking verdict RED
8
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue numbers can't be trusted for decision-making
Revenue reporting is unreliable, undermining every funnel decision until tracking is fixed.
What's happening

GA4 shows $1742 vs Shopify's ground-truth $3061 — a 43% gap signalling broken ecommerce tracking.

  • GA4 Revenue$1742 vs Shopify $3061
  • Shopify Revenue$3061 ground truth, 62 orders

Likely cause Likely a broken or duplicated GA4 purchase event, or consent-mode blocking; check transaction_id dedup vs confirmation-page firing.

Do this — in order
  1. Audit GA4 purchase event firing on order confirmation page
    Confirm it fires once per order with correct transaction_id to stop drops or double-counts.
    ~2 h · analytics · Evolut (analytics)
  2. Reconcile GA4 vs Shopify order counts daily for 7 days
    Pinpoints whether the gap comes from missing sessions, blockers, or dedup suppression.
    ~1 day · analytics · Evolut (analytics)
  3. Add Shopify-native or server-side GA4 tracking
    Reduces reliance on client-side script that can be blocked or delayed.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1742 vs Shopify revenue $3061 (-43% divergence)Tracking verdict: RED
9
Data-supportediSev 4 · blockeriInstrumentianalyticsi
You can't trust your revenue numbers — GA4 and Shopify disagree by 44%
GA4 reports $1,686 in revenue while Shopify shows $3,001, a 44% gap, so every funnel percentage below is unreliable until this is fixed.
What's happening

GA4 undercounts revenue by 44% vs Shopify ($1,686 vs $3,001), making all funnel metrics provisional.

  • GA4 vs Shopify Revenue-44% should be ~0%

Likely cause Likely a broken or duplicated GA4 purchase event, or consent-mode blocking the tag; check order-confirmation tag firing vs consent banner behavior.

Do this — in order
  1. Audit GA4 purchase event firing on order confirmation page
    Confirm it fires once per order and matches Shopify's 90 orders.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode/cookie banner for blocked tags
    consentRatePct is null — verify consent isn't suppressing purchase events.
    ~2 h · analytics · Evolut (analytics)
  3. Deduplicate GTM triggers firing the purchase tag
    Multiple containers/triggers can cause under- or over-counting.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,686 vs Shopify revenue $3,001 (-44% divergence)Tracking verdict: RED
10
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Finance and analytics disagree on revenue by 43%, so no funnel number here can be trusted yet
Tracking verdict is RED, which per policy must be the top fix before any funnel finding below is actioned.
What's happening

GA4 reports $1603 in revenue while Shopify's ledger shows $2820.04, a 43% undercount.

  • Shopify Revenue (source of truth)$2820.04 actual orders: 88
  • GA4 Revenue$1603 -43% vs Shopify

Likely cause Purchase event likely fails to fire on some checkout paths (e.g. Shop Pay/express checkout) or consent-mode is blocking pings; check null consent rate vs payment-method split to tell them apart.

Do this — in order
  1. Audit GA4 purchase event firing across all payment paths
    Confirm the event fires for Shop Pay, express wallets, and standard checkout equally.
    ~2 h · analytics · Evolut (analytics)
  2. Check GA4 consent mode configuration
    Null consentRatePct suggests consent signals may be unset, silently dropping purchase hits.
    ~2 h · analytics · Evolut (analytics)
  3. Reconcile GA4 vs Shopify order IDs for a sample week
    Pinpoint exactly which order types are missing from GA4 to confirm root cause.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1603 vs Shopify revenue $2820.04 (-43% divergence)tracking verdict: RED
11
TriangulatediSev 4 · blockeriInstrumentianalytics + behaviorali
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 12% vs 40–60% band$501/mo recoverable on desktop27 abandoned checkouts vs 88 total ordersdesktop dead clicks 210
12
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue numbers can't be trusted for decisions
A -39% revenue gap between GA4 and Shopify means every funnel and conversion number below is provisional until tracking is fixed.
What's happening

GA4 reports $1,355 vs Shopify's $2,208.37, a -39% gap that undermines all funnel analysis.

  • GA4 Revenue vs Shopify Revenue-39% expected ~0% divergence

Likely cause Likely a missing/broken GA4 purchase event (consent gating or tag misfire) versus lost attribution from ad-blockers; check server logs vs consent mode settings.

Do this — in order
  1. Audit GA4 purchase event firing
    Confirm the purchase event fires reliably on the order confirmation page for all traffic.
    ~2 h · analytics · Evolut (analytics)
  2. Add server-side tracking via Shopify app
    Reduce data loss from ad-blockers/consent by sending purchase events server-side.
    ~1 day · analytics · Evolut (analytics)
  3. Set weekly GA4-vs-Shopify revenue reconciliation
    Catch future divergence early before it skews decisions.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,355 vs Shopify revenue $2,208.37 (-39% divergence)tracking verdict: RED
13
Data-supportediSev 4 · blockeriInstrumentianalyticsi
You can't trust half your revenue data right now
Every funnel percentage and recommendation below is provisional until this gap is closed.
What's happening

GA4 shows $959 in revenue while Shopify shows $2,588.09 — a 63% gap that invalidates all funnel math.

  • GA4 Revenue$959 vs Shopify $2,588.09
  • Shopify Revenue$2,588.09 source of truth

Likely cause Likely a broken/duplicated GA4 purchase event or consent-mode blocking; compare GA4 event firing against the Shopify order webhook to isolate which.

Do this — in order
  1. Audit GA4 purchase event against Shopify order webhook
    Confirms whether GA4 is missing or double-counting transactions.
    ~2 h · analytics · Evolut (analytics)
  2. Verify gtag/GTM fires on order confirmation for all devices
    Mobile-only misfires are a common cause of large divergence.
    ~2 h · analytics · Evolut (analytics)
  3. Add server-side purchase tracking as backup feed
    Bypasses client-side/consent blocking if that's the root cause.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $959 vs Shopify revenue $2,588.09 (-63% divergence)Tracking verdict: RED
14
Data-supportediSev 4 · blockeriInstrumentianalyticsi
You're flying blind — reported revenue is off by over half, so every funnel number below is unreliable
A 58% revenue gap between GA4 and Shopify means the funnel data driving all other findings cannot be trusted until fixed.
What's happening

GA4 shows $900 in revenue vs Shopify's actual $2,128 — a 58% gap that invalidates downstream funnel conclusions.

  • GA4 Revenue vs Shopify Revenue$900 vs $2,128 -58% divergence

Likely cause Likely a broken or duplicated GA4 purchase event, or missing consent/server-side tagging; compare GA4 vs Shopify order counts to isolate.

Do this — in order
  1. Audit GA4 purchase event on order confirmation page
    Confirm it fires once per order with correct transaction_id and value.
    ~2 h · analytics · Evolut (analytics)
  2. Cross-check GA4 vs Shopify order counts, not just revenue
    Reveals whether the gap is missing orders or mismatched values.
    ~2 h · analytics · Evolut (analytics)
  3. Implement server-side tagging (Conversions API)
    Reduces client-side tracking loss from ad blockers and consent gaps.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $900 vs Shopify revenue $2,128 (-58% divergence)tracking verdict: RED
15
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue numbers can't be trusted for decision-making
A -51% revenue gap between GA4 and Shopify means every funnel percentage below is provisional until this is fixed; this must be resolved before trusting any CRO fix's impact.
What's happening

GA4 reports $763 in revenue vs Shopify's $1,565.18, a -51% gap that invalidates downstream funnel analysis.

  • GA4 vs Shopify Revenue-51% target ~0% divergence

Likely cause Likely a duplicated or missing purchase event, or consent-mode blocking a subset of GA4 tags before checkout completes.

Do this — in order
  1. Audit GA4 purchase event firing
    Confirm the purchase event fires exactly once per Shopify order, not zero or twice.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode banner defaults
    Verify the consent banner isn't blocking GA4 tags for a portion of shoppers pre-purchase.
    ~2 h · analytics · Evolut (analytics)
  3. Set up a daily GA4-vs-Shopify revenue diff alert
    Catch future tracking divergence before it distorts CRO decisions.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $763 vs Shopify revenue $1,565.18 (-51% divergence)tracking verdict: RED
16
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Reported revenue can't be trusted — GA4 and Shopify disagree by over a third
With a 36% revenue gap between GA4 and Shopify, every downstream funnel and revenue number in this report is provisional until measurement is fixed.
What's happening

GA4 shows 36% less revenue than Shopify ($713 vs $1121), so conversion data can't be trusted yet.

  • GA4 vs Shopify Revenue$713 vs $1121 -36% divergence

Likely cause Likely a broken or duplicated purchase event on the thank-you page, or consent-mode blocking GA4 before checkout completes.

Do this — in order
  1. Audit GA4 purchase event firing
    Confirm the purchase event fires exactly once per completed order.
    ~2 h · analytics · Evolut (analytics)
  2. Match GA4 DebugView order IDs to Shopify orders
    Find missing or duplicated events causing the gap.
    ~2 h · analytics · Evolut (analytics)
  3. Check consent banner and ad-blocker impact
    Verify consent mode isn't suppressing GA4 before purchase fires.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $713 vs Shopify revenue $1121 (-36% divergence)tracking verdict: red
17
Data-supportediSev 4 · blockeriInstrumentianalyticsi
You can't trust the revenue numbers driving decisions right now
With a 43% revenue gap between GA4 and Shopify, every funnel and CR number below is provisional until measurement is fixed.
What's happening

GA4 reports $1,074 in revenue vs Shopify's actual $1,868, a 43% undercount flagged RED.

  • GA4 vs Shopify Revenue-43% flagged RED, untrustworthy

Likely cause Likely the GA4 purchase event misfires on the order-confirmation page, or consent-mode blocking drops events without modeled fallback; DebugView will show which.

Do this — in order
  1. Audit GA4 purchase event firing in real time
    Use DebugView to confirm the purchase event fires on every completed Shopify order.
    ~2 h · analytics · Evolut (analytics)
  2. Reconcile GA4 transaction IDs against Shopify orders
    Match IDs to isolate whether events are missing, duplicated, or delayed.
    ~2 h · analytics · Evolut (analytics)
  3. Add server-side tracking as a fallback
    Reduces dependence on a client-side tag that can be blocked or delayed.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,074 vs Shopify revenue $1,868 (-43% divergence)Tracking verdict: RED
18
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Reported revenue is 43% off from actual, so every funnel number below is unreliable
A 43% revenue mismatch between GA4 and Shopify means every funnel percentage in this report is provisional until measurement is fixed.
What's happening

GA4 shows $1,141 in revenue while Shopify shows $2,005, a 43% gap that invalidates downstream funnel math.

  • GA4 vs Shopify revenue-43% should be near 0%

Likely cause Consent-mode default blocking the purchase event, or a broken/duplicated Shopify-GA4 integration; check consent defaults vs tag firing on order confirmation.

Do this — in order
  1. Audit GA4 purchase event firing
    Confirm the purchase event fires on the order confirmation page and isn't blocked by consent mode.
    ~2 h · analytics · Evolut (analytics)
  2. Verify Shopify-to-GA4 integration setup
    Check for a missing, duplicated, or misconfigured e-commerce pixel causing the revenue gap.
    ~2 h · analytics · Evolut (analytics)
  3. Reconcile consent banner default state
    Confirm analytics consent isn't defaulting to denied, which would suppress GA4 events.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,141 vs Shopify revenue $2,005 (-43% divergence)tracking verdict: RED
19
Data-supportediSev 4 · blockeriInstrumentianalyticsi
You can't trust your revenue numbers — GA4 and Shopify disagree by 27%
Tracking verdict is RED with GA4 undercounting revenue vs Shopify by $637 (27%), making all downstream funnel percentages unreliable until fixed.
What's happening

GA4 reports $1,759 in revenue vs Shopify's $2,396 — a 27% gap that invalidates funnel analysis.

  • GA4 vs Shopify Revenue-27% should be ~0% divergence

Likely cause Likely duplicate or missing purchase events, or a broken GA4-Shopify integration; check server-side vs client-side event firing and checkout redirect domains.

Do this — in order
  1. Audit GA4 purchase event against Shopify order webhook
    Compare order IDs to find missing or duplicated purchase events.
    ~2 h · analytics · Evolut (analytics)
  2. Verify GA4 purchase event fires once on thank-you page
    Duplicate firing on refresh or multi-domain checkout skews revenue.
    ~2 h · analytics · Evolut (analytics)
  3. Reconcile consent mode settings
    Null consent rate suggests Consent Mode may be blocking some purchase pings.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,759 vs Shopify revenue $2,396 (-27% divergence)tracking verdict: RED
20
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Analytics undercounts real revenue by 30%, making every funnel number unreliable
With GA4 undercounting revenue by 30% and a desktop step exceeding 100% retention, no downstream funnel finding can be trusted until measurement is fixed.
What's happening

GA4 shows $1,399 vs Shopify's $2,008 (-30%), and desktop Add to Cart→Checkout tracks at 107%, an impossible rate.

  • GA4 vs Shopify Revenue$1,399 vs $2,008 -30% divergence
  • Desktop Add to Cart → Begin Checkout107% impossible, max is 100%

Likely cause Likely duplicate begin_checkout/purchase tags firing in GTM, or consent-mode blocking causing GA4 to miss real purchases.

Do this — in order
  1. Audit GA4 event tags in GTM
    Check for duplicate begin_checkout/purchase triggers inflating or dropping counts.
    ~2 h · analytics · Evolut (analytics)
  2. Reconcile GA4 purchase events against Shopify orders
    Match order IDs to find missing or duplicated purchase events.
    ~2 h · analytics · Evolut (analytics)
  3. Switch to Shopify's native GA4 integration
    Reduces client-side/ad-blocker loss that likely drives the revenue gap.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,399 vs Shopify revenue $2,008 (-30% divergence)Desktop Add to Cart → Begin Checkout retention 107% (mathematically impossible)Tracking verdict: RED
21
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Reported revenue can't be trusted for decisions
A 31% gap between GA4 and Shopify revenue means every funnel percentage below is unreliable until measurement is fixed.
What's happening

GA4 shows $1,353 vs Shopify's $1,962 for the same 30 days, a 31% shortfall.

  • GA4 vs Shopify Revenue$1,353 vs $1,962 -31% divergence
  • Desktop Add to Cart → Begin Checkout107% impossible (>100%)

Likely cause Likely duplicate GA4 e-commerce events (e.g., begin_checkout firing twice) or consent-mode gaps blocking purchase hits; compare raw event counts to tell apart.

Do this — in order
  1. Audit GA4 e-commerce tags for duplicate firing
    Check begin_checkout/purchase tags in GTM preview mode
    ~2 h · analytics · Evolut (analytics)
  2. Reconcile GA4 purchase count vs Shopify order IDs
    Find missing or duplicated purchase events causing the gap
    ~2 h · analytics · Evolut (analytics)
  3. Add server-side or consent-mode fallback tagging
    Recovers data lost to consent-blocked browsers
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,353 vs Shopify revenue $1,962 (-31% divergence)Tracking verdict: RED
22
TriangulatediSev 4 · blockeriInstrumentianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Mobile Begin Checkout→Purchase retention 16% vs 40–60% bandRecoverable ~$1,573/mo on mobile32 abandoned checkouts vs 35 total orders sitewideMobile dead clicks: 288
23
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue numbers can't be trusted for decision-making
Measurement is broken; every funnel and revenue number below is provisional until this is fixed.
What's happening

GA4 shows $1271 in revenue while Shopify shows $2515, a 49% gap that invalidates downstream metrics.

  • GA4 vs Shopify Revenue-49% should be near 0%

Likely cause Likely a broken/duplicated GA4 purchase event, or consent-mode blocking tags given consentRatePct is null.

Do this — in order
  1. Audit GA4 purchase event firing
    Confirm it fires once per order and order IDs match Shopify.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent mode configuration
    Null consent rate suggests consent signals may be suppressing tags.
    ~2 h · analytics · Evolut (analytics)
  3. Reconcile GA4 with Shopify via native/server-side integration
    Close the gap using Shopify's GA4 app or server-side GTM.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1271 vs Shopify revenue $2515 (-49% divergence)tracking verdict: RED
24
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue numbers can't be trusted for decision-making
Revenue data disagrees by 51% between GA4 and Shopify, so every downstream funnel number is unreliable until tracking is fixed.
What's happening

GA4 captures only $1,271 of the $2,578 Shopify revenue recorded — a 51% shortfall.

  • GA4 Revenue vs Shopify Revenue$1,271 vs $2,578 -51% divergence, should be near 0%

Likely cause Likely missing/duplicated GA4 purchase events or consent-mode blocking tags; check consent default vs GTM firing order to distinguish.

Do this — in order
  1. Check consent-mode defaults blocking GA4 tags
    null consent rate suggests consent banner may suppress tracking
    ~30 min · analytics · Evolut (analytics)
  2. Audit GA4 purchase event firing on order confirmation
    confirm transaction_id dedupe and event fires once per order
    ~2 h · analytics · Evolut (analytics)
  3. Reconcile Shopify order webhook against GA4 nightly
    catch future divergence before it skews decisions
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Tracking verdict: REDGA4 revenue $1,271 vs Shopify revenue $2,578 (-51% divergence)
25
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue and funnel numbers can't be trusted for decision-making
GA4 shows $1,342 while Shopify shows $2,372.26 in actual revenue, a 43% gap — every funnel/CRO finding below is provisional until this is fixed.
What's happening

GA4 under-reports revenue by 43% versus Shopify's order data, making funnel analysis unreliable.

  • GA4 Revenue (30d)$1,342 vs Shopify $2,372.26
  • Shopify Revenue (30d)$2,372.26 source of truth from orders

Likely cause Likely missing GA4 purchase events from consent-mode blocking or a misfiring/duplicated purchase tag, rather than real revenue loss; compare order IDs to GA4 hits to tell which.

Do this — in order
  1. Turn on Shopify abandoned-checkout audit first
    Compare Shopify order IDs against GA4 purchase hits to quantify exactly which orders are missing.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent banner timing against tag firing
    consentRatePct is null, suggesting consent mode may be suppressing GA4 tags before purchase fires.
    ~2 h · analytics · Evolut (analytics)
  3. Verify purchase event only fires once per order
    Duplicate or missing pixel firing on the thank-you page is a common cause of this size of gap.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,342 vs Shopify revenue $2,372.26 over 30 days (-43% divergence)tracking verdict: RED
26
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue reports can't be trusted for any decision
Every funnel and revenue number downstream is unreliable until this gap is closed, so it must be fixed before acting on anything else.
What's happening

GA4 shows $1,342 in revenue while Shopify shows $2,415, a 44% gap that invalidates funnel analysis.

  • GA4 vs Shopify Revenue-44% should be near 0%

Likely cause Likely GA4 purchase event firing incompletely (ad-blockers/consent loss) or duplicate order counting; compare order IDs to confirm which.

Do this — in order
  1. Audit GA4 purchase event against Shopify orders
    Match order IDs to find missing or duplicate purchase events.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode settings before purchase fires
    Confirm the consent banner isn't blocking the GA4 tag on checkout completion.
    ~30 min · analytics · Evolut (analytics)
  3. Move to server-side GA4 tagging
    Reduces data loss from ad-blockers and browser tracking prevention.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,342 vs Shopify revenue $2,415 (-44% divergence)tracking verdict: RED
27
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue numbers can't be trusted for decision-making
A 39% gap between GA4 and Shopify revenue means every funnel percentage below is unverified until tracking is fixed.
What's happening

GA4 shows $1381 in revenue while Shopify shows $2263, a 39% undercount that invalidates downstream funnel math.

  • GA4 vs Shopify Revenue-39% should be near 0% divergence

Likely cause Purchase events are likely missing or blocked client-side (ad blockers, consent mode) rather than a Shopify order problem; compare server-side vs client-side event counts to confirm.

Do this — in order
  1. Audit GA4 purchase event firing on order confirmation
    Confirm it fires once per order and matches Shopify order IDs.
    ~2 h · analytics · Evolut (analytics)
  2. Reconcile daily GA4 vs Shopify revenue for 7 days
    Validates any fix before funnel percentages are trusted again.
    ~30 min · analytics · Evolut (analytics)
  3. Implement server-side GA4 tagging via Shopify app
    Reduces client-side blocking loss causing undercount.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1381 vs Shopify revenue $2263 (-39% divergence)Tracking verdict: RED
28
Data-supportediSev 4 · blockeriInstrumentianalyticsi
You can't trust the revenue numbers driving every decision here
A 40% gap between GA4 and Shopify revenue means every funnel percentage below is provisional until tracking is fixed.
What's happening

GA4 shows $1,381 in revenue while Shopify shows $2,308 — a 40% gap that invalidates downstream funnel math.

  • GA4 Revenue vs Shopify Revenue-40% should be within ~5% of each other

Likely cause Purchase events are likely missing or duplicated in GA4 (ad-blockers, consent mode, or broken confirmation-page tag) versus Shopify's native server-side order record.

Do this — in order
  1. Audit GA4 purchase event on the order confirmation page
    Confirm the tag fires reliably for every completed order
    ~2 h · analytics · Evolut (analytics)
  2. Cross-check GA4 transaction IDs against Shopify order IDs
    Pinpoints exactly which orders are missing from GA4
    ~2 h · analytics · Evolut (analytics)
  3. Set up server-side tracking via GA4 Measurement Protocol
    Removes reliance on client-side tags that ad-blockers can drop
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,381 vs Shopify revenue $2,308-40% divergence between platformstracking verdict: RED
29
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue numbers can't be trusted — GA4 is undercounting real sales by 41%
A 41% revenue gap between GA4 and Shopify means every funnel % below (view-to-cart, checkout-to-purchase) is unreliable until this is fixed.
What's happening

GA4 reports $1,524 in revenue while Shopify shows $2,564 actually paid — a 41% tracking gap.

  • GA4 Revenue vs Shopify Revenue-41% $1,524 vs $2,564

Likely cause Purchase event likely fails to fire on some orders (consent-mode blocking or thank-you page load issue) vs. duplicate/partial GA4 config; check consent logs and event firing rate.

Do this — in order
  1. Verify GA4 purchase event fires on every Shopify order confirmation
    Compare order IDs in Shopify to GA4 purchase hits to find the gap source
    ~2 h · analytics · Evolut (analytics)
  2. Check consent mode and cookie-banner settings blocking GA4
    consentRatePct is null, suggesting consent signals aren't being captured at all
    ~2 h · analytics · Evolut (analytics)
  3. Enable Shopify's native GA4 integration or server-side tagging
    Removes dependence on client-side script that can be blocked or dropped
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,524 vs Shopify revenue $2,564 (-41% divergence)tracking verdict: RED
30
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue reports can't be trusted for decisions
A 36% gap between GA4 and Shopify revenue means every funnel and CR number below is provisional until tracking is fixed.
What's happening

GA4 reports $1,698 in revenue vs Shopify's actual $2,634, a 36% shortfall.

  • GA4 Revenue vs Shopify Revenue$1,698 vs $2,634 -36% divergence

Likely cause Purchase events are likely blocked by consent-mode gating or failing to fire on the thank-you page; check both client-side tag firing and consent state.

Do this — in order
  1. Audit GA4 purchase event firing on order confirmation page
    Confirms whether the event tag fires reliably for every completed order.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent banner for blocking tracking scripts
    Consent-mode defaults can silently suppress GA4 events pre-consent.
    ~2 h · analytics · Evolut (analytics)
  3. Implement server-side event tracking as backup
    Captures purchases missed by client-side tags due to ad-blockers or script errors.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,698 vs Shopify revenue $2,634 (-36% divergence)tracking verdict RED
31
TriangulatediSev 4 · blockeriInstrumentianalytics + behaviorali
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout → Purchase retention 18% vs 40–60% bandDesktop recoverable ~290 orders/month29 abandoned checkouts vs 54 total Shopify ordersDesktop dead clicks: 180 (Clarity)
32
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue and funnel numbers can't be trusted for decisions
A 39% gap between GA4 and Shopify revenue means every funnel percentage below is provisional until tracking is fixed.
What's happening

GA4 reports $1,686 vs Shopify's actual $2,772, a 39% undercount that invalidates downstream funnel reads.

  • GA4 Revenue vs Shopify Revenue-39% should be within 10%

Likely cause Likely GA4 purchase events are lost client-side (ad-blockers/Safari ITP) or firing inconsistently; check if server-side tagging would close the gap vs a tag-config error.

Do this — in order
  1. Audit GA4 purchase event on the order confirmation page
    Confirm the purchase tag fires every time, not just on some browsers.
    ~2 h · analytics · Evolut (analytics)
  2. Install Shopify's native GA4 integration or server-side tagging
    Reduces client-side event loss from ad-blockers and ITP.
    ~1 day · analytics · Evolut (analytics)
  3. Reconcile GA4 vs Shopify revenue weekly until gap is under 10%
    Catches future tracking drift before it skews decisions.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,686 vs Shopify revenue $2,772 (-39% divergence)tracking verdict: RED
33
TriangulatediSev 4 · blockeriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
This is the steepest below-band leak in the whole funnel and mobile carries the larger session volume (3,478 vs 2,350).
What's happening

Mobile product pages convert to cart at only 3%, well under the 5–10% band, losing an estimated $1,484/month.

  • Session → View Product81% above 20–45% band
  • View Product → Add to Cart3% vs 5–10% band
  • Add to Cart → Begin Checkout53% vs 40–60% band
  • Begin Checkout → Purchase42% vs 40–60% band, borderline

Likely cause Likely weak on-page persuasion (price/reviews/CTA visibility) or a hard-to-reach Add-to-Cart button; 269 mobile dead clicks suggest shoppers tapping non-functional elements. Figures are provisional given RED tracking.

Do this — in order
  1. Add a sticky Add-to-Cart bar on mobile PDP
    Keeps the CTA visible given average scroll depth is only 23%.
    ~2 h · theme edit · Evolut (LP)
  2. Review mobile dead-click recordings in Clarity
    Find which of the 269 dead-click elements shoppers expect to work.
    ~2 h · analytics · Evolut (LP)
  3. Surface reviews/trust badges above the fold on mobile PDP
    Builds confidence before the scroll cutoff shoppers rarely pass.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View→Add to Cart retention 3% vs 5–10% bandRecoverable ~$1,484/monthMobile dead clicks 269, avg scroll depth 23%
34
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue and funnel numbers can't be trusted for decisions
Shopify revenue is 38% higher than GA4, making every downstream funnel and revenue metric unreliable until tracking is fixed.
What's happening

GA4 shows $1,365 vs Shopify's $2,213 in actual revenue, a 38% gap that invalidates funnel analysis.

  • GA4 Revenue$1,365 vs Shopify $2,213
  • Shopify Revenue$2,213 source of truth, 83 orders
  • Divergence-38% GA4 under-reporting vs Shopify

Likely cause GA4 purchase event is misfiring or blocked (consent/tag issue), or some orders complete outside GA4-tracked sessions; compare tag firing logs vs order source.

Do this — in order
  1. Audit GA4 purchase event firing against Shopify orders
    Confirms whether events are missing, duplicated, or blocked on completion.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent mode and tag triggers in GTM
    Null consent rate suggests consent banner may be suppressing GA4 hits.
    ~1 day · analytics · Evolut (analytics)
  3. Reconcile GA4 vs Shopify order IDs weekly
    Catches future drift early before it skews CRO decisions again.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,365 vs Shopify revenue $2,213GA4 vs Shopify revenue: -38%tracking verdict RED
35
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Your reported revenue is nearly half-wrong, so every other number here is suspect
Tracking is RED: GA4 revenue ($1,425) diverges -42% from Shopify revenue ($2,472), so no downstream funnel number can be trusted until fixed.
What's happening

GA4 revenue ($1,425) is 42% below Shopify revenue ($2,472), meaning funnel numbers below cannot be trusted yet.

  • GA4 vs Shopify Revenue-42% $1,425 vs $2,472

Likely cause Likely missing or mis-firing GA4 purchase events, or a broken Shopify-GA4 integration; check tag firing on the order confirmation page to distinguish.

Do this — in order
  1. Audit GA4 purchase event firing
    Verify the GA4 purchase tag fires correctly on the order confirmation page for every completed order.
    ~2 h · analytics · Evolut (analytics)
  2. Reconcile GA4 vs Shopify order counts
    Compare daily order IDs between platforms to pinpoint where revenue is lost in tracking.
    ~2 h · analytics · Evolut (analytics)
  3. Fix or reinstall GA4 Shopify integration
    Reinstall the official GA4/Shopify app or correct GTM container settings.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,425 vs Shopify revenue $2,472 (-42% divergence)tracking verdict: RED
36
Data-supportediSev 4 · blockeriInstrumentianalyticsi
You can't trust your reported revenue numbers to make decisions
GA4 is undercounting revenue by 42% relative to Shopify ($1,442 vs $2,489), making every funnel and conversion figure below this point provisional until fixed.
What's happening

GA4 shows $1,442 revenue vs Shopify's $2,489 — a 42% gap signals broken purchase tracking.

  • GA4 Revenue$1,442 vs Shopify $2,489
  • Revenue Divergence-42% tracking verdict RED

Likely cause Likely a GA4 purchase-event or consent-mode misconfiguration vs a missing/duplicated conversion tag; check consent banner firing vs raw tag presence to distinguish.

Do this — in order
  1. Audit GA4 purchase events against Shopify order webhook
    Compare per-order event counts to pinpoint where GA4 drops transactions.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode or cookie banner blocking the GA4 tag
    Null consentRatePct suggests consent signal isn't even being captured.
    ~2 h · analytics · Evolut (analytics)
  3. Implement server-side GA4 purchase tracking via Shopify webhook
    Removes reliance on client-side tag firing, closing the gap long-term.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,442 vs Shopify revenue $2,489 (-42% divergence)Tracking verdict: RED
37
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue numbers can't be trusted for decision-making
A -42% gap between GA4 and Shopify revenue means every downstream funnel and revenue metric is unreliable until tracking is fixed.
What's happening

GA4 shows $1,355 vs Shopify's $2,323 in actual revenue, a 42% shortfall in reported sales.

  • GA4 Revenue$1,355 vs Shopify $2,323
  • Shopify Revenue$2,323 source of truth

Likely cause Likely a broken or missing purchase event/consent gate in GA4, or a checkout redirect losing UTM/session data; check consent mode vs event firing to distinguish.

Do this — in order
  1. Audit GA4 purchase event firing
    Confirm the purchase event fires on the order-confirmation page for all sessions, not just consented ones.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent banner impact on tagging
    consentRatePct is null, suggesting consent mode may be blocking event collection entirely.
    ~2 h · analytics · Evolut (analytics)
  3. Reconcile GA4 vs Shopify order IDs
    Match a sample of orders to find exactly where events drop out of GA4.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
tracking verdict REDGA4 revenue $1,355 vs Shopify revenue $2,323GA4 vs Shopify revenue: -42%
38
Data-supportediSev 4 · blockeriInstrumentianalyticsi
You can't trust what your funnel data is telling you
A 49% revenue gap between GA4 and Shopify means every funnel percentage below is unreliable until tracking is fixed.
What's happening

GA4 shows $1,327 in revenue vs Shopify's actual $2,623, a 49% gap.

  • GA4 vs Shopify Revenue-49% GA4 $1,327 vs Shopify $2,623

Likely cause Likely missing/duplicate GA4 purchase events or consent-blocked tracking; compare order IDs vs check consent mode logs to isolate.

Do this — in order
  1. Audit GA4 purchase event firing
    Verify the purchase event fires exactly once per Shopify order via GTM preview.
    ~2 h · analytics · Evolut (analytics)
  2. Reconcile order IDs between GA4 and Shopify
    Match order IDs to find missing or duplicated purchase events causing the gap.
    ~2 h · analytics · Evolut (analytics)
  3. Implement server-side conversion tracking
    Send purchase events server-side to cut loss from ad-blockers/consent mode.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,327 vs Shopify revenue $2,623 (-49% divergence)tracking verdict RED
39
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue reports don't agree, so every conversion number here is unreliable
With a 38% revenue gap between GA4 and Shopify, every funnel and CR figure below must be treated as provisional until measurement is fixed.
What's happening

GA4 shows $664 vs Shopify's $1,072.08 in actual revenue, a 38% shortfall that invalidates downstream funnel math.

  • GA4 vs Shopify revenue-38% should be ~0% divergence
  • Consent rate capturenull unknown / not captured

Likely cause Either GA4's purchase event isn't firing on all order types, or a consent-mode/cookie banner is blocking tags before they send; compare tag-fire logs against Shopify order timestamps to tell which.

Do this — in order
  1. Audit GA4 purchase event firing on the order confirmation page
    Confirm the e-commerce purchase event fires for every order type, including express-checkout.
    ~2 h · analytics · Evolut (analytics)
  2. Check whether the cookie/consent banner blocks GA4 tags
    consentRatePct is null, suggesting tags may never fire for some visitors.
    ~2 h · analytics · Evolut (analytics)
  3. Reconcile GTM container events against Shopify checkout extensibility scripts
    Look for duplicate or missing event triggers causing the gap.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $664 vs Shopify revenue $1,072.08 (-38% divergence)tracking verdict: RED
40
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue and orders can't be trusted for decision-making right now
Tracking verdict is RED with a 41% revenue gap between GA4 and Shopify, so every downstream funnel number in this snapshot is provisional until fixed.
What's happening

GA4 reports $757 in revenue while Shopify shows $1293 — a 41% gap that undermines every funnel metric.

  • GA4 Revenue vs Shopify Revenue$757 vs $1293 -41% divergence
  • Consent Ratenot captured null value

Likely cause The purchase/conversion event likely under-fires due to a broken tag or unconfigured consent mode; confirm by comparing GA4 DebugView hits to Shopify order timestamps.

Do this — in order
  1. Audit GA4 purchase event firing on the order confirmation page
    Confirm the event fires once per order and the count matches Shopify's order total.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent mode and tag-blocking on checkout
    Null consent rate suggests the consent banner may be blocking GA4 tags before purchase.
    ~2 h · analytics · Evolut (analytics)
  3. Set up a weekly GA4-vs-Shopify revenue reconciliation check
    Catch future tracking drift before it skews CRO decisions.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $757 vs Shopify revenue $1293 (-41% divergence)tracking verdict: RED
41
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue reports don't match Shopify, so every funnel number is unreliable
A -33% GA4/Shopify divergence means downstream funnel conclusions (especially checkout-to-purchase) are provisional until measurement is fixed.
What's happening

GA4 undercounts revenue by 33% versus Shopify, making all downstream funnel figures unreliable.

  • GA4 vs Shopify Revenue$976 vs $1467 -33% divergence
  • Shopify orders vs abandoned checkouts18 orders / 23 abandoned ~44% real completion rate
  • Mobile Checkout → Purchase (GA4)15% vs 40–60% band
  • Desktop Checkout → Purchase (GA4)5% vs 40–60% band
Do this — in order
  1. Audit GA4 purchase event firing
    Compare GA4 order IDs against Shopify orders to find missing conversions.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode/cookie banner blocking
    consentRatePct is null — verify the banner isn't suppressing purchase pings.
    ~2 h · analytics · Evolut (analytics)
  3. Re-validate thank-you page purchase tag
    Ensure GTM/GA4 fires reliably on the order confirmation page.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $976 vs Shopify revenue $1467 (-33% divergence)Tracking verdict: REDShopify shows 18 orders and 23 abandoned checkouts (~44% real completion), inconsistent with the 5-15% checkout-to-purchase retention reported in the funnel
42
TriangulatediSev 4 · blockeriInstrumentianalytics + behaviorali
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 9% vs 40–60% band$391/month recoverable revenue on desktop23 abandoned checkouts vs only 20 total orders storewideDesktop Clarity: 165 rage clicks, 721 dead clicks, avg scroll only 37%Tracking verdict RED — treat exact percentages as provisional
43
Data-supportediSev 4 · blockeriInstrumentianalyticsi
You can't trust the revenue or conversion numbers you're looking at
Every downstream funnel and revenue number in this snapshot is provisional until this gap is closed — optimizing on broken data risks wasted effort.
What's happening

GA4 shows $1,035 in revenue vs Shopify's actual $1,685 — a 39% shortfall pointing to broken measurement.

  • GA4 Revenue vs Shopify Revenue-39% should track within a few % of each other

Likely cause Likely GA4's purchase event isn't firing for every order, or value/currency mapping is wrong; compare GA4 vs Shopify order counts to tell which.

Do this — in order
  1. Compare GA4 order count to Shopify order count
    Fastest way to tell if events are missing vs values being wrong.
    ~30 min · analytics · Evolut (analytics)
  2. Audit GA4 purchase event on order confirmation page
    Confirm it fires once per order with correct value/currency.
    ~2 h · analytics · Evolut (analytics)
  3. Move to server-side or native Shopify GA4 integration
    Cuts client-side tracking loss from ad-blockers and script issues.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,035 vs Shopify revenue $1,685 in the same 30 days (-39% divergence)Tracking verdict: RED
44
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Dashboard revenue can't be trusted for decisions
A 47% gap between GA4 and Shopify revenue means every funnel and CR number below is provisional until tracking is fixed.
What's happening

GA4 reports $946 in revenue while Shopify shows $1,779, a 47% shortfall pointing to broken measurement.

  • GA4 vs Shopify revenue$946 vs $1,779 -47% divergence
  • Consent rate trackingnull not configured

Likely cause Purchase event misfiring or consent-mode blocking client-side tags; comparing server-side Shopify webhook events to GA4 DebugView would isolate which.

Do this — in order
  1. Audit GA4 purchase event firing
    Confirm the purchase tag fires on every order confirmation page.
    ~2 h · analytics · Evolut (analytics)
  2. Reconcile GA4 transaction IDs against Shopify orders
    Pinpoint exactly which orders GA4 is missing.
    ~1 day · analytics · Evolut (analytics)
  3. Implement consent mode logging
    Capture consent state per session to explain revenue variance.
    ~2 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $946 vs Shopify revenue $1,779 (-47% divergence)
45
TriangulatediSev 4 · blockeriInstrumentianalytics + behaviorali
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
desktop Begin Checkout→Purchase retention 10% vs 40–60% band$1,543/mo recoverable on desktopdesktop sitewide CR 0.20% vs 1.5–3.5% banddesktop rage clicks 169 and dead clicks 762 (Clarity)18 abandoned checkouts sitewide vs 21 completed orders
46
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Every dollar figure in the dashboard is unreliable, making it risky to invest in any fix
With a -27% revenue gap between GA4 and Shopify and an impossible 104% cart-to-checkout rate on desktop, none of the funnel percentages below can be trusted until tracking is fixed.
What's happening

GA4 undercounts revenue by 27% vs Shopify and shows an impossible 104% desktop cart-to-checkout rate.

  • GA4 vs Shopify Revenue$1,587 vs $2,163 -27% divergence
  • Desktop Add to Cart → Begin Checkout104% impossible, vs 40–60% band

Likely cause Likely duplicate or missing GA4 event fires (e.g. begin_checkout firing without a matching add_to_cart, or purchase deduplication failure); confirm by comparing GTM trigger counts to Shopify order/session logs.

Do this — in order
  1. Audit GTM tags for add_to_cart, begin_checkout, purchase events
    Check for duplicate or missing fires causing the 104% and -27% anomalies.
    ~2 h · analytics · Evolut (analytics)
  2. Reconcile GA4 purchase count against Shopify order count
    Confirms whether purchase events are deduplicated correctly per order.
    ~2 h · analytics · Evolut (analytics)
  3. Enable Shopify's native GA4/server-side integration
    Reduces client-side event loss driving the revenue gap.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,587 vs Shopify revenue $2,163 (-27% divergence)Tracking verdict: REDDesktop Add to Cart → Begin Checkout retention is 104% (impossible, band 40–60%)
47
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase 15% vs 40–60% band$1,188/month recoverable revenue on desktop13 abandoned checkouts vs 27 total ordersDesktop Add to Cart→Begin Checkout 96% (implausibly high, suspect)
48
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue reports can't be trusted—GA4 and Shopify disagree by 30%
All funnel and revenue conclusions below are provisional until this measurement gap is closed.
What's happening

GA4 shows $1,702 in revenue while Shopify shows $2,427, a 30% gap that invalidates funnel conclusions.

  • GA4 vs Shopify Revenue-30% should be ~0% divergence

Likely cause Likely GA4 purchase event misfiring or consent-mode blocking causing missed transactions; check DebugView vs order IDs to confirm which.

Do this — in order
  1. Compare GA4 and Shopify order IDs for gaps
    Pinpoint whether events are missing, duplicated, or delayed.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent banner isn't blocking purchase pings
    Null consent rate suggests CMP may be dropping events.
    ~30 min · analytics · Evolut (analytics)
  3. Deploy server-side Shopify-to-GA4 forwarding
    Fills gaps lost to ad blockers or client-side script failures.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,702 vs Shopify revenue $2,427 (-30% divergence)tracking verdict: RED
49
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue and funnel numbers can't be trusted right now
Every downstream funnel finding is provisional until this 44% revenue gap between GA4 and Shopify is closed.
What's happening

GA4 reports $1,205 while Shopify shows $2,171 in revenue, a 44% gap that invalidates funnel math.

  • GA4 vs Shopify Revenue-44% should be within ~5%

Likely cause Likely missing/duplicate purchase events or unconfigured consent mode blocking tags; compare raw GA4 event counts vs Shopify order IDs to distinguish.

Do this — in order
  1. Audit purchase event firing on order confirmation page
    Confirm it fires exactly once per order and matches Shopify order IDs.
    ~2 h · analytics · Evolut (analytics)
  2. Configure and verify consent mode settings
    consentRatePct is null, meaning consent tracking isn't set up and may be dropping events.
    ~2 h · analytics · Evolut (analytics)
  3. Reconcile GA4 vs Shopify orders daily for two weeks
    Build an order-ID match report to confirm the fix before trusting funnel data.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,205 vs Shopify revenue $2,171 (-44% divergence)tracking verdict: RED
50
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue and funnel numbers can't be trusted for decisions
With a -35% GA4/Shopify revenue gap and a mathematically impossible 108% desktop cart-to-checkout rate, every downstream funnel finding is provisional until tracking is fixed.
What's happening

GA4 shows $1,904 vs Shopify's $2,927 (-35%), and desktop cart→checkout hits 108%—measurement is broken.

  • GA4 Revenue vs Shopify Revenue-35% GA4 $1,904 vs Shopify $2,927
  • Desktop Add to Cart → Begin Checkout108% impossible, vs 40–60% band

Likely cause Duplicated or missing add_to_cart/purchase tags (double-fired GTM triggers vs ad-blocker event loss) are skewing both revenue and funnel ratios.

Do this — in order
  1. Audit GA4 tags with GTM preview mode
    Check for duplicate or missing add_to_cart/purchase triggers causing the 108% and revenue gap.
    ~2 h · analytics · Evolut (analytics)
  2. Reconcile GA4 vs Shopify orders by ID
    Match individual orders to isolate exactly which events are lost or duplicated.
    ~2 h · analytics · Evolut (analytics)
  3. Implement server-side or Enhanced Conversions tagging
    Reduces client-side event loss from ad blockers and browser privacy limits.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,904 vs Shopify revenue $2,927 (-35% divergence)Desktop Add to Cart→Begin Checkout retention 108% (impossible, vs 40–60% band)Tracking verdict: RED
51
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Mobile Begin Checkout → Purchase retention 16% vs 40–60% bandRecoverable ≈$1,565/month on mobile32 abandoned checkouts vs 36 total orders sitewide (Shopify)
52
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue and funnel numbers can't be trusted right now
A 51% gap between GA4 and Shopify revenue means every conversion rate and funnel percentage in this snapshot is unreliable until tagging is fixed.
What's happening

GA4 shows $1,271 in revenue while Shopify shows $2,578.07, a 51% shortfall that invalidates downstream funnel math.

  • GA4 Revenue vs Shopify Revenue$1,271 vs $2,578 -51% divergence

Likely cause Likely a missing/duplicated GA4 purchase event or a consent-mode gap dropping conversions; compare GA4 order IDs against Shopify orders to tell them apart.

Do this — in order
  1. Reconcile GA4 purchase events against Shopify order IDs
    Find exactly which orders aren't firing or are double-counted in GA4
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode and purchase-event deduplication settings
    Consent gaps or duplicate client/server events are the most common cause of this gap size
    ~1 day · analytics · Evolut (analytics)
  3. Implement server-side purchase tracking via Shopify webhook
    Removes reliance on client-side JS that can fail or be blocked
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,271 vs Shopify revenue $2,578.07 (-51% divergence)Tracking verdict: RED
53
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue reporting can't be trusted—GA4 shows 43% less revenue than Shopify actually made
Tracking is flagged RED with a 43% revenue gap between GA4 and Shopify, so every funnel number below is provisional until this is fixed.
What's happening

GA4 reports $1,271 vs Shopify's $2,220 in actual revenue, a 43% shortfall in tracked sales.

  • GA4 Revenue$1,271 last 30 days
  • Shopify Revenue$2,220 last 30 days, source of truth
  • Divergence-43% GA4 under-reports vs Shopify

Likely cause GA4's purchase event likely misfires or is blocked by missing consent mode, versus duplicate/offline orders in Shopify; check consent banner default and event timing.

Do this — in order
  1. Verify GA4 purchase event fires on order confirmation
    Event may not trigger due to redirect timing or tag misconfiguration
    ~2 h · analytics · Evolut (analytics)
  2. Check consent mode banner default state
    Null consent rate suggests consent mode isn't configured, blocking GA4 data
    ~2 h · analytics · Evolut (analytics)
  3. Reconcile 30-day order list between GA4 and Shopify
    Pinpoint exact missing or duplicate transactions causing the gap
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,271 vs Shopify revenue $2,220 (-43% divergence)tracking verdict: RED
54
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue numbers can't be trusted for decision-making
A 43% revenue gap between GA4 and Shopify means every funnel and revenue figure below is provisional until tracking is fixed.
What's happening

GA4 reports $1,468 while Shopify reports $2,589.16 in the same 30 days, a 43% gap.

  • GA4 Revenue$1,468 vs Shopify $2,589.16
  • Shopify Revenue$2,589.16 source of truth (orders)

Likely cause Likely a missing/duplicated purchase event or consent-gated tag firing inconsistently; check GA4 purchase event dedupe vs Shopify order webhook timing.

Do this — in order
  1. Audit GA4 purchase event firing
    Confirm purchase event fires once per order and isn't blocked by consent mode or client-side errors
    ~2 h · analytics · Evolut (analytics)
  2. Cross-check order IDs GA4 vs Shopify
    Pull a day-level order ID match to isolate where events are lost or duplicated
    ~2 h · analytics · Evolut (analytics)
  3. Add server-side or GA4 e-commerce via Shopify app
    Reduce reliance on client-side tags prone to ad-blockers and script failures
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,468 vs Shopify revenue $2,589.16 (-43% divergence)tracking verdict: RED
55
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue numbers can't be trusted — GA4 and Shopify disagree by 43%
All downstream funnel and revenue findings are provisional until this is fixed; no CRO decision should be made on unreliable data.
What's happening

GA4 shows $1,496 in revenue while Shopify shows $2,643 — a 43% gap pointing to broken tracking.

  • GA4 Revenue vs Shopify Revenue-43% should be near 0% divergence

Likely cause Likely GA4 purchase events are under-firing from consent blocking, or duplicate/missing triggers in tag setup; check consent logs vs GTM trigger config.

Do this — in order
  1. Audit GA4 purchase event count vs Shopify orders
    Confirm every completed order fires exactly one GA4 purchase event.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent mode suppressing GA4 tags
    Blocked consent can hide purchases from GA4 while Shopify still records the sale.
    ~2 h · analytics · Evolut (analytics)
  3. Review GTM triggers for duplicate/conditional firing
    Misconfigured triggers can double count or drop purchase events.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,496 vs Shopify revenue $2,643 (-43% divergence)tracking verdict: RED
56
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue reporting is unreliable—GA4 undercounts sales by 41%
Shopify and GA4 disagree by 41% ($2,962 vs $1,742); until this is fixed, every downstream funnel metric here is provisional and decisions based on it are risky.
What's happening

GA4 shows $1,742 in revenue while Shopify shows $2,962, a 41% gap that invalidates funnel conclusions.

  • GA4 vs Shopify Revenue-41% GA4 $1,742 vs Shopify $2,962

Likely cause Likely a missing or duplicated GA4 purchase event, or broken consent mode; distinguish by comparing GA4 event counts to session counts in DebugView.

Do this — in order
  1. Audit GA4 purchase event firing
    41% revenue gap suggests duplicate or missing purchase events in GA4
    ~1 day · analytics · Evolut (analytics)
  2. Verify consent mode and pixel placement
    Null consent rate suggests GA4 isn't capturing accepted-consent sessions
    ~2 h · analytics · Evolut (analytics)
  3. Reconcile GA4 vs Shopify revenue weekly
    Catch future divergence before trusting any funnel number
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,742 vs Shopify revenue $2,962 (-41% divergence)tracking verdict: RED
57
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout → Purchase retention 17% vs 40-60% bandRecoverable revenue estimated $1,203/month27 abandoned checkouts vs 90 completed ordersTracking verdict RED — treat as provisional
58
Data-supportediSev 4 · blockeriInstrumentianalyticsi
You can't trust your revenue numbers — GA4 is undercounting by 41%
All downstream funnel percentages are built on this broken measurement, so every other finding is provisional until this is fixed.
What's happening

GA4 reports $1,603 in revenue while Shopify shows $2,700, a 41% gap that makes every funnel rate unreliable.

  • GA4 Revenue$1,603 vs Shopify $2,700.37
  • Revenue Divergence-41% acceptable range is ±10%

Likely cause Likely a broken or duplicated GA4 purchase event, or consent-mode blocking; compare order counts (not just revenue) to tell which.

Do this — in order
  1. Audit GA4 purchase event firing on order confirmation
    Confirm it fires once per order and matches Shopify order IDs.
    ~2 h · analytics · Evolut (analytics)
  2. Compare GA4 vs Shopify order counts directly
    Isolates whether the gap is missing events or wrong values.
    ~2 h · analytics · Evolut (analytics)
  3. Move to server-side or native Shopify GA4 integration
    Cuts client-side tracking loss from ad blockers and consent gaps.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,603 vs Shopify revenue $2,700.37 (-41% divergence)Tracking verdict: RED
59
Data-supportediSev 4 · blockeriInstrumentianalyticsi
You can't trust your revenue numbers right now
GA4 under-reports revenue by 36% versus Shopify's own ledger, meaning every funnel percentage in this snapshot is provisional until the measurement gap is closed.
What's happening

GA4 shows $1,566 in revenue while Shopify shows $2,459 — a 36% tracking gap.

  • GA4 Revenue vs Shopify Revenue$1,566 vs $2,459 -36% divergence

Likely cause Likely a GA4 purchase-event or consent-mode gap dropping orders, or a tag firing issue on the confirmation page; compare order IDs to tell which.

Do this — in order
  1. Audit GA4 purchase events against Shopify order IDs
    Pinpoint exactly which orders GA4 is missing or double-counting.
    ~2 h · analytics · Evolut (analytics)
  2. Verify consent-mode defaults aren't blocking the purchase tag
    A default-denied consent state silently drops GA4 purchase events.
    ~30 min · analytics · Evolut (analytics)
  3. Add Shopify webhook-based conversion tracking
    Server-side order data isn't affected by browser/ad-blocker issues.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,566 vs Shopify revenue $2,459 (-36% divergence)Tracking verdict: RED
60
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue reporting is off by over 40%, so no funnel decision can be trusted yet
A 43% revenue gap between GA4 and Shopify means every downstream funnel and CR number below is provisional until tracking is fixed.
What's happening

GA4 shows $1,365 in revenue while Shopify shows $2,390, a 43% under-count.

  • GA4 Revenue vs Shopify Revenue-43% GA4 under-reports actual sales

Likely cause Purchase events likely fail to fire for some sessions, or consent-mode blocking drops GA4 tags before checkout completes.

Do this — in order
  1. Audit GA4 purchase event firing
    Confirm the ecommerce purchase event fires on the order confirmation page across devices.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent banner impact on tagging
    Verify the consent banner isn't blocking GA4 tags before purchase completes.
    ~2 h · analytics · Evolut (analytics)
  3. Reconcile GA4 with Shopify via server-side tracking
    Add Shopify's GA4 app or a server-side Conversions API to close the gap.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,365 vs Shopify revenue $2,390 (-43% divergence)Tracking verdict: RED
61
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Nearly 40% of reported revenue may not exist — tracking can't be trusted
Every funnel and revenue number below is built on this data, so it must be fixed before any CRO spend is justified by current numbers.
What's happening

GA4 reports 39% less revenue than Shopify ($1,365 vs $2,252), making every downstream funnel metric unreliable.

  • GA4 vs Shopify Revenue-39% should be near 0% divergence

Likely cause Likely missing GA4 purchase events from unconfigured consent mode or duplicate/misfiring GTM tags; check consent wiring vs tag firing to distinguish.

Do this — in order
  1. Audit GA4 purchase event firing in GTM
    Confirm it fires once per order and matches Shopify order IDs.
    ~2 h · analytics · Evolut (analytics)
  2. Implement Google consent mode v2
    Null consent rate suggests consent signals aren't reaching GA4, undercounting revenue.
    ~1 day · analytics · Evolut (analytics)
  3. Set up a weekly GA4 vs Shopify reconciliation check
    Catch divergence early before decisions are made on bad data.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,365 vs Shopify revenue $2,252 (-39% divergence)tracking verdict: RED
62
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Nearly half of your reported revenue may not be real — tracking is broken
Every downstream funnel and revenue number is unreliable until this is fixed, so no optimization can be trusted.
What's happening

GA4 shows $1,552 vs Shopify's $2,691 in revenue this month, a 42% gap flagged RED.

  • GA4 vs Shopify Revenue-42% should be ~0%

Likely cause Missing/duplicated GA4 purchase events, or consent-mode blocking tags before they fire; compare event counts vs Shopify webhooks to isolate which.

Do this — in order
  1. Audit GA4 purchase event firing on order confirmation
    Compare dataLayer triggers vs Shopify order data to find dropped or duplicated events.
    ~2 h · analytics · Evolut (analytics)
  2. Verify consent banner isn't blocking GA4 tags
    Null consent rate suggests consent mode may be stripping hits before they're recorded.
    ~2 h · analytics · Evolut (analytics)
  3. Add server-side GA4 tagging via Shopify webhooks
    Removes reliance on client-side JS that can fail, be blocked, or double-fire.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,552 vs Shopify revenue $2,691 (-42% divergence)tracking verdict RED
63
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue reporting can't be trusted — GA4 is missing roughly $1,051 in sales each month
Tracking verdict is RED; all downstream funnel conclusions are provisional until this is fixed
What's happening

GA4 reports $1,481 in sales while Shopify shows $2,532, a 41% gap, making funnel numbers unreliable.

  • GA4 vs Shopify Revenue-41% should be within ~5%

Likely cause Likely GA4 purchase event firing inconsistently or consent-mode blocking hits; distinguish via GA4 DebugView vs consent banner logs.

Do this — in order
  1. Audit GA4 purchase event firing
    Confirm the purchase event fires reliably on every order confirmation page.
    ~2 h · analytics · Evolut (analytics)
  2. Implement consent mode defaults
    Missing consent signals may be silently dropping hits on both devices.
    ~2 h · analytics · Evolut (analytics)
  3. Cross-check Shopify order count vs GA4 purchase events
    Validate server-side counts match Shopify's 84 orders to locate the gap.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,481 vs Shopify revenue $2,532 (-41% divergence)
64
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue and conversion numbers can't be trusted for decision-making
A 46% revenue gap between GA4 and Shopify means every funnel percentage downstream is provisional until events are fixed; optimizing on broken data risks wasted effort.
What's happening

GA4 shows $1,442 in revenue vs Shopify's $2,649, a 46% shortfall, meaning purchase events are being lost.

  • GA4 vs Shopify Revenue-46% should be ~0%
  • Desktop Add to Cart → Begin Checkout91% vs 40–60%

Likely cause Likely missing/duplicated GA4 purchase events or consent-mode blocking; confirm by matching order IDs between GA4 and Shopify.

Do this — in order
  1. Audit GA4 purchase event against Shopify order IDs
    Find exactly which orders are missing or duplicated in GA4.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent banner impact on GA4 tag firing
    consentRatePct is null, suggesting the tag may be blocked for many visitors.
    ~2 h · analytics · Evolut (analytics)
  3. Fire purchase event server-side from Thank You page
    Reduces client-side event loss that likely causes the 46% gap.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,442 vs Shopify revenue $2,649 (-46% divergence)Tracking verdict: RED
65
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase 11% vs 40–60% band$623/mo recoverable revenuedesktop sessions 2,24223 abandoned checkouts sitewideRefunds: $123.15
66
TriangulatediSev 4 · blockeriInstrumentianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Mobile Begin Checkout→Purchase retention 14% vs 40–60% band$378/month recoverable revenue on mobile5,182 mobile sessions vs 2,248 desktop — mobile is the dominant traffic sourceMobile Clarity: 24 rage clicks, 301 dead clicks, avg scroll only 21%Tracking verdict RED — treat exact percentages as provisional
67
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Mobile Begin Checkout→Purchase retention 13% vs band 40-60%Desktop Begin Checkout→Purchase retention 9% vs band 40-60%23 abandoned checkouts vs 19 completed ordersRecoverable ~$287/mo mobile + $303/mo desktop (~$590/mo combined)Tracking verdict RED — magnitude provisional
68
Data-supportediSev 4 · blockeriInstrumentianalyticsi
You can't trust the revenue numbers guiding every decision
GA4 and Shopify revenue diverge by 26% ($1,162 vs $1,567), meaning every downstream funnel and revenue metric is unreliable until tracking is fixed.
What's happening

GA4 shows $1,162 while Shopify shows $1,567 for the same 30 days, a 26% gap.

  • GA4 Revenue$1,162 reported by analytics
  • Shopify Revenue$1,567 actual orders (18)
  • Divergence-26% exceeds trustworthy threshold

Likely cause Likely a broken or duplicated GA4 purchase event versus a consent/ad-blocker issue suppressing hits; comparing event payloads to blocked-request logs would distinguish them.

Do this — in order
  1. Audit the GA4 purchase event payload
    Confirm value, currency and transaction_id match Shopify order totals for every order.
    ~2 h · analytics · Evolut (analytics)
  2. Check for duplicate or blocked GA4 triggers
    Verify the purchase event fires exactly once and isn't blocked by consent mode.
    ~2 h · analytics · Evolut (analytics)
  3. Reconcile Shopify order webhook against GA4 hits
    Spot-check 10 recent orders line-by-line between the two systems.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
-26% divergence between GA4 revenue $1,162 and Shopify revenue $1,567tracking verdict RED
69
TriangulatediSev 4 · blockeriInstrumentianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
mobile Begin Checkout→Purchase retention 16% vs 40–60% band$1,454/mo recoverable on mobilemobile sitewide CR 0.15% vs 1.5–3.5% bandmobile dead clicks 331 and rage clicks 35 (Clarity)mobile avg scroll depth 20%
70
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Every revenue and conversion number in this report may be wrong
A 34% revenue gap between GA4 and Shopify means funnel percentages used to prioritize everything else are unreliable until tracking is fixed.
What's happening

GA4 reports $1131 vs Shopify's real $1726, a 34% shortfall, so downstream funnel math is provisional.

  • GA4 vs Shopify Revenue-34% target <5% divergence
  • Consent Rate Capturenull expected a %

Likely cause Likely missing GA4 purchase events from unconsented sessions or ad-blockers, vs a tagging bug double-firing/missing on checkout; check consent-mode logs first.

Do this — in order
  1. Audit GA4 purchase event firing vs Shopify orders
    Match order IDs/timestamps to find exactly which purchases GA4 misses
    ~2 h · analytics · Evolut (analytics)
  2. Implement Consent Mode v2 with default state
    Null consent rate suggests the banner isn't reporting to GA4, silently dropping revenue
    ~2 h · analytics · Evolut (analytics)
  3. Move to server-side GTM tagging
    Cuts ad-blocker and consent-related event loss that likely causes the 34% gap
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1131 vs Shopify revenue $1726 (-34% divergence)tracking verdict: red
71
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue numbers can't be trusted for decision-making
Tracking is RED, so every downstream funnel and revenue number is unreliable until this is fixed.
What's happening

GA4 undercounts revenue by 34% vs Shopify ($1,131 vs $1,708), making all funnel metrics unreliable.

  • GA4 vs Shopify Revenue$1,131 vs $1,708 -34% divergence

Likely cause Likely a purchase event that fails to fire on some orders or is blocked by consent mode; compare per-order GA4 vs Shopify logs to isolate which.

Do this — in order
  1. Audit GA4 purchase event firing
    Confirm the purchase event fires on every completed order to match Shopify's order count.
    ~2 h · analytics · Evolut (analytics)
  2. Compare GA4 vs Shopify order counts daily
    Pinpoint exact days/orders where GA4 misses events to isolate the cause.
    ~2 h · analytics · Evolut (analytics)
  3. Validate consent mode configuration
    Check whether the consent banner blocks GA4 tags for a subset of sessions.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,131 vs Shopify revenue $1,708 (-34% divergence)Tracking verdict: RED
72
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout → Purchase retention 9% (band 40-60%)Desktop Add to Cart → Begin Checkout is 96% (suspect, band 40-60%)17 abandoned checkouts vs 23 total orders (Shopify)Tracking verdict RED - treat as provisional
73
Data-supportediSev 4 · blockeriInstrumentianalyticsi
You can't trust the revenue numbers driving every decision
A -26% GA4/Shopify divergence means every funnel and revenue number below is unreliable until tracking is fixed; this must be resolved before acting on other findings.
What's happening

GA4 shows $1,502 vs Shopify's actual $2,039 in 30 days, a 26% gap that invalidates funnel analysis.

  • GA4 Revenue (30d)$1,502 vs Shopify $2,039
  • Revenue Divergence-26% acceptable threshold ~±10%

Likely cause Likely GA4 purchase events under-firing (consent-mode gating or broken checkout tag) or duplicate/missing events; DebugView vs order webhook comparison will distinguish.

Do this — in order
  1. Compare GA4 DebugView purchase events against Shopify order IDs
    Pinpoints whether events are missing, duplicated, or delayed.
    ~2 h · analytics · Evolut (analytics)
  2. Audit consent banner and consent-mode configuration
    consentRatePct is null, suggesting consent signals aren't being captured or passed to GA4.
    ~2 h · analytics · Evolut (analytics)
  3. Implement server-side purchase tracking via GA4/Shopify app
    Removes reliance on client-side JS that can be blocked or fail silently.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,502 vs Shopify revenue $2,039 (-26% divergence)tracking verdict: RED
74
TriangulatediSev 4 · blockeriInstrumentianalytics + behaviorali
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 10% vs 40–60% band$599/month recoverable revenue on desktop17 abandoned checkouts vs 24 total ordersDesktop rage clicks 98, dead clicks 455 (Clarity)Tracking verdict RED — treat as provisional
75
Data-supportediSev 4 · blockeriInstrumentianalyticsi
You can't trust revenue numbers to make decisions right now
A 29% revenue gap between GA4 and Shopify means every downstream funnel and revenue figure is unreliable until fixed.
What's happening

GA4 reports $1,694 vs Shopify's actual $2,370 in revenue — a 29% gap signals broken measurement.

  • GA4 vs Shopify revenue-29% should be near 0%

Likely cause Likely duplicate or missing GA4 purchase events, or consent-mode defaults blocking tags before load; check both.

Do this — in order
  1. Audit GA4 purchase event firing on order confirmation
    Confirm the event fires once per order and isn't blocked by consent defaults
    ~2 h · analytics · Evolut (analytics)
  2. Compare GA4 vs Shopify order counts day-by-day
    Pinpoint exact dates or pages where GA4 events drop to isolate the tag issue
    ~2 h · analytics · Evolut (analytics)
  3. Implement server-side GA4 tracking via Shopify
    Removes reliance on a client-side tag that can be blocked or delayed
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,694 vs Shopify revenue $2,370 (-29% divergence)tracking verdict RED
76
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue and funnel numbers can't be trusted for decision-making
Tracking verdict is RED with a -30% revenue divergence, so measurement must be fixed before any funnel finding can be trusted.
What's happening

GA4 undercounts revenue by 30% vs Shopify and shows an impossible 100% desktop cart-to-checkout rate.

  • GA4 vs Shopify Revenue$1655 vs $2370 -30% divergence
  • Desktop Add to Cart → Begin Checkout100% vs 40-60% band
  • Shopify Checkout Completion67% (26/39) vs GA4 12-26%

Likely cause Duplicate or missing GA4 begin_checkout/purchase tags, possibly from a consent-mode gap; confirm by comparing GA4 DebugView events to Shopify's checkout_completed webhook.

Do this — in order
  1. Audit GA4 purchase and begin_checkout tags
    Confirm each fires exactly once and isn't blocked by consent mode.
    ~2 h · analytics · Evolut (analytics)
  2. Reconcile GA4 with Shopify orders daily
    Set up a recurring report to catch revenue drift early.
    ~30 min · analytics · Evolut (analytics)
  3. Walk a live test order in GA4 DebugView
    Pinpoint exactly where GA4 events diverge from the real checkout.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1655 vs Shopify revenue $2370 (-30% divergence)Desktop Add to Cart→Begin Checkout retention recorded at 100% vs 40-60% bandShopify shows 26 orders and 13 abandoned checkouts (67% completion) vs GA4 funnel showing 12-26% checkout→purchase
77
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 17% vs 40–60% banddesktop recoverablePerMonth $79413 abandoned checkouts vs 28 total orders
78
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue and order data can't be trusted for decisions
A 37% revenue gap between GA4 and Shopify means every funnel and CRO number below is provisional until fixed.
What's happening

GA4 reports $1,315 in revenue while Shopify shows $2,087, a 37% gap that invalidates funnel analysis.

  • GA4 revenue vs Shopify revenue$1,315 vs $2,087 -37% divergence

Likely cause Likely GA4 purchase event misfiring/duplicating or a consent-mode gap dropping events; compare GA4 DebugView events against Shopify order webhooks to isolate.

Do this — in order
  1. Audit GA4 purchase event firing in DebugView
    Check for duplicate or missing purchase events against real orders
    ~2 h · analytics · Evolut (analytics)
  2. Verify consent mode and tag firing rules
    Consent gating can silently drop a chunk of purchase events
    ~2 h · analytics · Evolut (analytics)
  3. Cross-check GA4 order IDs vs Shopify order IDs
    Identify exactly which orders are missing or duplicated in GA4
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,315 vs Shopify revenue $2,087.21 (-37% divergence)Tracking verdict: REDShopify orders 26, refunds $0
79
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue and conversion reports can't be trusted for decisions
Tracking verdict is RED; every downstream funnel number is provisional until measurement is fixed.
What's happening

GA4 shows $1,205 in revenue vs Shopify's $2,257, a 47% gap, meaning purchase tracking is broken.

  • GA4 vs Shopify Revenue-47% should be near 0%
  • Desktop Add to Cart → Begin Checkout116% vs 40–60%, physically impossible

Likely cause Duplicate or missing GA4 add_to_cart/purchase events (double-fired tags or blocked consent) inflate retention and undercount revenue; check tag firing vs consent mode.

Do this — in order
  1. Audit GTM tags for duplicate purchase/ATC events
    Duplicate fires would explain desktop retention exceeding 100% and revenue mismatch.
    ~2 h · analytics · Evolut (analytics)
  2. Verify GA4 consent mode is configured correctly
    Blocked consent signals can undercount GA4 revenue versus Shopify.
    ~2 h · analytics · Evolut (analytics)
  3. Reconcile GA4 DebugView events against Shopify orders
    Confirms exactly where events are lost or duplicated.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,205 vs Shopify revenue $2,257 (-47% divergence)Desktop Add to Cart → Begin Checkout retention 116% (impossible, exceeds 100%)
80
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue and funnel numbers can't be trusted for decision-making
With GA4 undercounting revenue by 41% and desktop showing checkout events exceeding cart adds, every funnel percentage below is provisional until measurement is fixed.
What's happening

GA4 shows $1205 vs Shopify's $2048 (-41%), and desktop checkout events exceed add-to-carts, proving broken tracking.

  • GA4 vs Shopify Revenue$1205 vs $2048 -41% divergence
  • Desktop Add to Cart → Begin Checkout116% vs 40–60% (impossible)

Likely cause Duplicate begin_checkout/purchase event firing, or consent-mode blocking purchase pixels before conversion — check GTM preview vs. consent logs.

Do this — in order
  1. Audit GA4 e-commerce tags for duplicate firing
    Use GTM preview mode to check add_to_cart/begin_checkout firing twice per action.
    ~2 h · analytics · Evolut (analytics)
  2. Reconcile GA4 purchase event against Shopify order webhook
    Confirm purchase fires exactly once per completed order.
    ~2 h · analytics · Evolut (analytics)
  3. Check consent-mode gating on purchase pixel
    Verify the purchase tag isn't blocked before conversion completes.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Tracking verdict RED-41% revenue divergence: GA4 $1205 vs Shopify $2048Desktop Add to Cart→Begin Checkout retention 116% (impossible vs 40–60% band)
81
Data-supportediSev 4 · blockeriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
This is the steepest below-band leak in the whole funnel and mobile carries the majority of traffic (provisional pending tracking fix).
What's happening

Only 3% of mobile product-page viewers add to cart, well under the 5–10% band.

  • Session → View Product83% vs 20–45%
  • View Product → Add to Cart3% vs 5–10%
  • Add to Cart → Begin Checkout39% vs 40–60%

Likely cause Likely a weak or buried add-to-cart CTA on the mobile PDP, or slow mobile load suppressing intent; check page speed vs CTA placement to distinguish.

Do this — in order
  1. Move Add to Cart button above the fold on mobile PDP
    With 3,071 mobile sessions and only 3% adding to cart, the CTA likely needs no scrolling to reach.
    ~2 h · theme edit · Evolut (LP)
  2. Add trust badges and clear price near the CTA
    Reduce hesitation at the decision point to lift add-to-cart rate.
    ~2 h · copy · Evolut (LP)
  3. Run a mobile PDP page-speed audit
    Slow load times commonly suppress mobile add-to-cart; rule this out before further redesign.
    ~2 h · analytics · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product → Add to Cart retention 3% vs 5–10% bandRecoverable ≈$904/moMobile sessions: 3,071
82
Data-supportediSev 4 · blockeriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
This is the furthest-below-band leak in the funnel and mobile drives the most traffic (3,126 sessions/mo), making it the single biggest revenue opportunity.
What's happening

Mobile View→Add to Cart converts at only 3%, well under the 5–10% band floor.

  • Session → View Product83% vs 20–45% band
  • View Product → Add to Cart3% vs 5–10% band
  • Add to Cart → Checkout42% vs 40–60% band
  • Checkout → Purchase41% vs 40–60% band

Likely cause Mobile PDP CTA is likely hard to see/tap or the page is slow to become interactive; check load speed vs CTA placement to distinguish.

Do this — in order
  1. Add a sticky add-to-cart bar on mobile PDPs
    Keeps the CTA visible while scrolling, cutting drop-off before add-to-cart.
    ~2 h · theme edit · Evolut (LP)
  2. Audit mobile PDP load and interactivity speed
    Slow time-to-interactive can silently kill add-to-cart taps.
    ~2 h · analytics · Evolut (LP)
  3. Move price and CTA above the fold on mobile PDP
    Reduces scroll friction between viewing and adding to cart.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View→Add to Cart retention 3% vs 5–10% band floorMobile sessions: 3,126/moRecoverable revenue ~$1,238/moMobile sitewide CR 0.38% vs 1.5–3.5% band
83
Data-supportediSev 4 · blockeriInstrumentianalyticsi
You can't trust the revenue numbers driving every other decision
A 42% revenue gap between GA4 and Shopify means all funnel and revenue figures below are provisional until tracking is fixed.
What's happening

GA4 reports $1,468 in revenue vs Shopify's actual $2,543 — a 42% gap that invalidates funnel analysis.

  • GA4 vs Shopify Revenue-42% should be within ~5%

Likely cause Likely a broken or duplicated GA4 purchase event, or consent-mode blocking tags before purchase completes on part of traffic.

Do this — in order
  1. Audit GA4 purchase event firing
    Confirm the event fires once per order and matches Shopify order IDs.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent banner and ad-blocker impact
    Verify consent mode isn't suppressing GA4 tags before purchase fires.
    ~2 h · analytics · Evolut (analytics)
  3. Implement Shopify server-side GA4 tagging
    Capture events lost to client-side blocking and reconcile with Shopify.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,468 vs Shopify revenue $2,543 (-42% divergence)tracking verdict: RED
84
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue numbers can't be trusted for any decision right now
A 22% gap between GA4 and Shopify revenue means every funnel and revenue number below is provisional until measurement is fixed.
What's happening

GA4 reports $1,643 vs Shopify's $2,094 in revenue, a 22% gap flagged RED.

  • GA4 Revenue vs Shopify Revenue-22% exceeds trustworthy divergence threshold

Likely cause Likely a missing/duplicated GA4 purchase event or consent-blocking on checkout; compare order IDs between GA4 and Shopify to isolate which.

Do this — in order
  1. Audit GA4 purchase event on the thank-you page
    Confirm it fires exactly once per order and matches Shopify order IDs.
    ~2 h · analytics · Evolut (analytics)
  2. Compare daily GA4 vs Shopify order counts for a week
    Reveals whether the gap is a flat % or spikes by day/device.
    ~2 h · analytics · Evolut (analytics)
  3. Check consent mode setup on checkout pages
    Null consentRatePct suggests consent signals may not be firing at all.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,643 vs Shopify revenue $2,094 (-22% divergence)Tracking verdict: RED
85
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue numbers can't be trusted, so every other metric here is provisional
A 41% gap between GA4 and Shopify revenue means the funnel and CR numbers below cannot be trusted until measurement is fixed.
What's happening

GA4 reports $1,758 vs Shopify's $2,985 in actual revenue, a 41% shortfall.

  • GA4 vs Shopify Revenue-41% should be ~0%

Likely cause Likely a GA4 purchase event firing incompletely (consent mode gap or lost transactions) vs Shopify's server-recorded orders; check consent banner wiring vs duplicate/missing transaction IDs.

Do this — in order
  1. Audit GA4 purchase event on order confirmation
    Confirm it fires once per order with correct transaction_id and value.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent mode banner is feeding GA4 correctly
    Null consent rate suggests consent signals aren't reaching GA4.
    ~2 h · analytics · Evolut (analytics)
  3. Implement server-side tracking (GTM server/Conversions API)
    Reduces client-side loss from ad blockers and consent gaps.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,758 vs Shopify revenue $2,985 (-41% divergence)Tracking verdict: RED
86
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order$345/mo at stake
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 18% vs 40–60% bandRecoverable: $345/moShopify abandoned checkouts 30tracking verdict RED (figures provisional)
87
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase 17% vs 40–60% band$629/month recoverable revenue on desktop26 abandoned checkouts out of 88 total orderstracking verdict RED (desktop figures provisional)
88
TriangulatediSev 4 · blockeriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
This is the single largest leak in the funnel and the step furthest below its band; numbers are provisional pending the tracking fix above.
What's happening

Mobile View→Add to Cart is 3%, under the 5–10% band, losing an estimated $1,121/month.

  • Session → View Product81% vs 20–45% band
  • View Product → Add to Cart3% vs 5–10% band
  • Add to Cart → Checkout55% vs 40–60% band
  • Checkout → Purchase40% at 40–60% band floor

Likely cause 270 mobile dead clicks suggest unresponsive PDP buttons, or shoppers (23% avg scroll) never reach trust/CTA content lower on the page.

Do this — in order
  1. Add a sticky mobile Add-to-Cart bar with price
    Keeps the buy button reachable since most shoppers scroll only 23% of the page.
    ~2 h · theme edit · Evolut (LP)
  2. Fix unresponsive PDP buttons causing dead clicks
    270 mobile dead clicks indicate elements shoppers tap aren't responding.
    ~2 h · theme edit · Evolut (LP)
  3. Move key value props and CTA above the fold
    Low scroll depth means content below the fold is rarely seen.
    ~1 day · copy · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View→Add to Cart retention 3% vs 5–10% bandRecoverable ~$1,121/month on this stepMobile sessions: 3,492Mobile dead clicks: 270, rage clicks: 17Mobile avg scroll depth: 23%
89
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 11% vs 40–60% bandRecoverable ~$761/month29 abandoned checkouts (Shopify, 30 days)Desktop sessions: 2,366
90
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue and funnel numbers can't be trusted for decision-making
A 43% revenue gap between GA4 and Shopify means every funnel percentage downstream may be wrong; this must be fixed before acting on other findings.
What's happening

GA4 shows $1,365 in revenue while Shopify shows $2,390 for the same 30 days, a 43% gap.

  • GA4 Revenue vs Shopify Revenue$1,365 vs $2,390 -43% divergence

Likely cause Likely missing or duplicated purchase events, or consent-mode tag blocking (consentRatePct is null); order-ID reconciliation will tell which.

Do this — in order
  1. Audit GA4 purchase event firing
    Confirm the purchase event fires exactly once per Shopify order on the thank-you page.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent mode tag suppression
    consentRatePct is null — verify Consent Mode isn't blocking conversion tags for most visitors.
    ~2 h · analytics · Evolut (analytics)
  3. Reconcile GA4 vs Shopify order IDs
    Match order IDs day-by-day over 30 days to isolate exactly which events are missed.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,365 vs Shopify revenue $2,390 (-43% divergence)tracking verdict: RED
91
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 10% vs band 40–60%Recoverable ~$389/moDesktop Add to Cart→Begin Checkout 91% (vs 40–60% band)Shopify refunds $84.15 on $2,648.52 revenuecheckoutEditable: false
92
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout → Purchase retention 10% vs 40–60% bandDesktop recoverable ≈$782/monthShopify: 26 abandoned checkouts vs 79 total ordersDesktop Add to Cart → Begin Checkout at 87% (data provisional given RED tracking)
93
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Your analytics can't be trusted to guide decisions right now
Every funnel percentage below depends on this data being accurate; a 42% revenue gap means current numbers are not reliable enough to act on with full confidence.
What's happening

GA4 shows $1,442 in revenue while Shopify shows $2,489 — a 42% gap signals broken purchase tracking.

  • GA4 Revenue vs Shopify Revenue-42% tracking verdict RED

Likely cause Likely the GA4 purchase event fails to fire on some checkouts (e.g. SPA/Shop Pay redirects) or consent blocking drops events; compare missing order IDs to tell which.

Do this — in order
  1. Audit GA4 purchase event firing in GTM preview
    Confirm the ecommerce purchase tag fires on every completed order, not just some.
    ~2 h · analytics · Evolut (analytics)
  2. Reconcile GA4 order IDs against Shopify's order list
    Identify exactly which orders are missing from GA4 to isolate the broken trigger.
    ~2 h · analytics · Evolut (analytics)
  3. Implement Shopify-native or server-side GA4 integration
    Reduces event loss from ad blockers, consent gating, or client-side script failures.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,442 vs Shopify revenue $2,489 (-42% divergence)tracking verdict RED
94
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue and funnel numbers can't be trusted for decision-making
With a 39% revenue gap between GA4 and Shopify, every funnel percentage below is unreliable until tracking is fixed; this must be resolved before acting on other findings.
What's happening

GA4 shows $1,355 vs Shopify's $2,208 in revenue, a 39% gap that makes every funnel number unreliable.

  • GA4 Revenue vs Shopify Revenue-39% should be within ~5%
  • Consent Rate Trackingnull not measured

Likely cause Purchase events likely fail to fire or are blocked (consent mode/ad-blockers) rather than a real order mismatch; check GA4 DebugView on the confirmation page vs Shopify's order log.

Do this — in order
  1. Audit GA4 purchase event firing on order confirmation page
    Confirm the purchase tag fires reliably against Shopify's 74 real orders.
    ~2 h · analytics · Evolut (analytics)
  2. Deploy server-side tracking via GA4 Measurement Protocol
    Captures orders missed by blocked client-side pixels, closing the revenue gap.
    ~1 day · analytics · Evolut (analytics)
  3. Instrument consent-rate reporting
    consentRatePct is null; measure it to see if consent banners suppress tags.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,355 vs Shopify revenue $2,208 (-39% divergence)tracking verdict: RED
95
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue numbers can't be trusted for any decision right now
A 39% revenue gap between GA4 and Shopify means every downstream funnel percentage is provisional until measurement is fixed.
What's happening

GA4 reports $1,355 in revenue while Shopify shows $2,208, a 39% gap flagged RED.

  • GA4 Revenue$1,355 vs Shopify $2,208
  • Shopify Revenue$2,208 source of truth

Likely cause Likely a broken or duplicated GA4 purchase event, or missing consent-mode signals; distinguish by checking dataLayer purchase firing vs consent banner logs.

Do this — in order
  1. Audit GA4 purchase event for duplication or drop-off
    Compare event firing on order-confirmation page against Shopify order count
    ~2 h · analytics · Evolut (analytics)
  2. Verify Shopify-to-GA4 integration/consent mode setup
    Null consent rate suggests consent signals may be blocking tracking
    ~1 day · analytics · Evolut (analytics)
  3. Reconcile revenue weekly until variance is under 5%
    Prevents decisions being made on unreliable funnel data
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,355 vs Shopify revenue $2,208 (-39% divergence)tracking verdict: RED
96
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
desktop Begin Checkout→Purchase retention 12% vs 40–60% bandrecoverable $404/monthdesktop sitewide CR 0.22% vs 1.5–3.5% band22 abandoned checkouts$123.15 in refunds
97
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 12% vs 40–60% band$1,469/month recoverable revenue23 abandoned checkoutstracking verdict RED — figures provisional
98
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 10% vs 40–60% band$1,035/month recoverable on desktop25 abandoned checkouts vs 67 completed orderstracking verdict RED — treat as provisional
99
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Mobile Begin Checkout→Purchase retention 19% vs 40–60% band$725/month recoverable on mobilemobile sessions 4,737tracking verdict RED — treat as provisional
100
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 9% vs 40–60% bandRecoverable ~$595/monthAdd to Cart→Begin Checkout retention 83% (above 40–60% band)Tracking verdict RED (-51% divergence) — treat as provisional
101
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue reporting is unreliable, hiding the true funnel picture
All downstream funnel and revenue numbers are unverifiable until tracking is fixed, risking wrong prioritization of every other fix.
What's happening

GA4 reports $713 in revenue while Shopify shows $1,121 — a 36% gap signaling broken measurement.

  • GA4 vs Shopify Revenue$713 vs $1,121 -36% divergence

Likely cause Purchase events likely blocked by consent-mode gating or a broken GA4 tag on the order-confirmation page; check consent defaults vs tag firing.

Do this — in order
  1. Audit GA4 purchase event firing on confirmation page
    Confirm the event fires for 100% of completed Shopify orders via debug mode.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent banner blocking Analytics pre-purchase
    If consent defaults to denied, purchases from those sessions never reach GA4.
    ~2 h · analytics · Evolut (analytics)
  3. Install Shopify's server-side Conversions API app
    Server-side pass-through avoids client-side blocking losses.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $713 vs Shopify revenue $1,121.38 (-36% divergence)tracking verdict RED
102
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
mobile Begin Checkout→Purchase 16% vs 40-60% band (recoverable $555/mo)desktop Begin Checkout→Purchase 7% vs 40-60% band (recoverable $613/mo)21 abandoned checkouts vs 45 orders
103
TriangulatediSev 4 · blockeriInstrumentianalytics + behaviorali
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Checkout→Purchase retention 5% vs 40–60% band871/mo recoverable — the largest single leak on the siteTracking RED, so real completion may be closer to Shopify's ~44% (18 orders/23 abandoned checkouts)
104
Data-supportediSev 4 · blockeriInstrumentianalyticsi
You can't trust your own revenue numbers to guide any decision
A 37% revenue gap between GA4 and Shopify means every funnel percentage below is unreliable until this is fixed; per policy this must be the top item.
What's happening

GA4 shows $1,073 vs Shopify's $1,695 — a 37% gap that invalidates every downstream funnel number.

  • GA4 vs Shopify Revenue$1,073 vs $1,695 -37% divergence
  • Consent Rate Trackingnull not configured

Likely cause Likely a missing/duplicated GA4 purchase event or a consent-mode gap blocking the tag on some checkouts; check tag firing rate vs completed Shopify orders to tell which.

Do this — in order
  1. Audit GA4 purchase event firing on every completed order.
    Confirms whether the tag fires on all completions or only some, explaining the gap.
    ~2 h · analytics · Evolut (analytics)
  2. Add consent-mode logging to measure opt-out rate.
    Null consent rate hides how much traffic GA4 never measures at all.
    ~2 h · analytics · Evolut (analytics)
  3. Implement Shopify-native or server-side purchase event.
    Removes reliance on client-side tags broken by ad-blockers or consent denial.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,073 vs Shopify revenue $1,695 (-37% divergence)tracking verdict: RED
105
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue numbers can't be trusted, so every other finding here is provisional
A -34% revenue gap between GA4 and Shopify means the funnel numbers driving every other decision are unreliable until this is fixed.
What's happening

GA4 shows $1,073 in revenue while Shopify shows $1,639, a 34% gap that undermines all funnel analysis.

  • GA4 vs Shopify Revenue-34% should be near 0%
  • Consent rate signalnull unknown/missing

Likely cause Likely a missing or duplicated purchase event in GA4, or consent-mode blocking the tag before it fires; check GTM debug vs consent banner timing.

Do this — in order
  1. Cross-check consent-mode configuration
    Verify the consent banner isn't blocking conversion pings before GA4 loads.
    ~30 min · analytics · Evolut (analytics)
  2. Audit GA4 purchase event firing
    Use GTM preview to confirm purchase fires exactly once per Shopify order.
    ~2 h · analytics · Evolut (analytics)
  3. Add a server-side purchase backup event
    Send Shopify webhook order data to GA4 via Measurement Protocol as a fallback.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,073 vs Shopify revenue $1,639 (-34% divergence)tracking verdict: RED
106
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Mobile Begin Checkout→Purchase retention 13% vs 40–60% band (leak, ~$1,195/mo recoverable)Desktop Begin Checkout→Purchase retention 9% vs 40–60% band (leak, ~$1,222/mo recoverable)Shopify: 19 orders vs 22 abandoned checkouts in 30 days$39 in refundsTracking verdict RED — treat these rates as provisional until fixed
107
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Reported revenue is off by nearly half, so every funnel number below is unreliable
A 42% gap between GA4 and Shopify revenue means conversion and funnel percentages cannot be trusted for decisions until measurement is fixed.
What's happening

GA4 shows $992 in revenue while Shopify shows $1717 for the same 30 days, a 42% gap.

  • GA4 revenue vs Shopify revenue$992 vs $1717 -42% divergence

Likely cause GA4 purchase event is likely firing incompletely (consent-mode blocking or client-side tag failing before order confirmation loads) rather than actual lost sales; compare Shopify order timestamps against GA4 purchase event hits to confirm.

Do this — in order
  1. Audit GA4 purchase event firing on order confirmation page
    Confirm the event fires for every completed order, not just some sessions
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode settings for analytics blocking
    Consent banners can suppress purchase events before GA4 ever receives them
    ~2 h · analytics · Evolut (analytics)
  3. Add server-side purchase tracking via Shopify webhook to GA4
    Removes reliance on client-side JS that may fail after payment
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
tracking verdict REDGA4 revenue $992 vs Shopify revenue $1717 (-42% divergence)
108
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Mobile Checkout→Purchase 16% vs 40-60% band, recoverable $652/monthDesktop Checkout→Purchase 10% vs 40-60% band, recoverable $710/monthShopify: 20 abandoned checkouts vs only 21 completed orders in 30 days
109
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Reported revenue is unreliable, making every funnel number suspect
Analytics and the order platform disagree by 31%, so every funnel percentage below is provisional until this is fixed.
What's happening

GA4 shows $1,162 in revenue while Shopify shows $1,678, a 31% gap that invalidates funnel math.

  • GA4 vs Shopify Revenue-31% should be ~0%

Likely cause Likely a broken or duplicated GA4 purchase event, or consent-mode gating suppressing some conversions; compare tag firing against consent logs to tell apart.

Do this — in order
  1. Audit GA4 purchase event firing per order
    Match GA4 purchase hits to Shopify order IDs to find missing or duplicate fires.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode impact on purchase tracking
    consentRatePct is null; confirm the cookie banner isn't blocking the purchase pixel.
    ~2 h · analytics · Evolut (analytics)
  3. Reconcile GA4 vs Shopify revenue daily for 7 days
    Confirms the fix closes the 31% gap before trusting funnel %s.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,162 vs Shopify revenue $1,678 (-31% divergence)tracking verdict: RED
110
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout → Purchase retention 10% vs band 40–60%desktop sitewide CR 0.18% vs band 1.5–3.5%18 abandoned checkouts vs 20 total orders storewiderecoverable ≈$690/month
111
TriangulatediSev 4 · blockeriInstrumentianalytics + behaviorali
Reported revenue can't be trusted — GA4 and Shopify disagree by 28%
With a 28% gap between GA4 ($1,162) and Shopify ($1,606) revenue and Clarity reporting 0 sessions despite real click data, every funnel% below is unverified.
What's happening

GA4 undercounts revenue by 28% vs Shopify ($1,162 vs $1,606), so downstream funnel numbers are unreliable.

  • GA4 Revenue$1,162 vs Shopify $1,606
  • Shopify Revenue$1,606 source of truth (orders ledger)
  • Clarity session count0 despite 210 rage clicks + 1,115 dead clicks logged

Likely cause GA4 purchase event is likely missing/duplicating on checkout, or consent-mode is blocking it; check GTM trigger firing vs the Shopify order webhook.

Do this — in order
  1. Audit GA4 purchase event against Shopify order webhook
    Confirms whether GA4 is under-firing or double-counting purchases.
    ~2 h · analytics · Evolut (analytics)
  2. Reinstall Clarity snippet with session ID capture
    Session count of 0 despite click activity means Clarity isn't tagging sessions correctly.
    ~30 min · analytics · Evolut (analytics)
  3. Add Shopify order count as a cross-check dashboard
    Gives a trustworthy fallback while GA4 is being fixed.
    ~2 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,162 vs Shopify revenue $1,606 (-28% divergence)Tracking verdict: REDClarity shows 0 sessions on both mobile and desktop despite 210 rage clicks and 1,115 dead clicks recorded
112
TriangulatediSev 4 · blockeriInstrumentianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Mobile Begin Checkout→Purchase retention 17% (band 40–60%), $416/mo recoverableDesktop Begin Checkout→Purchase retention 10% (band 40–60%), $466/mo recoverableShopify: 17 abandoned checkouts vs only 19 completed orders in 30 daysSitewide CR mobile 0.15% / desktop 0.19% vs 1.5–3.5% band
113
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention is 7% vs 40–60% bandRecoverable ≈$1,166/month on desktopcheckoutEditable=false limits changes to pre-checkout/cart drawerDesktop dead clicks 763, rage clicks 169 (Clarity)
114
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Mobile Begin Checkout→Purchase 18% vs 40–60% band, recoverable $1307/moDesktop Begin Checkout→Purchase 7% vs 40–60% band, recoverable $1608/moOnly 19 orders and 22 abandoned checkouts in the 30-day window
115
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 8% vs 40-60% bandDesktop sitewide CR 0.15% vs 1.5-3.5% bandShopify abandoned checkouts: 18 vs orders: 19
116
TriangulatediSev 4 · blockeriInstrumentianalytics + behaviorali
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 7% vs 40–60% bandDesktop sitewide CR 0.15% vs 1.5–3.5% bandShopify abandonedCheckouts 16 vs orders 19 (30-day)
117
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Reported revenue is off by over $600, so decisions are based on bad numbers
GA4 and Shopify revenue diverge by 31%, meaning every downstream funnel percentage in this report is unreliable until tracking is fixed.
What's happening

GA4 shows $1391 in revenue vs Shopify's $2007, a 31% gap that invalidates all funnel percentages.

  • GA4 vs Shopify Revenue-31% should reconcile within ~5%

Likely cause Missing or duplicate purchase events (e.g. blocked by consent mode or firing before order confirmation) rather than real lost sales; check GA4 DebugView against the 21 Shopify orders to confirm.

Do this — in order
  1. Audit GA4 purchase event firing
    Compare GA4 order count to the 21 Shopify orders to quantify the gap.
    ~2 h · analytics · Evolut (analytics)
  2. Verify consent mode configuration
    Null consent rate suggests Consent Mode may be blocking or modeling events.
    ~2 h · analytics · Evolut (analytics)
  3. Implement server-side/Conversions API tracking
    Reduces reliance on client-side JS and closes the revenue gap.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1391 vs Shopify revenue $2007 (-31%)tracking verdict RED
118
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 9% vs 40–60% band$758/month recoverable revenue16 abandoned checkouts (Shopify)tracking verdict RED — treat as provisional
119
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 12% vs 40–60% bandrecoverable ~562 purchases/monthShopify shows 14 abandoned checkouts vs 26 orderstracking verdict RED — treat as provisional
120
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout → Purchase retention 15% vs 40–60% bandRecoverable ≈$1,005/monthDesktop Add to Cart → Begin Checkout is 94%, an implausibly high carry-overTracking verdict RED — treat figures as provisional
121
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue reports can't be trusted for decisions
A 28% revenue gap between GA4 and Shopify means every funnel and CRO number below is provisional until tracking is fixed.
What's happening

GA4 undercounts revenue by 28% vs Shopify ($1,852 vs $2,577), making funnel metrics unreliable.

  • GA4 vs Shopify revenue-28% should be ~0% divergence

Likely cause Likely a missing/duplicated GA4 purchase event or consent-mode gating dropping orders; compare server vs client-side firing to distinguish.

Do this — in order
  1. Audit GA4 purchase event firing
    Compare Shopify order IDs against GA4 purchase hits to find where events drop.
    ~1 day · analytics · Evolut (analytics)
  2. Verify GTM purchase trigger fires once per order
    Duplicate or missing triggers on the order-confirmation page cause revenue mismatch.
    ~2 h · analytics · Evolut (analytics)
  3. Check consent-mode/ad-blocker impact on tracking
    Null consentRatePct suggests consent mode may be blocking hits.
    ~2 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,852 vs Shopify revenue $2,577 (-28% divergence)Tracking verdict: RED
122
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Mobile Begin Checkout → Purchase 29% (band 40-60%), $622/mo recoverableDesktop Begin Checkout → Purchase 18% (band 40-60%), $1,509/mo recoverable12 abandoned checkouts vs 26 completed orders
123
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue numbers can't be trusted for decisions
With a 31% revenue gap and an impossible 105% checkout retention on desktop, every downstream funnel number is unreliable until measurement is fixed.
What's happening

GA4 shows $1507 vs Shopify's $2190 (-31%), and desktop checkout retention is an impossible 105%.

  • GA4 vs Shopify revenue-31% $1507 vs $2190
  • Desktop Add to Cart → Begin Checkout105% vs 40-60% band

Likely cause Likely duplicate begin_checkout event firing or a consent/attribution gap dropping GA4 purchases; compare event counts vs Shopify order IDs to distinguish.

Do this — in order
  1. Audit GTM tags for duplicate event firing
    Check begin_checkout/purchase triggers for double counts causing the 105% retention.
    ~2 h · analytics · Evolut (analytics)
  2. Reconcile GA4 vs Shopify order IDs daily
    Pinpoint exactly where events are lost or duplicated.
    ~2 h · analytics · Evolut (analytics)
  3. Implement server-side conversion tagging
    Recover client-side loss from ad blockers/consent gaps driving the revenue gap.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1507 vs Shopify revenue $2190 (-31% divergence)Desktop Add to Cart → Begin Checkout retention 105% (impossible, vs 40-60% band)
124
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue and conversion numbers can't be trusted for decisions
GA4 undercounts actual Shopify revenue by 31% ($1,353 vs $1,962), meaning every funnel percentage built on GA4 events is unreliable until fixed.
What's happening

GA4 reports $1,353 in revenue vs Shopify's $1,962, a 31% gap — measurement itself is broken.

  • GA4 vs Shopify revenue-31% should be ~0%

Likely cause Missing purchase events on some checkout paths or duplicate/broken GA4 e-commerce tagging; check consent-mode gaps vs tag firing order.

Do this — in order
  1. Audit GA4 purchase event firing on every checkout completion path
    Confirm the purchase event fires once per order, including express/wallet checkouts.
    ~2 h · analytics · Evolut (analytics)
  2. Reconcile GA4 vs Shopify order counts daily for one week
    Pinpoint which order types (discounted, subscription, express) are missing from GA4.
    ~1 day · analytics · Evolut (analytics)
  3. Add server-side or native Shopify GA4 tagging
    Reduces client-side ad-blocker and consent losses causing undercounting.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,353 vs Shopify revenue $1,962 (-31% divergence)tracking verdict RED
125
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout → Purchase retention 16% vs 40–60% band$1,358/month recoverable revenue13 abandoned checkouts vs 28 total orderstracking verdict RED — treat as provisional
126
TriangulatediSev 4 · blockeriInstrumentianalytics + behaviorali
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout → Purchase retention 16% vs 40–60% bandRecoverable ≈$1,496/moDesktop sessions: 1,392Desktop dead clicks: 83, rage clicks: 25 (Clarity)Shopify abandoned checkouts: 13 of 28 orders
127
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Nearly half of reported revenue is untrustworthy because tracking is broken
Tracking is flagged RED with a -52% GA4-vs-Shopify revenue gap and an impossible 127% desktop cart-to-checkout carryover, so every downstream funnel number below is provisional until this is fixed.
What's happening

GA4 shows $1222 vs Shopify's $2548 (-52%), and desktop cart→checkout hits 127%, both signaling broken measurement.

  • GA4 Revenue vs Shopify Revenue$1222 vs $2548 -52% divergence
  • Desktop Add to Cart → Begin Checkout127% vs 40–60% band, impossible

Likely cause Duplicate or missing GA4 purchase/add_to_cart tags, e.g. a double-firing checkout tag or a broken purchase trigger; check GTM firing rules vs consent mode to isolate which.

Do this — in order
  1. Audit GA4 purchase and add_to_cart tags in GTM
    Check for duplicate or missing triggers causing the 52% revenue gap.
    ~2 h · analytics · Evolut (analytics)
  2. Step through checkout in GA4 DebugView
    Confirms whether add_to_cart or purchase events fire twice on desktop.
    ~2 h · analytics · Evolut (analytics)
  3. Reconcile GA4 vs Shopify revenue daily for a week
    Confirms the fix before trusting funnel numbers again.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1222 vs Shopify revenue $2548.22 (-52% divergence)Desktop Add to Cart → Begin Checkout retention 127% (impossible, vs 40–60% band)Tracking verdict: RED
128
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue numbers can't be trusted — GA4 undercounts by 36% vs actual sales
All funnel and revenue metrics are unreliable until this gap is closed, so decisions based on current data are provisional.
What's happening

GA4 revenue ($1183) is 36% below Shopify's actual $1846, meaning purchase events aren't fully captured.

  • GA4 Revenue vs Shopify Revenue$1183 vs $1846 -36% divergence

Likely cause Purchase event under-firing (e.g., ad-blocker/consent-mode loss) or a broken GA4 e-commerce tag; check server-side vs client-side event counts.

Do this — in order
  1. Audit GA4 purchase event firing
    Compare GA4 purchase count to Shopify order count to isolate missing events.
    ~2 h · analytics · Evolut (analytics)
  2. Implement Shopify's native GA4/Conversions API integration
    Server-side tracking recovers events lost to ad-blockers or consent gaps.
    ~1 day · analytics · Evolut (analytics)
  3. Add GTM preview QA checklist for checkout events
    Prevents future silent tag failures on purchase/begin_checkout events.
    ~2 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 tracked revenue: $1183Shopify actual revenue: $1846Divergence: -36%Tracking verdict: RED
129
TriangulatediSev 4 · blockeriInstrumentianalytics + behaviorali
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention: 19% (band 40-60%)Recoverable revenue: $1028/monthDesktop rage clicks: 25Desktop dead clicks: 78Abandoned checkouts: 13 vs 27 ordersAdd to Cart→Begin Checkout retention: 124% (impossible, vs 40-60% band)
130
Data-supportediSev 4 · blockeriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
This is the single largest recoverable-revenue gap in the snapshot and the metric furthest below its band floor on the highest-traffic device.
What's happening

Only 3% of mobile product viewers add to cart, far below the 5–10% band floor.

  • Session → View Product83% vs 20–45% band
  • View Product → Add to Cart3% vs 5–10% band
  • Add to Cart → Begin Checkout41% vs 40–60% band, near floor
  • Begin Checkout → Purchase40% vs 40–60% band, at floor

Likely cause Mobile PDP likely hides or delays the add-to-cart action — either the CTA sits below the fold or slow-loading assets delay taps; check scroll-to-CTA distance vs page load time to tell which.

Do this — in order
  1. Add a sticky Add to Cart bar on mobile PDPs
    Keeps the primary action visible without scrolling, directly targeting the 3% conversion gap.
    ~2 h · theme edit · Evolut (LP)
  2. Move price and CTA above the fold on mobile
    Reduces scroll needed before a shopper can act.
    ~2 h · theme edit · Evolut (LP)
  3. Audit mobile PDP load speed for image/script delays
    Slow renders can suppress taps on the add-to-cart button.
    ~30 min · analytics · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
mobile View Product→Add to Cart retention 3% vs band 5–10%recoverable $1,134/mo on mobilemobile sitewide CR 0.38% vs band 1.5–3.5%mobile sessions 3,184
131
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue reports can't be trusted for decisions
A 40% revenue gap between GA4 and Shopify means every funnel and CR number below is unreliable until measurement is fixed.
What's happening

GA4 shows $1,468 in revenue while Shopify shows $2,456 — a 40% gap that invalidates downstream funnel math.

  • GA4 revenue vs Shopify revenue$1,468 vs $2,456 -40% divergence

Likely cause GA4 Purchase event likely under-fires (dedupe/client-side blocking) or orders complete without the confirmation page loading; check event fire count vs Shopify order count to distinguish.

Do this — in order
  1. Audit GA4 Purchase event firing per order
    Confirm it fires exactly once and isn't blocked by ad blockers or consent tools.
    ~2 h · analytics · Evolut (analytics)
  2. Add server-side purchase tracking via Shopify webhook
    Pushes order data to GA4 Measurement Protocol as a backstop to client-side loss.
    ~1 day · analytics · Evolut (analytics)
  3. Review consent banner impact on tracked sessions
    consentRatePct is null — confirm consent mode isn't silently dropping events.
    ~2 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,468 vs Shopify revenue $2,456 (-40% divergence)tracking verdict: RED
132
TriangulatediSev 4 · blockeriInstrumentianalytics + behaviorali
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 17% vs band 40-60%desktop recoverable $794/monthAdd to Cart→Begin Checkout 73% (above 40-60% band)desktop rage clicks 12, dead clicks 182tracking verdict RED
133
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 16% vs 40–60% bandRecoverable revenue estimate $1,152/month27 abandoned checkouts vs 62 total ordersTracking verdict RED — treat findings as provisional
134
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention is 15% vs 40–60% bandRecoverable estimate: $975/month26 abandoned checkouts vs 89 completed orders (Shopify)
135
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 14% vs 40–60% bandRecoverable ~$1,407/month27 abandoned checkouts vs 88 completed orders storewide
136
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 15% vs 40–60% bandRecoverable ~$1,095/month on this stepDesktop sessions: 2,344Abandoned checkouts: 27 vs 89 total orderscheckoutEditable: false
137
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout → Purchase retention 9% vs 40–60% bandRecoverable $821/mo on desktop31 abandoned checkouts in 30 daysTracking verdict RED (GA4 $1,365 vs Shopify $2,390, -43%) means this figure is provisional
138
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout → Purchase retention 9% vs band 40–60%recoverable $557/modesktop sessions 2,40431 abandoned checkoutstracking verdict RED (findings provisional)
139
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout → Purchase retention 9% vs 40–60% band$573/month recoverable revenue estimated29 abandoned checkouts in 30 daystracking verdict RED — treat as provisional pending fix
140
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase 12% vs 40–60% bandDesktop sitewide CR 0.22% vs 1.5–3.5% bandShopify abandoned checkouts 25 of 75 total ordersTracking verdict RED (data provisional)
141
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 12% vs 40-60% bandDesktop sitewide CR 0.22% vs 1.5-3.5% band25 abandoned checkoutsDesktop Add to Cart→Checkout 74%, above the 40-60% bandTracking verdict RED - treat as provisional
142
TriangulatediSev 4 · blockeriInstrumentianalytics + behaviorali
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 10% vs 40–60% bandDesktop Add to Cart→Begin Checkout is 76%, above the 40–60% bandDesktop recoverable revenue $1,018/moDesktop dead clicks: 492 (Clarity)Tracking verdict RED — treat as provisional
143
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Mobile Begin Checkout→Purchase retention 16% vs 40–60% bandRecoverable ~$433/monthMobile sessions 4,879 vs desktop 2,262Tracking verdict RED — treat as provisional
144
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 5% vs 40–60% bandDesktop sitewide CR 0.09% vs 1.5–3.5% band22 abandoned checkouts vs 44 total orders (Shopify)
145
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Reported revenue can't be trusted for any decision
A -40% GA4 vs Shopify revenue gap means every funnel and revenue number below is unreliable until fixed.
What's happening

GA4 shows $757 in revenue while Shopify shows $1254.44, a 40% gap that undermines every downstream metric.

  • GA4 vs Shopify revenue-40% divergence flagged RED

Likely cause Likely duplicate or missing purchase events, or consent-mode blocking; compare GTM tag firing against the Shopify order webhook to isolate.

Do this — in order
  1. Audit GA4 purchase event firing
    Compare GTM tag conditions against Shopify's checkout-completion webhook to find dropped events.
    ~2 h · analytics · Evolut (analytics)
  2. Deduplicate the purchase event
    Ensure GA4 doesn't double-fire or miss the event on redirect-based checkout completion.
    ~2 h · analytics · Evolut (analytics)
  3. Reconcile revenue daily for two weeks
    Cross-check GA4 vs Shopify revenue until divergence stays under 5%.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $757 vs Shopify revenue $1254.44 (-40% divergence)Tracking verdict: RED
146
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Mobile Checkout→Purchase retention 15% vs 40–60% band761/mo recoverable on this step aloneTracking RED — GA4 revenue undercounts by 33% sitewide
147
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Mobile Begin Checkout→Purchase 14% vs 40–60% band ($1,355/mo recoverable)Desktop Begin Checkout→Purchase 9% vs 40–60% band ($1,581/mo recoverable)Shopify: 22 abandoned checkouts vs 20 completed ordersMobile sitewide CR 0.13% and desktop 0.18% vs 1.5–3.5% bandRefunds $39 on $1,779 total revenue
148
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Mobile Begin Checkout → Purchase retention 17% vs band 40–60%mobile sitewide CR 0.15% vs band 1.5–3.5%recoverable ≈$595/monthmobile carries 5,413 sessions vs 2,189 desktop
149
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Mobile Begin Checkout → Purchase 17% vs 40–60% bandDesktop Begin Checkout → Purchase 10% vs 40–60% band18 total orders against 7,482 combined sessions17 abandoned checkouts$39 in refundstracking verdict RED (figures provisional)
150
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Reported revenue is $843 off from actual store sales, so every metric below is unreliable
A -42% GA4/Shopify revenue gap means all funnel percentages and $ recoverable figures below are provisional until tracking is fixed.
What's happening

GA4 shows $1,141 in revenue vs Shopify's actual $1,984, a 42% shortfall.

  • GA4 Revenue (30d)$1,141 vs Shopify $1,984 actual
  • Revenue Divergence-42% triggers RED tracking verdict

Likely cause Either GA4 purchase events are partially blocked (consent-mode gating, since consentRatePct is null) or the confirmation-page tag fails to fire on some orders.

Do this — in order
  1. Audit GA4 purchase tag firing on order confirmation
    Check for consent-mode blocking since consentRatePct is null
    ~2 h · analytics · Evolut (analytics)
  2. Reconcile order IDs between Shopify and GA4
    Identify which specific orders GA4 is missing to isolate the failure point
    ~1 day · analytics · Evolut (analytics)
  3. Add Shopify's server-side Conversions API feed
    Reduces reliance on client-side tags that consent tools or ad-blockers can drop
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,141 vs Shopify revenue $1,984 (-42% divergence)tracking verdict: RED
151
Data-supportediSev 4 · blockeriInstrumentianalyticsi
You can't trust the revenue numbers guiding decisions
Tracking verdict is RED and GA4 undercounts revenue by 38% vs Shopify, so every downstream conversion number is unreliable until fixed.
What's happening

GA4 shows $1,014 revenue vs Shopify's $1,648 (-38%), and desktop checkout events exceed plausible carry-over.

  • GA4 vs Shopify Revenue-38% $1,014 vs $1,648
  • Desktop Add to Cart → Begin Checkout73% vs 40–60% band (above ceiling)
  • Mobile Session → View Product88% vs 20–45% band (above ceiling)

Likely cause Likely duplicate/missing GA4 purchase events or a broken consent/tag setup; distinguish by auditing GTM triggers vs checking Shopify webhook-to-GA4 mapping.

Do this — in order
  1. Audit GA4 purchase & begin_checkout tags in GTM
    Confirm each fires once per order and matches Shopify order IDs to close the $634 gap.
    ~2 h · analytics · Evolut (analytics)
  2. Add server-side GA4 tagging via Shopify webhooks
    Removes ad-blocker/consent loss that likely causes client-side GA4 undercounting.
    ~1 day · analytics · Evolut (analytics)
  3. Re-baseline all funnel bands after fix
    Current mobile/desktop retention numbers are provisional until tracking is trustworthy.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,014 vs Shopify revenue $1,648 (-38% divergence)Desktop Add to Cart→Begin Checkout at 73% is above the 40–60% band ceilingTracking verdict: RED
152
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Mobile Begin Checkout→Purchase retention is 16% vs 40–60% bandRecoverable ≈$901/month on mobileMobile dead clicks 327, rage clicks 35 (Clarity)
153
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Analytics and Shopify disagree on revenue by over a third, so every funnel number below is provisional
Numbers are not trustworthy; this must be fixed before acting on any downstream funnel diagnosis.
What's happening

GA4 shows $1,131 in revenue while Shopify shows $1,708, a 34% gap that signals broken tracking.

  • GA4 vs Shopify Revenue-34% should be near 0% divergence

Likely cause Likely missing/duplicated GA4 purchase events (tag blocked post-checkout) or a broken Shopify-to-GA4 integration; compare GA4 DebugView to order webhooks to tell which.

Do this — in order
  1. Audit GA4 purchase event firing on the order confirmation page
    Confirms whether the tag loads after redirect or is blocked by ad blockers/consent tools.
    ~2 h · analytics · Evolut (analytics)
  2. Compare GA4 DebugView events against Shopify order webhooks
    Pinpoints exactly where events are dropped or duplicated.
    ~2 h · analytics · Evolut (analytics)
  3. Reinstall GA4 via Shopify's native integration or server-side tagging
    Removes reliance on a client-side tag that may be blocked.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,131 vs Shopify revenue $1,708.26 (-34% divergence)tracking verdict: red
154
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue reports can't be trusted—decisions are flying blind
With a 32% gap between GA4 and Shopify revenue, every funnel and revenue number below is unreliable until this is fixed.
What's happening

GA4 shows $1,502 in revenue while Shopify shows $2,207, a 32% gap, so tracking can't be trusted.

  • GA4 Revenue vs Shopify Revenue$1,502 vs $2,207 -32% divergence

Likely cause Likely a broken/duplicated purchase event or ad-blocker/consent-mode loss on GA4; check consent banner default vs server-side tagging to distinguish.

Do this — in order
  1. Audit GA4 purchase event firing against Shopify orders
    Compare order IDs event-by-event to find missing or duplicate GA4 purchase events.
    ~2 h · analytics · Evolut (analytics)
  2. Implement server-side or Shopify-native purchase tracking
    Use Shopify's Web Pixel or Conversions API so purchase data doesn't rely on client-side JS.
    ~1 day · analytics · Evolut (analytics)
  3. Add consent-mode fallback for ad-blocker loss
    Ensure GA4 tags fire regardless of consent-banner default state.
    ~2 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,502 vs Shopify revenue $2,207.26 (-32% divergence)tracking verdict: RED
155
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 17% vs 40–60% bandRecoverable ~$1,800/month on desktop12 abandoned checkouts recorded storewideCheckout not editable (Basic Shopify plan)
156
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout → Purchase retention 16% vs 40-60% band$1255/month recoverable revenue11 abandoned checkouts vs 26 total orders (Shopify)Tracking verdict RED — treat as provisional
157
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout → Purchase retention 11% vs 40–60% bandDesktop recoverable $580/monthDesktop Add to Cart → Begin Checkout at 110% (impossible, data anomaly)tracking verdict RED
158
Data-supportediSev 4 · blockeriInstrumentianalyticsi
You can't trust your revenue and funnel numbers to make decisions
GA4 is undercounting revenue by 37% versus Shopify's actual $2,303, and desktop shows an impossible 113% cart-to-checkout carryover — every downstream funnel number below is provisional until this is fixed.
What's happening

GA4 revenue ($1,460) is 37% below Shopify's real $2,303, and one desktop step exceeds 100%.

  • GA4 vs Shopify Revenue-37% should be ~0%
  • Desktop Add to Cart → Begin Checkout113% vs 40–60% band

Likely cause Duplicate or missing GA4 purchase/begin_checkout events (e.g. firing on refresh, or a consent-mode gap) are corrupting both revenue and step counts; check GTM trigger conditions vs consent state.

Do this — in order
  1. Audit GTM tags for duplicate begin_checkout/purchase firing
    113% desktop retention means an event is firing more than once per session.
    ~2 h · analytics · Evolut (analytics)
  2. Cross-check GA4 consent mode against Shopify checkout events
    Consent gaps commonly explain a ~37% revenue undercount in GA4.
    ~2 h · analytics · Evolut (analytics)
  3. Reconcile GA4 purchase event value with Shopify order totals
    Confirms whether the gap is event volume or event value mapping.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,460 vs Shopify revenue $2,303.21 (-37% divergence)tracking verdict: REDDesktop Add to Cart → Begin Checkout retention 113% (impossible, vs 40–60% band)
159
TriangulatediSev 4 · blockeriInstrumentianalytics + behaviorali
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout → Purchase retention 16% vs 40–60% band$2,217/month recoverable revenue on desktop28 rage clicks and 141 dead clicks on desktop (Clarity)
160
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue and funnel numbers can't be trusted right now
Tracking is flagged RED with a 36% revenue divergence ($2,084 GA4 vs $3,257 Shopify) and an impossible 105% desktop checkout carry-over, so all downstream funnel figures are provisional until fixed.
What's happening

GA4 revenue ($2,084) is 36% below Shopify's actual revenue ($3,257), and desktop shows an impossible 105% checkout carry-over.

  • GA4 vs Shopify Revenue$2,084 vs $3,257 -36% divergence
  • Desktop Add to Cart → Begin Checkout105% vs 40–60% band (impossible)
  • Mobile Add to Cart → Begin Checkout44% vs 40–60%, plausible

Likely cause Likely duplicate begin_checkout events or a broken GA4 purchase tag; check GTM triggers vs Shopify order webhook to confirm which.

Do this — in order
  1. Audit GA4 purchase & begin_checkout tags
    Compare GTM trigger firing vs Shopify webhook to find duplicate/missing events causing the 36% gap.
    ~2 h · analytics · Evolut (analytics)
  2. Deduplicate checkout event on drawer button
    Slide-out cart drawer's checkout button may fire begin_checkout twice, inflating desktop step to 105%.
    ~2 h · analytics · Evolut (analytics)
  3. Add server-side purchase event via Shopify webhook
    Server-side tracking bypasses ad-blockers/consent gaps that likely cause GA4 undercount.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
tracking verdict REDGA4 revenue $2,084 vs Shopify revenue $3,257 (-36% divergence)Desktop Add to Cart→Begin Checkout retention 105% vs 40–60% band
161
Data-supportediSev 4 · blockeriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile is the highest-traffic channel (3,094 sessions) but only 3% of product viewers add to cart versus a 5–10% band, capping sitewide CR at 0.42% and leaving an estimated $1,000/month on the table.
What's happening

On mobile, only 3% of product viewers add to cart, far below the 5–10% band, driving 0.42% sitewide CR.

  • Session Start → View Product82% vs 20–45% band
  • View Product → Add to Cart3% vs 5–10% band
  • Add to Cart → Begin Checkout40% at floor of 40–60% band
  • Begin Checkout → Purchase42% within 40–60% band

Likely cause PDP likely hides pricing, shipping cost, or subscription terms until scroll, stalling the tap-to-cart decision; distinguish by checking above-the-fold PDP content vs CTA visibility.

Do this — in order
  1. Surface price and shipping cost above the fold
    Removes late cost surprises that commonly stall mobile Add to Cart.
    ~2 h · theme edit · Evolut (LP)
  2. Simplify variant/subscription selector on PDP
    Confusing options block a quick one-tap add to cart on mobile.
    ~2 h · theme edit · Evolut (LP)
  3. Add a sticky mobile Add-to-Cart bar
    Keeps the CTA visible while scrolling, cutting drop-off before ATC.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
mobile View Product→Add to Cart retention 3% vs 5–10% bandrecoverable $1000/monthmobile sessions 3094mobile sitewide CR 0.42% vs 1.5–3.5% band
162
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 14% vs band 40–60%Recoverable $1858/moAbandoned checkouts: 26Refunds: $84.15checkoutEditable: false (Shopify plan)
163
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue numbers can't be trusted for decisions right now
Analytics and commerce platform disagree by 39% on revenue, so every funnel and CR number below is provisional until fixed.
What's happening

GA4 reports $1,730 vs Shopify's $2,828 in actual revenue, a 39% gap that invalidates funnel analysis.

  • GA4 Revenue$1,730 vs Shopify source of truth
  • Shopify Revenue$2,828 actual processed revenue

Likely cause Either the GA4 purchase event is misfiring/missing on the order confirmation page, or unconfigured consent mode is suppressing conversion pings.

Do this — in order
  1. Audit GA4 purchase event on order confirmation page
    Confirm it fires once per order with correct transaction_id and value.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent banner and consent mode configuration
    Null consent rate suggests tracking may be blocked for some visitors.
    ~2 h · analytics · Evolut (analytics)
  3. Reconcile GA4 vs Shopify order counts daily for 2 weeks
    Confirms the fix and establishes a trustworthy baseline for future calls.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,730 vs Shopify revenue $2,828 (-39% divergence)Tracking verdict: RED
164
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 9% vs 40–60% bandRecoverable ~$1,626/mo on desktopDesktop Add to Cart→Begin Checkout 85% (far above band)Shopify abandonedCheckouts: 29Tracking verdict RED (GA4 revenue -43% vs Shopify)
165
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 11% vs 40–60% band$622/mo recoverable revenue on desktopGA4/Shopify revenue divergence -42% (tracking RED) adds uncertainty to this read
166
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Mobile Begin Checkout→Purchase retention 16% vs 40–60% bandMobile sitewide CR 0.15% vs 1.5–3.5% band22 abandoned checkouts overall vs 44 orders
167
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 5% vs 40–60% band (leak, ~40 orders/month recoverable)Desktop Add to Cart→Begin Checkout 73% vs 40–60% band (unusually high)22 abandoned checkouts vs 46 total ordersRefunds $123.15 on $1254.44 revenue (9.8%)Tracking verdict RED — treat as provisional
168
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout → Purchase retention 9% vs 40–60% bandRecoverable ~$2,215/moDesktop sitewide CR 0.18% vs 1.5–3.5% bandTracking verdict RED — treat as provisional
169
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 12% vs 40-60% bandDesktop recoverable ~$993/monthDesktop sitewide CR 0.31% vs 1.5-3.5% band
170
Data-supportediSev 4 · blockeriInstrumentianalyticsi
Revenue numbers can't be trusted, and desktop cart data looks impossible
Measurement is broken at the source, so every downstream funnel and revenue number is provisional until fixed.
What's happening

GA4 undercounts revenue by 27% vs Shopify ($1,759 vs $2,403), and desktop shows an impossible 104% cart-to-checkout rate.

  • GA4 vs Shopify Revenue$1,759 vs $2,403 -27% divergence
  • Desktop Add to Cart → Begin Checkout104% vs 40–60% band (impossible)

Likely cause Duplicate or missing GA4 events (double-fired add_to_cart/purchase tags) vs consent-mode blocking losing conversions; check tag firing counts vs order IDs to distinguish.

Do this — in order
  1. Audit GA4 add_to_cart and purchase tag firing
    Duplicate triggers likely explain the impossible 104% desktop rate
    ~2 h · analytics · Evolut (analytics)
  2. Reconcile GA4 order IDs against Shopify orders
    Identify exactly which events are missing or duplicated
    ~1 day · analytics · Evolut (analytics)
  3. Implement Shopify's native/server-side GA4 tagging
    Removes reliance on client-side tags prone to blocking or dupes
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,759 vs Shopify revenue $2,403 (-27% divergence)Desktop Add to Cart→Begin Checkout retention 104% (exceeds 100%, band 40–60%)Tracking verdict: RED
171
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Mobile Begin Checkout→Purchase retention 17% vs 40–60% band (leak, ~33 orders/month recoverable)22 abandoned checkouts vs 46 total ordersRefunds $123.15 on $1254.44 revenue (9.8%)Tracking verdict RED — treat as provisional
172
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Mobile Begin Checkout → Purchase retention 16% vs 40–60% bandRecoverable ~$1,868/moMobile sitewide CR 0.15% vs 1.5–3.5% bandTracking verdict RED — treat as provisional
173
Data-supportediSev 4 · blockeriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
desktop Add to Cart→Begin Checkout retention 95% (band 40-60%, suspect)desktop Begin Checkout→Purchase retention 9% (band 40-60%, leak)recoverable ~$564/monthtracking verdict RED (-26% divergence)
174
Data-supportediSev 3 · majoriInstrumentianalyticsi
No behavioral data exists to explain why shoppers are dropping off
With zero recorded Clarity sessions against 3,126 mobile and 1,395 desktop GA sessions, there's no behavioral evidence to diagnose the mobile ATC leak or desktop checkout leak.
What's happening

Clarity shows 0 sessions on both devices despite thousands of GA4 sessions, leaving no behavioral evidence.

  • Clarity mobile sessions0 vs 3,126 GA4 mobile sessions
  • Clarity desktop sessions0 vs 1,395 GA4 desktop sessions

Likely cause The Clarity snippet likely isn't deployed on all templates, or is being blocked by consent gating; check tag deployment vs consent-script blocking.

Do this — in order
  1. Verify Clarity tag fires on PDP, drawer, and checkout
    Confirms the script is installed site-wide, not just on some templates.
    ~30 min · analytics · Evolut (analytics)
  2. Check consent banner isn't blocking the Clarity script
    Consent gating can silently suppress all session recordings.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Clarity mobile sessions recorded: 0Clarity desktop sessions recorded: 0All Clarity behavioral metrics reporting 0 on both devices
175
Data-supportediSev 2 · minoriInstrumentianalyticsi
You have zero visibility into why shoppers are actually dropping off
Without session replay data, the two funnel leaks above can only be guessed at, not confirmed.
What's happening

Clarity shows 0 recorded sessions on both devices, so no behavioral evidence exists to diagnose the funnel leaks.

  • Mobile Clarity sessions0 expected >0 given 3,064 GA4 sessions
  • Desktop Clarity sessions0 expected >0 given 1,390 GA4 sessions

Likely cause The Clarity snippet is likely missing, misconfigured, or blocked by a consent tool, rather than there being genuinely zero traffic.

Do this — in order
  1. Verify the Clarity snippet is installed site-wide
    Confirms the tag fires on every template, not just some pages.
    ~30 min · analytics · Evolut (analytics)
  2. Check the consent banner isn't blocking Clarity
    Consent tools can silently suppress the recording script from firing.
    ~30 min · analytics · Evolut (analytics)
  3. Test Clarity capture in an incognito session
    Confirms recordings populate within minutes of a live visit.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Clarity recorded 0 sessions on mobile in 30 daysClarity recorded 0 sessions on desktop in 30 daysAll behavioral metrics (rage clicks, dead clicks, scroll depth) show 0 on both devices
176
Data-supportediSev 2 · minoriInstrumentianalyticsi
No session recordings exist to explain why shoppers are dropping off
Zero Clarity sessions on both devices means no behavioral data backs any hypothesis about why shoppers stall on mobile or desktop.
What's happening

Clarity shows 0 recorded sessions on both devices, leaving no behavioral evidence to diagnose the leaks above.

  • Clarity mobile sessions0 no data
  • Clarity desktop sessions0 no data

Likely cause The Clarity tracking script is likely not installed or not firing on the storefront; verify script presence versus consent-blocking.

Do this — in order
  1. Verify Clarity script is installed site-wide
    Confirm the tracking snippet loads on both mobile and desktop templates.
    ~30 min · analytics · Evolut (analytics)
  2. Check consent banner isn't blocking Clarity
    Cookie consent settings may prevent session recording from firing.
    ~30 min · analytics · Evolut (analytics)
  3. Re-run Clarity for 7 days and review recordings
    Gathers real session replays to confirm PDP and checkout hypotheses.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Clarity mobile sessions = 0Clarity desktop sessions = 0No behavioral evidence available to diagnose funnel leaks
177
Data-supportediSev 2 · minoriInstrumentianalyticsi
No behavioral data exists to explain any of the funnel drop-offs
Without Clarity data, the causes behind the checkout and PDP leaks above can't be visually confirmed.
What's happening

Clarity shows zero recorded sessions on both devices, so no rage-click/scroll evidence backs the funnel findings.

  • Clarity mobile sessions0 vs GA 2905 mobile sessions
  • Clarity desktop sessions0 vs GA 1350 desktop sessions

Likely cause The Clarity snippet is likely missing or broken on the live theme, or being blocked by a CSP/consent rule before it can log sessions.

Do this — in order
  1. Confirm Clarity snippet loads on live site
    Check page source/network tab for the Clarity script firing.
    ~30 min · analytics · Evolut (analytics)
  2. Check CSP/consent settings for blocks
    A content-security-policy or consent gate may silently block Clarity.
    ~30 min · analytics · Evolut (analytics)
  3. Reinstall Clarity via Shopify app embed
    Ensures the snippet persists across theme updates.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
clarity.mobile.sessions=0 vs GA mobile sessions 2905clarity.desktop.sessions=0 vs GA desktop sessions 1350clarity rageClicks/deadClicks/scroll all 0 sitewide
178
Data-supportediSev 3 · majoriInstrumentianalyticsi
Revenue numbers can't be trusted for decision-making
A 65% gap between GA4 and Shopify revenue means every funnel and CR number in this snapshot is unreliable until measurement is fixed.
What's happening

GA4 shows $1,133 in revenue while Shopify shows $3,201 — a 65% gap that invalidates downstream funnel analysis.

  • GA4 vs Shopify revenue-65% acceptable divergence is roughly ±10%

Likely cause Either GA4 purchase events are under-firing (consent-mode gating, tag misconfiguration) or Shopify orders are being double-counted; checking event counts per order will distinguish them.

Do this — in order
  1. Compare GA4 DebugView to 10 live test orders
    Confirms whether purchase events fire once per order or not at all
    ~2 h · analytics · Evolut (analytics)
  2. Audit consent-mode default state on checkout pages
    Consent gating before user action can silently block GA4 purchase tags
    ~1 h · analytics · Evolut (analytics)
  3. Reconcile GA4 vs Shopify order IDs for the last 30 days
    Pinpoints exactly which orders are missing or duplicated in GA4
    ~2 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,133 vs Shopify revenue $3,201 (-65% divergence)tracking verdict: RED
179
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile is the majority of sessions (2,771) yet converts views to carts at half the band floor, losing an estimated 63 carts/month.
What's happening

Mobile View→Add to Cart retention is 4%, below the 5–10% band, costing an estimated 63 carts/month.

  • Session → View Product74% vs 20–45%
  • View Product → Add to Cart4% vs 5–10%
  • Add to Cart → Begin Checkout52% vs 40–60%

Likely cause placeholder

Do this — in order$63/mo at stake
  1. Move Add-to-Cart button above the fold on mobile PDP
    252 dead clicks suggest shoppers can't find or tap the current CTA
    ~2 h · theme edit · Evolut (LP)
  2. Review Clarity recordings on the mobile PDP
    Pinpoint exactly which non-functional elements are absorbing taps
    ~2 h · analytics · Evolut (LP)
  3. Shorten mobile PDP above the CTA
    Only 24% avg scroll means most shoppers never reach key content
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 4% vs 5–10% bandRecoverable: $63/moMobile dead clicks 252Mobile avg scroll 24%
73
ICE i
I8·C7·E7
180
Data-supportediSev 3 · majoriInstrumentianalyticsi
You can't trust any conversion number right now because GA4 is missing 43% of revenue
All downstream funnel and revenue figures are unreliable until tracking is reconciled, so this must be fixed before acting on any other number.
What's happening

GA4 shows $1,659 in revenue while Shopify shows $2,898, a 43% gap that invalidates the funnel data.

  • GA4 Revenue$1,659 vs Shopify ground truth
  • Shopify Revenue$2,898 source of truth

Likely cause Likely missing purchase events or consent-mode blocking GA4 tags; distinguish by checking tag firing on the order-confirmation page versus consent-banner logs.

Do this — in order
  1. Audit GA4 purchase event firing on order confirmation
    Confirms whether the purchase event tag actually fires after checkout.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode settings blocking GA4 tags
    Cookie banner defaults can silently suppress purchase tracking.
    ~2 h · analytics · Evolut (analytics)
  3. Reconcile GA4 against Shopify via server-side tracking
    A server-side or CAPI setup removes browser-blocking as a variable.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,659 vs Shopify revenue $2,898 (-43% divergence)tracking verdict: RED
181
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
This is the single worst-below-band step in the whole funnel and the largest recoverable mobile revenue opportunity.
What's happening

Mobile View Product→Add to Cart is 3%, well under the 5–10% band, costing an est. $657/month.

  • Session → View Product79% vs 20–45% band
  • View Product → Add to Cart3% vs 5–10% band
  • Add to Cart → Begin Checkout50% within 40–60% band
  • Begin Checkout → Purchase40% at floor of 40–60% band

Likely cause 263 mobile dead clicks plus only 23% avg scroll suggest the Add to Cart control is hidden or unresponsive below the fold; distinguish via session recordings on PDP versus checking button hit-area/z-index.

Do this — in order
  1. Add a sticky Add to Cart bar on mobile PDP
    Keeps the CTA visible without requiring scroll past 23% of the page.
    ~2 h · theme edit · Evolut (LP)
  2. Audit PDP elements causing dead clicks
    263 dead clicks suggest buttons or images aren't triggering expected actions.
    ~2 h · theme edit · Evolut (LP)
  3. Move price and CTA higher on the PDP
    Low scroll depth means most content below the fold is never seen.
    ~1 day · copy · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View→Add to Cart retention is 3% vs 5–10% bandRecoverable estimate: $657/month263 dead clicks recorded on mobileAverage mobile scroll depth is only 23%
73
ICE i
I8·C7·E7
182
TriangulatediSev 2 · minoriInstrumentianalytics + behaviorali
Behavioral analytics is reporting zero sessions per device, so click data can't be trusted yet
Without a valid session denominator, rage/dead click counts used to support other findings can't be rate-checked and may mislead prioritization.
What's happening

Clarity shows 0 sessions per device despite GA4 logging 3,403 mobile and 2,353 desktop sessions.

  • Clarity Mobile Sessions0 vs 3403 GA4 sessions
  • Clarity Desktop Sessions0 vs 2353 GA4 sessions

Likely cause Clarity's install likely isn't passing device/session dimensions correctly, or a sampling filter is excluding all traffic; check script placement vs project filters.

Do this — in order
  1. Verify Clarity script fires on every page template
    Confirms tag isn't blocked or missing on key templates like PDP or checkout.
    ~2 h · analytics · Evolut (analytics)
  2. Check Clarity project sampling and device filters
    A misconfigured filter could be excluding all sessions from device reporting.
    ~30 min · analytics · Evolut (analytics)
  3. Re-pull rage/dead click rates once session counts are fixed
    Ensures future UX decisions are based on a real session denominator.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Clarity mobile sessions: 0 vs 3403 GA4 mobile sessionsClarity desktop sessions: 0 vs 2353 GA4 desktop sessionsMobile dead clicks: 252, Desktop dead clicks: 227 reported without a session base
183
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile product-page retention (3%) is roughly half the 5–10% band floor, costing an estimated $588/month, with only 23% average scroll and 260 dead clicks pointing to a hard-to-reach or unresponsive Add to Cart control; treat as provisional given RED tracking.
What's happening

Only 3% of mobile product-page viewers add to cart, well under the 5–10% band floor.

  • Session Start → View Product81% vs 20–45%
  • View Product → Add to Cart3% vs 5–10%
  • Add to Cart → Begin Checkout54% vs 40–60%

Likely cause Either the Add to Cart button sits below the fold (avg scroll only 23%) or a tap-target is broken, driving the 260 dead clicks; recordings vs scroll-map would distinguish.

Do this — in order
  1. Move the Add to Cart button above the fold on mobile PDP
    Avg scroll is only 23%, so most shoppers never reach a below-fold button.
    ~2 h · theme edit · Evolut (LP)
  2. Review Clarity recordings for the 260 mobile dead clicks
    Dead clicks often mean a tappable-looking element isn't functioning.
    ~2 h · analytics · Evolut (LP)
  3. Add a sticky mobile Add to Cart bar
    Keeps the action reachable regardless of scroll depth.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View→Add to Cart retention 3% vs 5–10% bandRecoverable ~$588/monthMobile sessions: 3,476Mobile dead clicks: 260, avg scroll: 23%
73
ICE i
I9·C6·E7
184
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile view-to-cart (3%) is below its 5–10% band and mobile drives 3,607 sessions/month, making it the next highest-value fix.
What's happening

Mobile product views convert to cart adds at only 3%, half the 5–10% band floor, costing roughly $425/month.

  • Session Start → View Product81% vs 20–45% band (unusually high)
  • View Product → Add to Cart3% vs 5–10% band
  • Add to Cart → Begin Checkout49% vs 40–60% band
  • Begin Checkout → Purchase39% vs 40–60% band

Likely cause The add-to-cart CTA likely sits below the fold since avg scroll is only 23%, or dead clicks indicate an unresponsive button; check session recordings to tell which.

Do this — in order
  1. Move add-to-cart button above the fold on mobile PDP
    Avg scroll of only 23% means a lower CTA is rarely seen.
    ~2 h · theme edit · Evolut (LP)
  2. Fix unresponsive elements causing 251 mobile dead clicks
    Review Clarity recordings to locate the broken tap target.
    ~1 day · theme edit · Evolut (LP)
  3. Add a sticky add-to-cart bar on mobile PDP
    Keeps the CTA visible regardless of scroll position.
    ~2 h · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product → Add to Cart retention 3% vs band 5–10%recoverable $425/momobile sessions 3,607mobile dead clicks 251mobile avg scroll depth 23%
73
ICE i
I8·C7·E7
185
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
This is a confirmed below-band leak on mobile, the higher-traffic device (3,979 sessions), with behavioral evidence of a UI breakdown.
What's happening

Only 3% of mobile product-page viewers add to cart, below the 5–10% band, costing ~$215/mo.

  • Session → View Product83% vs 20–45%
  • View Product → Add to Cart3% vs 5–10%
  • Add to Cart → Begin Checkout42% vs 40–60%

Likely cause 294 mobile dead clicks suggest the add-to-cart button or variant selector isn't registering taps, versus a pure messaging/price problem; check tap logs.

Do this — in order
  1. Check add-to-cart button tap targets and JS bindings
    294 dead clicks indicate taps aren't registering on mobile PDP.
    ~2 h · theme edit · Evolut (LP)
  2. Add sticky add-to-cart bar on mobile PDP
    Average scroll is only 22%, so CTA visibility is likely the gap.
    ~2 h · theme edit · Evolut (LP)
  3. Simplify variant/quantity selection steps
    Fewer taps needed before the add-to-cart action can fire.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 3% vs band 5–10%Recoverable ~$215/moMobile dead clicks: 294Mobile sitewide CR 0.38% vs band 1.5–3.5%
73
ICE i
I8·C7·E7
186
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile ATC conversion sits at 4%, below the 5–10% healthy band, costing an estimated $316/month; low scroll depth (22%) and heavy dead-clicking (293) suggest shoppers aren't finding the Add to Cart action.
What's happening

Only 4% of mobile product viewers add to cart, below the 5–10% band, alongside heavy dead-clicking.

  • Session → View Product84% vs 20–45% band
  • View Product → Add to Cart4% vs 5–10% band

Likely cause Low scroll depth (22%) plus 293 dead clicks point to the Add to Cart button sitting below the fold or reading as non-interactive; check heatmap position vs scroll-depth chart to confirm.

Do this — in order
  1. Move Add to Cart button above the fold on mobile PDP
    22% avg scroll means most shoppers never reach a lower-placed button.
    ~2 h · theme edit · Evolut (LP)
  2. Add a sticky mobile Add-to-Cart bar
    Keeps the CTA visible through scroll, reducing dead-click confusion.
    ~2 h · theme edit · Evolut (LP)
  3. Review PDP dead-click hotspots in session recordings
    293 dead clicks indicate taps on elements shoppers expect to be interactive.
    ~2 h · analytics · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product → Add to Cart retention 4% vs 5–10% bandRecoverable ≈$316/monthMobile avg scroll depth 22%Mobile dead clicks 293, rage clicks 26
73
ICE i
I8·C7·E7
187
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
This leak sits just below the healthy floor but touches the largest mobile session volume (4,152), so even a small lift recovers meaningful revenue.
What's happening

Only 4% of mobile product viewers add to cart, below the 5–10% healthy band.

  • Session Start → View Product84% above 20–45% band, reported ok
  • View Product → Add to Cart4% vs 5–10% band

Likely cause Key info/CTA is likely buried below the fold (avg scroll only 22%) or buttons are mis-tappable (285 dead clicks); compare scroll-depth heatmap to click-map to tell apart.

Do this — in order
  1. Move Add to Cart button and key benefits above the fold
    Mobile scroll depth is only 22%, so most page content below it goes unseen.
    ~2 h · theme edit · Evolut (LP)
  2. Fix dead-click elements near the product gallery/CTA
    285 mobile dead clicks suggest shoppers tap elements that don't respond.
    ~2 h · theme edit · Evolut (LP)
  3. Add a sticky mobile Add to Cart bar
    Keeps the CTA visible while scrolling, reducing exits before adding to cart.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 4% vs 5–10% band$232/mo recoverable revenue on mobileMobile avg scroll depth 22%, 285 mobile dead clicks
73
ICE i
I7·C8·E7
188
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Only 26% of mobile add-to-cart sessions proceed to checkout, well below the 40-60% band, and dead-click volume suggests drawer UI friction.
What's happening

Only 26% of mobile add-to-cart sessions proceed to checkout, well below the 40–60% band.

  • Session → View Product85% vs 20-45%
  • View Product → Add to Cart4% vs 5-10%
  • Add to Cart → Begin Checkout26% vs 40-60%
  • Begin Checkout → Purchase26% vs 40-60%

Likely cause Likely the cart drawer's checkout CTA is unclear or buried, causing shoppers to close it; the 309 mobile dead clicks support a non-responsive UI element.

Do this — in order
  1. Move checkout button above the fold in drawer
    Ensure the primary CTA is visible without scrolling on mobile.
    ~30 min · theme edit · Client dev
  2. Add express checkout buttons inside the drawer
    Shop Pay/PayPal buttons reduce steps from cart to purchase.
    ~2 h · payment config · Client dev
  3. Add shipping/returns reassurance copy near CTA
    Short trust text next to the checkout button addresses hesitation.
    ~30 min · copy · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention 26% vs 40–60% band$687/month recoverable revenue309 mobile dead clicks recorded
73
ICE i
I8·C6·E8
189
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Mobile carry-over from cart to checkout is roughly half the desktop rate (21% vs 65%), pointing at a drawer-specific friction point.
What's happening

Only 21% of mobile add-to-carts reach checkout, versus 65% on desktop for the same step.

  • Add to Cart → Begin Checkout (Mobile)21% vs 40-60% band
  • Add to Cart → Begin Checkout (Desktop)65% vs 40-60% band

Likely cause The slide-out cart drawer's checkout button may be hard to locate or tap on mobile, or unresponsive elements (363 mobile dead clicks) are blocking progress; drawer session recordings would distinguish placement vs a broken tap target.

Do this — in order
  1. Add a sticky high-contrast checkout button inside the drawer
    Makes the next step obvious without scrolling the drawer on mobile
    ~2 h · theme edit · Client dev
  2. Add trust badges and returns info inside the drawer
    Reassures shoppers before they decide to proceed
    ~1 h · copy · Client dev
  3. Review Clarity recordings for dead-click hotspots in the drawer
    363 mobile dead clicks likely mark an unresponsive tap target
    ~2 h · analytics · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout 21% vs 40-60% band, recoverable $397/month363 dead clicks recorded on mobile
73
ICE i
I8·C7·E7
190
Data-supportediSev 3 · majoriInstrumentianalyticsi
You can't trust your revenue numbers to make any decision right now
A 33% gap between GA4 and Shopify revenue means every funnel and CR figure below is unverified until measurement is fixed.
What's happening

GA4 shows $1,430 vs Shopify's $2,135 revenue, a 33% gap flagging broken measurement.

  • GA4 Revenue vs Shopify Revenue-33% should be near 0%
  • Desktop Add to Cart → Begin Checkout96% vs 40-60% band (implausible)

Likely cause Likely duplicate GA4 purchase events or missed conversions from Shop Pay/PayPal redirects; check order-ID dedup vs consent-mode blocking.

Do this — in order
  1. Audit GA4 purchase events against Shopify order IDs
    Compare order counts to find duplicate or missing purchase fires.
    ~2 h · analytics · Evolut (analytics)
  2. Verify tracking on Shop Pay/PayPal redirect flows
    External payment redirects often drop GA4 client IDs, undercounting purchases.
    ~2 h · analytics · Evolut (analytics)
  3. Add Shopify-native or server-side GA4 pixel
    Server-side tagging avoids ad-blocker and redirect losses causing the 33% gap.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,430 vs Shopify revenue $2,135 (-33% divergence)tracking verdict: RED
191
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
This is mobile's largest recoverable leak and sits inside the cart drawer shoppers actually use.
What's happening

71% of mobile shoppers who add to cart never begin checkout, below the 40–60% expected range.

  • Add to Cart→Begin Checkout29% vs 40–60%

Likely cause The drawer likely lacks a prominent checkout CTA or trust/shipping info, or shoppers are tapping non-functional elements (225 mobile dead clicks).

Do this — in order
  1. Add shipping threshold and returns line inside drawer
    Builds confidence to proceed without leaving the drawer
    ~30 min · copy · Client dev
  2. Make checkout button sticky and full-width in drawer
    Ensures the CTA is visible without scrolling on mobile
    ~2 h · theme edit · Client dev
  3. Fix dead-click elements inside the drawer
    225 mobile dead clicks suggest tappable-looking elements aren't responding
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention 29% vs 40–60% bandrecoverable ~189 checkouts/monthmobile dead clicks 225, rage clicks 26
73
ICE i
I8·C7·E7
192
Data-supportediSev 3 · majoriInstrumentianalyticsi
Revenue data can't be trusted for decisions right now
A 30% revenue gap between GA4 and Shopify means every funnel percentage below is unreliable until fixed.
What's happening

GA4 shows $1,728 vs Shopify's actual $2,453, a 30% gap, meaning purchase tracking is broken.

  • GA4 Revenue vs Shopify Revenue-30% should be within ~5%

Likely cause Purchase event is likely duplicated or blocked by consent gating before firing; compare GA4 DebugView timestamps against Shopify order IDs to isolate.

Do this — in order
  1. Audit GA4 purchase event firing logic
    Confirm the purchase event fires exactly once per completed Shopify order.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode tag gating on checkout
    Verify cookie consent isn't blocking GA4 tags before purchase completes.
    ~2 h · analytics · Evolut (analytics)
  3. Reconcile transaction IDs GA4 vs Shopify
    Match order IDs across both systems to find missing or duplicate hits.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1,728 vs Shopify revenue $2,453 (-30% divergence)Tracking verdict: RED
193
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
The largest recoverable revenue on mobile sits at the product-to-cart step, well below its band floor, alongside signs of low engagement.
What's happening

Mobile View→Add to Cart is 3%, under half the 5% band floor, across 3,258 sessions.

  • Session → View Product84% vs 20–45% band
  • View Product → Add to Cart3% vs 5–10%
  • Add to Cart → Begin Checkout41% vs 40–60%

Likely cause Low average scroll depth (21%) and 131 dead clicks suggest the Add-to-Cart control or key info is unseen or unresponsive; heatmap vs click-map data will separate the two.

Do this — in order
  1. Move Add to Cart button above the fold
    Avg scroll is only 21%, so most never reach the current button
    ~2 h · theme edit · Evolut (LP)
  2. Review Clarity recordings for the 131 mobile dead clicks
    Identify unresponsive elements blocking add-to-cart
    ~2 h · analytics · Evolut (LP)
  3. Simplify mobile product page layout
    Shorten path to the add-to-cart action
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 3% vs 5–10% bandRecoverable ~$278/monthMobile sessions 3,258Mobile dead clicks 131, rage clicks 22, avg scroll 21%
73
ICE i
I9·C7·E6
194
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile product-page viewers convert to cart adds at 3%, well under the 5–10% band, an estimated $865/month left on the table (provisional pending tracking fix).
What's happening

Only 3% of mobile product viewers add to cart, versus a 5–10% band, with scroll depth stopping at 22%.

  • Session → View Product83% vs 20–45% band
  • View Product → Add to Cart3% vs 5–10%
  • Add to Cart → Begin Checkout41% vs 40–60%
  • Begin Checkout → Purchase30% vs 40–60%

Likely cause Mobile PDP likely buries the CTA/price below the fold (22% scroll) or a tap target is broken; compare heatmap position of ATC button to fold line.

Do this — in order
  1. Add sticky Add to Cart bar on mobile PDP
    Keeps CTA visible since most users never scroll past 22%.
    ~2 h · theme edit · Evolut (LP)
  2. Move price and CTA above the fold
    Surface the buy button before long-form benefit copy.
    ~2 h · theme edit · Evolut (LP)
  3. Fix unresponsive PDP tap targets
    39 mobile dead clicks suggest an element isn't functioning correctly.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 3% vs 5–10% bandRecoverable ~$865/moMobile avg scroll depth 22%Mobile dead clicks 39
73
ICE i
I8·C7·E7
195
Data-supportediSev 2 · minoriInstrumentibehaviorali
No behavioral data exists to explain why shoppers are dropping off
Without behavioral capture, the funnel leaks above can only be diagnosed from counts, not from seeing what shoppers actually do.
What's happening

Clarity shows zero sessions and zero metrics on both devices, meaning behavioral tracking isn't installed or firing.

  • Mobile Clarity sessions0 expected ~3139 mobile sessions tracked
  • Desktop Clarity sessions0 expected ~1363 desktop sessions tracked

Likely cause Clarity snippet missing or misconfigured, or a consent gate is silently blocking the script from loading.

Do this — in order
  1. Verify Clarity snippet is installed sitewide
    Confirm the tracking script is present in theme.liquid on all templates.
    ~30 min · analytics · Evolut (analytics)
  2. Check consent banner isn't blocking Clarity
    Confirm the analytics consent category fires before Clarity loads.
    ~30 min · analytics · Evolut (analytics)
  3. Re-test after 48 hours for session capture
    Confirm sessions and rage-click counts populate before trusting data.
    ~2 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Clarity mobile sessions 0, scriptErrorsPct 0, botPct 0Clarity desktop sessions 0, scriptErrorsPct 0, botPct 0all Clarity metrics read zero over 30 days despite 3139 mobile and 1363 desktop sessions
196
Data-supportediSev 3 · majoriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Largest dollar leak in the funnel; high mobile traffic means small PDP fixes carry outsized upside.
What's happening

Mobile shoppers view products but almost never add to cart — 3% vs the 5–10% band floor.

  • Session → View Product82% far above 20–45% band, unusually high
  • View → Add to Cart3% vs 5–10% band
  • Add to Cart → Checkout37% vs 40–60% band
  • Checkout → Purchase47% within 40–60% band

Likely cause Mobile PDP likely hides the Add-to-Cart CTA below the fold or needs extra variant taps; rule out slow image/JS load pushing the CTA down.

Do this — in order
  1. Pin Add to Cart button above the fold
    Keeps the primary CTA visible without scrolling on mobile PDP.
    ~2 h · theme edit · Evolut (LP)
  2. Reduce variant selector to one tap
    Fewer taps before add-to-cart lowers PDP friction.
    ~2 h · theme edit · Evolut (LP)
  3. Add stock/review count near CTA
    Social proof beside the button can nudge hesitant mobile shoppers.
    ~30 min · copy · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
mobile view→ATC retention 3% vs 5–10% bandmobile recoverable revenue $921/mo (largest single gap)mobile sitewide CR 0.45% vs 1.5–3.5% bandmobile sessions 2905
73
ICE i
I9·C6·E7
197
Data-supportediSev 2 · minoriInstrumentianalyticsi
You have no visibility into how shoppers actually behave on the site because behavioral tracking is capturing zero sessions
Without behavioral data, the funnel leaks above can only be diagnosed from numbers, not from seeing what shoppers actually do.
What's happening

Clarity reports zero sessions on both devices despite over 4,000 combined GA4 sessions, so no behavioral data exists.

  • Mobile Clarity sessions0 expected ~2,751 tracked sessions
  • Desktop Clarity sessions0 expected ~1,424 tracked sessions

Likely cause The Clarity script is likely not installed on live templates, or a cookie-consent gate is blocking it from firing.

Do this — in order
  1. Verify the Clarity snippet is present on all live templates
    Confirms whether the tracking code was ever deployed correctly.
    ~30 min · analytics · Evolut (analytics)
  2. Check consent/cookie banner isn't blocking the Clarity script
    Consent gating is a common cause of zero-session reporting.
    ~30 min · analytics · Evolut (analytics)
  3. Re-check Clarity dashboard 24h after the fix
    Confirms sessions are now populating before relying on it again.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Clarity mobile sessions = 0 against 2,751 GA4 mobile sessionsClarity desktop sessions = 0 against 1,424 GA4 desktop sessionsAll Clarity metrics (rage clicks, dead clicks, scroll, script errors) reported as 0 on both devices
198
Data-supportediSev 3 · majoriInstrumentianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
desktop Begin Checkout→Purchase 18% vs 40–60% band (leak)mobile Begin Checkout→Purchase 38% vs 40–60% band (leak)recoverable $1,272/month (desktop) + $103/month (mobile)27 abandoned checkouts/monthcheckoutEditable: falseAOV: $114.76
199
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile product pages convert to cart at 4%, below the 5-10% band, costing an estimated $400/month, with heavy dead-click activity nearby.
What's happening

Mobile View Product→Add to Cart sits at 4%, below the 5–10% band, alongside 269 mobile dead clicks.

  • Session → View Product79% vs 20–45%
  • View Product → Add to Cart4% vs 5–10%
  • Add to Cart → Begin Checkout49% vs 40–60%

Likely cause High dead-click volume suggests the mobile Add to Cart button or variant selector isn't responding to taps, or it sits below a 23%-deep average scroll.

Do this — in order
  1. Fix or enlarge the mobile Add to Cart tap target
    269 monthly dead clicks suggest shoppers tap it without effect.
    ~2 h · theme edit · Evolut (LP)
  2. Move Add to Cart button above the fold on mobile PDP
    Average mobile scroll depth is only 23%, many never reach it lower down.
    ~2 h · theme edit · Evolut (LP)
  3. Manually test variant/size selectors on real mobile devices
    Confirm selectors aren't silently failing and blocking the add-to-cart action.
    ~30 min · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart 4% vs 5–10% band$400/month recoverable revenue on mobile269 dead clicks on mobile (vs 203 desktop)mobile avg scroll depth 23%
70
ICE i
I8·C7·E6
200
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile carries the most sessions (3,655) and has the steepest relative leak, so a small lift here recovers the most volume.
What's happening

Mobile View→Add to Cart is 3%, roughly half the 5–10% floor, despite 81% of sessions reaching a product page.

  • Session → View Product81% vs 20–45% band
  • View Product → Add to Cart3% vs 5–10% band
  • Add to Cart → Begin Checkout50% within 40–60% band
  • Begin Checkout → Purchase38% vs 40–60% band

Likely cause Low 23% average scroll plus 262 dead clicks suggest the Add to Cart button sits below the fold or near unresponsive elements; check Clarity recordings to confirm.

Do this — in order
  1. Add a sticky mobile Add to Cart bar
    81% reach the PDP but only 3% add to cart — keep the CTA visible without scrolling.
    ~1 day · theme edit · Evolut (LP)
  2. Review Clarity recordings on top dead-click elements
    262 dead clicks imply shoppers are tapping non-functional elements near the buy box.
    ~2 h · analytics · Evolut (LP)
  3. Move key value content above the fold
    23% average scroll means most page content is never seen.
    ~2 h · copy · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product → Add to Cart retention 3% vs 5–10% band$452/month recoverable revenue estimatedMobile average scroll depth only 23%262 dead clicks recorded on mobile
70
ICE i
I8·C7·E6
201
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
This is the highest-volume mobile leak (3,684 sessions) and is corroborated by behavioral data, not just a funnel number.
What's happening

Only 3% of mobile product viewers add to cart, below the 5–10% band, despite 82% reaching the product page.

  • Session → View Product82% vs 20–45% band
  • View Product → Add to Cart3% vs 5–10%
  • Add to Cart → Begin Checkout49% vs 40–60%

Likely cause 268 mobile dead clicks plus only 23% avg scroll suggest the Add-to-Cart control sits below the fold or isn't registering taps.

Do this — in order
  1. Make the Add-to-Cart button sticky on mobile PDP
    23% avg scroll means most shoppers never reach a static ATC button.
    ~2 h · theme edit · Evolut (LP)
  2. Fix unresponsive tap targets on the product page
    268 dead clicks indicate elements that look tappable but don't respond.
    ~1 day · theme edit · Evolut (LP)
  3. Move price, variant picker and ATC above the fold
    Matches the low scroll behavior so key actions are seen immediately.
    ~2 h · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 3% vs 5–10% bandRecoverable ~$1,364/mo on mobileMobile Clarity dead clicks: 268Mobile avg scroll depth: 23%
70
ICE i
I8·C7·E6
202
Data-supportediSev 2 · minoriInstrumentianalyticsi
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
27 abandoned checkouts vs 87 completed orders (30 days)Shopify revenue $2,472.38
203
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile is the highest-traffic device (3,831 sessions) but converts viewers to cart-adds at nearly half the healthy rate, suppressing all downstream revenue.
What's happening

Mobile Add-to-Cart rate is 3%, below the 5–10% floor, despite 83% of sessions reaching a product page.

  • Session → View Product83% vs 20–45%
  • View Product → Add to Cart3% vs 5–10%
  • Add to Cart → Begin Checkout45% vs 40–60%

Likely cause Low scroll depth (22%) suggests the Add-to-Cart CTA sits below the fold, or 291 dead clicks indicate shoppers tapping non-functional elements instead.

Do this — in order
  1. Move Add to Cart button above the fold on mobile PDP
    22% avg scroll means most shoppers never reach a lower CTA.
    ~2 h · theme edit · Evolut (LP)
  2. Add a sticky mobile Add-to-Cart bar
    Keeps the CTA accessible regardless of scroll position, lifting ATC rate directly.
    ~1 day · theme edit · Evolut (LP)
  3. Fix mobile PDP elements generating 291 dead clicks
    Identify non-clickable images or badges shoppers mistake for buttons and link or remove them.
    ~2 h · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 3% vs 5–10% band$432/mo recoverable on mobilemobile dead clicks 291mobile avg scroll depth 22%
70
ICE i
I8·C7·E6
204
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
70% of mobile cart-adders abandon before checkout begins, well under the 40% floor, on the highest-volume device.
What's happening

Mobile cart-to-checkout retention is 30%, below the 40–60% band, losing most cart adds before checkout starts.

  • View Product → Add to Cart4% vs 5–10%
  • Add to Cart → Begin Checkout30% vs 40–60%

Likely cause Likely drawer friction from a missing/unclear checkout CTA or hidden costs revealed late; distinguish via drawer session recordings vs a cost-reveal check.

Do this — in order
  1. Add prominent Checkout button atop cart drawer
    Reduce taps needed to reach checkout from the slide-out cart.
    ~30 min · theme edit · Client dev
  2. Show shipping/trust info inside drawer
    Reassure shoppers on cost and security before they leave the drawer.
    ~2 h · theme edit · Client dev
  3. Enable Shop Pay/PayPal express buttons in drawer
    Let mobile shoppers skip the full checkout flow.
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout 30% vs 40–60% bandMobile sessions 4,267Clarity mobile dead clicks 294
70
ICE i
I8·C6·E7
205
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Mobile drives 4,390 of ~6,674 sessions yet loses 71% of cart-adders before checkout (29% vs 40-60%), the largest reachable leak by volume.
What's happening

71% of mobile shoppers who add to cart abandon before starting checkout (29% vs 40-60% band).

  • Session → View Product85% above 20-45% band
  • View Product → Add to Cart4% vs 5-10% band
  • Add to Cart → Begin Checkout29% vs 40-60% band
  • Begin Checkout → Purchase33% vs 40-60% band

Likely cause The slide-out drawer likely lacks a clear, trusted path to checkout; distinguish low CTA visibility from missing trust/shipping info via drawer session recordings.

Do this — in order
  1. Pin a prominent Checkout button in the cart drawer
    Ensures the CTA is visible without scrolling on mobile.
    ~2 h · theme edit · Client dev
  2. Add trust badges and shipping/returns info inside the drawer
    Reduces last-second hesitation before checkout.
    ~2 h · copy · Client dev
  3. Add Shop Pay/Apple Pay buttons inside the drawer
    Lets shoppers skip to one-tap checkout.
    ~30 min · platform config · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention 29% vs 40-60% bandMobile sitewide CR 0.3% vs 1.5-3.5% bandMobile Clarity deadClicks 303, avgScroll 21%
70
ICE i
I8·C6·E7
206
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
This is the officially flagged mobile leak and mobile carries the majority of site traffic (4,434 sessions).
What's happening

Mobile cart-to-checkout retention is 27%, well under the 40–60% band, costing roughly $291/month.

  • Session → View Product85% vs 20–45%
  • View → Add to Cart4% vs 5–10%
  • Add to Cart → Begin Checkout27% vs 40–60%
  • Begin Checkout → Purchase31% vs 40–60%

Likely cause Drawer checkout CTA likely lacks visibility or trust cues; 298 mobile dead clicks suggest shoppers tapping non-functional elements instead of the checkout button.

Do this — in order
  1. Make checkout button sticky and high-contrast in cart drawer
    Drawer sits above a /cart page — CTA visibility directly drives this step
    ~2 h · theme edit · Client dev
  2. Add express wallets (Shop Pay, Apple Pay) inside drawer
    Removes steps for mobile shoppers most prone to drop-off
    ~2 h · theme edit · Client dev
  3. Show shipping threshold and trust badges in drawer
    Builds confidence before the checkout tap, closing the 27% vs 40–60% gap
    ~30 min · copy · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout 27% vs 40–60% band$291/mo recoverable revenuemobile sessions 4,434298 mobile dead clicks, 25 mobile rage clicks
70
ICE i
I8·C6·E7
207
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Mobile-only: cart-to-checkout retention is 20% vs a 40–60% band while desktop hits 61%, and mobile shows 364 dead clicks — pointing at drawer friction worth ~$303/mo.
What's happening

Mobile Add to Cart→Begin Checkout is 20% vs 40–60% band; desktop is 61%, so the gap is mobile-drawer specific.

  • Add to Cart → Begin Checkout (Mobile)20% vs 40–60% band (desktop 61%, healthy)

Likely cause The slide-out drawer's checkout CTA is likely hard to see/tap on mobile, or shipping cost isn't shown until checkout; check drawer session recordings for scroll/tap struggle.

Do this — in order
  1. Add a sticky, high-contrast checkout button in the drawer
    Improves tap visibility for the drawer's primary action on small screens.
    ~2 h · theme edit · Client dev
  2. Add one-tap express checkout button inside the drawer
    Shop Pay/Apple Pay in-drawer removes an extra step for mobile users.
    ~2 h · theme edit · Client dev
  3. Surface free-shipping threshold text in the drawer
    Reduces mid-drawer drop-off from shipping-cost uncertainty.
    ~30 min · copy · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention 20% (band 40–60%), $303/mo recoverableDesktop same step is 61% (healthy) — mobile-only gapMobile Clarity: 364 dead clicks, 41 rage clicks recorded
70
ICE i
I7·C6·E8
208
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
This is mobile's second funnel leak, upstream of the checkout-completion leak, and is fixable inside the cart drawer without touching the checkout page.
What's happening

Only 21% of mobile add-to-cart events open checkout, well below the 40–60% band.

  • View Product → Add to Cart5% at floor of 5–10% band
  • Add to Cart → Begin Checkout21% vs 40–60% band
  • Begin Checkout → Purchase16% vs 40–60% band

Likely cause Dead clicks (331) suggest shoppers are tapping non-functional drawer elements, or the checkout CTA isn't visible without scrolling.

Do this — in order
  1. Make the drawer's checkout button sticky and full-width
    Ensures the single next step is always visible on small screens
    ~30 min · theme edit · Client dev
  2. Add a one-line shipping/returns reassurance in the drawer
    Reduces hesitation right before the checkout tap
    ~30 min · copy · Client dev
  3. Fix unresponsive drawer icons/buttons
    331 mobile dead clicks indicate elements that look clickable but aren't
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
mobile Add to Cart→Begin Checkout retention 21% vs 40–60% band$922/mo recoverable on mobilemobile dead clicks 331 (Clarity)
70
ICE i
I7·C6·E8
209
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Mobile shoppers who add to cart mostly stall before starting checkout, likely losing them inside the slide-out cart drawer.
What's happening

27% of mobile cart-adders begin checkout, far below the 40–60% band, losing an estimated $312/month.

  • Add to Cart → Begin Checkout (mobile)27% vs 40–60% band

Likely cause The drawer likely lacks a prominent checkout CTA or trust/shipping info, or unresponsive elements (276 mobile dead clicks) block taps.

Do this — in order
  1. Make checkout button sticky and dominant
    Ensure the CTA sits above the fold with no competing links.
    ~2 h · theme edit · Client dev
  2. Add express-pay buttons inside the drawer
    Shop Pay, Apple Pay, PayPal buttons cut steps to checkout.
    ~30 min · theme edit · Client dev
  3. Show shipping cost and returns note
    Surface shipping/returns info in-drawer to reduce checkout hesitation.
    ~2 h · copy · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout 27% vs band 40–60%recoverable ≈$312/month757 dead clicks sitewide (276 on mobile)
70
ICE i
I7·C7·E7
210
Data-supportediSev 3 · majoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
27% vs a 40-60% band on the drawer step is losing ~$223/month and is a fast, low-effort fix since it only requires drawer UI changes.
What's happening

Only 27% of mobile add-to-carts proceed to checkout from the drawer, well below the 40-60% band.

  • Add to Cart → Begin Checkout27% vs 40-60% band

Likely cause The drawer's checkout CTA is likely low-visibility or missing reassurance (shipping/returns), causing shoppers to close it rather than proceed; check CTA prominence versus missing trust copy.

Do this — in order
  1. Make the checkout button sticky and above the fold in the drawer
    Ensures the primary action is visible without scrolling on mobile.
    ~30 min · theme edit · Client dev
  2. Add a shipping/returns trust line beside the checkout button
    Reduces last-second hesitation before leaving the drawer.
    ~30 min · copy · Client dev
  3. Add express checkout wallet buttons inside the drawer
    Lets shoppers skip to payment without opening the checkout page.
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
mobile Add to Cart→Begin Checkout retention 27% (band 40-60%)recoverable ~$223/monthcart is slide-out drawer with no separate /cart page
70
ICE i
I7·C6·E8
211
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
On mobile's 3,626 monthly sessions, this below-band ATC rate is the highest-volume leak in the funnel.
What's happening

Only 4% of mobile product viewers add to cart, below the 5–10% healthy band, on 3,626 sessions.

  • Session → View Product84% vs 20–45% band (implausibly high)
  • View Product → Add to Cart4% vs 5–10%

Likely cause Product pages likely lack a clear value/price/CTA for mobile shoppers, or the add-to-cart button is hard to tap; check tap-accuracy heatmaps to distinguish.

Do this — in order
  1. Move Add to Cart button above the fold on mobile PDP
    188 mobile dead clicks suggest shoppers tap non-functional areas expecting action.
    ~2 h · theme edit · Evolut (LP)
  2. Simplify mobile PDP copy and pricing display
    Clarify the value proposition to reduce hesitation before adding to cart.
    ~2 h · copy · Evolut (LP)
  3. Increase Add to Cart button size/contrast on mobile
    Improves tap target given the 4% ATC rate on high mobile traffic.
    ~30 min · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product → Add to Cart retention 4% vs band 5–10%Recoverable ≈$328/month188 dead clicks recorded on mobile
70
ICE i
I8·C6·E7
212
Data-supportediSev 3 · majoriInstrumentianalyticsi
Analytics is undercounting real revenue by over a quarter, so every funnel number below is unreliable
With a 28% revenue gap between GA4 and Shopify, all funnel percentages and recoverable-revenue estimates are provisional until measurement is fixed.
What's happening

GA4 reports $1852 vs Shopify's $2577.41 in actual revenue, a 28% shortfall in tracked sales.

  • GA4 Revenue vs Shopify Revenue-28% should be ~0% divergence

Likely cause Likely a missing/duplicated GA4 purchase event or a consent/ad-blocker gap; compare transaction IDs between GA4 and Shopify order webhooks to isolate.

Do this — in order
  1. Compare GA4 purchase event IDs against Shopify order IDs
    Reveals whether events are missing, duplicated, or mistimed.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent mode and ad-blocker impact on purchase tracking
    Consent gaps commonly explain a 20-30% undercount.
    ~2 h · analytics · Evolut (analytics)
  3. Add server-side purchase event as backup source
    Reduces reliance on client-side JS that can fail silently.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
GA4 revenue $1852 vs Shopify revenue $2577.41 (-28% divergence)tracking verdict: RED
213
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
This is the largest clearly-diagnosable mobile leak, combining a below-band conversion drop with direct behavioral evidence of disengagement.
What's happening

Only 4% of mobile product viewers add to cart, below the 5-10% band, with just 21% average scroll depth.

  • Session → View Product84% vs 20-45%, unusually high
  • View Product → Add to Cart4% vs 5-10%

Likely cause Sticky CTA missing or key price/benefit info sits below the 21% scroll fold; check dead-click positions relative to the CTA to distinguish.

Do this — in order
  1. Add sticky 'Add to Cart' bar on mobile PDP
    Keep CTA visible without scrolling to capture low-scroll visitors.
    ~2 h · theme edit · Evolut (LP)
  2. Move key benefits/price above the fold
    Only 21% avg scroll means most content goes unseen.
    ~2 h · copy · Evolut (LP)
  3. Fix dead-click elements on mobile PDP
    169 dead clicks suggest tappable-looking elements aren't functioning.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product → Add to Cart retention 4% vs 5-10% band$532/month recoverable revenue169 dead clicks on mobileMobile avg scroll depth 21%
70
ICE i
I8·C7·E6
214
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Only 3% of mobile product viewers add to cart versus an expected 5–10%, worth an estimated $254/month, and 165 mobile dead clicks suggest the add-to-cart control itself may be unresponsive.
What's happening

Mobile View→Add to Cart conversion is 3% vs a 5–10% band, mobile's clearest funnel leak.

  • View Product → Add to Cart3% vs 5–10%

Likely cause Either the add-to-cart button is hard to tap or unresponsive (165 mobile dead clicks), or content above it fails to justify purchase; tap-target size vs copy would distinguish these.

Do this — in order
  1. Make the add-to-cart button sticky and full-width on mobile PDP
    Removes scrolling/tapping friction implied by 165 dead clicks.
    ~2 h · theme edit · Evolut (LP)
  2. Increase tap-target size and spacing around variant selectors
    Dead clicks often mean shoppers are missing or mis-tapping controls.
    ~2 h · theme edit · Evolut (LP)
  3. Move key benefit bullets and price above the fold
    Mobile average scroll is only 21%, so most content below the fold goes unseen.
    ~1 day · copy · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product → Add to Cart retention 3% vs 5–10% bandMobile recoverable $254/monthMobile Clarity dead clicks 165Mobile Clarity rage clicks 26
70
ICE i
I8·C6·E7
215
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
3% add-to-cart conversion is well under the 5-10% band and is the largest recoverable mobile opportunity ($301/mo), corroborated by heavy dead-click activity.
What's happening

Only 3% of mobile product viewers add to cart, under the 5-10% band, alongside 139 dead clicks.

  • Session Start → View Product84% vs 20-45% band
  • View Product → Add to Cart3% vs 5-10% band
  • Add to Cart → Begin Checkout41% vs 40-60% band

Likely cause Either the mobile Add to Cart button is hard to see/tap (139 dead clicks), or product pages lack persuasive content since average scroll is only 21%.

Do this — in order
  1. Move Add to Cart button above the fold
    21% avg scroll means most shoppers never reach a lower CTA.
    ~2 h · theme edit · Evolut (LP)
  2. Increase mobile Add to Cart button size and contrast
    139 dead clicks suggest shoppers are tapping unresponsive elements nearby.
    ~30 min · theme edit · Evolut (LP)
  3. Add a sticky Add to Cart bar on mobile PDP
    Keeps the CTA visible regardless of scroll depth.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product → Add to Cart retention 3% vs 5-10% bandRecoverable $301/monthMobile dead clicks 139Mobile avg scroll depth 21%
70
ICE i
I8·C7·E6
216
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
This is the furthest-below-band step on the highest-traffic device, and Clarity shows heavy dead-click activity supporting a UX cause.
What's happening

Only 3% of mobile product viewers add to cart, roughly half the 5–10% floor, losing an est. $267/month.

  • Session → View Product (mobile)84% vs 20–45%
  • View Product → Add to Cart (mobile)3% vs 5–10%
  • Add to Cart → Begin Checkout (mobile)41% vs 40–60%

Likely cause Mobile PDP likely has a hard-to-tap or unclear add-to-cart button causing the 128 recorded dead clicks, or a confusing variant selector; screen recordings will confirm which.

Do this — in order
  1. Make the add-to-cart button sticky and full-width on mobile
    128 dead clicks suggest shoppers can't find or trigger it easily
    ~2 h · theme edit · Evolut (LP)
  2. Simplify the variant/size selector on product pages
    Reduces friction near where dead clicks likely cluster
    ~2 h · theme edit · Evolut (LP)
  3. Add price and trust copy directly above the ATC button
    Reduces hesitation right before the action shoppers are missing
    ~30 min · copy · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product → Add to Cart retention 3% vs band 5–10%Mobile sessions 3,289Recoverable ~$267/monthMobile dead clicks 128, rage clicks 22 (Clarity)
70
ICE i
I8·C7·E6
217
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile view-to-cart conversion is 3%, roughly half the 5–10% floor, and 120 dead clicks plus only 22% average scroll on mobile point to a broken or hard-to-reach Add to Cart control, costing ~$946/month.
What's happening

Mobile view-to-cart conversion is 3%, below the 5–10% floor, losing an estimated $946/month.

  • Session Start → View Product84% vs 20–45% band
  • View Product → Add to Cart3% vs 5–10% band

Likely cause Low 22% scroll depth combined with 120 dead clicks suggests the mobile PDP's Add-to-Cart button is unresponsive or below the fold; confirm which via Clarity PDP recordings.

Do this — in order
  1. Make Add to Cart button sticky on mobile PDP
    Puts the CTA above the fold regardless of scroll depth, directly targeting the leak.
    ~2 h · theme edit · Evolut (LP)
  2. Review Clarity recordings at dead-click hotspots on PDP
    120 mobile dead clicks likely mark the exact broken element.
    ~30 min · analytics · Evolut (LP)
  3. Shorten mobile PDP above the fold to surface price and CTA sooner
    22% avg scroll means most shoppers never see content below the top.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product → Add to Cart retention 3% vs 5–10% band$946/month recoverable revenue120 dead clicks on mobilemobile avg scroll depth 22%
70
ICE i
I8·C7·E6
218
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Second-largest recoverable leak and below-band on mobile, the device carrying 2,960 of roughly 4,341 total sessions.
What's happening

Mobile View→Add to Cart is 3% versus a 5–10% band, an estimated $824/month left on the table.

  • Session → View Product82% vs 20-45% band
  • View Product → Add to Cart3% vs 5-10%

Likely cause Low 23% average scroll suggests price/CTA sit below the fold; alternatively slow image load on mobile suppresses engagement before shoppers reach the button.

Do this — in order
  1. Move price and Add to Cart button above the fold
    23% scroll depth means most shoppers never reach the current CTA.
    ~2 h · theme edit · Evolut (LP)
  2. Add a sticky mobile add-to-cart bar
    Keeps the CTA reachable as shoppers scroll product details.
    ~2 h · theme edit · Evolut (LP)
  3. Compress and lazy-load mobile product images
    Faster load reduces early drop-off from a sluggish page.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention: 3% (band 5-10%)Recoverable revenue: $824/monthMobile avg scroll depth: 23%Mobile dead clicks: 27
70
ICE i
I8·C6·E7
219
Data-supportediSev 2 · minoriInstrumentibehaviorali
You can't see why shoppers abandon — behavioral tracking shows zero sessions
Clarity reports zero recorded sessions on both devices, so there's no behavioral evidence to diagnose either the mobile ATC leak or the desktop checkout leak.
What's happening

Clarity shows 0 sessions on mobile and desktop despite thousands of GA4 sessions, leaving root causes unproven.

  • Clarity mobile sessions0 vs 3,094 GA4 mobile sessions
  • Clarity desktop sessions0 vs 1,386 GA4 desktop sessions

Likely cause Clarity's tracking snippet may be missing or blocked on the live domain, or a project filter/sampling rule is silently excluding all traffic.

Do this — in order
  1. Verify Clarity snippet loads on the live site
    Zero sessions suggests the script may be missing or blocked.
    ~30 min · analytics · Evolut (analytics)
  2. Check Clarity project filters and sampling rules
    A misconfigured filter can silently exclude all sessions.
    ~30 min · analytics · Evolut (analytics)
  3. Re-verify Clarity data after 48h once fixed
    Confirms behavioral data flows before trusting future UX diagnoses.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Clarity mobile sessions=0 despite 3,094 GA4 mobile sessionsClarity desktop sessions=0 despite 1,386 GA4 desktop sessionsrageClicks/deadClicks/avgScroll all 0 on both devices
220
Data-supportediSev 2 · minoriInstrumentianalyticsi
You currently have zero visibility into how shoppers actually behave on the site
Without behavioral recordings, the funnel leaks above can only be diagnosed from analytics numbers, not confirmed with real user behavior — every downstream cause is a hypothesis until this is fixed.
What's happening

Clarity recorded 0 sessions on both devices this month despite thousands of GA4 sessions, so no behavior data exists.

  • Mobile Clarity sessions0 vs 2699 GA4 sessions
  • Desktop Clarity sessions0 vs 1400 GA4 sessions

Likely cause Clarity script is likely missing on the live theme or blocked by a consent/cookie banner; check install presence vs consent-gating rules.

Do this — in order
  1. Verify Clarity snippet fires on the live theme
    Confirm the tracking script loads in browser console and reports to the Clarity dashboard.
    ~30 min · analytics · Evolut (analytics)
  2. Check consent banner isn't blocking Clarity
    Some CMPs block third-party recorders until consent is explicitly given.
    ~30 min · analytics · Evolut (analytics)
  3. Recheck session counts after 48 hours
    Confirm sessions populate before trusting any future behavioral findings.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Clarity mobile sessions: 0 despite 2699 GA4 mobile sessionsClarity desktop sessions: 0 despite 1400 GA4 desktop sessionsAll Clarity behavioral metrics (rage clicks, dead clicks, scroll, script errors) reported as 0 on both devices
221
TriangulatediSev 2 · minoriInvestigateibehavioral + analyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most product-page visitors never add to cart
High dead-click volume plus shallow scroll suggests broken or unclear UI elements are frustrating visitors right at the point they'd add to cart.
What's happening

Dead clicks and shallow scroll depth point to unresponsive page elements suppressing mobile add-to-cart, which sits at the band floor.

  • View Product → Add to Cart (Mobile)5% floor of 5-10% band
  • Dead clicks (Mobile)289 high
  • Dead clicks (Desktop)220 elevated
  • Avg scroll depth (Mobile)24% low engagement

Likely cause Visitors are clicking non-interactive elements (images, badges) expecting them to work, or key content sits below the 24-38% scroll fold they rarely reach.

Do this — in order
  1. Watch Clarity replays of top dead-click sessions
    Pinpoint the exact page and element causing the non-interactive click attempts
    ~2 h · analytics · Evolut (LP)
  2. Make flagged elements clickable or strip their button-like styling
    Removes the false affordance currently frustrating shoppers
    ~1 day · theme edit · Evolut (LP)
  3. Move key trust content above the ~24-38% scroll line
    Ensures reviews/benefits are seen before visitors disengage
    ~2 h · copy · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
509 total dead clicks (289 mobile, 220 desktop)Average scroll depth 31% sitewide (24% mobile, 38% desktop)Mobile View→Add to Cart retention at 5%, the floor of the 5-10% band
67
ICE i
I6·C7·E7
222
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile is the larger traffic source (2,775 sessions) and this step sits below its floor, directly costing add-to-carts every month.
What's happening

Only 4% of mobile product viewers add to cart, half the 5-10% floor, costing roughly $154/month.

  • Session → View Product75% vs 20-45% band
  • View Product → Add to Cart4% vs 5-10% band
  • Add to Cart → Begin Checkout49% vs 40-60% band

Likely cause High dead-click count (254) and shallow 24% scroll depth suggest the mobile Add to Cart button or key product info is hard to find or unresponsive.

Do this — in order
  1. Make the Add to Cart button sticky on mobile PDP
    Keeps the CTA visible despite only 24% average scroll depth.
    ~2 h · theme edit · Evolut (LP)
  2. Review dead-click hotspots on mobile product pages
    254 dead clicks suggest shoppers tap non-interactive elements expecting action.
    ~2 h · theme edit · Evolut (LP)
  3. Shorten above-fold product copy to surface CTA sooner
    Low scroll depth means the buy button may be missed before shoppers leave.
    ~1 day · copy · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View→Add to Cart retention 4% vs band 5-10%recoverable $154/monthmobile dead clicks 254mobile avg scroll 24%
67
ICE i
I7·C6·E7
223
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile product pages convert viewers to cart adds at less than half the floor of the healthy range.
What's happening

Mobile View→Add to Cart is 4%, below the 5–10% band, while desktop converts at a healthy 8%.

  • Session → View Product76% vs 20–45%
  • View Product → Add to Cart4% vs 5–10%
  • Add to Cart → Begin Checkout48% vs 40–60%

Likely cause Mobile PDP likely hides the add-to-cart button below the fold (24% avg scroll) or a tappable element isn't responding (262 dead clicks); check layout vs heatmap.

Do this — in order
  1. Move Add to Cart button and price above the fold on mobile
    Only 24% average scroll means most shoppers never reach a lower-placed CTA.
    ~2 h · theme edit · Evolut (LP)
  2. Review the 262 mobile dead clicks in Clarity recordings
    Identify which non-responsive element shoppers tap before leaving without adding to cart.
    ~2 h · analytics · Evolut (LP)
  3. Simplify the variant/size selector on mobile PDP
    Reduces friction if dead clicks cluster on selector controls.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 4% vs 5–10% bandRecoverable revenue estimate $334/monthMobile dead clicks: 262 (Clarity)Mobile avg scroll depth: 24%
67
ICE i
I7·C6·E7
224
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile View Product→Add to Cart sits at 4% vs the 5–10% band, worth an estimated $514/month, and correlates with 270 mobile dead clicks and only 24% average scroll depth.
What's happening

Mobile Add to Cart retention is 4%, below the 5–10% band, while visitors scroll only 24% of the page.

  • View Product → Add to Cart (mobile)4% vs 5–10% band
  • Avg scroll depth (mobile)24% low engagement

Likely cause Low scroll depth hides the Add to Cart button, or dead clicks (270) indicate it's visible but non-responsive; recordings can distinguish placement vs functionality.

Do this — in order
  1. Make Add to Cart button sticky on mobile PDP
    Avg scroll is only 24%, so most shoppers never reach a static button
    ~2 h · theme edit · Evolut (LP)
  2. Fix unresponsive PDP elements causing dead clicks
    270 mobile dead clicks suggest buttons or swatches that look clickable but aren't
    ~2 h · theme edit · Evolut (LP)
  3. Move key product value content above the fold
    76% of mobile visitors never scroll past the first screen
    ~1 day · copy · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
mobile View Product→Add to Cart 4% vs 5–10% band (leak)recoverable $514/monthmobile dead clicks: 270mobile avg scroll: 24%
67
ICE i
I7·C7·E6
225
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile add-to-cart rate of 4% sits below the 5% band floor, and mobile Clarity shows 264 dead clicks with only 24% average scroll, suggesting shoppers aren't reaching or engaging the add-to-cart control.
What's happening

Mobile View→Add to Cart is 4%, below the 5–10% band, alongside 264 dead clicks and 24% scroll depth.

  • Session → View Product77% vs 20–45% band
  • View Product → Add to Cart4% vs 5–10%

Likely cause Low scroll depth (24%) suggests the add-to-cart CTA sits below the fold, or dead clicks mean a tap target isn't registering; check CTA placement vs element responsiveness.

Do this — in order
  1. Add a sticky add-to-cart bar on mobile product pages
    Keeps the CTA visible given only 24% average scroll depth.
    ~2 h · theme edit · Evolut (LP)
  2. Audit the 264 mobile dead-click elements in Clarity recordings
    Identify which product-page elements shoppers tap but get no response from.
    ~2 h · theme edit · Evolut (LP)
  3. Move price, reviews, and add-to-cart above the fold
    Surfaces key purchase info without requiring scroll.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product → Add to Cart retention 4% vs 5–10% bandRecoverable revenue estimated $569/month264 dead clicks and 24% average scroll depth on mobile (Clarity)Tracking verdict RED — treat as provisional
67
ICE i
I7·C7·E6
226
TriangulatediSev 3 · majoriInvestigateianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
This is the worst-below-band step in the whole funnel and the largest mobile revenue leak.
What's happening

Mobile PDP-to-cart conversion is 3%, roughly half the 5–10% floor, costing $655/mo.

  • Session → View Product81% vs 20–45% band
  • View Product → Add to Cart3% vs 5–10%
  • Add to Cart → Begin Checkout51% vs 40–60%
  • Begin Checkout → Purchase38% vs 40–60%

Likely cause Low add-to-cart suggests PDP friction — a broken size/variant selector or a slow-loading ATC button, evidenced by 256 mobile dead clicks.

Do this — in order
  1. Review mobile Clarity recordings on PDP
    Pinpoint the exact element causing 256 dead clicks before changing anything.
    ~2 h · analytics · Evolut (LP)
  2. Simplify the mobile variant selector
    Replace dropdowns with tap-friendly swatches to reduce taps to add to cart.
    ~1 day · theme edit · Evolut (LP)
  3. Make Add to Cart sticky on mobile PDP
    Keep the ATC button visible while scrolling to cut friction.
    ~2 h · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product → Add to Cart retention 3% vs 5–10% bandRecoverable $655/mo on mobile256 dead clicks on mobile17 mobile rage clicks
67
ICE i
I8·C6·E6
227
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Below-band leak with a behavioral signal (dead clicks) pointing to a likely unresponsive UI element
What's happening

Only 3% of mobile product viewers add to cart, below the 5–10% band, costing an est. $236/month.

  • View Product → Add to Cart3% vs 5–10%

Likely cause 288 mobile dead clicks suggest taps on unresponsive elements (e.g., variant/qty selectors) rather than true disinterest; confirm via session recordings.

Do this — in order
  1. Check Add to Cart button responsiveness on mobile PDP
    High dead-click count suggests taps may not be registering.
    ~2 h · theme edit · Evolut (LP)
  2. Simplify PDP variant and quantity selectors
    Redesign elements users tap without effect to reduce dead clicks.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart 3% vs 5–10% bandMobile recoverable $236/month498 dead clicks sitewide, 288 on mobile
67
ICE i
I7·C7·E6
228
Data-supportediSev 3 · majoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
28% vs a 40–60% floor on mobile's cart-to-checkout step is a major leak worth an estimated $186/month, and the fix lives entirely inside the cart drawer since there's no separate cart page.
What's happening

Only 28% of mobile carts reach checkout, well below the 40–60% band, unlike desktop's 75%.

  • Session → View Product85% far above 20–45% band
  • View Product → Add to Cart4% just below 5–10% band
  • Add to Cart → Begin Checkout28% vs 40–60% band
  • Begin Checkout → Purchase29% vs 40–60% band

Likely cause The slide-out drawer likely lacks a prominent checkout CTA or trust signals, causing shoppers to close it instead of proceeding; drawer UX vs shipping-cost shock are the two candidates.

Do this — in order
  1. Add a prominent sticky checkout button in the drawer
    Make the checkout CTA the largest, highest-contrast element in the slide-out cart.
    ~2 h · theme edit · Client dev
  2. Show shipping and returns info inside the drawer
    Reduce hesitation by stating shipping cost/returns policy directly in the cart drawer.
    ~2 h · copy · Client dev
  3. Enable express wallet buttons in the drawer
    Let mobile shoppers pay with Shop Pay/Apple Pay directly from the drawer without a full checkout page.
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
mobile Add to Cart→Begin Checkout retention 28% vs 40–60% bandrecoverable $186/monthmobile sitewide CR 0.27% vs 1.5–3.5% bandcart is a slide-out drawer with no /cart page
67
ICE i
I8·C6·E6
229
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile add-to-cart rate is 4%, below the 5-10% band, and shoppers scroll only 21% of the page on average.
What's happening

Mobile product-page visitors add to cart at just 4%, below the 5–10% band, with only 21% average scroll depth.

  • Session → View Product85% vs 20-45%
  • View Product → Add to Cart4% vs 5-10%
  • Add to Cart → Begin Checkout26% vs 40-60%
  • Begin Checkout → Purchase26% vs 40-60%

Likely cause Likely the Add to Cart CTA and key benefit info sit below the 21% average scroll point; check PDP layout order to confirm.

Do this — in order
  1. Move Add to Cart button above the fold
    21% average scroll means most visitors never reach a low CTA.
    ~2 h · theme edit · Evolut (LP)
  2. Shorten hero and benefits copy on PDP
    Reduce scrolling needed to reach the purchase decision.
    ~2 h · copy · Evolut (LP)
  3. Add a sticky Add to Cart bar on mobile PDP
    Keeps the CTA visible regardless of scroll position.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 4% vs 5–10% band$318/month recoverable revenue21% average mobile scroll depth
67
ICE i
I7·C6·E7
230
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Only 26% of mobile add-to-carts progress to checkout, well under the 40-60% band, with high dead-click volume suggesting drawer friction.
What's happening

Mobile shoppers add to cart but only 26% proceed to checkout, well under the 40-60% band.

  • Mobile Add to Cart → Begin Checkout26% vs 40-60%

Likely cause Cart drawer likely lacks a clear or reachable checkout CTA, or shows confusing shipping/trust info causing dead clicks.

Do this — in order
  1. Make the checkout button sticky and prominent in drawer
    327 monthly dead clicks suggest users are missing the CTA.
    ~2 h · theme edit · Client dev
  2. Add trust badges and shipping info inside the drawer
    Reassures shoppers before they'd otherwise leave.
    ~2 h · theme edit · Client dev
  3. Add express checkout buttons in the drawer
    Cuts steps for mobile shoppers reaching payment.
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
mobile Add to Cart→Begin Checkout 26% vs 40-60% band (recoverable $192/mo)mobile dead clicks 327/momobile rage clicks 34/mo
67
ICE i
I7·C6·E7
231
Data-supportediSev 3 · majoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Mobile cart-to-checkout retention (25%) sits far below the 40-60% band, an estimated $206/month in recoverable revenue.
What's happening

Mobile shoppers add to cart but only 25% proceed to checkout, versus a 40-60% healthy band.

  • Add to Cart → Begin Checkout (mobile)25% vs 40-60% band
  • View Product → Add to Cart (mobile)5% at floor of 5-10% band

Likely cause The slide-out cart drawer likely lacks a prominent checkout CTA or visible trust/shipping info, causing hesitation; confirm via drawer session recordings showing exits vs. clicks.

Do this — in order
  1. Add a sticky, high-contrast checkout button inside the drawer
    Makes the primary CTA impossible to miss so fewer shoppers exit unconverted.
    ~2 h · theme edit · Client dev
  2. Show shipping cost and returns info inside the drawer
    Removes the need to click away to find shipping/returns, a common abandonment trigger.
    ~2 h · theme edit · Client dev
  3. Add Shop Pay/Apple Pay express buttons to the drawer
    Cuts steps to checkout for the mobile shoppers most prone to abandoning.
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention 25% vs 40-60% bandrecoverable ~$206/month5316 mobile sessions
67
ICE i
I7·C6·E7
232
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
This is a clear below-band leak in the cart drawer itself, with behavioral data (dead clicks) supporting a friction diagnosis.
What's happening

Only 25% of mobile cart-adds reach checkout, well under the 40–60% band, pointing to drawer friction.

  • Add to Cart → Begin Checkout (mobile)25% vs 40–60% band
  • Add to Cart → Begin Checkout (desktop)71% above 40–60% band

Likely cause The mobile cart drawer likely lacks a prominent checkout CTA or trust/shipping info, causing hesitation; confirm via drawer recordings.

Do this — in order
  1. Make the checkout button sticky in the drawer
    Ensure the CTA sits above the fold without scrolling on mobile.
    ~2 h · theme edit · Client dev
  2. Show shipping threshold and returns copy in-drawer
    Reduce hesitation by surfacing trust info inline before checkout.
    ~2 h · copy · Client dev
  3. Add express wallet buttons inside the drawer
    Let shoppers skip straight to Apple Pay/Shop Pay from the cart.
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention 25% vs 40–60% band277/mo recoverable on this step314 dead clicks and 26 rage clicks recorded on mobile (Clarity)
67
ICE i
I7·C6·E7
233
Data-supportediSev 3 · majoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Second-largest leak by volume on the highest-traffic device, and fixable directly inside the existing cart drawer.
What's happening

Only 22% of mobile cart-adders reach checkout, well under the 40-60% band.

  • Add to Cart → Begin Checkout (Mobile)22% vs 40-60%
  • View Product → Add to Cart (Mobile)5% at band floor 5-10%

Likely cause The drawer likely lacks a prominent checkout CTA or shipping/returns reassurance, causing hesitation before committing to checkout.

Do this — in order
  1. Move the checkout button above the fold in the drawer
    Ensure the CTA is visible without scrolling inside the cart drawer.
    ~30 min · theme edit · Client dev
  2. Enable express wallet buttons in the drawer
    Let mobile shoppers pay via Shop Pay/Apple Pay directly from the drawer.
    ~30 min · theme edit · Client dev
  3. Add shipping and returns reassurance under cart items
    State the free-shipping threshold and return policy in the drawer.
    ~2 h · copy · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention 22% vs band 40-60%Recoverable ~$112/mo5,204 mobile sessions — the largest traffic segmentCart is a slide-out drawer, no /cart page
67
ICE i
I7·C6·E7
234
Data-supportediSev 3 · majoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Mobile is the majority of traffic but loses 3x more cart-holders than desktop before checkout even starts.
What's happening

Mobile Add to Cart→Begin Checkout is 22%, far below the 40–60% band; desktop is 74% on the same step.

  • Mobile Add to Cart → Begin Checkout22% vs 40–60%
  • Desktop Add to Cart → Begin Checkout74% vs 40–60%, above range

Likely cause Likely the slide-out cart drawer lacks a visible checkout path or trust info on small screens; compare drawer session recordings by device to confirm.

Do this — in order
  1. Add a sticky, prominent checkout button in the drawer
    Mobile users need one-tap access without scrolling the drawer.
    ~2 h · theme edit · Client dev
  2. Add express checkout buttons inside the drawer
    Shop Pay/PayPal shortcuts shorten the path to purchase on mobile.
    ~2 h · theme edit · Client dev
  3. Show shipping threshold and returns note in the drawer
    Builds trust and removes hesitation before checkout starts.
    ~30 min · copy · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention 22% vs 40–60% band (leak, ~$451/mo recoverable)Desktop same step is 74%, within/above band — this is mobile-onlyMobile carries 5,219 of total sessions, the majority of traffic
67
ICE i
I7·C6·E7
235
Data-supportediSev 2 · minoriInstrumentianalyticsi
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Shopify abandonedCheckouts: 21 vs orders: 20 in 30 daysShopify revenue $1,867.94 from 20 orders
236
Data-supportediSev 3 · majoriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 10% vs 40–60% band (30pts below floor, the worst gap in the whole funnel)Desktop recoverable ≈$1,580/monthcheckoutEditable: false
237
Data-supportediSev 3 · majoriInstrumentianalyticsi
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
22 abandoned checkouts vs 19 completed orders this month (Shopify)Only $1,648 revenue from 19 orders at $78 AOV
238
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Cart drawer likely lacks the trust/CTA elements needed to move mobile shoppers into checkout.
What's happening

Only 22% of mobile shoppers who add to cart proceed to checkout, half the expected 40–60%.

  • View Product → Add to Cart5% vs 5–10% (floor)
  • Add to Cart → Begin Checkout22% vs 40–60%

Likely cause Cart drawer likely lacks a prominent checkout CTA or shipping/trust info, causing hesitation; check drawer button visibility against low scroll depth (21%).

Do this — in order
  1. Add sticky checkout button to cart drawer
    Make the checkout CTA always visible above the fold in the drawer.
    ~2 h · theme edit · Client dev
  2. Add trust badges and shipping info in drawer
    Show returns policy and shipping threshold inside the drawer to reduce hesitation.
    ~2 h · copy · Client dev
  3. Add express checkout buttons in drawer
    Let mobile shoppers jump straight to Shop Pay/PayPal from the drawer.
    ~30 min · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention 22% vs 40–60% bandMobile Clarity: 315 dead clicks, 35 rage clicks, 21% avg scroll
67
ICE i
I8·C6·E6
239
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
30% cart-to-checkout on mobile is well below the 40–60% band and directly costs $181/month; the drawer itself is the point of failure.
What's happening

Only 30% of mobile shoppers who add to cart proceed to checkout, below the 40–60% band, costing ~$181/month.

  • View Product → Add to Cart4% vs 5–10% band
  • Add to Cart → Begin Checkout30% vs 40–60% band

Likely cause Drawer likely lacks a prominent checkout CTA or shows unexpected costs; compare drawer open rate to checkout-button click rate to isolate.

Do this — in order
  1. Make the drawer's Checkout button sticky and full-width
    Reduces steps needed to convert once the cart is open.
    ~30 min · theme edit · Client dev
  2. Add shipping/returns trust copy inside the drawer
    Removes hesitation from hidden costs or policy uncertainty.
    ~30 min · copy · Client dev
  3. Add express checkout buttons inside the drawer
    Lets mobile shoppers skip the full checkout form.
    ~30 min · checkout config · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention 30% vs 40–60% band$181/month recoverable revenueMobile dead clicks 235 (Clarity)Cart is a slide-out drawer with no separate /cart page
67
ICE i
I7·C5·E8
240
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Below-band conversion combined with low scroll depth points to a weak or unreachable add-to-cart moment.
What's happening

Only 4% of mobile product viewers add to cart, below the 5–10% band, missing about $290/month.

  • View Product → Add to Cart4% vs 5–10%

Likely cause Mobile PDP likely hides the add-to-cart button below the fold or lacks a clear value prop; distinguish via scroll-depth heatmaps versus dead-click locations.

Do this — in order
  1. Move Add to Cart button above the fold on mobile
    21% avg scroll means most shoppers never reach a lower CTA.
    ~2 h · theme edit · Evolut (LP)
  2. Add key benefit bullets near price on mobile PDP
    Gives shoppers a reason to buy without further scrolling.
    ~2 h · copy · Evolut (LP)
  3. Fix unresponsive elements causing mobile dead clicks
    189 dead clicks suggest taps landing on non-functional elements.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product → Add to Cart retention 4% vs 5–10% bandRecoverable ≈$290/monthMobile avg scroll depth only 21%Mobile dead clicks 189, rage clicks 26
67
ICE i
I7·C7·E6
241
TriangulatediSev 2 · minoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Below-band drawer-to-checkout conversion is losing shoppers who already added an item.
What's happening

33% of mobile cart-adders begin checkout, below the 40–60% band, losing roughly $213/month.

  • Add to Cart → Begin Checkout33% vs 40–60%

Likely cause The cart drawer likely lacks a prominent checkout CTA or shipping/trust info, causing hesitation; check CTA visibility vs shipping-cost surprise to distinguish.

Do this — in order
  1. Make the checkout button sticky and prominent in drawer
    A low ATC→checkout rate suggests the CTA is easy to miss on mobile.
    ~30 min · theme edit · Client dev
  2. Show shipping cost/threshold in the drawer
    Removes surprise costs that stall checkout progression.
    ~2 h · theme edit · Client dev
  3. Add express checkout wallets to the drawer
    Lets shoppers skip full checkout form entry directly from the drawer.
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart → Begin Checkout retention 33% vs band 40–60%Recoverable ≈$213/month188 dead clicks recorded on mobile
67
ICE i
I6·C6·E8
242
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile PDP conversion is below band floor and low scroll depth (21%) suggests shoppers aren't reaching the add-to-cart CTA or trust content.
What's happening

Only 4% of mobile product viewers add to cart, half the 5–10% band floor.

  • View Product → Add to Cart4% vs 5–10%

Likely cause Low mobile scroll depth (21%) points to the CTA/price being buried below the fold, or missing above-fold trust signals to justify the add-to-cart decision.

Do this — in order
  1. Move price and Add to Cart button above the fold
    Low 21% scroll depth means most never reach a lower CTA.
    ~2 h · theme edit · Evolut (LP)
  2. Add reviews/trust badge near the CTA
    Builds confidence before the shopper decides to add to cart.
    ~2 h · theme edit · Evolut (LP)
  3. Trim above-fold copy to lift effective scroll reach
    Shorter content surfaces the CTA sooner for mobile scrollers.
    ~1 day · copy · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 4% vs 5–10% bandmobile recoverablePerMonth $241mobile avgScrollPct 21%
67
ICE i
I7·C6·E7
243
Data-supportediSev 3 · majoriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most desktop carts never reach checkout
A carry-over above 100% is mathematically impossible and signals duplicate begin_checkout events, compounding the RED tracking verdict.
What's happening

Desktop Add to Cart→Begin Checkout shows 104% retention, above the 40-60% band ceiling.

  • Add to Cart → Begin Checkout104% vs 40-60%

Likely cause Begin_checkout event likely fires twice per session (e.g. on drawer open and checkout page load), or bot traffic re-triggers the event.

Do this — in order
  1. Check GTM trigger conditions for begin_checkout tag
    Confirm it only fires once per checkout attempt, not on every drawer open.
    ~2 h · analytics · Evolut (analytics)
  2. Add event de-duplication via session or cart token
    Prevents inflated checkout counts from repeated triggers.
    ~2 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Add to Cart → Begin Checkout retention 104% (band 40-60%)tracking verdict RED
244
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile ATC conversion sits below the 5-10% band floor, and mobile Clarity shows 175 dead clicks, suggesting shoppers are tapping non-functional elements on the PDP.
What's happening

Mobile View→Add to Cart retention is 4%, below the 5-10% band, losing an estimated $499/month.

  • View Product → Add to Cart4% vs 5-10%

Likely cause Add-to-cart button may sit below the fold on mobile PDP; 175 mobile dead clicks support a UI element not responding as expected.

Do this — in order
  1. Move Add to Cart button above the fold on mobile PDP
    Reduces scrolling needed to act; avg mobile scroll is only 21%.
    ~2 h · theme edit · Evolut (LP)
  2. Review Clarity recordings for PDP dead-click hotspots
    Identify which non-interactive elements shoppers are tapping.
    ~2 h · analytics · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product → Add to Cart retention 4% (band 5-10%)$499/mo recoverableMobile dead clicks 175, rage clicks 26
67
ICE i
I7·C6·E7
245
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
This is the worst-below-band leak on mobile, mobile's dominant traffic channel (3,359 sessions), and second-largest recoverable dollar figure.
What's happening

Only 4% of mobile product viewers add to cart, below the 5–10% band, losing an estimated $655/month.

  • Session → View Product84% strong vs 20–45% band
  • View Product → Add to Cart4% vs 5–10% band

Likely cause 21% average scroll depth suggests the Add-to-Cart CTA sits below the fold, or 171 dead clicks point to a non-responsive buy button.

Do this — in order
  1. Move Add to Cart button above the fold on mobile PDP
    21% scroll depth means most visitors never reach the current CTA
    ~2 h · theme edit · Evolut (LP)
  2. Add a sticky Add-to-Cart bar on mobile
    Keeps the CTA visible regardless of scroll position
    ~1 day · theme edit · Evolut (LP)
  3. Investigate the 171 mobile dead clicks on PDP elements
    Dead clicks indicate shoppers tapping something non-functional
    ~2 h · analytics · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 4% vs 5–10% bandRecoverable ~$655/month on mobileMobile average scroll depth 21%Mobile dead clicks: 171
67
ICE i
I8·C5·E7
246
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile drives the majority of sessions (3,090) yet converts to cart at roughly half the band floor.
What's happening

Only 3% of mobile product viewers add to cart, about half the 5–10% band floor.

  • Session → View Product83% vs 20–45%, strong
  • View Product → Add to Cart3% vs 5–10%

Likely cause Low 22% scroll depth and 47 dead clicks suggest the add-to-cart control or key info isn't visible or isn't responding on mobile PDP; distinguish via layout vs load speed.

Do this — in order
  1. Move Add to Cart button above the fold on mobile
    22% average scroll means most shoppers never reach a lower CTA.
    ~2 h · theme edit · Evolut (LP)
  2. Review Clarity recordings for the 47 dead-click elements
    Identify which mobile PDP element shoppers tap without effect.
    ~1 day · analytics · Evolut (LP)
  3. Compress mobile PDP hero images
    Faster load reduces early exits before the CTA renders.
    ~2 h · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product → Add to Cart retention 3% vs 5–10% band$1,137/month recoverable revenue on mobile47 dead clicks and 22% average scroll depth on mobile (Clarity)
67
ICE i
I8·C6·E6
247
TriangulatediSev 3 · majoriInstrumentianalytics + behaviorali
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout → Purchase retention 19% vs 40–60% bandRecoverable revenue estimate $1,544/monthDesktop dead clicks 78, rage clicks 25 (Clarity)
248
Data-supportediSev 3 · majoriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile drives 3,003 sessions/month but only 3% of product viewers add to cart against a 5–10% band, leaving an estimated $1,146/month recoverable.
What's happening

Mobile View Product→Add to Cart sits at 3%, far under the 5–10% band, despite 82% of sessions reaching a product page.

  • Session → View Product82% vs 20–45% band, well above
  • View Product → Add to Cart3% vs 5–10%
  • Add to Cart → Begin Checkout44% vs 40–60%, healthy

Likely cause Mobile PDP CTA is likely hidden below the fold or slow to load; distinguish by checking add-to-cart tap position vs page-load timing.

Do this — in order
  1. Pin Add to Cart button above the fold
    Sticky mobile CTA keeps the button visible without scrolling.
    ~2 h · theme edit · Evolut (LP)
  2. Compress PDP hero images for mobile
    Faster load reduces bounce before the CTA is seen.
    ~2 h · theme edit · Evolut (LP)
  3. Simplify mobile PDP above-the-fold copy
    Surface price and primary benefit immediately to prompt add-to-cart.
    ~1 day · copy · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 3% vs 5–10% bandRecoverable ~$1,146/monthMobile sessions 3,003 (majority of traffic)
67
ICE i
I8·C6·E6
249
Data-supportediSev 3 · majoriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most desktop carts never reach checkout
A 100% carry-over from cart to checkout is not physically plausible and signals a measurement defect that undermines confidence in the desktop checkout leak finding.
What's happening

Desktop Add to Cart→Checkout shows 100% retention, an implausible value against the 40–60% band.

  • Add to Cart → Checkout100% vs 40–60% band

Likely cause begin_checkout is likely firing without a preceding real add-to-cart, or add-to-cart is under-firing; check GTM trigger logic vs event de-duplication.

Do this — in order
  1. Audit GTM triggers for add_to_cart and begin_checkout
    Confirms each event fires once and only on the correct action.
    ~2 h · analytics · Evolut (analytics)
  2. Cross-check Shopify checkout starts against GA4 events
    Validates the true desktop cart-to-checkout rate independent of tags.
    ~2 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Add to Cart→Begin Checkout retention 100% vs 40–60% bandDesktop sessions: 1,395/mo
250
Data-supportediSev 3 · majoriInstrumentianalyticsi
There is currently zero behavioral visibility into how shoppers actually use the site on either device
Without any behavioral session data, every funnel finding above rests on numbers alone and can't be visually confirmed or diagnosed further.
What's happening

Clarity recorded 0 sessions on both mobile and desktop, leaving no rage-click, dead-click or scroll data.

  • Mobile Clarity sessions0 no behavioral data collected
  • Desktop Clarity sessions0 no behavioral data collected

Likely cause The Clarity tracking snippet is likely not installed on live templates, or a consent/tag-manager rule is blocking it; check the theme/GTM install to tell which.

Do this — in order
  1. Verify the Clarity snippet is installed on all live templates
    Confirms the script is actually present on PDP, cart and checkout pages.
    ~30 min · analytics · Evolut (analytics)
  2. Check consent or tag-manager rules aren't blocking Clarity
    Consent gating can silently prevent session recording.
    ~30 min · analytics · Evolut (analytics)
  3. Confirm the Clarity project ID matches the live store
    A mismatched ID sends data to the wrong project, showing as zero sessions here.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
clarity.mobile.sessions=0clarity.desktop.sessions=0rage clicks, dead clicks and scroll depth all recorded as 0 on both devices
251
Data-supportediSev 3 · majoriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
This is the single deepest below-band step across both devices and carries the largest recoverable revenue ($1,211/mo) on the highest-traffic device.
What's happening

On mobile, only 3% of product viewers add to cart, well under the 5–10% band floor.

  • Session Start → View Product82% vs 20–45% band
  • View Product → Add to Cart3% vs 5–10% band
  • Add to Cart → Begin Checkout39% vs 40–60% band
  • Begin Checkout → Purchase47% vs 40–60% band

Likely cause Either the mobile Add-to-Cart CTA is not visible/reachable (below the fold, slow load), or a required selector (size/variant) blocks the tap; page-speed vs. layout audit distinguishes them.

Do this — in order
  1. Add a sticky mobile add-to-cart bar
    Keeps the CTA visible while scrolling long product pages, reducing drop-off before ATC.
    ~2 h · theme edit · Evolut (LP)
  2. Compress mobile product-page hero images
    Faster load reduces bounce before shoppers reach the Add to Cart button.
    ~2 h · theme edit · Evolut (LP)
  3. Move variant/size selector above the fold
    Removes an extra scroll/tap step that stalls mobile add-to-cart intent.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 3% vs band 5–10%Recoverable $1,211/monthMobile sessions 3,175 (30 days)Mobile sitewide CR 0.44% vs band 1.5–3.5%
67
ICE i
I8·C5·E7
252
Data-supportediSev 3 · majoriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
This is the single largest leak in the account: mobile View→Add to Cart sits at 3%, well under the 5–10% band, costing an estimated $897/month across 3,064 sessions.
What's happening

Mobile View→Add to Cart is 3%, far under the 5–10% band — the site's biggest leak.

  • Session → View Product82% vs 20–45% band
  • View Product → Add to Cart3% vs 5–10% band
  • Add to Cart → Begin Checkout40% vs 40–60% band
  • Begin Checkout → Purchase39% vs 40–60% band

Likely cause Mobile PDP likely hides or buries the Add-to-Cart CTA, or the page loads too slowly, but no session recordings exist yet to confirm which.

Do this — in order
  1. Add a sticky mobile Add-to-Cart bar
    Keeps the CTA visible while scrolling product details, cutting drop-off before add-to-cart.
    ~2 h · theme edit · Evolut (LP)
  2. Compress PDP hero images and video for mobile
    Faster loads reduce bounce before shoppers ever reach the Add to Cart button.
    ~2 h · theme edit · Evolut (LP)
  3. Verify Clarity recording is active on PDP
    Captures real mobile sessions to confirm whether CTA visibility or speed drives the drop.
    ~30 min · analytics · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product → Add to Cart retention is 3% vs 5–10% band floor3,064 mobile sessions/mo$897/mo recoverable revenue if restored to band floor
67
ICE i
I9·C5·E6
253
Data-supportediSev 3 · majoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
This is the step furthest below its band on the highest-traffic device, and carries the largest recoverable revenue of any leak in the snapshot.
What's happening

Mobile View→Add to Cart conversion is 3%, under half the 5–10% band floor, costing ~$880/month.

  • Session → View Product82% vs 20–45% band
  • View Product → Add to Cart3% vs 5–10% band
  • Add to Cart → Begin Checkout37% vs 40–60% band
  • Begin Checkout → Purchase45% vs 40–60% band

Likely cause Mobile PDP likely hides the CTA or trust cues below the fold, or variant selection adds friction; check tap-heatmaps once available vs page-speed logs to tell which.

Do this — in order
  1. Move Add-to-Cart button above the fold
    Puts the CTA in immediate view so shoppers don't have to scroll to convert.
    ~2 h · theme edit · Evolut (LP)
  2. Add price, reviews, and stock badge near CTA
    Builds instant confidence needed to tap add-to-cart on a small screen.
    ~2 h · copy · Evolut (LP)
  3. Simplify variant selector to one tap
    Removes extra steps that cause mobile shoppers to abandon before adding.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention is 3% vs the 5–10% band floorRecoverable ~$880/month on mobileMobile sessions 3,029/30 days, the largest traffic segment
67
ICE i
I8·C5·E7
254
Data-supportediSev 2 · minoriInstrumentianalyticsi
You have no behavioral data to explain why shoppers are leaving
Without working session-replay data, every leak above is diagnosed from funnel percentages alone — fixing this unlocks faster, higher-confidence prescriptions.
What's happening

Clarity shows 0 sessions on both devices despite 4,338 combined GA4 sessions, meaning no behavioral data is being captured.

  • Clarity mobile sessions0 vs 2,944 GA4 sessions
  • Clarity desktop sessions0 vs 1,394 GA4 sessions

Likely cause The Clarity snippet is likely missing, misconfigured, or blocked by consent-mode gating; check tag installation vs consent settings to distinguish.

Do this — in order
  1. Verify the Clarity snippet fires on all pages
    Use GTM preview or view-source to confirm the tag is actually present.
    ~30 min · analytics · Evolut (analytics)
  2. Check consent-mode isn't blocking Clarity from loading
    Ensure Clarity isn't gated behind a consent category it shouldn't need.
    ~30 min · analytics · Evolut (analytics)
  3. Reinstall Clarity via the Shopify app
    Rules out a theme-code conflict causing silent script failure.
    ~1 day · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Clarity mobile sessions: 0 vs 2,944 GA4 mobile sessionsClarity desktop sessions: 0 vs 1,394 GA4 desktop sessionsAll Clarity metrics (rage clicks, dead clicks, scroll, script errors, bot%) reporting 0
255
Data-supportediSev 3 · majoriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Largest dollar-recoverable leak in the funnel and clearly device-specific since desktop performs within band on the same step.
What's happening

Mobile visitors view products heavily but convert to Add to Cart at just 3% vs a 5–10% band.

  • Session→View Product82% far above 20–45% band
  • View Product→Add to Cart3% vs 5–10% band
  • Add to Cart→Begin Checkout33% vs 40–60% band
  • Begin Checkout→Purchase52% within 40–60% band

Likely cause Mobile PDP likely hides the Add-to-Cart button below the fold or loads slowly, versus price/trust friction deterring the tap.

Do this — in order
  1. Add sticky 'Add to Cart' bar on mobile PDP
    Keeps the CTA visible while scrolling to cut mobile-only drop-off.
    ~2 h · theme edit · Evolut (LP)
  2. Compress hero images to speed mobile PDP load
    Faster load reduces exits before the add-to-cart action.
    ~2 h · theme edit · Evolut (LP)
  3. Show trust badges and reviews above the fold on mobile
    Builds confidence needed for a quick add-to-cart decision.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 3% vs 5–10% band (40% below floor)Mobile recoverable revenue $808/monthDesktop View→Add to Cart retention 10% (top of band) shows the gap is mobile-specific
67
ICE i
I9·C5·E6
256
Data-supportediSev 3 · majoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Store uses a slide-out cart drawer (no /cart page), so this drop-off must be fixed inside the drawer itself, not on a cart page.
What's happening

29% of mobile cart-adds proceed to checkout, well under the 40–60% band, pointing to drawer friction.

  • Session Start → View Product81% vs 20–45%
  • View Product → Add to Cart4% vs 5–10%
  • Add to Cart → Begin Checkout29% vs 40–60%
  • Begin Checkout → Purchase49% vs 40–60%

Likely cause Drawer likely lacks a clear, prominent checkout CTA or hides shipping/fees; distinguish via drawer CTA visibility vs cost-transparency review.

Do this — in order
  1. Pin a prominent Checkout button in the drawer
    Improves CTA visibility to reduce mobile drop-off after adding to cart.
    ~30 min · theme edit · Client dev
  2. Add express checkout buttons inside the drawer
    Shop Pay/Apple Pay let shoppers skip straight to payment from the drawer.
    ~30 min · payment settings · Client dev
  3. Show shipping cost and returns policy in drawer
    Removes cost/uncertainty as a reason to abandon before checkout.
    ~1 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention is 29% vs the 40–60% bandRecoverable ~548/month on mobile (~$65,760/month at $120 AOV)Mobile sitewide CR is 0.44% vs the 1.5–3.5% band
67
ICE i
I8·C5·E7
257
Data-supportediSev 2 · minoriInstrumentibehaviorali
Behavioral tracking isn't capturing any sessions, hiding why shoppers leave
With zero recorded behavioral sessions despite 4,031 GA4 sessions, every funnel leak above can only be diagnosed from analytics numbers, not real shopper behavior.
What's happening

Clarity recorded 0 sessions on both devices despite 4,031 combined GA4 sessions this month.

  • Mobile Clarity sessions0 vs 2,641 GA4 mobile sessions
  • Desktop Clarity sessions0 vs 1,390 GA4 desktop sessions

Likely cause The Clarity tracking snippet likely isn't installed on the live theme, or the project ID doesn't match production; check the site source and Clarity dashboard to tell which.

Do this — in order
  1. Verify the Clarity snippet fires on the live site
    Zero sessions despite real traffic suggests the tag isn't installed or is blocked
    ~30 min · analytics · Evolut (analytics)
  2. Confirm the Clarity project ID matches the live theme
    A mismatched ID would silently send data nowhere useful
    ~30 min · analytics · Evolut (analytics)
  3. Set up device-level Clarity segments once fixed
    Enables mobile vs desktop behavioral diagnosis of the funnel leaks above
    ~2 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Clarity mobile sessions: 0 vs 2641 GA4 mobile sessionsClarity desktop sessions: 0 vs 1390 GA4 desktop sessionsAll Clarity metrics (rage clicks, dead clicks, scroll, script errors) reported as 0 on both devices
258
Data-supportediSev 2 · minoriInstrumentibehaviorali
No behavioral data exists to confirm why shoppers are dropping off
Every funnel-leak hypothesis above rests on analytics alone; without session recordings or click data the true cause can't be confirmed, capping confidence on all findings.
What's happening

Clarity recorded zero sessions on both devices this period, leaving no behavioral evidence to verify funnel leaks.

  • Mobile Clarity sessions0 no data captured
  • Desktop Clarity sessions0 no data captured

Likely cause Clarity tracking snippet likely isn't firing sitewide, or session sampling/filters are excluding all traffic; check install tag vs sampling config.

Do this — in order
  1. Verify Clarity snippet fires on all pages
    Confirms the tracking script is actually installed sitewide.
    ~30 min · analytics · Evolut (analytics)
  2. Check Clarity project sampling and filter settings
    Ensures sessions aren't being excluded before capture.
    ~30 min · analytics · Evolut (analytics)
  3. Re-check session counts after 48 hours
    Validates the fix before relying on behavioral data again.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Clarity mobile sessions=0, all behavioral metrics 0Clarity desktop sessions=0, all behavioral metrics 0
259
Data-supportediSev 3 · majoriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Second-largest below-band gap (13pts under floor) and second-highest recoverable revenue, directly limiting mobile purchases despite healthy top-of-funnel traffic.
What's happening

27% of mobile cart-adders begin checkout, well under the 40–60% band.

  • Session → View Product79% well above 20–45% band
  • View Product → Add to Cart4% vs 5–10% band
  • Add to Cart → Begin Checkout27% vs 40–60% band
  • Begin Checkout → Purchase71% above 40–60% band

Likely cause Likely cart-page friction (unclear CTA or missing cost info) or slow mobile load between cart and checkout; check cart-page speed vs CTA prominence.

Do this — in order
  1. Add accelerated checkout button to mobile cart
    Shop Pay button lets shoppers skip steps straight to checkout.
    ~30 min · checkout config · Client dev
  2. Show shipping estimate inside the cart drawer
    Prevents late cost surprises that stall mobile checkouts.
    ~2 h · theme edit · Client dev
  3. Simplify mobile cart to one prominent checkout CTA
    Reduces on-screen clutter and clarifies the next step.
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart → Begin Checkout retention 27% vs 40–60% band (leak)$887/mo recoverable revenueMobile sitewide CR 0.6% vs 1.5–3.5% band
67
ICE i
I8·C6·E6
260
TriangulatediSev 2 · minoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile add-to-cart sits right at the band floor, with low scroll depth and high dead-click counts suggesting the CTA isn't reachable or usable.
What's happening

Mobile View→Add to Cart is 5%, the very bottom of the 5–10% expected band.

  • View Product → Add to Cart (Mobile)5% vs 5–10% floor
  • Avg scroll depth (Mobile)25% low engagement

Likely cause Shoppers aren't scrolling far enough to reach the add-to-cart button (25% avg scroll), or dead clicks (232) show taps on unresponsive elements near it.

Do this — in order
  1. Move Add to Cart button above the fold on mobile
    With only 25% avg scroll, a lower CTA goes largely unseen.
    ~2 h · theme edit · Evolut (LP)
  2. Add a sticky add-to-cart bar on mobile PDP
    Keeps the purchase action visible regardless of scroll depth.
    ~1 day · theme edit · Evolut (LP)
  3. Review top mobile dead-click elements near PDP CTA
    232 dead clicks suggest shoppers tap something expecting a response.
    ~2 h · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart 5% vs 5–10% band floor ($163/mo recoverable)Mobile avg scroll depth 25%Mobile dead clicks 232 in 30 days
63
ICE i
I6·C6·E7
261
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Weak mobile PDP engagement (low scroll, high dead clicks) is capping add-to-cart at the bottom of its healthy band.
What's happening

Mobile View→Add to Cart sits at 5%, the band floor, alongside only 25% average scroll depth.

  • View Product → Add to Cart5% floor of 5–10% band
  • Avg scroll depth (mobile)25% low PDP engagement
  • Dead clicks (mobile)243 high non-responsive taps

Likely cause Shoppers are tapping non-interactive elements instead of the Add to Cart button, or the CTA sits below the 25% scroll fold; heatmaps will confirm which.

Do this — in order
  1. Move Add to Cart above the fold on mobile PDP
    25% average scroll means most shoppers never reach a buried CTA.
    ~2 h · theme edit · Evolut (LP)
  2. Add a sticky Add to Cart bar on mobile PDP
    Keeps the primary action reachable at any scroll position.
    ~1 day · theme edit · Evolut (LP)
  3. Review Clarity recordings behind the 243 mobile dead clicks
    Identify which non-clickable elements shoppers mistake for buttons.
    ~2 h · analytics · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 5%, at the floor of the 5–10% bandRecoverable ~31 add-to-carts/month (~$600 at $19.35 AOV)Mobile Clarity: 243 dead clicks, avg scroll depth only 25%
63
ICE i
I6·C6·E7
262
Data-supportediSev 2 · minoriInstrumentibehaviorali
Behavioral analytics session counts are missing, hiding the real friction story
Without session counts or page attribution, dead/rage click volumes can't be converted to rates or tied to a specific page.
What's happening

Clarity reports 0 sessions on both devices yet logs hundreds of dead clicks, making rates uncalculable.

  • Mobile Clarity sessions0 vs 262 dead clicks logged
  • Desktop Clarity sessions0 vs 183 dead clicks logged

Likely cause Clarity session counting is likely misconfigured or omitted from the export; verify project setup against the raw API export.

Do this — in order
  1. Verify Clarity session counting is enabled correctly
    Confirms whether the 0-session figure is a config bug or an export omission.
    ~30 min · analytics · Evolut (analytics)
  2. Identify and populate the worst-performing page field
    Currently blank, preventing page-level prioritization of dead clicks.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Clarity mobile sessions = 0 despite 262 dead clicks and 5 rage clicks loggedClarity desktop sessions = 0 despite 183 dead clicks and 12 rage clicks loggedworstPage field unresolved ('—')
263
Data-supportediSev 2 · minoriInstrumentianalyticsi
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
26 abandoned checkouts in the last 30 days (Shopify)89 completed ordersShopify revenue $2,898
264
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
This is the step furthest below its band on the highest-traffic device, with the largest recoverable monthly value.
What's happening

Only 3% of mobile product viewers add to cart, well under the 5–10% band, costing an est. $1983/month.

  • Session → View Product80% vs 20–45% band
  • View Product → Add to Cart3% vs 5–10% band
  • Add to Cart → Begin Checkout53% vs 40–60% band
  • Begin Checkout → Purchase43% vs 40–60% band

Likely cause Mobile Add-to-Cart button is likely hard to find/tap or product value isn't clear above the fold; 252 dead clicks suggest shoppers are tapping non-responsive elements near it.

Do this — in order
  1. Enlarge and reposition the mobile Add to Cart button
    High dead-click count near PDP suggests shoppers are missing or mis-tapping the current CTA.
    ~2 h · theme edit · Evolut (LP)
  2. Add a sticky mobile Add-to-Cart bar
    Keeps the CTA visible as users scroll past a 29% average scroll depth.
    ~1 day · theme edit · Evolut (LP)
  3. Surface price-per-serving and key benefit near the CTA
    Clarifies value without requiring more scrolling or reading.
    ~2 h · copy · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View→Add to Cart retention 3% vs band 5–10%Recoverable $1983/moMobile dead clicks: 252Mobile sessions: 3403
63
ICE i
I8·C5·E6
265
TriangulatediSev 3 · majoriInvestigateianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile View→Add to Cart retention is 3%, well under the 5–10% band, losing an estimated $687/month in recoverable revenue.
What's happening

Only 3% of mobile product viewers add to cart, far below the 5–10% band, losing ~$687/month.

  • Session Start → View Product82% vs 20–45% band
  • View Product → Add to Cart3% vs 5–10% band
  • Add to Cart → Begin Checkout47% vs 40–60% band
  • Begin Checkout → Purchase42% vs 40–60% band

Likely cause Likely an unresponsive Add to Cart button (287 mobile dead clicks) or weak product content (23% avg scroll); check click maps to distinguish.

Do this — in order
  1. Review mobile PDP click maps in Clarity
    Pinpoint exactly where the 287 dead clicks cluster near the Add to Cart area.
    ~2 h · analytics · Evolut (LP)
  2. Enlarge and anchor the Add to Cart button
    Make the CTA sticky so it's reachable without relying on the 23% average scroll.
    ~2 h · theme edit · Evolut (LP)
  3. Simplify above-fold product info
    Surface price, reviews and CTA higher so shoppers decide before they stop scrolling.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product → Add to Cart retention 3% vs band 5–10%Recoverable $687/moMobile dead clicks: 287Mobile avg scroll 23%
63
ICE i
I8·C6·E5
266
Data-supportediSev 3 · majoriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase 11% vs 40–60% bandDesktop recoverable $354/month23 abandoned checkouts vs 84 total orders (Shopify)
267
Data-supportediSev 3 · majoriInstrumentibehaviorali
Behavioral analytics can't confirm real visitor volume on either device
Zero session counts alongside non-zero click metrics indicate broken session tagging in Clarity
What's happening

Clarity shows 0 sessions per device yet logs hundreds of dead/rage clicks, so click rates can't be trusted.

  • Clarity Session Count0 vs expected >0

Likely cause Clarity's session or page-view tagging is likely misconfigured, undercounting sessions while still capturing click events.

Do this — in order
  1. Verify Clarity install snippet fires on every page
    A session counter stuck at 0 suggests partial or delayed script load.
    ~2 h · analytics · Evolut (analytics)
  2. Cross-check Clarity session counts against GA4 sessions
    Confirms whether the gap is a tagging bug or just a reporting delay.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Clarity mobile sessions: 0 despite 26 rage clicks and 288 dead clicksClarity desktop sessions: 0 despite 12 rage clicks and 210 dead clicks
268
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Below-band add-to-cart rate combined with very shallow scroll suggests shoppers aren't reaching purchase-decision content.
What's happening

Only 4% of mobile product viewers add to cart, below the 5–10% band, costing roughly $207/month.

  • Session → View Product85% vs 20–45%
  • View → Add to Cart4% vs 5–10%
  • Add to Cart → Begin Checkout27% vs 40–60%
  • Begin Checkout → Purchase31% vs 40–60%

Likely cause 21% avg scroll means the Add to Cart CTA and key benefits likely sit below the fold, or dead clicks (298) indicate shoppers tapping non-functional page elements.

Do this — in order
  1. Move Add to Cart button and key benefits above the fold
    21% avg scroll means most mobile shoppers never see current placement
    ~2 h · theme edit · Evolut (LP)
  2. Audit product page for elements causing dead clicks
    298 mobile dead clicks suggest shoppers tapping images/text expecting action
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart 4% vs 5–10% band$207/mo recoverable revenuemobile avg scroll depth 21%298 mobile dead clicks
63
ICE i
I7·C6·E6
269
TriangulatediSev 2 · minoriInvestigateianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Smallest single leak in dollar terms but sits at the top of the funnel where mobile volume (4,879 sessions) is highest.
What's happening

Only 4% of mobile product viewers add to cart, below the 5–10% band, costing about $54/month.

  • View Product → Add to Cart4% vs 5–10%

Likely cause 324 mobile dead clicks suggest shoppers tap a non-functional element (e.g., variant selector) instead of the Add to Cart button; confirm with recordings.

Do this — in order
  1. Watch mobile session recordings on PDP
    Locate where the 324 dead clicks cluster to identify the broken tap target.
    ~2 h · analytics · Evolut (LP)
  2. Enlarge and anchor the mobile Add to Cart button
    Make it sticky/visible without scrolling once the root cause is confirmed.
    ~2 h · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 4% vs 5–10% bandRecoverable ~$54/monthMobile dead clicks 324, rage clicks 34 (Clarity)
63
ICE i
I6·C6·E7
270
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
26% vs a 40–60% band inside the only cart surface (the drawer) is losing roughly 13 orders/month before checkout even starts.
What's happening

Only 26% of mobile add-to-cart shoppers begin checkout, below the 40–60% band, likely lost inside the cart drawer.

  • Add to Cart → Begin Checkout26% vs 40–60% band

Likely cause The drawer likely lacks a prominent checkout CTA or trust signals; 971 sitewide dead-clicks suggest shoppers tap non-functional elements.

Do this — in order
  1. Make the checkout button sticky in the drawer
    Keep the CTA above the fold and always visible inside the slide-out drawer.
    ~30 min · theme edit · Client dev
  2. Add a shipping/returns trust line to the drawer
    Reduce hesitation by showing delivery time and return policy inside the drawer.
    ~2 h · copy · Client dev
  3. Add express checkout buttons to the drawer
    Shop Pay/PayPal buttons let shoppers skip the extra step toward checkout.
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention 26% vs 40–60% band (leak, ~13 orders/month recoverable)Sitewide dead clicks 971 and avg scroll only 29%Store uses a slide-out cart drawer with no separate /cart page
63
ICE i
I7·C5·E7
271
Data-supportediSev 3 · majoriInstrumentianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Mobile Begin Checkout→Purchase 17% vs 40-60% bandDesktop Begin Checkout→Purchase 2% vs 40-60% bandShopify orders 19 vs abandoned checkouts 22 (~46% real completion)tracking verdict: RED
272
TriangulatediSev 2 · minoriInvestigateianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
High dead-click counts and shallow scroll depth suggest unresponsive or buried elements are stopping shoppers before add-to-cart, especially on mobile (21% avg scroll).
What's happening

952 dead clicks and just 29% average scroll depth suggest shoppers disengage before reaching add-to-cart.

  • View Product → Add to Cart (mobile)5% at floor of 5-10% band
  • Dead clicks (sitewide)952 638 desktop / 314 mobile
  • Avg scroll depth (mobile)21% low engagement

Likely cause Non-clickable elements (badges/images) are likely being tapped as if interactive, or the add-to-cart CTA sits below the fold; check Clarity recordings to tell them apart.

Do this — in order
  1. Watch 10 Clarity recordings on the top product page
    Identify exactly which elements shoppers are dead-clicking on.
    ~2 h · analytics · Evolut (LP)
  2. Move the add-to-cart button and trust badges above the fold
    Scroll depth of 21-37% means most shoppers never see content placed lower.
    ~1 day · theme edit · Evolut (LP)
  3. Make dead-clicked static elements inert or properly linked
    Reduces frustration behind the 191 rage clicks recorded.
    ~2 h · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
952 dead clicks sitewide (638 desktop / 314 mobile)191 rage clicks sitewide (165 desktop / 26 mobile)avg scroll depth 29% sitewide (37% desktop / 21% mobile)Mobile View→Add to Cart retention 5%, at floor of 5-10% band
63
ICE i
I6·C7·E6
273
TriangulatediSev 2 · minoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Retention sits at the very bottom of the acceptable band while scroll depth and dead clicks suggest key PDP content and CTAs aren't being seen or working.
What's happening

Mobile View→Add to Cart sits at just 5%, the bottom of its band, with shoppers scrolling only 21% of the page.

  • View Product → Add to Cart (mobile)5% floor of 5–10% band
  • Avg scroll depth (mobile)21% low engagement
  • Dead clicks (mobile)314 high vs 5,338 sessions

Likely cause Add-to-cart CTA or key info likely sits below the fold, or dead-click elements block taps; check PDP layout versus tap targets.

Do this — in order
  1. Move the Add to Cart button above the fold
    With only 21% average scroll, the CTA must be visible immediately.
    ~2 h · theme edit · Evolut (LP)
  2. Audit top dead-click elements on the PDP
    Identify non-functional elements causing 314 mobile dead clicks.
    ~2 h · theme edit · Evolut (LP)
  3. Compress above-fold PDP content on mobile
    Shorten hero/trust content so CTA appears sooner in the scroll.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View→Add to Cart retention 5%, at the floor of the 5–10% bandMobile avg scroll depth 21%314 dead clicks recorded on mobile (Clarity)
63
ICE i
I6·C6·E7
274
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Third-largest leak; the drawer is the only path from cart to checkout, so friction here directly blocks progression.
What's happening

Mobile shoppers add to cart but only 23% proceed to checkout, versus the healthy 40–60% band.

  • View Product → Add to Cart5% at 5–10% band floor
  • Add to Cart → Begin Checkout23% vs 40–60% band

Likely cause The cart drawer likely buries or weakens its checkout CTA, or lacks trust signals, causing shoppers to close it instead of proceeding.

Do this — in order
  1. Make checkout the drawer's single primary button.
    A buried or secondary checkout CTA is the top cause of drawer abandonment.
    ~2 h · theme edit · Client dev
  2. Add express wallet buttons inside the drawer.
    Lets shoppers skip an extra step entirely, raising carry-over to checkout.
    ~30 min · checkout config · Client dev
  3. Add trust badges and shipping/returns note in drawer.
    Reduces last-second doubt before shoppers commit to checkout.
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention 23% vs 40–60% band$145/month recoverable revenue on mobileStore uses a slide-out cart drawer, no separate /cart page
63
ICE i
I6·C6·E7
275
Data-supportediSev 3 · majoriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Mobile carries 5,198 of the 7,412 total sessions, so this mobile-only leak affects the majority of traffic.
What's happening

Mobile Add to Cart→Begin Checkout is 21% versus a 40–60% band and 70% on desktop.

  • Mobile Add to Cart → Begin Checkout21% vs 40–60%
  • Desktop Add to Cart → Begin Checkout70% vs 40–60%

Likely cause Mobile cart drawer likely lacks a persistent, visible checkout CTA or trust cues; session recordings of drawer taps vs scroll would confirm UI vs hesitation.

Do this — in order
  1. Make checkout button sticky in the mobile drawer
    Keeps the CTA visible without scrolling on small screens.
    ~2 h · theme edit · Client dev
  2. Add delivery estimate and trust badges to drawer
    Reduces last-second hesitation before advancing to checkout.
    ~2 h · theme edit · Client dev
  3. Add express checkout buttons inside the drawer
    Apple Pay/Shop Pay let mobile users skip manual steps entirely.
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout 21% vs 40–60% band ($679/mo recoverable)Desktop same step is 70%, well above mobile's rate
63
ICE i
I7·C5·E7
276
Data-supportediSev 3 · majoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Third-largest mobile leak, directly upstream of the checkout leak, compounding lost revenue.
What's happening

Only 20% of mobile carts reach checkout, half the 40–60% healthy floor.

  • Add to Cart → Begin Checkout20% vs 40–60%

Likely cause The cart drawer likely lacks a prominent checkout CTA or shows unexpected costs; cross-check against the 1,072 dead clicks recorded sitewide.

Do this — in order
  1. Move the checkout button above the fold in the drawer
    Make the sticky CTA visible with no scrolling needed inside the drawer.
    ~30 min · theme edit · Client dev
  2. Show free-shipping progress bar in the drawer
    Motivates completing checkout instead of closing the drawer.
    ~2 h · theme edit · Client dev
  3. Add express checkout buttons inside the drawer
    Shop Pay/PayPal buttons shorten the path from cart to purchase.
    ~1 day · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart → Begin Checkout retention 20% vs band 40–60%recoverable ≈$438/month
63
ICE i
I7·C5·E7
277
Data-supportediSev 3 · majoriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Mobile cart-to-checkout retention (21%) is roughly half the 40–60% band and far below desktop's healthy 61%, an estimated 462 lost checkouts a month.
What's happening

Mobile Add to Cart → Begin Checkout is 21%, well under the 40–60% band and desktop's 61%.

  • Mobile Add to Cart → Checkout21% vs 40–60%
  • Desktop Add to Cart → Checkout61% vs 40–60%

Likely cause The slide-out cart drawer likely lacks a prominent checkout CTA or express-wallet buttons on small screens; comparing drawer layouts by device would confirm.

Do this — in order
  1. Add a sticky, full-width checkout button in the drawer
    Make the primary CTA impossible to miss on small screens.
    ~2 h · theme edit · Client dev
  2. Enable Shop Pay, Apple Pay and PayPal express buttons
    Let mobile shoppers skip manual checkout entry entirely.
    ~30 min · theme edit · Client dev
  3. Show free-shipping threshold progress in the drawer
    Give mobile shoppers a reason to proceed instead of abandoning.
    ~2 h · copy · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart → Begin Checkout 21% vs 40–60% band~462 recoverable orders/month estimatedDesktop retention on same step is 61%
63
ICE i
I7·C5·E7
278
Data-supportediSev 3 · majoriInstrumentianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Mobile Begin Checkout→Purchase retention 17% vs 40–60% band (leak)Mobile recoverable ≈$1,461/monthMobile sessions 5,371 (largest traffic share)
279
Data-supportediSev 3 · majoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
The cart drawer isn't converting adds into checkout starts; this is fixable directly inside the drawer without needing checkout access.
What's happening

Only 20% of mobile shoppers who add to cart begin checkout, half the 40% floor.

  • Session → View Product88% vs 20–45% band (implausibly high)
  • View Product → Add to Cart5% at floor of 5–10% band
  • Add to Cart → Begin Checkout20% vs 40–60% floor
  • Begin Checkout → Purchase17% vs 40–60% floor

Likely cause The cart drawer likely lacks a clear checkout CTA or reveals shipping cost too late; compare drawer-open-to-checkout-click rate vs shipping threshold messaging.

Do this — in order
  1. Add a prominent checkout button atop the cart drawer
    Makes the next step obvious instead of leaving shoppers to close the drawer.
    ~30 min · theme edit · Client dev
  2. Show shipping cost or free-shipping threshold in drawer
    Hidden shipping costs are a leading cause of cart abandonment before checkout.
    ~30 min · copy · Client dev
  3. Add trust badges (secure checkout, returns) inside drawer
    Builds confidence to move from cart to checkout.
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention 20% vs 40–60% band (leak)Mobile recoverable ≈$1,054/month
63
ICE i
I7·C5·E7
280
Data-supportediSev 3 · majoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
This is a mobile-only leak — desktop's same step (73%) is healthy — so the fix lives in the mobile cart drawer, not the checkout itself.
What's happening

Only 21% of mobile Add-to-Cart shoppers reach Begin Checkout, vs a healthy 73% on desktop.

  • Mobile Add to Cart → Begin Checkout21% vs 40–60% band
  • Desktop Add to Cart → Begin Checkout73% vs 40–60% band (above ceiling)

Likely cause Likely the mobile drawer's checkout CTA is hard to find/tap or hidden below the fold; distinguish via drawer scroll depth vs button visibility in Clarity recordings.

Do this — in order
  1. Pin a full-width Checkout button at drawer top
    Make the primary CTA visible without scrolling on small screens.
    ~30 min · theme edit · Client dev
  2. Add express checkout buttons directly in drawer
    Shop Pay/Apple Pay buttons above the fold shortcut the tap-through to checkout.
    ~2 h · theme edit · Client dev
  3. Show free-shipping progress bar in drawer
    Gives shoppers a reason to proceed to checkout instead of closing the drawer.
    ~2 h · copy · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention is 21% vs 40–60% bandRecoverable ≈$566/month on mobileCart is a slide-out drawer (no /cart page)
63
ICE i
I7·C5·E7
281
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
The slide-out cart drawer likely has friction that stops shoppers from ever reaching checkout.
What's happening

Only 22% of mobile add-to-cart shoppers begin checkout, well under the 40-60% band.

  • Add to Cart→Begin Checkout22% vs 40-60%

Likely cause The cart drawer likely lacks a prominent checkout CTA or has a UI bug; distinguish via drawer session recordings vs a button-placement audit.

Do this — in order
  1. Make the checkout button sticky and full-width in the cart drawer
    Removes scrolling/searching needed to proceed since there's no separate /cart page.
    ~2 h · theme edit · Client dev
  2. Add express checkout wallet buttons inside the drawer
    Lets shoppers skip the full checkout form entirely from the drawer.
    ~30 min · checkout settings · Client dev
  3. Surface shipping and returns trust copy directly in the drawer
    Addresses hesitation before the shopper commits to checkout.
    ~1 day · copy · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention 22% vs 40-60% bandMobile dead clicks 322 and rage clicks 35 (Clarity)
63
ICE i
I7·C5·E7
282
Data-supportediSev 3 · majoriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
This is the second mobile leak in sequence — most cart adds die inside the drawer before checkout even starts.
What's happening

Only 25% of mobile shoppers who add to cart proceed to begin checkout, versus a 40–60% band.

  • Add to Cart → Begin Checkout25% vs 40–60% band

Likely cause The cart drawer's checkout button may be hard to find or trust signals (shipping/returns) are missing, causing shoppers to close the drawer instead of continuing.

Do this — in order
  1. Make the checkout button the drawer's most prominent element
    Increase size/contrast of the checkout CTA inside the drawer.
    ~2 h · theme edit · Client dev
  2. Add shipping and returns info inside the drawer
    Answer cost/return questions before shoppers leave the drawer.
    ~2 h · copy · Client dev
  3. Add express-checkout buttons directly in the drawer
    Let shoppers skip the standard checkout flow entirely.
    ~30 min · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention 25% vs 40–60% band$343/month recoverable revenueslide-out cart drawer (no /cart page)
63
ICE i
I7·C5·E7
283
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Only 26% of mobile carts reach checkout vs a 40-60% band, an estimated $345/month lost, likely drawer friction.
What's happening

Mobile Add to Cart → Begin Checkout is 26% vs a 40–60% band, losing about $345/month.

  • View Product → Add to Cart5% vs 5-10% floor
  • Add to Cart → Begin Checkout26% vs 40-60%

Likely cause Likely the cart drawer lacks a clear checkout CTA or trust/shipping info, or the 766 sitewide dead clicks show taps on non-functional elements.

Do this — in order
  1. Add a prominent sticky checkout button in the drawer
    Make the primary action unmissable right after adding to cart.
    ~2 h · theme edit · Client dev
  2. Show shipping and returns trust copy inside the drawer
    Answers cost and policy doubts without forcing a page navigation.
    ~2 h · copy · Client dev
  3. Add Shop Pay/Apple Pay express buttons in the drawer
    Lets ready buyers skip checkout entirely, recovering impatient shoppers.
    ~30 min · checkout config · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart → Begin Checkout retention 26% (band 40-60%)Recoverable ~$345/month766 dead clicks & 133 rage clicks sitewide (Clarity)Tracking verdict RED - treat as provisional
63
ICE i
I7·C5·E7
284
Data-supportediSev 3 · majoriInstrumentianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Mobile Begin Checkout→Purchase 24% vs band 40–60%Desktop Add to Cart→Begin Checkout 98% (band 40–60%)Desktop Begin Checkout→Purchase 9% vs band 40–60%Shopify: 24 orders + 17 abandoned checkouts = 41 total, ~58% completiontracking verdict RED
285
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
This is the first leak in the mobile funnel and compounds every downstream drop.
What's happening

Only 4% of mobile product-page viewers add to cart, just under the 5–10% floor.

  • View Product→Add to Cart4% vs 5–10%

Likely cause The Add to Cart button is likely below the fold given 21% avg scroll depth, or obscured by non-functional UI causing dead clicks.

Do this — in order
  1. Move Add to Cart button above the fold on mobile
    Avg scroll is only 21%, so most shoppers never reach a lower CTA
    ~2 h · theme edit · Evolut (LP)
  2. Audit and fix dead-click zones on product page
    225 mobile dead clicks suggest shoppers tap non-interactive elements expecting action
    ~2 h · theme edit · Evolut (LP)
  3. Add sticky add-to-cart bar on scroll
    Keeps CTA visible as shopper scrolls past current 21% depth
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 4% vs 5–10% bandrecoverable ~79 add-to-carts/monthmobile avg scroll 21%, dead clicks 225
63
ICE i
I6·C7·E6
286
TriangulatediSev 2 · minoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Below-band add-to-cart rate combined with very shallow scroll depth points to a visibility problem on the product page.
What's happening

Only 4% of mobile product viewers add to cart, just under the 5-10% band, costing ~$131/month.

  • Session → View Product86% vs 20-45% band
  • View Product → Add to Cart4% vs 5-10% band
  • Add to Cart → Begin Checkout31% vs 40-60% band

Likely cause The add-to-cart CTA is likely below the fold given 21% avg scroll; confirm via Clarity recordings showing where mobile sessions stop scrolling.

Do this — in order
  1. Move Add to Cart button above the fold on mobile
    Avg scroll is only 21%, so the CTA is probably unseen.
    ~2 h · theme edit · Evolut (LP)
  2. Add a sticky add-to-cart bar on mobile PDP
    Keep the CTA visible regardless of scroll position.
    ~1 day · theme edit · Evolut (LP)
  3. Tighten above-fold value proposition copy
    Clarify the benefit before the shopper decides to scroll away.
    ~2 h · copy · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 4% vs 5-10% bandMobile recoverable ~$131/monthMobile avg scroll depth only 21%
63
ICE i
I6·C6·E7
287
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Shoppers aren't scrolling far enough to see buying reasons or the add-to-cart control.
What's happening

Mobile add-to-cart rate is 4% vs a 5–10% band, while average scroll depth is only 21%.

  • View Product → Add to Cart4% vs 5–10%

Likely cause Key buying info or the add-to-cart control sits below the 21% scroll depth most mobile visitors reach.

Do this — in order
  1. Move Add to Cart button above the fold
    21% average scroll means most shoppers never reach a lower CTA.
    ~2 h · theme edit · Evolut (LP)
  2. Add a sticky add-to-cart bar on mobile PDP
    Keep the CTA accessible regardless of scroll position.
    ~2 h · theme edit · Evolut (LP)
  3. Surface key benefits and price near the top
    Give shoppers a reason to buy before they stop scrolling.
    ~1 day · copy · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart 4% vs 5–10% band$276/month recoverable revenue on mobileMobile average scroll depth 21%
63
ICE i
I6·C6·E7
288
Data-supportediSev 3 · majoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Drawer likely lacks a strong next step, and this fix lives entirely inside the drawer, not a cart page.
What's happening

32% of mobile cart-adds proceed to checkout, below the 40–60% band, leaking about $264/month.

  • Add to Cart → Begin Checkout32% vs 40–60%

Likely cause Drawer probably lacks a prominent checkout CTA or shipping/returns reassurance; distinguish via drawer session recordings versus CTA visibility checks.

Do this — in order
  1. Add a sticky, high-contrast checkout button in the drawer
    Makes the next step unmissable, cutting pre-checkout drop-off.
    ~2 h · theme edit · Client dev
  2. Show shipping threshold and returns policy in the drawer
    Removes the uncertainty that stalls shoppers before checkout.
    ~2 h · copy · Client dev
  3. Add Shop Pay/Apple Pay button inside the drawer
    One-tap express checkout skips steps between cart and purchase.
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart → Begin Checkout retention 32% vs 40–60% bandRecoverable ≈$264/monthCart is a slide-out drawer (no /cart page)
63
ICE i
I7·C5·E7
289
TriangulatediSev 3 · majoriInstrumentianalytics + behaviorali
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout → Purchase retention 17% vs band 40–60%Recoverable ≈$943/monthAdd to Cart → Begin Checkout is 94% (suspect, likely inflated)Tracking verdict RED — figures provisional
290
TriangulatediSev 2 · minoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Cart-drawer to checkout conversion is below band, and high dead-click volume (186) suggests shoppers are tapping non-functional elements instead of proceeding.
What's happening

34% of mobile cart-adders begin checkout, below the 40–60% healthy range.

  • Add to Cart → Begin Checkout34% vs 40–60%

Likely cause High mobile dead clicks (186) suggest shoppers tap unresponsive drawer elements rather than the real checkout button, or the button is easy to miss.

Do this — in order
  1. Make the drawer checkout button sticky and full-width
    Increases visibility and reduces mis-taps in the cart drawer.
    ~2 h · theme edit · Client dev
  2. Review Clarity recordings for dead-click hotspots in the drawer
    Pinpoints which elements shoppers mistake for functional controls.
    ~2 h · analytics · Client dev
  3. Add an express checkout button inside the drawer
    Lets ready-to-buy shoppers skip an extra step.
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention 34% vs 40–60% bandmobile recoverablePerMonth $162mobile deadClicks 186
63
ICE i
I6·C6·E7
291
Data-supportediSev 2 · minoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Mobile cart-to-checkout retention is 35%, below the 40-60% band, and since the store uses a slide-out drawer, the fix must live inside the drawer itself.
What's happening

Mobile Add to Cart→Begin Checkout is 35%, under the 40-60% band, losing about $246/month.

  • Add to Cart → Begin Checkout35% vs 40-60%

Likely cause Checkout button may not be prominent enough in the drawer, or missing trust/shipping info causes hesitation before proceeding.

Do this — in order
  1. Make checkout button sticky and full-width in the drawer
    Increases visibility so shoppers don't need to scroll to proceed.
    ~2 h · theme edit · Client dev
  2. Add trust badges and returns info inside the drawer
    Reduces hesitation at the point of proceeding to checkout.
    ~2 h · copy · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart → Begin Checkout retention 35% (band 40-60%)$246/mo recoverablecart is a slide-out drawer with no /cart page
63
ICE i
I6·C5·E8
292
Data-supportediSev 2 · minoriInstrumentianalyticsi
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
2enrateePct,page,26orders/1,759,Shopify rev,26,shopify revenue $2,396.19,abandoned checkouts 12
293
Data-supportediSev 3 · majoriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 16% vs 40–60% bandRecoverable ~$1480/moShopify: 13 abandoned checkouts vs 26 orders (33% abandonment)Desktop rage clicks 28, dead clicks 137
294
Data-supportediSev 3 · majoriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most desktop carts never reach checkout
A retention rate above 100% confirms event double-counting in the same tracking layer already flagged RED; these desktop mid-funnel numbers can't guide decisions yet.
What's happening

Desktop Add to Cart → Begin Checkout shows 130% retention, which cannot happen with real users.

  • Add to Cart → Begin Checkout130% vs 40–60%

Likely cause Likely a duplicate begin_checkout tag firing per session, or under-counted add_to_cart on quick-buy flows; check GTM trigger de-dup vs missing add_to_cart tags.

Do this — in order
  1. Audit begin_checkout and add_to_cart tag firing rules
    De-duplicate events firing on back-button navigation or re-renders.
    ~2 h · analytics · Evolut (analytics)
  2. Cross-check GA4 event counts against Shopify checkout starts
    Confirm true counts before trusting this transition again.
    ~2 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Add to Cart → Begin Checkout retention 130% vs 40–60% bandTracking verdict RED, -44% revenue divergence
295
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
3% is less than half the 5% band floor and represents the largest single recoverable dollar amount on mobile, despite 83% of sessions reaching the PDP.
What's happening

Mobile View→Add to Cart is 3%, under half the 5% band floor, despite 83% reaching the PDP.

  • Session → View Product83% vs 20–45% band (high)
  • View Product → Add to Cart3% vs 5–10%
  • Add to Cart → Begin Checkout43% vs 40–60%
  • Begin Checkout → Purchase34% vs 40–60%

Likely cause Low mobile scroll depth (22%) suggests the Add to Cart button or price sits below the fold, or the value proposition is unclear before scrolling; verify by checking PDP layout above the fold.

Do this — in order
  1. Move Add to Cart button and price above the fold
    22% average scroll means most mobile users never reach a below-fold CTA.
    ~2 h · theme edit · Evolut (LP)
  2. Shorten hero and description content on mobile PDP
    Gets shoppers to the buy box faster, reducing drop-off before Add to Cart.
    ~2 h · theme edit · Evolut (LP)
  3. Add a sticky Add to Cart bar on mobile PDP
    Keeps the CTA visible regardless of scroll position.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product → Add to Cart retention 3% vs 5–10% bandRecoverable revenue estimate $1,418/monthMobile average scroll depth 22%Mobile dead clicks 28
63
ICE i
I8·C5·E6
296
Data-supportediSev 3 · majoriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile drives the most traffic (2,970 sessions) but converts views to cart at just 3%, the single largest recoverable leak (~$965/mo); provisional given RED tracking.
What's happening

Mobile shoppers view products but add to cart at just 3%, well under the 5–10% band floor.

  • Session → View Product82% vs 20–45% band
  • View Product → Add to Cart3% vs 5–10% band
  • Add to Cart → Begin Checkout42% vs 40–60% band
  • Begin Checkout → Purchase36% vs 40–60% band

Likely cause Mobile PDP likely buries price/trust signals below the fold, or slow mobile load times suppress add-to-cart before shoppers decide; check page speed vs content placement.

Do this — in order
  1. Add a sticky mobile Add-to-Cart bar
    Keeps the CTA visible during scroll, removing a low-effort friction point.
    ~2 h · theme edit · Evolut (LP)
  2. Move price, reviews and shipping above the fold
    Mobile PDP may hide key decision info causing hesitation.
    ~1 day · copy · Evolut (LP)
  3. Audit mobile PDP load speed
    Slow load disproportionately suppresses add-to-cart on mobile.
    ~2 h · analytics · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 3% vs 5–10% band (leak)Recoverable ~$965/month on mobileMobile sessions: 2,970 in 30 daysMobile sitewide CR 0.34% vs 1.5–3.5% band
63
ICE i
I8·C5·E6
297
Data-supportediSev 2 · minoriInstrumentianalyticsi
Behavioral data is not being captured, so no visual evidence exists for why shoppers drop off
Without behavioral data, every funnel finding above rests on analytics alone, capping confidence and blocking root-cause diagnosis.
What's happening

Clarity shows zero recorded sessions on both devices despite thousands of GA sessions this window.

  • Mobile Clarity sessions0 vs 3,175 GA sessions
  • Desktop Clarity sessions0 vs 1,329 GA sessions

Likely cause The Clarity snippet is likely missing or misfiring on the live theme, or the dashboard project/date filter excludes this window.

Do this — in order
  1. Confirm Clarity script fires on the live theme
    Check theme.liquid or tag manager for the snippet and console errors.
    ~30 min · analytics · Evolut (analytics)
  2. Check Clarity project ID and date filters
    Ensure the correct project and 30-day range are selected before re-checking.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Clarity mobile sessions recorded: 0 vs GA mobile sessions 3,175Clarity desktop sessions recorded: 0 vs GA desktop sessions 1,329
298
Data-supportediSev 3 · majoriTestianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
This is the deepest below-band leak in the funnel and touches the most traffic, capping mobile revenue at $2128 GA4 total.
What's happening

Mobile product-page visitors add to cart at just 3%, far below the 5–10% band, capping mobile revenue.

  • Session → View Product82% above 20–45% band, strong
  • View Product → Add to Cart3% vs 5–10% band
  • Add to Cart → Begin Checkout39% just below 40–60% band
  • Begin Checkout → Purchase43% within 40–60% band

Likely cause Weak on-page conversion signals (buried Add-to-Cart button or unclear value prop) suppress carts; a PDP test isolates which.

Do this — in order
  1. Move Add-to-Cart button above the fold
    A sticky, prominent mobile ATC button cuts friction to purchase intent.
    ~2 h · theme edit · Evolut (LP)
  2. Add trust badges near price
    Guarantees/reviews next to price reduce buying hesitation.
    ~2 h · theme edit · Evolut (LP)
  3. Simplify PDP value proposition copy
    Clearer benefit statement helps shoppers decide faster to add to cart.
    ~1 day · copy · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
mobile View Product→Add to Cart retention 3% vs 5–10% bandmobile sessions 3139recoverable $1036/momobile sitewide CR 0.41% vs 1.5–3.5% band
63
ICE i
I8·C6·E5
299
Data-supportediSev 3 · majoriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile add-to-cart rate (3%) is below the 5–10% band and represents $840/mo in recoverable revenue from 2,966 sessions.
What's happening

Only 3% of mobile product-page visitors add to cart, well under the 5–10% band, despite strong page traffic.

  • Session → View Product82% vs 20–45%
  • View Product → Add to Cart3% vs 5–10%
  • Add to Cart → Begin Checkout38% vs 40–60%

Likely cause Mobile PDP CTA may be hard to reach or trust signals insufficient, causing hesitation; distinguishable via sticky-CTA rollout vs added trust badges.

Do this — in order
  1. Add sticky mobile Add-to-Cart bar
    Keeps the CTA visible while scrolling to reduce drop-off before adding to cart.
    ~2 h · theme edit · Evolut (LP)
  2. Show reviews and guarantee badge above the fold
    Builds trust immediately to counter hesitation on the mobile PDP.
    ~2 h · theme edit · Evolut (LP)
  3. Simplify PDP layout to one primary CTA
    Removes competing links that distract from adding to cart.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product → Add to Cart retention 3% vs 5–10% bandMobile recoverable revenue estimated $840/monthMobile sessions 2,966 in periodMobile sitewide CR 0.44% vs 1.5–3.5% band
63
ICE i
I8·C5·E6
300
Data-supportediSev 3 · majoriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
This step carries the biggest dollar opportunity ($909/mo) and sits at less than half the band floor, pointing to a mobile PDP conversion problem.
What's happening

Mobile View Product → Add to Cart is 3%, under half the 5–10% band floor, costing an est. $909/mo.

  • Session → View Product82% strong, above 20–45% band
  • View Product → Add to Cart3% vs 5–10% band
  • Add to Cart → Begin Checkout37% vs 40–60% band
  • Begin Checkout → Purchase45% within 40–60% band

Likely cause Mobile PDP likely buries the CTA or fails to build enough confidence before the add-to-cart decision; distinguish by checking CTA visibility vs missing trust/reviews above the fold.

Do this — in order
  1. Add a sticky Add to Cart bar on mobile PDP
    Keeps the CTA visible while scrolling instead of only appearing once, above the fold.
    ~2 h · theme edit · Evolut (LP)
  2. Surface reviews/trust badges above the fold
    Builds credibility earlier in the scroll to support the add-to-cart decision.
    ~2 h · theme edit · Evolut (LP)
  3. Simplify the variant/quantity selector
    Reduces taps between viewing and adding to cart on small screens.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product → Add to Cart retention 3% vs 5–10% bandMobile recoverable ~$909/mo — the largest single leak in the accountMobile sitewide CR 0.41% vs 1.5–3.5% bandMobile sessions: 2,944 (30 days)
63
ICE i
I8·C5·E6
301
Data-supportediSev 2 · minoriInstrumentianalyticsi
No behavioral data exists to explain why shoppers are dropping off
Every leak above is diagnosed from analytics numbers alone; without working session-recording data the real cause (UX vs technical) can't be confirmed.
What's happening

Clarity shows zero recorded sessions despite 4,195 GA4 sessions, leaving all funnel leaks undiagnosed at the UX level.

  • Clarity mobile sessions0 vs 2,830 GA4 mobile sessions
  • Clarity desktop sessions0 vs 1,365 GA4 desktop sessions

Likely cause The Clarity tracking snippet is likely missing or blocked on the live theme, versus a project-ID mismatch silently dropping data.

Do this — in order
  1. Verify the Clarity snippet fires on the live site
    Use browser dev tools to confirm the script loads on real pages.
    ~30 min · analytics · Evolut (analytics)
  2. Reinstall Clarity via Shopify app or theme.liquid
    Rules out app conflicts or caching blocking the snippet.
    ~2 h · analytics · Evolut (analytics)
  3. Confirm Clarity project ID matches the live domain
    A wrong ID sends zero data even with real traffic.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Clarity mobile sessions = 0 vs GA4 mobile sessions 2,830Clarity desktop sessions = 0 vs GA4 desktop sessions 1,365All Clarity metrics (rage clicks, dead clicks, scroll, script errors) reported as 0 on both devices
302
Data-supportediSev 3 · majoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Nearly three-quarters of mobile cart-adders drop off before checkout begins, and the fix lives entirely inside the drawer.
What's happening

Mobile Add to Cart → Begin Checkout retention is 28%, far below the 40–60% band.

  • Session → View Product80% vs 20–45% band (strong)
  • View Product → Add to Cart4% vs 5–10% band
  • Add to Cart → Begin Checkout28% vs 40–60% band
  • Begin Checkout → Purchase58% vs 40–60% band

Likely cause The drawer likely lacks a prominent checkout CTA or trust/shipping info; distinguish a missing CTA from missing trust signals by checking drawer scroll/tap behavior once tracking is fixed.

Do this — in order
  1. Add a prominent sticky checkout button in the drawer
    Makes the next step obvious instead of requiring extra scrolling or taps
    ~30 min · theme edit · Client dev
  2. Show shipping and returns info inside the drawer
    Builds trust before checkout since there is no dedicated cart page
    ~2 h · theme edit · Client dev
  3. Add Shop Pay/Apple Pay buttons to the drawer
    Lets mobile shoppers skip a step straight from the drawer
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart → Begin Checkout retention 28% vs 40–60% bandRecoverable ~$698/mo on mobileMobile sessions 2641 in the last 30 daysCart is a slide-out drawer with no separate /cart page
63
ICE i
I7·C5·E7
303
Data-supportediSev 2 · minoriInstrumentianalyticsi
You have no behavioral data to see why shoppers are dropping off
Every funnel finding above rests on GA4 numbers alone because Clarity recorded zero sessions on both devices, so root causes can't be confirmed with session replay yet.
What's happening

Clarity recorded 0 sessions on both devices this month despite thousands of GA4 sessions, leaving no behavioral evidence.

  • Clarity mobile sessions0 vs 2,596 GA4 mobile sessions
  • Clarity desktop sessions0 vs 1,370 GA4 desktop sessions

Likely cause The Clarity snippet is likely missing, misfiring, or blocked by consent settings; check tag installation vs consent gating.

Do this — in order
  1. Verify Clarity snippet fires on all pages
    Check theme/GTM install and browser console for errors.
    ~30 min · analytics · Evolut (analytics)
  2. Check consent banner isn't blocking Clarity
    Confirm the Clarity tag isn't gated behind an unconsented category.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Clarity mobile sessions 0 despite 2,596 GA4 mobile sessionsClarity desktop sessions 0 despite 1,370 GA4 desktop sessions
304
TriangulatediSev 2 · minoriInvestigateianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile add-to-cart rate sits at the bottom edge of its healthy band while dead clicks and low scroll suggest shoppers aren't reaching or engaging with the buying action.
What's happening

Mobile View→Add to Cart sits at the band floor (5%) alongside 294 dead clicks and only 24% average scroll depth.

  • View Product → Add to Cart (mobile)5% floor of 5–10% band
  • Avg Scroll Depth (mobile)24% low engagement

Likely cause Mobile PDP likely buries the Add-to-Cart button or key info below the fold, or shoppers are tapping non-functional elements; verify via heatmap of CTA position.

Do this — in order
  1. Move Add-to-Cart button above the fold on mobile
    Only 24% scroll depth means most shoppers never reach a buried CTA.
    ~2 h · theme edit · Evolut (LP)
  2. Review session recordings for top dead-click elements on PDP
    294 dead clicks suggest shoppers expect action from non-functional elements.
    ~2 h · analytics · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View→Add to Cart 5% vs 5–10% band (at floor)Mobile avg scroll depth 24%Mobile dead clicks 294
60
ICE i
I6·C5·E7
305
Data-supportediSev 2 · minoriInstrumentibehaviorali
Behavioral data volume can't be verified, so UX findings are directional only
A session count of 0 with real click events logged means the sample size behind behavioral findings is unverifiable.
What's happening

Clarity logs real dead-click events on both devices yet reports 0 sessions, an internal inconsistency.

  • Clarity mobile sessions0 inconsistent with 262 dead clicks logged
  • Clarity desktop sessions0 inconsistent with 126 dead clicks logged

Likely cause The session-count export field likely isn't syncing correctly; check the live Clarity dashboard rather than relying on this export.

Do this — in order
  1. Verify session totals directly in the Clarity dashboard
    Confirm true session volume behind the dead-click counts.
    ~30 min · analytics · Evolut (analytics)
  2. Check the Clarity snippet is installed on every template
    Ensures recording fires sitewide, not just on some pages.
    ~2 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Clarity mobile sessions reported as 0 alongside 262 logged dead clicksClarity desktop sessions reported as 0 alongside 126 logged dead clicks
306
TriangulatediSev 2 · minoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile sits at the very floor of the add-to-cart band, and shallow scrolling plus heavy dead-clicking point to an unseen or broken CTA.
What's happening

Mobile View→Add to Cart is 5%, the bottom edge of the 5–10% band, with shallow scrolling.

  • Session → View Product (mobile)72% well above 20–45%
  • View Product → Add to Cart (mobile)5% floor of 5–10%
  • Add to Cart → Begin Checkout (mobile)60% within 40–60%

Likely cause CTA likely sits below the fold (25% avg scroll) or dead clicks (230) hit non-functional elements mistaken for buttons; recordings would show which.

Do this — in order
  1. Move Add to Cart button above the fold on mobile PDP
    25% average scroll means most shoppers never reach a lower CTA
    ~2 h · theme edit · Evolut (LP)
  2. Audit top dead-click elements on mobile product pages
    230 dead clicks suggest shoppers tapping non-interactive elements
    ~2 h · theme edit · Evolut (LP)
  3. Trim above-fold PDP content to price, CTA, and one benefit
    Reduces scroll needed to reach the purchase action
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart 5% vs 5–10% band ($54/mo recoverable)Mobile avg scroll depth 25%Mobile dead clicks 230 in 30 days
60
ICE i
I4·C7·E7
307
TriangulatediSev 2 · minoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Low scroll depth plus a high dead-click count on mobile point to a concrete on-page obstacle stopping add-to-cart, not just a lower-funnel issue.
What's happening

Mobile View→Add to Cart sits at the 5% floor of its 5–10% band.

  • Session → View Product74% well above 20–45% band
  • View Product → Add to Cart5% at floor of 5–10% band
  • Add to Cart → Begin Checkout54% within 40–60% band

Likely cause The Add to Cart button or key product info sits below the fold (25% avg scroll), or dead clicks indicate non-functional tap targets near it.

Do this — in order
  1. Move Add to Cart button above the fold on mobile PDP
    Low 25% scroll depth means most shoppers never reach a lower CTA.
    ~2 h · theme edit · Evolut (LP)
  2. Audit dead-click zones on the mobile product page
    243 dead clicks suggest shoppers are tapping non-interactive elements expecting action.
    ~2 h · theme edit · Evolut (LP)
  3. Add a sticky add-to-cart bar on mobile PDPs
    Keeps the CTA reachable regardless of scroll position.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart 5% vs 5–10% band floorrecoverable ~9 orders/monthmobile dead clicks 243 (Clarity)mobile avg scroll depth 25%
60
ICE i
I5·C6·E7
308
Data-supportediSev 2 · minoriInstrumentibehaviorali
Behavioral session data isn't being captured, so UX problems are flying blind
Session counts of 0 alongside real click events mean the Clarity session tracker is misconfigured, undermining UX diagnosis.
What's happening

Clarity shows 0 sessions on both devices while still logging hundreds of dead/rage clicks, a tracking inconsistency.

  • Mobile Clarity Sessions0 vs non-zero click events
  • Desktop Clarity Sessions0 vs non-zero click events

Likely cause Session-count metric likely isn't wired to the same event pipeline as click tracking; check Clarity project config vs a sampling/filter rule excluding session totals.

Do this — in order
  1. Check Clarity project setup for session-count reporting
    Verify the snippet reports session totals, not just click events.
    ~30 min · analytics · Evolut (analytics)
  2. Confirm Clarity sampling rate is not set to exclude session counts
    A misconfigured sample rate can zero out aggregate session metrics.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Clarity mobile sessions: 0 despite 269 dead clicks and 12 rage clicks loggedClarity desktop sessions: 0 despite 203 dead clicks and 12 rage clicks logged
309
TriangulatediSev 2 · minoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile add-to-cart rate sits just under the 5% floor while dead clicks and low scroll depth suggest PDP interaction problems.
What's happening

Mobile product-page add-to-cart rate is 4%, just below the 5–10% band, alongside 294 dead clicks.

  • Session Start → View Product84% vs 20–45%
  • View Product → Add to Cart4% vs 5–10%

Likely cause Possibly a low-visibility Add-to-Cart button below the 22% average scroll depth, or a non-functional PDP element; check button placement vs recordings of dead clicks.

Do this — in order
  1. Move Add-to-Cart button above the fold
    Only 22% average scroll means most shoppers never reach a lower CTA.
    ~2 h · theme edit · Evolut (LP)
  2. Review 294 mobile dead clicks via session recordings
    Identify which PDP element shoppers tap without effect.
    ~2 h · analytics · Evolut (LP)
  3. Simplify PDP layout to surface CTA sooner
    Reduce content competing with the add-to-cart button.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart 4% vs 5–10% bandClarity mobile dead clicks 294Clarity mobile avg scroll 22%
60
ICE i
I6·C6·E6
310
TriangulatediSev 2 · minoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile's view-to-cart rate (4%) sits just under the 5–10% band floor, worth an estimated $113/month, and 288 dead clicks suggest shoppers are tapping non-interactive elements on PDPs.
What's happening

Mobile product pages convert to Add to Cart at 4%, just below the 5–10% band, with 288 dead clicks recorded.

  • View Product → Add to Cart4% just below 5–10% band

Likely cause A non-sticky or low-visibility Add to Cart button is likely causing dead clicks on price/image elements; button placement vs unclear pricing are the two candidates.

Do this — in order
  1. Add a sticky Add to Cart button on mobile PDPs
    Keep the CTA visible while scrolling to reduce lost intent from a 4% conversion rate.
    ~2 h · theme edit · Evolut (LP)
  2. Audit PDP elements causing 288 dead clicks
    Identify which images/text shoppers are tapping expecting interactivity.
    ~2 h · analytics · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
mobile View Product→Add to Cart retention 4% vs 5–10% bandrecoverable $113/monthmobile dead clicks 288
60
ICE i
I6·C5·E7
311
Data-supportediSev 3 · majoriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
A sharp drop between adding to cart and starting checkout on mobile points to friction inside the cart drawer itself.
What's happening

Only 25% of mobile shoppers who add to cart proceed to checkout, below the 40–60% band.

  • Add to Cart → Begin Checkout25% vs 40–60%

Likely cause The cart drawer likely buries the checkout CTA or omits shipping/trust info, causing shoppers to close it before proceeding.

Do this — in order
  1. Move checkout button to top of the cart drawer
    Ensures the CTA is visible without scrolling on mobile.
    ~30 min · theme edit · Client dev
  2. Add shipping threshold and returns note inside the drawer
    Answers common objections before the shopper exits.
    ~30 min · copy · Client dev
  3. Add express checkout buttons inside the drawer
    Lets shoppers skip straight to payment from the cart.
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention 25% vs 40–60% band$373/month recoverable on mobilecart is a slide-out drawer, no /cart page
60
ICE i
I6·C4·E8
312
Data-supportediSev 3 · majoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Cart-drawer friction is the likely mid-funnel blocker, sitting between the two other mobile leaks.
What's happening

Only 25% of mobile add-to-cart shoppers proceed to checkout, below the 40–60% band.

  • Add to Cart → Begin Checkout25% vs 40–60%

Likely cause The drawer likely lacks a prominent checkout CTA or reveals an unexpected shipping cost; distinguish via drawer recordings vs a shipping-cost audit.

Do this — in order
  1. Move the checkout button above the fold in the drawer
    Ensure the CTA is visible without scrolling inside the slide-out cart.
    ~30 min · theme edit · Client dev
  2. Show a shipping-threshold progress bar in the drawer
    Reduce surprise costs that cause drawer abandonment.
    ~2 h · theme edit · Client dev
  3. Add express checkout buttons inside the drawer
    Let shoppers jump straight to Apple Pay/Shop Pay from the cart drawer.
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention 25% vs 40–60% bandRecoverable ~$167/monthCart is a slide-out drawer (no /cart page)
60
ICE i
I6·C5·E7
313
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
A quarter of mobile cart-adds ever reach checkout, well under the 40% floor, pointing to drawer-level friction.
What's happening

26% of mobile add-to-cart sessions reach checkout, below the 40% floor, pointing to drawer friction.

  • Add to Cart → Begin Checkout26% vs 40–60% band

Likely cause The slide-out cart drawer likely buries the checkout button or omits shipping/trust info; high dead-click volume (325 on mobile) supports UI confusion over lack of intent.

Do this — in order
  1. Make the checkout button sticky and visible in the cart drawer
    The drawer is the only path to checkout; remove scrolling needed to find it.
    ~2 h · theme edit · Client dev
  2. Show shipping cost and returns info inside the drawer
    Removes a common pre-checkout hesitation without needing a cart page.
    ~30 min · copy · Client dev
  3. Add Shop Pay/PayPal express buttons inside the drawer
    Lets shoppers skip straight to checkout in one tap.
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention 26% vs 40–60% bandRecoverable ~6 orders/month per snapshot957 dead clicks and 199 rage clicks recorded sitewide in Clarity
60
ICE i
I6·C5·E7
314
Data-supportediSev 3 · majoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
The same transition is fine on desktop, pointing to a mobile-specific cart drawer problem rather than a demand issue.
What's happening

22% of mobile cart-adders reach checkout vs 71% on desktop for the identical step.

  • Add to Cart → Begin Checkout (Mobile)22% vs 40–60%
  • Add to Cart → Begin Checkout (Desktop)71% vs 40–60%

Likely cause Mobile drawer likely hides the checkout CTA below the fold or lacks visible trust/shipping info; Clarity drawer recordings would confirm which.

Do this — in order
  1. Pin checkout button to top of cart drawer
    Ensure the CTA is visible without scrolling on small screens
    ~2 h · theme edit · Client dev
  2. Add shipping/returns trust line inside drawer
    Reduce last-second hesitation before tapping checkout
    ~2 h · theme edit · Client dev
  3. Surface Shop Pay/Apple Pay buttons in the drawer
    Let mobile users skip to express checkout directly from the drawer
    ~30 min · checkout config · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout 22% vs 40–60% band, recoverable $852/moDesktop same step is healthy at 71%
60
ICE i
I7·C4·E7
315
TriangulatediSev 2 · minoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
At 4% add-to-cart rate, mobile PDPs are underperforming the 5–10% band, and only 21% average scroll suggests the CTA and key info aren't seen.
What's happening

Mobile shoppers add to cart at just 4%, below the 5–10% band, with only 21% average PDP scroll depth.

  • Session → View Product86% far above 20–45% band
  • View Product → Add to Cart4% vs 5–10% band

Likely cause Low add-to-cart likely stems from a below-the-fold CTA or unclear product benefits, given only 21% average scroll depth on PDP.

Do this — in order
  1. Move Add to Cart button above the fold on mobile PDP
    21% average scroll means most shoppers never reach a lower CTA.
    ~30 min · theme edit · Evolut (LP)
  2. Add concise benefit bullets near the price at the top
    Gives shoppers a reason to buy without needing to scroll.
    ~2 h · copy · Evolut (LP)
  3. Fix unresponsive PDP elements causing dead clicks
    235 mobile dead clicks suggest buttons or images that don't respond.
    ~2 h · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 4% vs 5–10% band$65/month recoverable revenueMobile average scroll depth 21%Mobile dead clicks 235, rage clicks 26 (Clarity)
60
ICE i
I6·C5·E7
316
Data-supportediSev 3 · majoriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Cart drawer likely lacks the CTA clarity or trust info needed to push shoppers into checkout.
What's happening

Mobile cart-to-checkout carry-over is 32% vs a 40–60% band, losing roughly $322/month.

  • Add to Cart → Begin Checkout32% vs 40–60%

Likely cause The cart drawer likely lacks a prominent checkout CTA or shipping/trust info, causing hesitation before proceeding.

Do this — in order
  1. Make the checkout button sticky in the drawer
    Ensure the CTA is the obvious next step once the drawer opens.
    ~30 min · theme edit · Client dev
  2. Add shipping and returns note in the drawer
    Answer cost and return questions before shoppers close the drawer.
    ~30 min · copy · Client dev
  3. Add express-pay buttons inside the drawer
    Let shoppers skip full checkout form entry.
    ~2 h · payment config · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout 32% vs 40–60% band$322/month recoverable revenue on mobileCart is a slide-out drawer with no separate /cart page
60
ICE i
I6·C5·E7
317
Data-supportediSev 2 · minoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Smallest of the funnel leaks but cheap to fix directly inside the existing drawer without touching the locked checkout page.
What's happening

37% of mobile cart-adds proceed to checkout, just under the 40-60% band.

  • Add to Cart → Begin Checkout37% vs 40-60%

Likely cause Drawer likely lacks a prominent checkout CTA or shipping/trust info; compare drawer layout against desktop's overperforming rate.

Do this — in order
  1. Make checkout button full-width and sticky in drawer
    Increase visibility of the primary CTA inside the slide-out cart.
    ~30 min · theme edit · Client dev
  2. Add shipping threshold/trust badges inside drawer
    Reduce hesitation before checkout without needing a cart page.
    ~2 h · theme edit · Client dev
  3. Add express checkout buttons in the drawer
    Let mobile shoppers skip steps directly from the drawer.
    ~1 day · checkout config · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart → Begin Checkout retention 37% vs 40-60% band$97/month recoverable revenueCart is a slide-out drawer (no /cart page)
60
ICE i
I5·C5·E8
318
Data-supportediSev 3 · majoriInstrumentianalyticsi
Desktop cart-to-checkout numbers are literally impossible to believe
A 110% carry-over from Add to Cart to Begin Checkout is mathematically impossible and signals broken event tracking, not real shopper behavior.
What's happening

Desktop shows 110% Add-to-Cart-to-Checkout retention, an impossible rate revealing broken tracking.

  • Add to Cart → Begin Checkout110% vs 40–60%, cannot exceed 100%

Likely cause Begin_checkout is firing multiple times per session, or add_to_cart is undercounted because express/buy-now paths skip that event.

Do this — in order
  1. Check if express/buy-now buttons skip the add_to_cart event
    These paths would inflate checkout starts relative to recorded cart adds.
    ~2 h · analytics · Evolut (analytics)
  2. Deduplicate begin_checkout firing per session in tag manager
    Prevents one checkout visit from logging multiple events.
    ~2 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Add to Cart → Begin Checkout retention 110% vs 40–60% band
319
Data-supportediSev 2 · minoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Secondary mobile leak — shoppers commit to a product but hesitate right before checkout in the drawer.
What's happening

Mobile shoppers add to cart but often don't start checkout — 37% vs the 40–60% band.

  • Add to Cart → Checkout37% vs 40–60% band
  • Checkout → Purchase47% within 40–60% band

Likely cause The slide-out drawer likely lacks a prominent checkout CTA or visible shipping/trust info, causing hesitation before checkout.

Do this — in order
  1. Pin high-contrast Checkout button in drawer
    Removes scrolling/searching for the CTA inside the drawer.
    ~30 min · theme edit · Client dev
  2. Show shipping/returns trust line in drawer
    Reduces hesitation from unknown shipping cost before checkout.
    ~30 min · copy · Client dev
  3. Add express wallet buttons in drawer
    Shop Pay/Apple Pay cut steps and may lift completion.
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
mobile Add to Cart→Checkout retention 37% vs 40–60% bandmobile recoverable revenue $118/mocart is a slide-out drawer (no /cart page)
60
ICE i
I5·C5·E8
320
Data-supportediSev 2 · minoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Retention is well below band right where the drawer experience should carry shoppers into checkout, and fixes are cheap theme-level changes.
What's happening

67% of mobile shoppers who add to cart abandon the drawer before starting checkout.

  • Add to Cart→Begin Checkout33% vs 40–60% band
  • Begin Checkout→Purchase52% within 40–60% band

Likely cause The drawer likely lacks a prominent checkout button or reassurance copy, versus shoppers using it only to review contents before leaving.

Do this — in order
  1. Make the checkout button full-width and above the fold
    Removes scrolling needed to find the primary action in the drawer.
    ~30 min · theme edit · Client dev
  2. Add shipping threshold and returns copy inside the drawer
    Answers common objections without leaving the drawer.
    ~2 h · copy · Client dev
  3. Enable Shop Pay/PayPal express buttons in the drawer
    Lets mobile users skip straight to one-tap checkout.
    ~30 min · checkout config · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention 33% vs 40–60% bandMobile recoverable revenue $348/monthStore uses a slide-out cart drawer with no separate /cart page
60
ICE i
I6·C5·E7
321
Data-supportediSev 3 · majoriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
This is the deepest proportional leak on mobile and sits right at the cart-drawer-to-checkout handoff, where drawer UX controls the outcome.
What's happening

Mobile cart-to-checkout retention is 28%, well under the 40–60% band, right where the drawer hands off to checkout.

  • View Product → Add to Cart4% vs 5–10% band
  • Add to Cart → Begin Checkout28% vs 40–60% band
  • Begin Checkout → Purchase65% within 40–60% band

Likely cause Shoppers likely can't find or trust the checkout button in the drawer, or shipping cost surprises them; check drawer CTA visibility vs shipping disclosure.

Do this — in order
  1. Make checkout button sticky and prominent in drawer
    Ensure one clear CTA is visible without scrolling on mobile.
    ~2 h · theme edit · Client dev
  2. Add trust badges and returns info inside drawer
    Build confidence to proceed without leaving the drawer.
    ~30 min · copy · Client dev
  3. Show free-shipping threshold progress in drawer
    Motivates completing checkout to hit the threshold.
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
mobile Add to Cart→Begin Checkout retention 28% vs band 40–60%mobile recoverable revenue $792/momobile sitewide CR 0.58% vs band 1.5–3.5%
60
ICE i
I7·C5·E6
322
Data-supportediSev 3 · majoriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Smallest but still real below-band leak; fixing it compounds with the downstream cart-to-checkout leak to lift total mobile revenue.
What's happening

Only 4% of mobile product viewers add to cart, just under the 5–10% band floor.

  • Session → View Product79% well above 20–45% band
  • View Product → Add to Cart4% vs 5–10% band
  • Add to Cart → Begin Checkout27% vs 40–60% band
  • Begin Checkout → Purchase71% above 40–60% band

Likely cause Likely weak on-page CTA visibility or missing purchase-decision cues (reviews, size guidance) on mobile PDP; check CTA placement vs content above the fold.

Do this — in order
  1. Add sticky Add to Cart bar on mobile product pages
    Keeps the CTA visible while shoppers scroll long PDPs.
    ~2 h · theme edit · Evolut (LP)
  2. Place reviews/trust badges next to Add to Cart button
    Builds confidence at the exact mobile decision point.
    ~2 h · theme edit · Evolut (LP)
  3. Simplify variant/size selector for one-tap add
    Fewer taps before adding reduces mobile drop-off.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product → Add to Cart retention 4% vs 5–10% band (leak)$446/mo recoverable revenueMobile sitewide CR 0.6% vs 1.5–3.5% band
60
ICE i
I6·C6·E6
323
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers repeatedly click things that don't respond
High dead-click volume and shallow scroll depth point to unresponsive UI elements frustrating users before they can convert.
What's happening

509 dead clicks and 32% avg scroll depth suggest users hit unresponsive elements before engaging with content.

  • Mobile dead clicks288 vs 221 desktop
  • Desktop dead clicks221 sitewide total 509
  • Avg scroll depth32% low engagement sitewide

Likely cause Likely non-functional buttons/links (e.g., accordions, size guides) or slow-loading scripts; review Clarity recordings to find which template drives most dead clicks.

Do this — in order
  1. Review Clarity recordings for top dead-click elements
    Identify which specific buttons/links fail to respond to prioritize fixes.
    ~2 h · analytics · Evolut (LP)
  2. Fix or remove non-functional UI elements
    Eliminate the dead/rage-click triggers found in recordings.
    ~1 day · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
509 dead clicks in 30 days (288 mobile, 221 desktop)26 rage clicks (22 desktop, 4 mobile)Avg scroll depth only 32% (24% mobile, 40% desktop)
57
ICE i
I6·C5·E6
324
TriangulatediSev 2 · minoriInvestigateibehavioral + analyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most product-page visitors never add to cart
Low scroll depth plus hundreds of dead clicks suggest shoppers aren't reaching or can't engage with key PDP content, capping Add-to-Cart at the low end of its band.
What's happening

Visitors scroll only 24–39% of product pages and generate 281 (mobile) and 215 (desktop) dead clicks.

  • Avg Scroll Depth (mobile)24% low engagement
  • Avg Scroll Depth (desktop)39% low engagement
  • Dead Clicks (mobile/desktop)281 / 215 high on both devices
  • View→Add to Cart (mobile)5% floor of 5–10% band

Likely cause Key CTA or trust content likely sits below the fold, or non-functional elements (accordions/images) are absorbing clicks; review Clarity recordings to tell these apart.

Do this — in order
  1. Move Add-to-Cart button and key trust content above the fold
    Low scroll depth means most shoppers never see lower-page content.
    ~2 h · theme edit · Evolut (LP)
  2. Review Clarity recordings for the highest dead-click elements
    Identify and fix non-functional accordions/images on product pages.
    ~2 h · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile avg scroll depth 24% / Desktop avg scroll depth 39%Mobile dead clicks 281 / Desktop dead clicks 215Desktop rage clicks 22Mobile View→Add to Cart retention 5% (band 5–10% floor)
57
ICE i
I6·C4·E7
325
TriangulatediSev 2 · minoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile add-to-cart sits right at the bottom edge of the healthy range, risking a slide into leak territory as traffic grows.
What's happening

Mobile product-page visitors add to cart at just 5%, the minimum edge of the 5-10% healthy band.

  • View Product → Add to Cart5% floor of 5-10% band

Likely cause Weak PDP conversion elements (CTA visibility, pricing clarity) or slow mobile load; PDP load-time data vs CTA placement will distinguish them.

Do this — in order
  1. Move Add to Cart button above the fold on mobile
    Reduces scrolling needed given only 24% avg mobile scroll depth
    ~2 h · theme edit · Evolut (LP)
  2. Simplify mobile pricing and subscription options
    Clearer pricing reduces hesitation before adding to cart
    ~1 day · copy · Evolut (LP)
  3. Compress mobile PDP images for faster load
    Faster loads typically correlate with higher add-to-cart rates
    ~2 h · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 5%, at the floor of the 5-10% band288 dead clicks recorded on mobileavg mobile scroll depth only 24%
57
ICE i
I5·C6·E6
326
TriangulatediSev 2 · minoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile sits exactly at the band floor; combined with shallow scroll depth this points to a persuasion or visibility gap on product pages.
What's happening

Mobile shoppers add to cart at just 5%, the bottom edge of the 5–10% healthy range.

  • Mobile View Product → Add to Cart5% vs 5–10%
  • Desktop View Product → Add to Cart11% vs 5–10%

Likely cause Likely the Add to Cart CTA or price sits below the fold, or slow mobile load delays interaction before users leave.

Do this — in order
  1. Pin Add to Cart button above the fold on mobile
    25% avg scroll depth means most users never reach a lower CTA.
    ~2 h · theme edit · Evolut (LP)
  2. Add price and key benefit near the top of the page
    Surface value proposition before users stop scrolling.
    ~2 h · copy · Evolut (LP)
  3. Compress mobile hero images for faster load
    Speed up time-to-interactive to cut early mobile drop-off.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart 5%, at the floor of the 5–10% band~$30/mo recoverableMobile avg scroll depth 25%
57
ICE i
I4·C7·E6
327
TriangulatediSev 2 · minoriInvestigateianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile sits at the very floor of the view-to-cart band, and high dead-click volume plus shallow scroll on the same device suggest a UI issue is suppressing add-to-cart.
What's happening

Mobile view-to-cart is 5%, the floor of its band, alongside 215 dead clicks and only 25% average scroll.

  • View Product → Add to Cart5% vs 5-10%
  • Dead clicks (mobile)215 high relative to desktop's 132

Likely cause Shoppers may be tapping non-functional elements (e.g. an accordion or swatch) that don't register, or the add-to-cart button sits below the fold at 25% average scroll.

Do this — in order
  1. Review mobile product-page recordings for dead-click elements
    Identify which tapped element isn't responding using Clarity session replays.
    ~2 h · theme edit · Evolut (LP)
  2. Make the Add to Cart button sticky on mobile product pages
    Keeps the CTA visible given only 25% average scroll depth.
    ~2 h · theme edit · Evolut (LP)
  3. Check mobile page load speed and image weight
    Slow loads can suppress scroll and interaction before CTA is seen.
    ~1 day · analytics · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 5% vs 5-10% band (at floor)215 dead clicks on mobile (Clarity)avg scroll depth 25% on mobile$21/month recoverable
57
ICE i
I5·C6·E6
328
TriangulatediSev 2 · minoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Sitting at the very bottom of the healthy band, paired with high dead-click counts, points to a PDP interaction problem.
What's happening

Only 5% of mobile product viewers add to cart, the lowest edge of the 5–10% healthy range.

  • View Product → Add to Cart5% vs 5–10%

Likely cause High mobile dead-clicks (238) suggest shoppers tap non-functional elements like size/variant selectors instead of reaching Add to Cart; confirm via session recordings.

Do this — in order
  1. Review Clarity recordings for mobile PDP dead-click hotspots
    Pinpoint exactly which tapped elements aren't registering
    ~2 h · analytics · Evolut (LP)
  2. Make the Add to Cart button sticky on mobile PDP
    Keeps the CTA visible while shoppers scroll product details
    ~2 h · theme edit · Evolut (LP)
  3. Simplify the mobile variant/size selector UI
    Likely source of dead clicks blocking the path to Add to Cart
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product → Add to Cart retention 5%, at the floor of the 5–10% band$179/mo recoverableMobile dead clicks: 238
57
ICE i
I4·C7·E6
329
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers are tapping things on the site that don't respond, and we don't know which pages
High dead-click volume signals broken or confusing UI elements, but missing page-level tagging means the exact location is unknown.
What's happening

Shoppers register 409 dead clicks sitewide with only 30% average scroll depth, but the worst page isn't identified.

  • Avg Scroll Depth30% sitewide
  • Dead Clicks409 mobile 238 / desktop 171

Likely cause Clarity isn't tagging individual page URLs (worstPage blank), a setup gap, rather than a single rogue page causing all the clicks.

Do this — in order
  1. Configure Clarity to tag and report worst-performing page URLs
    Without page tagging the dead-click source can't be diagnosed
    ~2 h · analytics · Evolut (LP)
  2. Audit the top-trafficked PDP for elements styled as buttons that aren't clickable
    Common cause of dead clicks that silently suppress engagement
    ~2 h · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
409 total dead clicks (mobile 238 / desktop 171)Average scroll depth only 30% sitewideworstPage not identified ('—') in Clarity
57
ICE i
I5·C5·E7
330
TriangulatediSev 2 · minoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile product pages convert to cart at the bottom edge of the healthy range, and shallow scroll depth suggests shoppers aren't reaching the CTA.
What's happening

Mobile View→Add to Cart is 5%, the floor of the 5–10% band, with only 24% average scroll depth.

  • Session → View Product74% vs 20–45%
  • View → Add to Cart5% at floor of 5–10%
  • Add to Cart → Begin Checkout51% within 40–60%

Likely cause Low scroll depth suggests the add-to-cart CTA or value copy sits below the fold on mobile; distinguish via page-level scroll heatmaps on top PDPs.

Do this — in order
  1. Move Add to Cart button and benefit copy above the fold
    Only 24% of mobile scroll depth is reached; put the CTA where it's seen.
    ~2 h · theme edit · Evolut (LP)
  2. Add a sticky mobile add-to-cart bar
    Keeps the CTA accessible without further scrolling.
    ~2 h · theme edit · Evolut (LP)
  3. Trim above-fold image weight for faster PDP load
    Speeds time-to-CTA visibility on mobile.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product → Add to Cart retention 5%, at the floor of the 5–10% bandMobile recoverable ~41 adds/monthMobile avg scroll depth 24%Mobile dead clicks: 247 (Clarity)
57
ICE i
I6·C5·E6
331
Data-supportediSev 2 · minoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
37% of mobile cart adds proceed to checkout, just under the 40–60% band — a smaller but real leak worth roughly $56/month.
What's happening

Mobile cart-to-checkout carry-over is 37%, slightly below the 40–60% band.

  • Add to Cart → Begin Checkout37% vs 40–60% band

Likely cause The slide-out cart drawer may lack a prominent checkout button or trust signals, causing hesitation; compare drawer CTA visibility against shipping-cost transparency.

Do this — in order
  1. Make the checkout button full-width and sticky in the cart drawer
    Improves visibility of the next step since there's no separate cart page.
    ~30 min · theme edit · Client dev
  2. Add trust badges and return policy inside the cart drawer
    Builds confidence before committing to checkout.
    ~30 min · copy · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart → Begin Checkout retention 37% vs 40–60% bandRecoverable ≈$56/month
57
ICE i
I4·C5·E8
332
Data-supportediSev 3 · majoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
The drawer likely lacks a clear path or trust signals to move shoppers forward, below the 40–60% healthy band.
What's happening

Mobile cart-to-checkout conversion is 33%, below the 40–60% healthy band.

  • Add to Cart → Begin Checkout33% vs 40–60%

Likely cause The cart drawer likely lacks a prominent checkout CTA or trust/shipping info, or shoppers close it to keep browsing; check drawer click-maps to confirm.

Do this — in order
  1. Add a prominent sticky Checkout button inside the cart drawer
    Makes the next step obvious without needing a separate cart page.
    ~2 h · theme edit · Client dev
  2. Show shipping threshold and trust badges in the drawer
    Answers cost/trust hesitations right where shoppers are deciding.
    ~2 h · copy · Client dev
  3. Add express checkout buttons inside the drawer
    Shortens the path from cart to purchase for mobile shoppers.
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention 33% vs 40–60% band$151/mo recoverable revenue on mobileCart is a slide-out drawer (no separate /cart page)
57
ICE i
I5·C5·E7
333
TriangulatediSev 3 · majoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile View→Add to Cart sits at 4% vs the 5-10% band floor, compounding the downstream checkout leak.
What's happening

Only 4% of mobile product viewers add to cart, below the 5-10% band, alongside a thin 21% average scroll.

  • Session → View Product85% above 20-45% band
  • View Product → Add to Cart4% vs 5-10% band

Likely cause Key benefit/price/CTA content may sit below the fold given only 21% average scroll; distinguish slow PDP load from poor content placement via a load-time check.

Do this — in order
  1. Move price, reviews, and Add to Cart above the fold
    Avg scroll is only 21%, so most PDP content goes unseen.
    ~1 day · theme edit · Evolut (LP)
  2. Add a sticky Add to Cart bar on mobile PDP
    Keeps the CTA reachable without scrolling.
    ~2 h · theme edit · Evolut (LP)
  3. Check mobile PDP load speed
    Slow rendering could be causing early exits before scroll.
    ~2 h · analytics · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 4% vs 5-10% bandMobile avgScroll 21%Mobile deadClicks 303
57
ICE i
I6·C5·E6
334
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
High dead-click volume on mobile points to a drawer UI issue directly blocking this step.
What's happening

Only 26% of mobile shoppers who add to cart proceed to checkout, below the 40–60% band.

  • View → Add to Cart4% vs 5–10% band
  • Add to Cart → Checkout26% vs 40–60% band

Likely cause Cart drawer checkout CTA may be unclear or below the fold, or dead clicks (307) indicate shoppers tapping non-functional elements in the drawer.

Do this — in order
  1. Make checkout button sticky and full-width in mobile drawer
    Ensures the primary action is always visible without scrolling.
    ~30 min · theme edit · Client dev
  2. Fix or remove elements generating dead clicks in the drawer
    Non-functional taps are actively costing conversions.
    ~2 h · theme edit · Client dev
  3. Add secure-checkout and free-returns copy inside drawer
    Builds confidence to proceed past add-to-cart.
    ~30 min · copy · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention 26% vs 40–60% bandMobile recoverable revenue $393/moMobile dead clicks: 307 (Clarity)Tracking verdict RED — treat as provisional
57
ICE i
I6·C5·E6
335
TriangulatediSev 3 · majoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Low scroll depth plus a high dead-click count on mobile product pages suggest shoppers aren't reaching or can't use the add-to-cart CTA.
What's happening

Mobile product-page visitors add to cart only 4% of the time, just under the 5–10% band floor.

  • View Product → Add to Cart4% vs 5–10%

Likely cause Low scroll depth (21% avg) suggests the CTA sits below the fold; 310 mobile dead clicks hint at non-functional elements shoppers try to tap.

Do this — in order
  1. Move Add to Cart button and price above the fold
    21% average scroll means most visitors never reach the current CTA.
    ~2 h · theme edit · Evolut (LP)
  2. Audit and fix dead-click elements on mobile PDP
    310 dead clicks suggest unresponsive elements frustrating shoppers.
    ~2 h · theme edit · Evolut (LP)
  3. Add a sticky Add to Cart bar on mobile PDP
    Keeps the CTA accessible regardless of scroll position.
    ~2 h · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 4% vs 5–10% band$121/month recoverable on mobilemobile average scroll depth 21%819 dead clicks sitewide (310 on mobile)
57
ICE i
I5·C5·E7
336
TriangulatediSev 2 · minoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile add-to-cart rate sits below the healthy 5-10% band, and low scroll depth suggests key content isn't being seen.
What's happening

Only 4% of mobile product viewers add to cart, below the 5-10% band, with average scroll just 21%.

  • Mobile View Product → Add to Cart4% vs 5-10%

Likely cause Low scroll depth (21%) suggests the Add to Cart button or key benefits sit below the fold on mobile product pages.

Do this — in order
  1. Move Add to Cart button above the fold
    21% average scroll means most never reach a lower CTA.
    ~2 h · theme edit · Evolut (LP)
  2. Add key benefit bullets near the price
    Surfaces value props early so scroll depth matters less.
    ~2 h · copy · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
mobile View Product→Add to Cart 4% vs 5-10% band (recoverable $49/mo)mobile avg scroll 21%mobile dead clicks 327/mo
57
ICE i
I5·C5·E7
337
TriangulatediSev 2 · minoriJust Do Itianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
A smaller gap than checkout, but still below floor and affects the largest traffic segment (5,292 mobile sessions).
What's happening

Only 4% of mobile product viewers add to cart, just under the 5% floor.

  • View Product → Add to Cart4% vs 5–10% band

Likely cause The add-to-cart button may sit below the fold or variant selection may confuse shoppers; 21% average scroll depth suggests most never reach a lower button.

Do this — in order
  1. Move the Add to Cart button above the fold on mobile PDP
    Avg mobile scroll is only 21%, so most visitors never reach a lower button.
    ~2 h · theme edit · Evolut (LP)
  2. Simplify variant/size selection UI on the product page
    Reduce the 325 mobile dead clicks likely caused by confusing selectors.
    ~2 h · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 4% vs 5–10% bandRecoverable ~2 orders/month per snapshot325 dead clicks and 34 rage clicks on mobile (Clarity), avg scroll only 21%
57
ICE i
I5·C5·E7
338
Data-supportediSev 2 · minoriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most desktop carts never reach checkout
An implausibly high carry-over combined with the RED tracking verdict suggests this number is inflated, not a real strength.
What's happening

Desktop cart-to-checkout carries over at 77%, above the 40–60% band, implausible given the RED tracking status.

  • Add to Cart → Begin Checkout77% vs 40–60% band

Likely cause Duplicate begin_checkout tags or double-counted GA4 events likely inflate this rate; compare GTM tag-fire counts to actual Shopify checkout starts to confirm.

Do this — in order
  1. Audit GTM for duplicate begin_checkout triggers on desktop
    Rule out double-firing before trusting this metric for decisions.
    ~2 h · analytics · Evolut (analytics)
  2. Compare Shopify checkout-started count to GA4 begin_checkout count
    Confirms whether the 77% figure is real or a tracking artifact.
    ~2 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Add to Cart→Begin Checkout retention 77% vs 40–60% band (above range)Tracking verdict RED with -38% revenue divergence
339
Data-supportediSev 2 · minoriInvestigateibehaviorali
Visitors are clicking things that don't work and barely scrolling the page
Broken or confusing UI elements are frustrating visitors before they ever reach cart or checkout, likely suppressing every step below.
What's happening

High dead/rage clicks (1,000/191) and shallow scroll depth (29% avg) suggest UI elements aren't behaving as expected.

  • Dead clicks (desktop)695 high for the traffic volume
  • Dead clicks (mobile)305 high for the traffic volume
  • Avg scroll depth29% low engagement with page content

Likely cause Likely non-interactive elements (swatches, accordions, badges) styled to look clickable; session recordings would confirm exact elements.

Do this — in order
  1. Review recordings for the top dead/rage-click elements
    Pinpoint exact elements users try to click that don't respond.
    ~2 h · analytics · Evolut (LP)
  2. Fix or restyle the flagged non-interactive elements
    Removes friction once specific culprits are identified.
    ~1 day · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
1,000 dead clicks and 191 rage clicks sitewide in 30 days (desktop: 695 dead/165 rage; mobile: 305 dead/26 rage)Average scroll depth only 29% (mobile 21%, desktop 37%)
57
ICE i
I6·C5·E6
340
Data-supportediSev 3 · majoriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
An upstream leak unique to mobile that compounds the downstream checkout collapse.
What's happening

Mobile cart-to-checkout retention is 22% vs the 40–60% band, while desktop hits a healthy 72%.

  • View Product → Add to Cart5% at floor of 5–10% band
  • Add to Cart → Begin Checkout22% vs 40–60%, desktop 72%

Likely cause Likely mobile cart-drawer friction (hidden or hard-to-reach checkout CTA) rather than lost interest, given desktop performs well on the identical step.

Do this — in order
  1. Make the checkout button sticky in the cart drawer
    Mobile users may not scroll far enough to see the CTA today.
    ~30 min · theme edit · Client dev
  2. Show free-shipping progress bar in the drawer
    Nudges shoppers to proceed instead of closing the drawer.
    ~2 h · copy · Client dev
  3. Auto-open the drawer with checkout CTA visible on add
    Immediate next-step visibility reduces mobile drop-off.
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart → Begin Checkout retention 22% vs 40–60% bandRecoverable ~$1,003/moDesktop's same step is 72%, healthy
57
ICE i
I7·C4·E6
341
Data-supportediSev 3 · majoriInvestigateibehaviorali
Visitors repeatedly click things on the site that don't respond, and most never scroll far
High dead-click volume paired with shallow scroll suggests broken or confusing page elements are suppressing engagement across the site.
What's happening

1073 dead clicks and 29% average scroll depth indicate visitors disengage before seeing most page content.

  • Dead clicks (Desktop)710 high
  • Dead clicks (Mobile)363 high
  • Avg scroll depth29% low engagement

Likely cause Non-interactive visual elements (badges, disabled buttons, images) may look clickable, or key CTAs sit below the fold where most sessions drop off; a heatmap review of top dead-click elements would distinguish the two.

Do this — in order
  1. Review Clarity heatmaps for top dead-click elements
    Identify the specific components causing repeated failed clicks
    ~2 h · analytics · Evolut (LP)
  2. Move key CTAs and trust content above the fold
    29% average scroll means most page content is never seen
    ~1 day · theme edit · Evolut (LP)
  3. Convert misleading static visuals into functional links or remove them
    Reduces frustration clicks on elements that appear interactive
    ~2 h · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
1073 total dead clicks (710 desktop, 363 mobile)210 rage clicks sitewideavg scroll depth 29% sitewide (38% desktop, 21% mobile)
57
ICE i
I6·C5·E6
342
Data-supportediSev 2 · minoriInstrumentibehaviorali
Behavioral analytics is reporting zero sessions despite hundreds of recorded clicks, hiding real shopper behavior
A session count of zero alongside recorded clicks means Clarity's session tracking is misconfigured, hiding the true behavioral picture behind the funnel leaks above.
What's happening

Clarity logs 0 sessions on both devices while still recording hundreds of click events, an internal contradiction.

  • Mobile sessions vs clicks0 sessions / 378 total clicks sessions should be >0 if clicks recorded
  • Desktop sessions vs clicks0 sessions / 921 total clicks sessions should be >0 if clicks recorded

Likely cause Clarity's session-initialization script isn't firing correctly, or a sampling/config error zeroes session counts; check snippet placement vs SPA route-change events.

Do this — in order
  1. Verify Clarity snippet fires on every page load
    Zero recorded sessions despite logged clicks points to a broken install.
    ~2 h · analytics · Evolut (analytics)
  2. Check SPA route-change handling for session counting
    Theme's client-side navigation may not trigger Clarity's session-start event.
    ~2 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Clarity mobile: 0 sessions but 36 rageClicks / 342 deadClicks loggedClarity desktop: 0 sessions but 169 rageClicks / 752 deadClicks logged
343
Data-supportediSev 2 · minoriInvestigateibehaviorali
Visitors keep clicking things on the site that don't work, especially on desktop
High dead/rage click volume signals broken or misleading UI elements causing shopper frustration before they even reach checkout.
What's happening

Desktop shows far more dead clicks (785) and rage clicks (176) than mobile, with low overall scroll depth.

  • Dead Clicks (Desktop)785 vs 326 mobile
  • Rage Clicks (Desktop)176 vs 35 mobile

Likely cause Non-clickable elements (product images, badges) likely look actionable; a Clarity session review of hotspot pages will confirm which elements need fixing.

Do this — in order
  1. Review top dead-click zones in Clarity recordings
    Pinpoint which fake buttons/images shoppers try to click
    ~2 h · analytics · Evolut (LP)
  2. Convert dead-click hotspots into working links
    Make badges/images clickable or remove affordance cues
    ~1 day · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
1,111 dead clicks sitewide (785 desktop, 326 mobile)211 rage clicks sitewide (176 desktop, 35 mobile)avgScrollPct only 30% (39% desktop, 21% mobile)
57
ICE i
I6·C5·E6
344
TriangulatediSev 2 · minoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile shoppers barely scroll and hit dead clicks on product pages, capping add-to-cart at the bottom edge of the healthy range.
What's happening

Mobile view-to-cart sits at 5%, the bottom of the 5–10% band, with only 21% average scroll depth.

  • View Product → Add to Cart (mobile)5% vs 5–10% band, at floor

Likely cause The add-to-cart CTA or key info sits below the fold shoppers rarely reach, or a dead-click element blocks taps.

Do this — in order
  1. Move Add to Cart button above fold
    With only 21% average scroll, the CTA must be visible without scrolling.
    ~2 h · theme edit · Evolut (LP)
  2. Fix the unresponsive dead-click element on PDP
    276 mobile dead clicks suggest a non-responsive image or swatch blocking taps.
    ~2 h · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart 5%, at the floor of the 5–10% bandrecoverable ≈$47/monthaverage scroll depth 21% on mobile276 mobile dead clicks
57
ICE i
I4·C6·E7
345
TriangulatediSev 2 · minoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Sitting at the very floor of the 5-10% band with 264 dead clicks and only 21% average scroll, this is a smaller but clear PDP engagement problem.
What's happening

Mobile PDP visitors add to cart at just 5%, the band floor, alongside 264 logged dead clicks.

  • View Product → Add to Cart5% at 5-10% band floor

Likely cause Low 21% scroll depth plus heavy dead-clicking suggests the Add to Cart button or price sits below the fold or feels unresponsive; check button placement versus above-fold content length.

Do this — in order
  1. Move the Add to Cart button above the fold on mobile PDP
    Puts the primary action within immediate view without scrolling.
    ~2 h · theme edit · Evolut (LP)
  2. Shorten above-fold copy so price and CTA are visible first
    Reduces the scroll needed to reach the purchase decision.
    ~2 h · copy · Evolut (LP)
  3. Review Clarity recordings for dead-click hotspots on PDP
    Identifies exactly which element shoppers are trying to tap.
    ~2 h · analytics · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
mobile View Product→Add to Cart retention 5% (band 5-10% floor)recoverable ~$49/monthmobile Clarity dead clicks: 264mobile avg scroll depth: 21%
57
ICE i
I5·C5·E7
346
Data-supportediSev 3 · majoriInvestigateianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most desktop carts never reach checkout
A 100% carryover rate cannot happen in reality and points to a broken or duplicated event, not strong performance.
What's happening

Desktop shows 100% of add-to-carts becoming checkouts, impossible against the 40–60% band.

  • Add to Cart→Begin Checkout100% vs 40–60% band

Likely cause The Begin Checkout event likely fires without a valid preceding Add to Cart event, or both events share the same trigger and double-count.

Do this — in order
  1. Verify Begin Checkout event fires only post add-to-cart
    Check tag manager trigger conditions to rule out firing on page load
    ~2 h · analytics · Client dev
  2. Cross-check GA4 event counts against Shopify checkout starts
    Confirms whether the 100% carryover is a tagging artifact
    ~2 h · analytics · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Desktop Add to Cart→Begin Checkout retention 100% vs 40–60% bandtracking verdict RED
57
ICE i
I5·C5·E7
347
Data-supportediSev 3 · majoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
This step sits below its band and there is no separate cart page, so the fix must live inside the slide-out drawer.
What's happening

Mobile Add to Cart→Begin Checkout is 31% vs a 40-60% band, costing an estimated $234/month.

  • View Product → Add to Cart4% vs 5-10% band
  • Add to Cart → Begin Checkout31% vs 40-60% band
  • Begin Checkout → Purchase26% vs 40-60% band

Likely cause The cart drawer likely lacks a prominent checkout CTA or reassurance content; confirm via dead-click locations inside the drawer.

Do this — in order
  1. Make the checkout button full-width and sticky in the drawer
    Reduce friction to proceed since there's no separate cart page.
    ~2 h · theme edit · Client dev
  2. Show shipping threshold and returns info in the drawer
    Answer objections without the shopper leaving the drawer.
    ~2 h · copy · Client dev
  3. Add express checkout buttons to the drawer
    Let shoppers skip manual checkout entry entirely.
    ~1 day · shipping config · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention 31% vs 40-60% bandMobile recoverable ~$234/month
57
ICE i
I6·C4·E7
348
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers are repeatedly clicking things that don't respond, but we don't yet know where
High friction signals exist but lack page-level attribution needed to prescribe a fix.
What's happening

555 dead clicks and 113 rage clicks sitewide suggest broken or unresponsive elements, but the specific page is unidentified.

  • Dead Clicks555 high sitewide volume
  • Avg Scroll Depth30% low engagement

Likely cause Likely non-functional buttons/links or slow-loading interactive elements; distinguish by segmenting recordings by URL to find the worst offender.

Do this — in order
  1. Segment Clarity recordings by URL to find worst page
    worstPage is currently unidentified; needed before any fix.
    ~2 h · analytics · Evolut (LP)
  2. Watch 10 rage-click recordings this week
    Identify the specific elements shoppers repeatedly click without effect.
    ~2 h · analytics · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
555 dead clicks and 113 rage clicks sitewide in 30 daysAverage scroll depth only 30%worstPage not identified in Clarity data
57
ICE i
I6·C4·E7
349
Data-supportediSev 2 · minoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
A below-band leak in the cart drawer itself, the last step before checkout on the dominant mobile channel.
What's happening

36% of mobile cart-adders begin checkout, below the 40–60% band, leaving about $207/month unconverted.

  • Add to Cart → Begin Checkout36% vs 40–60% band

Likely cause The drawer's checkout button may lack visibility or shipping/returns reassurance, stalling the move to checkout.

Do this — in order
  1. Make the drawer checkout button more prominent
    Increase size and contrast so it's the obvious next step
    ~30 min · theme edit · Client dev
  2. Add express wallet buttons inside the drawer
    Shop Pay/Apple Pay reduce steps needed to begin checkout
    ~30 min · storefront config · Client dev
  3. Add shipping and returns info inside the drawer
    Reduces uncertainty that stalls checkout initiation
    ~2 h · copy · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention 36% vs 40–60% bandRecoverable ~$207/month on mobileCart is a slide-out drawer with no /cart page
57
ICE i
I5·C4·E8
350
Data-supportediSev 3 · majoriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout → Purchase retention 14% vs 40-60% bandDesktop Add to Cart → Begin Checkout 107% (impossible, tracking issue)Recoverable $511/monthTracking verdict RED
351
Data-supportediSev 3 · majoriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase retention 14% vs 40–60% bandRecoverable ~$491/monthDesktop Add to Cart→Begin Checkout at 107% (impossible, likely tracking artifact)Tracking verdict RED — treat as provisional
352
Data-supportediSev 3 · majoriInvestigateianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most desktop carts never reach checkout
A retention rate above 100% is mathematically impossible and signals duplicated or misattributed events on desktop, undermining any checkout diagnosis.
What's happening

Desktop shows 107% of add-to-carts reaching checkout, a mathematically impossible rate pointing to event duplication.

  • Add to Cart → Begin Checkout (desktop)107% vs 40–60%
  • Begin Checkout → Purchase (desktop)14% vs 40–60%

Likely cause begin_checkout likely fires multiple times per session (e.g., on page reload/back button) or add_to_cart under-fires; compare GTM trigger conditions against GA4 DebugView to isolate.

Do this — in order
  1. Inspect GTM begin_checkout trigger for duplicate firing
    Reloads or back-navigation may re-fire the event multiple times
    ~2 h · analytics · Client dev
  2. Add event deduplication logic to begin_checkout tag
    Prevents one checkout session from counting as several
    ~2 h · analytics · Client dev
  3. Cross-validate against Shopify checkout-started count
    Confirms the true add-to-cart-to-checkout rate before acting on it
    ~30 min · analytics · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Desktop Add to Cart → Begin Checkout retention 107% vs band 40–60%Desktop sessions 1,475Tracking verdict RED (GA4 vs Shopify -37%)
57
ICE i
I7·C5·E5
353
Data-supportediSev 3 · majoriInvestigateianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most desktop carts never reach checkout
Desktop shows 105% carry-over from Add to Cart to Begin Checkout, over 100%, only possible with double-counted events or misattributed sessions, consistent with the RED tracking verdict.
What's happening

Desktop Add to Cart→Begin Checkout retention is 105%, an impossible value confirming broken event tracking.

  • Add to Cart → Begin Checkout105% vs 40–60% band
  • Begin Checkout → Purchase24% vs 40–60%

Likely cause Begin_checkout tag likely fires multiple times per session, or GA4 session stitching miscounts users across devices; check GTM trigger count per order.

Do this — in order
  1. Log begin_checkout events per order ID
    Confirms whether the tag fires once or multiple times per checkout.
    ~2 h · analytics · Client dev
  2. Review GTM trigger conditions for duplicates
    Duplicate bindings on the drawer checkout button commonly cause double firing.
    ~2 h · analytics · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Desktop Add to Cart→Begin Checkout retention 105% vs 40–60% bandtracking verdict REDGA4 vs Shopify revenue divergence -36%
57
ICE i
I5·C6·E6
354
Data-supportediSev 2 · minoriInvestigateianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most desktop carts never reach checkout
An 87% add-to-cart-to-checkout carryover on desktop is implausible versus the 40–60% band and warrants a tracking audit before trusting downstream numbers.
What's happening

Desktop cart-to-checkout carryover of 87% is implausibly high compared to the 40–60% band.

  • Add to Cart → Begin Checkout87% vs 40–60%

Likely cause Begin-checkout event may fire twice per session (e.g., on drawer open and page load), inflating this rate; check GA4 event de-duplication.

Do this — in order
  1. Audit GA4 begin_checkout trigger conditions
    Confirm the event fires once per session, not on every drawer open.
    ~2 h · analytics · Client dev
  2. Cross-check Shopify admin checkout count vs GA4
    Validates whether the 87% carryover is real or a tracking duplicate.
    ~30 min · analytics · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Desktop Add to Cart → Begin Checkout retention 87% vs 40–60% band (unusually high)Desktop Begin Checkout → Purchase drops to 22% immediately afterTracking verdict GREEN overall (GA4 revenue $2,513, 0% divergence from Shopify)
57
ICE i
I5·C4·E8
355
Data-supportediSev 2 · minoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Mobile cart-to-checkout carryover (38%) sits just under the 40–60% band, costing an estimated $84/mo.
What's happening

38% of mobile cart-drawer users proceed to checkout, just under the 40–60% band.

  • Add to Cart → Begin Checkout38% vs 40–60%
  • Begin Checkout → Purchase44% vs 40–60%

Likely cause Drawer may lack a clear checkout CTA or reassurance copy, causing hesitation; compare button prominence vs added shipping/returns text.

Do this — in order
  1. Make checkout button primary and sticky in drawer
    Ensures the CTA is the clear next step, not lost among cart items.
    ~30 min · theme edit · Client dev
  2. Enable express checkout buttons in drawer
    Shop Pay/PayPal buttons reduce steps to begin checkout.
    ~30 min · checkout config · Client dev
  3. Add shipping and returns note inside drawer
    Answers cost and return concerns before the shopper leaves the drawer.
    ~2 h · copy · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart → Begin Checkout retention 38% vs 40–60% bandMobile recoverable revenue estimated $84/monthStore uses slide-out cart drawer, no /cart page
57
ICE i
I4·C5·E8
356
Data-supportediSev 2 · minoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
A smaller but real leak right after add-to-cart, in the drawer experience that shoppers actually use to proceed.
What's happening

Mobile Add to Cart → Begin Checkout is 37%, just under the 40–60% band floor.

  • Add to Cart → Begin Checkout37% vs 40–60% band
  • Begin Checkout → Purchase45% within 40–60% band

Likely cause The cart drawer likely lacks a prominent checkout CTA or reassurance copy, causing hesitation; distinguish via CTA visibility vs missing shipping/returns trust info.

Do this — in order
  1. Make the Checkout button sticky and prominent in the drawer
    Ensures a single, unmissable CTA above the fold inside the drawer.
    ~30 min · theme edit · Client dev
  2. Add a shipping/returns trust line in the drawer
    Reduces last-second hesitation before proceeding to checkout.
    ~30 min · copy · Client dev
  3. Enable express checkout buttons in the drawer
    Shop Pay/PayPal buttons let shoppers skip straight to payment.
    ~30 min · payment settings · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart → Begin Checkout retention 37% vs 40–60% bandMobile recoverable ~$132/mo at this stepCart is a slide-out drawer (no /cart page)
57
ICE i
I4·C5·E8
357
Data-supportediSev 3 · majoriInvestigateianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Second-largest leak by recoverable revenue and clearly below its band floor.
What's happening

Only 4% of mobile product viewers add to cart, below the 5–10% band.

  • Session → View Product81% vs 20–45%
  • View → Add to Cart4% vs 5–10%
  • Add to Cart → Checkout31% vs 40–60%

Likely cause The abnormally high 81% view rate suggests possible duplicate view_item events inflating the denominator, versus a genuinely weak mobile PDP add-to-cart CTA; check GA4 event de-duplication first.

Do this — in order
  1. Audit GA4 view_item event firing for duplicates
    Confirms whether the 81% view rate is real or a tracking artifact before acting on it.
    ~1 day · analytics · Evolut (LP)
  2. Move Add to Cart button above the fold on mobile PDP
    Reduces scrolling needed to convert an engaged viewer.
    ~2 h · theme edit · Evolut (LP)
  3. Add reviews/trust copy next to the Add to Cart button
    Addresses hesitation at the point of decision.
    ~30 min · copy · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 4% vs 5–10% bandRecoverable ~$530/mo on mobileMobile Session→View retention 81% vs 20–45% band
57
ICE i
I7·C4·E6
358
Data-supportediSev 3 · majoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Third funnel leak by recoverable revenue; fix lives inside the cart drawer since there is no dedicated cart page.
What's happening

31% of mobile cart-adders proceed to checkout, below the 40–60% band.

  • Add to Cart → Checkout31% vs 40–60%
  • Checkout → Purchase50% vs 40–60%

Likely cause The cart drawer likely lacks a prominent checkout CTA or hides shipping costs, causing shoppers to close it instead of proceeding.

Do this — in order
  1. Add a sticky, prominent checkout button in the drawer
    Makes the next step obvious without scrolling within the drawer.
    ~2 h · theme edit · Client dev
  2. Show free-shipping threshold or shipping cost in the drawer
    Removes cost surprise that drives drawer abandonment.
    ~30 min · copy · Client dev
  3. Add express checkout buttons inside the drawer
    Lets shoppers skip to a wallet checkout directly from the drawer.
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention 31% vs 40–60% bandRecoverable ~$442/mo on mobileStore uses a slide-out cart drawer, no separate /cart page
57
ICE i
I6·C4·E7
359
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers are clicking things that don't work, hundreds of times a month, sitewide
High dead-click counts and shallow scroll depth suggest UI elements that look interactive but aren't, frustrating visitors before they convert.
What's happening

Visitors clicked non-responsive elements 509 times sitewide while average scroll depth stayed near 30%.

  • Mobile dead clicks284 paired with only 24% avg scroll
  • Desktop dead clicks225 paired with 37% avg scroll
  • Rage clicks (desktop)22 concentrated frustration signal

Likely cause Dead clicks suggest non-functional buttons or static elements styled like links; confirm by reviewing session recordings on the pages with highest click volume.

Do this — in order
  1. Review session recordings to find top dead-click elements
    Pinpoint which buttons or images appear clickable but aren't
    ~2 h · analytics · Evolut (LP)
  2. Fix or remove identified non-functional UI elements
    Eliminates frustration points once specific elements are confirmed
    ~1 day · theme edit · Evolut (LP)
  3. Strengthen above-fold content to lift scroll engagement
    Low 30% scroll depth suggests early disengagement from key content
    ~2 h · copy · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
509 dead clicks sitewide (284 mobile, 225 desktop)Average scroll depth only 30% (24% mobile, 37% desktop)25 rage clicks sitewide (3 mobile, 22 desktop)
53
ICE i
I5·C5·E6
360
TriangulatediSev 2 · minoriHypothesizeibehavioral + analyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Average scroll depth is only 30% (24% on mobile), consistent with mobile Add-to-Cart retention sitting right at the 5% band floor.
What's happening

Mobile shoppers scroll only 24% of product pages on average while mobile View→Cart sits at the band floor.

  • Avg scroll depth (mobile)24% low engagement
  • Avg scroll depth (desktop)37% low engagement
  • View→Add to Cart (mobile)5% at floor of 5–10% band
  • View→Add to Cart (desktop)12% above 5–10% band

Likely cause Key buy-triggers (benefits, reviews, CTA) likely sit below the fold out of initial view; slow page load vs a weak above-fold hook would distinguish the cause.

Do this — in order
  1. Move primary CTA and top benefit bullets above the fold
    Most mobile users never scroll past 24%, so key content must be visible immediately.
    ~2 h · theme edit · Evolut (LP)
  2. Add a sticky Add-to-Cart bar on mobile PDP
    Keeps the buy action visible regardless of how far the user scrolls.
    ~2 h · theme edit · Evolut (LP)
  3. Check PDP load speed and compress hero image
    Slow-loading hero sections can suppress scroll and engagement on mobile.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
avg scroll depth 30% sitewide (24% mobile, 37% desktop)mobile View→Add to Cart retention 5%, sitting at the floor of the 5–10% banddesktop View→Add to Cart retention 12%, above the 5–10% band
53
ICE i
I6·C4·E6
361
TriangulatediSev 2 · minoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile product-page engagement sits at the bottom edge of its band with very shallow scroll and heavy dead-click activity.
What's happening

Mobile View→Add to Cart is 5%, the floor of its 5–10% band, with only 24% average scroll depth.

  • Session → View Product (mobile)70% above typical 20–45% band, strong
  • View Product → Add to Cart (mobile)5% at floor of 5–10% band

Likely cause Weak above-fold product content or unresponsive page elements reduce engagement; session recordings of the 262 dead clicks would distinguish content vs. technical causes.

Do this — in order
  1. Review Clarity recordings for the 262 mobile dead clicks
    Identify which elements shoppers tap expecting a response
    ~2 h · analytics · Evolut (LP)
  2. Add a sticky mobile Add-to-Cart bar
    Keeps the CTA visible given only 24% average scroll depth
    ~1 day · theme edit · Evolut (LP)
  3. Move key benefit copy above the fold
    Surfaces purchase-driving info before scroll drop-off at 24%
    ~2 h · copy · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
mobile View Product→Add to Cart 5%, at the floor of the 5–10% bandmobile average scroll depth 24%262 dead clicks recorded on mobile~$18/mo recoverable
53
ICE i
I4·C5·E7
362
Data-supportediSev 2 · minoriInvestigateibehaviorali
Hundreds of shoppers are clicking things on your site that don't respond
High dead-click volume signals broken or non-interactive UI elements frustrating shoppers before they can act, which can suppress every funnel step above.
What's happening

Visitors register 498 dead clicks sitewide, more on mobile (269) than desktop (229), pointing to unresponsive UI elements.

  • Mobile dead clicks269 higher than desktop
  • Desktop dead clicks229 elevated
  • Avg scroll depth29% shoppers rarely reach lower content

Likely cause Likely non-functional accordions, carousels, or elements styled as buttons that don't act; confirm by reviewing session recordings on the highest-traffic pages.

Do this — in order
  1. Review Clarity recordings for top dead-click zones
    Pinpoint the exact elements generating the 498 dead clicks.
    ~2 h · analytics · Evolut (LP)
  2. Fix or remove the non-functional elements identified
    Converts dead zones into working links, buttons, or removes them.
    ~1 day · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
498 total dead clicks sitewide (269 mobile, 229 desktop)Average scroll depth only 29% sitewide
53
ICE i
I6·C4·E6
363
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers are repeatedly clicking things that don't respond
High dead/rage-click volume signals broken or confusing UI elements that likely suppress conversion on both devices.
What's happening

493 dead clicks and 29 rage clicks across both devices point to unresponsive or confusing page elements.

  • Dead clicks (mobile)270 elevated, near-zero expected
  • Dead clicks (desktop)223 elevated, near-zero expected
  • Rage clicks (mobile)17 elevated

Likely cause Elements appear clickable but aren't wired up (disabled buttons, slow scripts), or shoppers expect interactive features (filters/accordions) that don't exist.

Do this — in order
  1. Review Clarity recordings on highest-traffic PDPs
    Pinpoint exact elements generating dead and rage clicks before changing UI.
    ~2 h · analytics · Evolut (LP)
  2. Fix or remove the non-functional elements identified
    Removes friction once session review flags the offending components.
    ~1 day · theme edit · Evolut (LP)
  3. Test PDP and cart drawer load speed
    Slow scripts can make working elements appear unresponsive, inflating dead clicks.
    ~2 h · analytics · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
493 total dead clicks (270 mobile, 223 desktop)29 total rage clicks (17 mobile, 12 desktop)Average scroll depth 29% sitewide (23% mobile, 35% desktop)
53
ICE i
I6·C4·E6
364
TriangulatediSev 2 · minoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Sitting at the bottom of its own band, this is the smallest of the four leaks but still limits everything downstream.
What's happening

Mobile view-to-cart sits at the 5% band floor, with shoppers scrolling only 21% of the product page.

  • View Product → Add to Cart5% at floor of 5–10% band

Likely cause Key info (price, benefits, CTA) may sit below the 21% average scroll depth, or the 328 dead clicks indicate broken product-page elements.

Do this — in order
  1. Move Add to Cart above the fold
    With only 21% average scroll, price and CTA must be visible without scrolling.
    ~2 h · theme edit · Evolut (LP)
  2. Audit the product page for dead-click elements
    328 dead clicks suggest shoppers tap images or badges expecting them to work.
    ~2 h · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 5%, at the floor of the 5–10% bandMobile avg scroll depth only 21%Mobile dead clicks 328
53
ICE i
I6·C4·E6
365
Data-supportediSev 2 · minoriInvestigateianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most desktop carts never reach checkout
An implausibly high carry-over combined with a RED tracking verdict suggests event miscounting rather than genuine shopper behavior.
What's happening

74% of desktop cart-adders begin checkout, above the 40-60% band ceiling — an implausible jump.

  • Add to Cart → Begin Checkout (Desktop)74% vs 40-60% band

Likely cause Possibly duplicate begin_checkout firing or under-counted add_to_cart events; check GTM tag order versus raw event counts.

Do this — in order
  1. Compare Shopify checkout-started count to GA4 begin_checkout count
    Reveals whether GA4 is over- or under-firing this event on desktop.
    ~30 min · analytics · Client dev
  2. Audit add_to_cart and begin_checkout tag firing in GTM
    Check preview mode for duplicate or missing fires on desktop product/cart pages.
    ~2 h · analytics · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Desktop Add to Cart→Begin Checkout retention 74% vs band 40-60% (exceeds ceiling)Tracking verdict RED with -34% revenue divergenceDesktop scriptErrorsPct 0%, botPct 0% — rules out script errors or bots as the cause
53
ICE i
I5·C5·E6
366
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers are clicking on things that don't respond, especially near checkout
High dead/rage-click volume signals broken or confusing UI elements likely feeding the checkout leaks above.
What's happening

1,072 dead clicks and 210 rage clicks recorded sitewide, more concentrated on desktop (706/166).

  • Dead clicks (sitewide)1,072 high volume
  • Avg scroll depth29% low engagement

Likely cause Non-interactive elements (badges, accordions) may look clickable, or slow-loading elements aren't registering taps; watch recordings to tell apart.

Do this — in order
  1. Watch 10 Clarity recordings on product and cart pages
    Identify exactly which elements trigger dead/rage clicks before checkout.
    ~2 h · analytics · Evolut (LP)
  2. Remove clickable-looking styling from inert elements
    Strip hover/cursor styling from badges/icons that aren't actually interactive.
    ~2 h · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
1,072 dead clicks and 210 rage clicks sitewide (Clarity)desktop: 706 dead clicks, 166 rage clicksmobile: 366 dead clicks, 44 rage clicksavg scroll depth 29% overall (20% mobile, 38% desktop)
53
ICE i
I6·C4·E6
367
Data-supportediSev 3 · majoriInvestigateibehaviorali
Shoppers repeatedly click things that don't respond, especially on desktop
High dead/rage-click volume signals broken or unresponsive UI elements, a plausible contributor to the desktop checkout collapse.
What's happening

Desktop sees 763 dead clicks and 169 rage clicks with only 39% average scroll depth this month.

  • Desktop Dead Clicks763 of 1,090 sitewide
  • Desktop Rage Clicks169 of 204 sitewide
  • Desktop Avg Scroll Depth39% low engagement

Likely cause Likely non-functional buttons/links (e.g., disabled add-to-cart or filters) or slow-loading interactive elements; distinguish by reviewing session recordings on top-exit pages.

Do this — in order
  1. Review top 10 Clarity recordings with rage/dead clicks
    Identify the exact broken elements driving frustration before prescribing a fix.
    ~2 h · analytics · Evolut (LP)
  2. Fix or remove identified non-responsive elements
    Once located, repair broken buttons/links or replace with working equivalents.
    ~1 day · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
Desktop dead clicks 763 and rage clicks 169 (Clarity)Desktop avg scroll depth only 39%Desktop Begin Checkout→Purchase leak at 7%
53
ICE i
I6·C4·E6
368
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers are clicking on things that don't work and leaving before scrolling far
Broad UX friction signal pointing to broken or misleading elements that likely touch multiple funnel steps.
What's happening

1,132 dead clicks and 229 rage clicks show shoppers hitting non-responsive elements across the site.

  • Dead+Rage Clicks1,361 total desktop 1,004 / mobile 357

Likely cause Non-functional buttons/links, or elements styled to look clickable but aren't; confirm via Clarity recordings filtered to rage-click sessions.

Do this — in order
  1. Watch the top 10 Clarity rage-click recordings this week
    Identifies the exact broken elements driving the 229 rage clicks.
    ~2 h · analytics · Evolut (LP)
  2. Fix or remove any non-clickable elements styled as buttons
    Directly eliminates dead-click frustration once identified.
    ~1 day · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
1,132 dead clicks and 229 rage clicks sitewide in 30 daysAverage scroll depth only 30% (desktop 39%, mobile 21%)
53
ICE i
I6·C4·E6
369
Data-supportediSev 3 · majoriInvestigateibehaviorali
Shoppers are repeatedly clicking things on the site that don't respond
High dead/rage click volume signals broken or unresponsive UI elements, likely suppressing add-to-cart and checkout actions.
What's happening

780 dead clicks and 133 rage clicks in 30 days point to UI elements shoppers expect to work but don't.

  • Dead clicks (sitewide)780 desktop 484 / mobile 296
  • Rage clicks (sitewide)133 desktop 98 / mobile 35

Likely cause Non-interactive elements styled as buttons (e.g. disabled add-to-cart states) or slow-loading scripts; watch a sample of Clarity recordings to confirm which.

Do this — in order
  1. Watch 10 Clarity recordings with rage clicks
    Identify the exact element(s) shoppers repeatedly click without result.
    ~2 h · analytics · Evolut (LP)
  2. Fix or remove any non-functional buttons found
    Restore expected click behavior on those elements.
    ~2 h · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
780 dead clicks and 133 rage clicks sitewide in 30 daysdesktop: 484 dead clicks, 98 rage clicksmobile: 296 dead clicks, 35 rage clicks
53
ICE i
I6·C4·E6
370
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers are clicking things on the site that don't respond
High dead- and rage-click counts on both devices signal broken or misleading UI elements independent of the funnel leaks.
What's happening

High dead-click and rage-click volumes sitewide suggest shoppers are clicking non-functional elements.

  • Desktop Dead Clicks416 high
  • Mobile Dead Clicks217 high
  • Sitewide Rage Clicks118 elevated

Likely cause Non-interactive elements (images, disabled buttons) may be styled to look clickable; confirm via Clarity recordings on the worst pages.

Do this — in order
  1. Review Clarity recordings for top dead-click elements
    Identify which non-clickable elements shoppers try to tap.
    ~2 h · analytics · Evolut (LP)
  2. Fix or restyle non-functional visual elements
    Convert to real links/buttons or make clearly non-clickable.
    ~1 day · theme edit · Evolut (LP)
  3. Re-check rage-click hotspots after the fix
    Confirm counts drop in the following reporting period.
    ~30 min · analytics · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
633 dead clicks sitewide (217 mobile, 416 desktop)118 rage clicks sitewide (26 mobile, 92 desktop)Avg scroll depth 30% sitewide (21% mobile, 40% desktop)
53
ICE i
I5·C5·E6
371
Data-supportediSev 3 · majoriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout → Purchase retention 14% vs band 40–60%Recoverable ~$473/monthDesktop Add to Cart→Checkout 107% (data quality flag, tracking RED)
372
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers are clicking on things that don't work and leaving before scrolling
Widespread click frustration and shallow scroll depth likely suppress add-to-cart and purchase across both devices.
What's happening

280 dead clicks and 51 rage clicks sitewide, with only 32% average scroll depth, show broad on-page friction.

  • Dead clicks (mobile / desktop)128 / 152 high
  • Avg scroll depth (mobile / desktop)21% / 43% low

Likely cause Non-interactive elements (images, badges) are probably styled to look clickable, or key content sits below a fold most visitors never reach.

Do this — in order
  1. Review top dead-click elements in session recordings
    Identify and fix or remove elements shoppers mistake for buttons
    ~2 h · theme edit · Evolut (LP)
  2. Move key value props and CTA above the 32% scroll line
    Most visitors never scroll past this point on either device
    ~2 h · LP build · Evolut (LP)
  3. Fix buttons in identified rage-click zones
    51 rage clicks indicate shoppers repeatedly clicking something broken
    ~30 min · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
Sitewide dead clicks 280 (mobile 128, desktop 152)Sitewide rage clicks 51 (mobile 22, desktop 29)Average scroll depth 32% (mobile 21%, desktop 43%)
53
ICE i
I6·C5·E5
373
Data-supportediSev 2 · minoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Secondary mobile leak below band, smaller dollar value than the PDP and desktop checkout leaks but still recoverable with low-effort drawer fixes.
What's happening

Mobile Add to Cart→Checkout conversion is 37%, just under the 40–60% band, losing ~$137/month.

  • Add to Cart → Begin Checkout37% vs 40–60% band
  • Begin Checkout → Purchase45% vs 40–60% band

Likely cause Cart drawer may lack a prominent checkout CTA or shipping/trust reassurance, or shoppers are price-checking before committing; drawer heatmaps would clarify.

Do this — in order
  1. Add persistent checkout button at top of drawer
    Reduces steps needed to move from cart to checkout on mobile.
    ~30 min · theme edit · Client dev
  2. Add free-shipping progress bar in drawer
    Motivates shoppers to proceed to checkout to unlock the threshold.
    ~2 h · theme edit · Client dev
  3. Show trust badges for secure checkout and returns
    Reassures shoppers before they leave the cart for checkout.
    ~30 min · copy · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout retention is 37% vs the 40–60% band floorRecoverable ~$137/month on mobile
53
ICE i
I4·C5·E7
374
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers are clicking things on the site that don't do anything
High dead-click volume and shallow scroll suggest broken or non-functional UI elements that may be suppressing engagement across the funnel.
What's happening

Hundreds of dead clicks and shallow scroll depth suggest shoppers try to interact with elements that don't respond.

  • Dead clicks (mobile)288 high volume
  • Dead clicks (desktop)222 high volume
  • Avg scroll depth (sitewide)31% low engagement

Likely cause Elements styled as interactive (accordions, swatches, badges) that aren't clickable, or delayed script handlers; Clarity recordings will show which.

Do this — in order
  1. Review 10 Clarity recordings on top product pages
    Identifies exactly which elements trigger dead clicks
    ~2 h · analytics · Evolut (LP)
  2. Fix or remove the non-functional elements found
    Restores expected interactivity and may lift add-to-cart
    ~1 day · theme edit · Evolut (LP)
  3. Move key content (reviews, FAQ) higher on the page
    Improves the low 31% scroll depth by front-loading engagement
    ~2 h · copy · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
510 total dead clicks (288 mobile, 222 desktop)avg scroll depth only 31% sitewide (24% mobile, 39% desktop)
50
ICE i
I5·C4·E6
375
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers are clicking things on the site that don't respond
High dead-click volume alongside low scroll depth points to unresponsive UI elements hurting engagement before the checkout leak.
What's happening

528 dead clicks and only 31% average scroll depth suggest shoppers try to interact with elements that don't respond.

  • Mobile dead clicks297 vs 3 rage clicks
  • Desktop dead clicks231 vs 22 rage clicks
  • Avg scroll depth31% low page engagement

Likely cause Dead clicks likely target non-interactive images or badges, or slow-loading elements that appear clickable; session replays will confirm which.

Do this — in order
  1. Review top Clarity recordings with dead clicks
    Pinpoints exact elements shoppers mistake for buttons.
    ~2 h · UX review · Evolut (LP)
  2. Make or remove clickable-looking static elements
    Stops wasted clicks on badges/images that do nothing.
    ~1 day · theme edit · Evolut (LP)
  3. Fix lazy-load delays causing perceived unresponsiveness
    Reduces dead clicks caused by elements not yet interactive.
    ~2 h · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
Sitewide dead clicks 528 (mobile 297, desktop 231)Average scroll depth 31% sitewideRage clicks 25
50
ICE i
I5·C4·E6
376
TriangulatediSev 2 · minoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile is at the low edge of its band with weak page engagement signals, suggesting PDP content isn't landing before the bigger checkout leak.
What's happening

Mobile product-page engagement is weak: 24% average scroll depth and 297 dead clicks on PDP-area interactions.

  • View → Add to Cart6% within 5–10% band, low end
  • Avg scroll depth24% low vs desktop 39%

Likely cause Key product info (ingredients, dosage, reviews) likely sits below the fold on mobile, or dead clicks show shoppers tapping non-functional elements expecting Add-to-Cart.

Do this — in order
  1. Move Add-to-Cart and key benefits above the fold
    Surfaces the buy action before shoppers stop scrolling.
    ~2 h · theme edit · Evolut (LP)
  2. Add a sticky mobile Add-to-Cart bar
    Keeps the buy action reachable throughout the page.
    ~1 day · theme edit · Evolut (LP)
  3. Review dead-click hotspots on mobile PDP
    Identifies which elements shoppers mistake for Add-to-Cart.
    ~2 h · UX review · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View→Add to Cart retention 6% (band 5–10%, amber)Mobile avg scroll depth 24%Mobile dead clicks 297
50
ICE i
I4·C5·E6
377
Data-supportediSev 2 · minoriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile product pages convert to cart adds at the very bottom edge of benchmark, capping sitewide CR at 0.51% vs the 1.5–3.5% target.
What's happening

Mobile View→Add to Cart sits at 5%, the floor of the 5–10% band, while sitewide CR is 0.51%.

  • Session → View Product (mobile)69% above 20–45% band, strong
  • View Product → Add to Cart (mobile)5% floor of 5–10% band

Likely cause Weak product-page persuasion (reviews, pricing clarity) or mismatched ad-to-page intent are the two likely drivers; segment by traffic source to isolate.

Do this — in order
  1. Add above-fold social proof (ratings, review count) on mobile PDP
    lifts trust at the floor-level ATC step
    ~2 h · theme edit · Evolut (LP)
  2. Clarify pricing/subscription savings near Add to Cart button
    reduces hesitation before the cart click
    ~2 h · copy · Evolut (LP)
  3. Compress mobile PDP hero and reviews above the fold
    shortens path to the add-to-cart decision
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 5% (floor of 5–10% band)Mobile sessions 1,376/30 daysMobile sitewide CR 0.51% vs 1.5–3.5% band
50
ICE i
I5·C4·E6
378
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers are clicking on things that don't work
High dead-click volume signals shoppers trying to interact with non-functional elements, adding friction throughout the browsing experience.
What's happening

Shoppers generate 515 dead clicks in 30 days, suggesting UI elements that look interactive but aren't.

  • Dead clicks (mobile)291 high volume, 30 days
  • Dead clicks (desktop)224 high volume, 30 days
  • Rage clicks (desktop)22 moderate frustration signal

Likely cause Likely non-linked images/swatches or broken accordions mimic buttons; review Clarity recordings on highest-traffic PDPs to confirm which elements are involved.

Do this — in order
  1. Watch Clarity recordings for top dead-click elements
    identify exact elements shoppers try to click
    ~2 h · analytics · Evolut (LP)
  2. Fix or remove clickable-looking but inert elements
    converts friction points into functional links
    ~1 day · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
515 dead clicks sitewide in 30 days (mobile 291, desktop 224)Rage clicks 25 total (mobile 3, desktop 22)Script errors 0% on both devices — not a script failureBot traffic 0% on both devices — clean data
50
ICE i
I5·C5·E5
379
Data-supportediSev 2 · minoriInvestigateibehaviorali
Hundreds of visitors click things that don't respond
High dead-click volume and shallow scrolling suggest confusing or non-functional UI elements that may suppress conversion sitewide.
What's happening

496 dead clicks and ~30% average scroll depth point to visitors disengaging or clicking unresponsive elements.

  • Dead clicks (mobile)273 high volume
  • Dead clicks (desktop)223 high volume
  • Avg scroll depth (sitewide)30% low engagement

Likely cause Likely non-functional buttons/accordions or elements mistaken for clickable; verify by watching session recordings on the highest-dead-click pages.

Do this — in order
  1. Watch recordings on top dead-click pages
    Identify exactly which elements users repeatedly click without response.
    ~2 h · analytics · Evolut (LP)
  2. Fix or remove non-functional UI elements found
    Rebind broken click handlers or remove decorative elements styled like buttons.
    ~1 day · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
496 dead clicks sitewide (273 mobile, 223 desktop) in 30 daysaverage scroll depth only 30% sitewide (24% mobile, 36% desktop)
50
ICE i
I6·C4·E5
380
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers are clicking things on the site that don't respond
High dead-click counts without script errors point to confusing, non-functional UI elements rather than a broken site, likely suppressing engagement sitewide.
What's happening

262 mobile and 126 desktop dead clicks occur despite 0% script errors, suggesting misleading UI rather than broken code.

  • Dead clicks (mobile)262 high with no script errors to explain it
  • Dead clicks (desktop)126 high with no script errors to explain it
  • Avg scroll depth30% low engagement overall

Likely cause Elements styled like buttons/links (badges, disabled accordions) are inviting clicks that do nothing; recordings would confirm the exact elements.

Do this — in order
  1. Review 10 Clarity recordings showing dead clicks
    Identify which specific elements users try to click.
    ~2 h · analytics · Evolut (LP)
  2. Restyle or activate the identified non-functional elements
    Remove button affordance or make them actually clickable once found.
    ~2 h · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
388 total dead clicks (262 mobile, 126 desktop) with 0% script errors on both devicesAverage scroll depth only 30% (24% mobile, 36% desktop)
50
ICE i
I5·C4·E6
381
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers keep clicking things that don't work
High dead-click volume with shallow scrolling signals broken or misleading UI elements, but the exact page isn't yet known.
What's happening

408 dead clicks and shallow scrolling (30% avg) suggest shoppers are clicking non-functional elements sitewide.

Likely cause Elements styled like buttons (badges, images) may be non-clickable, or lazy-loaded content shifts layout; a per-page Clarity breakdown would confirm.

Do this — in order
  1. Segment Clarity recordings by URL to find worst page
    worstPage is currently unidentified and needed to target the fix
    ~2 h · analytics · Evolut (LP)
  2. Review flagged elements for fake-button styling
    Remove or wire up elements that look clickable but aren't
    ~2 h · theme edit · Evolut (LP)
  3. Re-check dead-click count after the fix
    Confirms the change actually reduced frustrated clicks
    ~30 min · analytics · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
408 dead clicks sitewide (230 mobile, 178 desktop)Average scroll depth 30% (25% mobile, 35% desktop)
50
ICE i
I4·C4·E7
382
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers are tapping things on the site that don't do anything
High dead-click volume across both devices points to confusing UI that frustrates shoppers before they convert.
What's happening

399 dead clicks sitewide in 30 days show visitors repeatedly tapping elements that don't respond.

  • Dead clicks (Desktop)167 sitewide 30-day count
  • Rage clicks (Desktop)10 sitewide 30-day count

Likely cause Non-interactive elements (images/text) styled to look clickable, or slow button response causing repeated taps before action registers.

Do this — in order
  1. Review top 10 Clarity dead-click session recordings
    Identify which elements shoppers expect to be clickable.
    ~2 h · analytics · Evolut (LP)
  2. Limit hover/cursor-pointer styling to real controls
    Removes visual ambiguity about what can be clicked.
    ~2 h · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
399 total dead clicks in 30 days (232 mobile, 167 desktop)13 rage clicks (3 mobile, 10 desktop)avg scroll depth 30% sitewide (25% mobile, 35% desktop)
50
ICE i
I4·C4·E7
383
Data-supportediSev 2 · minoriInvestigateibehaviorali
Hundreds of monthly taps land on page elements that don't actually do anything
High dead-click volume on both devices suggests UI elements are confusing shoppers, independent of the funnel leaks already identified.
What's happening

439 dead clicks per month across mobile and desktop point to unresponsive elements shoppers mistake for buttons.

  • Dead clicks (mobile)252 high
  • Dead clicks (desktop)187 high

Likely cause Non-interactive elements styled like buttons/badges, or a broken component; confirm by watching session recordings of dead-click hotspots.

Do this — in order
  1. Watch top Clarity recordings with dead clicks
    Pinpoint exactly which elements shoppers mistake for interactive controls
    ~2 h · analytics · Evolut (LP)
  2. Fix or remove button-like styling on non-clickable elements
    Reduces wasted taps and shopper frustration once hotspots are found
    ~1 day · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
439 dead clicks sitewide (252 mobile, 187 desktop)rage clicks 15 total (3 mobile, 12 desktop)avg scroll 29% sitewide
50
ICE i
I5·C4·E6
384
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers are tapping on things that don't work, across both mobile and desktop
High dead-click volume on both devices points to unresponsive page elements that may be depressing engagement across the funnel.
What's happening

463 dead clicks and low scroll depth (29%) across both devices point to broken or confusing page elements.

  • Mobile dead clicks264 high
  • Desktop dead clicks199 high

Likely cause Elements that look clickable (badges, images, fake buttons) may not be wired up, or layout shift is moving targets after load; confirm via recordings.'

Do this — in order
  1. Watch 10-15 Clarity recordings with dead clicks
    Identify the specific non-responsive elements causing failed taps.
    ~2 h · analytics · Evolut (LP)
  2. Remove or wire up non-functional visual elements
    Convert decorative badges/images that look clickable into real links or remove them.
    ~1 day · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
463 total dead clicks (264 mobile, 199 desktop)23 rage clicks (11 mobile, 12 desktop)Average scroll depth 29% sitewide
50
ICE i
I5·C4·E6
385
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers repeatedly tap things on the site that don't respond
High dead/rage click volume signals broken or confusing interactive elements that likely compound the funnel leaks above.
What's happening

490 dead clicks and 37 rage clicks across the site show shoppers hitting controls that don't respond.

  • Dead clicks (mobile/desktop)268 / 222 high
  • Rage clicks (mobile/desktop)25 / 12 elevated

Likely cause Either elements are styled to look clickable without a handler, or slow-loading scripts delay real buttons — reviewing recordings will show which.

Do this — in order
  1. Watch 10 Clarity recordings per device
    Identify exactly which elements generate the dead and rage clicks.
    ~2 h · analytics · Evolut (LP)
  2. Fix or remove the worst offending elements
    Likely candidates: fake buttons, disabled swatches, slow-loading widgets.
    ~1 day · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
Sitewide dead clicks: 490 (268 mobile, 222 desktop)Sitewide rage clicks: 37 (25 mobile, 12 desktop)Avg scroll depth 29% sitewide
50
ICE i
I5·C4·E6
386
Data-supportediSev 3 · majoriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout → Purchase retention 9% vs band 40–60%Recoverable $774/moDesktop Add to Cart → Begin Checkout 86% (vs 40–60% band)Tracking verdict RED - treat as provisional
387
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers across the site are clicking things that don't respond
High dead/rage click volume signals broken or misleading UI elements that erode trust and silently suppress conversion everywhere, not just on flagged funnel steps.
What's happening

501 dead clicks and 38 rage clicks across the site show shoppers repeatedly clicking elements that don't respond.

  • Dead Clicks (mobile/desktop)291/210 elevated volume
  • Rage Clicks (mobile/desktop)26/12 elevated volume

Likely cause Decorative elements styled like buttons, or slow-loading interactive components; session recordings would distinguish broken UI from slow load.

Do this — in order
  1. Review top Clarity recordings with dead clicks
    Pinpoint exact page elements shoppers try to click that don't respond.
    ~2 h · analytics · Evolut (LP)
  2. Fix or de-style non-functional visual elements site-wide
    Converts false affordances into real links/buttons or removes clickable-looking styling.
    ~1 day · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
Site-wide dead clicks 501 (mobile 291, desktop 210)Site-wide rage clicks 38 (mobile 26, desktop 12)overall avg scroll depth 29%
50
ICE i
I6·C4·E5
388
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers are clicking on things that don't respond
High dead- and rage-click volume signals confusing or broken UI elements, but the specific page hasn't been isolated yet.
What's happening

804 dead clicks and 132 rage clicks recorded sitewide, but the worst page is not yet identified.

  • Dead Clicks804 495 desktop / 309 mobile
  • Rage Clicks132 98 desktop / 34 mobile

Likely cause Likely non-interactive elements styled as clickable (e.g., disabled buttons, fake links); segment recordings by page to confirm vs a slow-loading element.

Do this — in order
  1. Filter session recordings by dead-click volume
    Identify which specific template drives the 804 dead clicks.
    ~2 h · analytics · Evolut (LP)
  2. Review PDP and cart drawer for non-functional elements
    Check for disabled buttons or tooltips mistaken for clickable CTAs.
    ~2 h · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
804 dead clicks sitewide (309 mobile / 495 desktop)132 rage clicks sitewide (34 mobile / 98 desktop)worst-offending page not yet identified
50
ICE i
I5·C4·E6
389
TriangulatediSev 2 · minoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Shoppers are leaving before reaching add-to-cart, and low scroll depth suggests they never see it.
What's happening

Mobile View→Add to Cart sits at 4%, just under the 5–10% floor, with only 21% average scroll depth.

  • Session → View Product86% vs 20–45% band
  • View → Add to Cart4% vs 5–10% band

Likely cause Low scroll depth (21%) suggests the add-to-cart CTA or key value props sit below the fold on mobile PDPs.

Do this — in order
  1. Move Add-to-Cart button and price above the fold
    Puts the primary action within immediate view on mobile PDPs.
    ~2 h · theme edit · Evolut (LP)
  2. Add a sticky Add-to-Cart bar on mobile PDP
    Keeps the CTA accessible regardless of scroll position.
    ~2 h · theme edit · Evolut (LP)
  3. Add concise benefit bullets near the top of the PDP
    Gives shoppers a reason to add to cart before they scroll away.
    ~2 h · copy · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 4% vs 5–10% bandMobile recoverable revenue $136/moMobile average scroll depth 21%
50
ICE i
I5·C4·E6
390
Data-supportediSev 2 · minoriInvestigateianalyticsi
About 1 in 9 dollars sold gets refunded
An 11% refund rate is high for DTC supplements and erodes net revenue beyond the funnel numbers.
What's happening

Refunds equal about 11% of monthly revenue ($123 of $1121), above typical DTC supplement refund rates.

  • Refunds as % of Revenue11% typical <5%

Likely cause Could stem from product not matching on-site claims/expectations, or shipping damage/delays; refund reason codes would distinguish these.

Do this — in order
  1. Pull refund reason codes from Shopify
    Identify whether refunds cluster around quality, shipping, or expectation issues.
    ~30 min · analytics · Evolut (LP)
  2. Review product page claims against refund complaints
    Check for expectation mismatch driving returns.
    ~2 h · copy · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
refunds $123.15 on $1121.38 revenue (~11% refund rate)
50
ICE i
I4·C3·E8
391
Data-supportediSev 2 · minoriInvestigateianalyticsi
Nearly 1 in 12 dollars sold gets refunded
An 8.4% refund rate is notable for a supplement brand and warrants root-cause investigation before more traffic is driven to the same offer.
What's happening

Refunds equal 8.4% of Shopify revenue ($123.15 of $1,466.82), higher than typical for this category.

  • Refunds / Revenue8.4% $123.15 of $1,466.82

Likely cause Possible mismatch between PDP claims/expectations and the actual product, or shipping/fulfillment issues; check refund reason codes to distinguish.

Do this — in order
  1. Pull refund reason codes from Shopify
    Identify the top two reasons driving the 8.4% refund rate.
    ~2 h · analytics · Evolut (LP)
  2. Compare refunded SKUs' PDP copy for overpromising claims
    Check if refunded orders share descriptions that set wrong expectations.
    ~2 h · copy · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
Refunds $123.15 of $1,466.82 revenue (8.4%) in the 30-day window
50
ICE i
I5·C3·E7
392
Data-supportediSev 2 · minoriInvestigateianalyticsi
7% of monthly revenue is being refunded after purchase
A refund rate this high on such a small order base signals a mismatch between what's promised pre-purchase and what's delivered.
What's happening

$123.15 of $1,694.79 revenue (7.3%) was refunded across just 20 orders this month.

  • Refund Rate7.3% of monthly revenue

Likely cause Either PDP/subscription terms are unclear at purchase, or shipping delays are driving cancellations; refund reason codes would distinguish the two.

Do this — in order
  1. Pull refund reason codes for the last 20 orders.
    Identifies whether refunds are product-fit, shipping, or subscription-related.
    ~30 min · analytics · Evolut (LP)
  2. Clarify usage/results expectations on the PDP.
    Prevents mismatch-driven refunds if dissatisfaction is the main reason.
    ~2 h · copy · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
Refunds $123.15 against $1,694.79 Shopify revenue (~7.3%)20 total orders in 30 days
50
ICE i
I4·C4·E7
393
Data-supportediSev 3 · majoriInvestigateibehaviorali
Shoppers keep clicking things that don't respond and rarely scroll down the page
High dead/rage clicks plus shallow scroll point to unresponsive UI or unclear layout suppressing engagement, though the specific page is not yet identified.
What's happening

1,026 dead clicks and 29% average scroll depth suggest shoppers hit unresponsive elements and rarely explore pages.

  • Dead clicks (sitewide)1,026 711 desktop / 315 mobile, unusually high
  • Average scroll depth29% most content likely unseen

Likely cause Likely non-functional buttons (e.g., size/quantity selectors) or a long above-fold section burying key content; a page-level heatmap would confirm which.

Do this — in order
  1. Filter Clarity recordings by dead-click count
    Identify the exact page and element causing the unresponsive clicks.
    ~2 h · analytics · Evolut (LP)
  2. Fix or remove the unresponsive elements found
    Rebind click handlers or remove decorative elements that look clickable.
    ~1 day · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
1,026 dead clicks sitewide (315 mobile / 711 desktop)193 rage clicks sitewide (28 mobile / 165 desktop)Average scroll depth 29% (21% mobile / 37% desktop)
50
ICE i
I6·C4·E5
394
TriangulatediSev 2 · minoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile sits at the very bottom of the acceptable range while desktop reaches the top (10%), suggesting a mobile-specific presentation gap.
What's happening

Mobile product-page visitors add to cart at just 5%, the floor of the 5-10% band, versus 10% on desktop.

  • View Product → Add to Cart (Mobile)5% floor of 5-10% band
  • View Product → Add to Cart (Desktop)10% top of band

Likely cause The add-to-cart button or price/value proposition may sit below the fold on mobile given the 21% average mobile scroll depth; compare button position against scroll drop-off point.

Do this — in order
  1. Pin the Add to Cart button in a sticky mobile bar
    Keeps the CTA visible without requiring scroll on mobile
    ~2 h · theme edit · Evolut (LP)
  2. Shorten above-fold product copy to surface price and CTA sooner
    Mobile scroll depth of 21% means most copy below it goes unread
    ~1 day · copy · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart 5% vs 5-10% band (floor)recoverable $14/month
50
ICE i
I4·C4·E7
395
Data-supportediSev 2 · minoriInvestigateibehaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most product-page visitors never add to cart
High dead-click and rage-click counts alongside shallow scroll depth suggest shoppers are trying to interact with non-functional elements before adding to cart.
What's happening

1,110 dead clicks and 210 rage clicks recorded sitewide with only 30% average scroll depth.

  • Dead Clicks1,110 sitewide, mostly desktop (755)
  • Rage Clicks210 sitewide, mostly desktop (169)
  • Avg Scroll Depth30% mobile 20% / desktop 39%

Likely cause Likely non-clickable images or badges styled like buttons, or a slow-loading element users click repeatedly; session recordings would confirm which.

Do this — in order
  1. Watch top Clarity recordings with dead clicks
    Identify the exact element shoppers repeatedly click without response.
    ~2 h · analytics · Evolut (LP)
  2. Remove button-like styling from static elements
    Stop badges/icons that aren't links from looking clickable.
    ~2 h · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
1,110 dead clicks sitewide (355 mobile, 755 desktop)210 rage clicks sitewide (41 mobile, 169 desktop)avg scroll depth only 30% (20% mobile, 39% desktop)
50
ICE i
I5·C4·E6
396
Data-supportediSev 3 · majoriInvestigateianalyticsi
Refunds this month outnumber orders, quietly eating into revenue
More refund events than orders signals a billing or fulfillment problem eating into revenue that isn't visible in the funnel view.
What's happening

39 refund transactions occurred against only 21 orders in the same 30-day window.

  • Refunds vs Orders39 vs 21 refunds exceed orders

Likely cause Either multiple partial refunds per order from split shipments, or a duplicate-charge billing bug; check refund reason codes per order ID to distinguish.

Do this — in order
  1. Pull refund reason codes from Shopify admin
    Identify whether refunds stem from billing errors, quality issues, or split-shipment partials.
    ~2 h · analytics · Evolut (LP)
  2. Check payment gateway for duplicate-charge bug
    Rule out a technical double-charge issue inflating refund count above order count.
    ~2 h · analytics · Evolut (LP)
  3. Review support tickets tied to refunded orders
    Surface product-quality or fulfillment complaints driving refunds.
    ~1 day · analytics · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
Shopify refunds count 39 exceeds orders count 21 in 30 daysShopify revenue $2,005.34
50
ICE i
I6·C4·E5
397
Data-supportediSev 2 · minoriInstrumentianalyticsi
Mobile funnel data shows an impossible 88% product-view rate, hiding the real story
An implausible carryover this far above band suggests duplicate or misfired events, undermining trust in mobile funnel numbers used elsewhere.
What's happening

Mobile session-to-view retention is 88%, more than double the expected 20-45% band.

  • Session Start→View Product88% vs 20-45%

Likely cause Likely duplicate view_item/page_view event firing per session, or undercounted sessions; check GA4 events-per-session vs Shopify Analytics sessions.

Do this — in order
  1. Check GA4 for duplicate view_item tags firing on product pages
    Duplicate firing artificially inflates this step's retention rate.
    ~2 h · analytics · Evolut (analytics)
  2. Cross-check mobile session counts against Shopify Analytics
    Confirms whether GA4 mobile sessions are undercounted, inflating the ratio.
    ~2 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Mobile Session Start→View Product retention 88% vs 20-45% bandTracking verdict red with -34% revenue divergence
398
Data-supportediSev 2 · minoriInvestigateianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most desktop carts never reach checkout
A carry-over this far above band alongside a RED tracking verdict suggests undercounted Add-to-Cart events rather than genuinely strong performance.
What's happening

Desktop cart-to-checkout carries over at 76%, above the 40–60% norm, suggesting undercounted Add-to-Cart events.

  • Add to Cart → Begin Checkout76% vs 40–60%

Likely cause Add-to-Cart event likely fires inconsistently on desktop (missed by tag manager), inflating the ratio; verify against Shopify cart API calls.

Do this — in order
  1. Verify Add-to-Cart GA4 event firing on desktop
    Compare GA4 add_to_cart counts vs Shopify cart creation events.
    ~2 h · analytics · Client dev
  2. Cross-check tag trigger conditions for ATC
    Ensure the trigger fires on all cart-drawer add actions, not just the PDP form.
    ~2 h · analytics · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Desktop Add to Cart→Begin Checkout retention 76% vs 40–60% bandTracking verdict RED, GA4 vs Shopify revenue divergence -34%
50
ICE i
I5·C5·E5
399
Data-supportediSev 2 · minoriInvestigateianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most desktop carts never reach checkout
A 94% carry-over is implausible and likely reflects duplicate or misfiring begin_checkout events rather than real behavior.
What's happening

Desktop shows 94% of cart-adders beginning checkout, far above the 40–60% band, an implausible result.

  • Add to Cart → Begin Checkout94% vs 40–60% (implausibly high)

Likely cause Likely duplicate begin_checkout event firing (e.g., on drawer open and again on checkout load) rather than genuine conversion; verify by counting unique begin_checkout hits per session.

Do this — in order
  1. Audit begin_checkout event triggers in GTM
    Check for duplicate firing on cart drawer interactions vs actual checkout page load.
    ~2 h · analytics · Client dev
  2. Deduplicate begin_checkout by session/order ID
    Prevents inflated retention numbers from skewing funnel analysis.
    ~2 h · analytics · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Desktop Add to Cart → Begin Checkout retention 94% vs band 40–60%Tracking verdict REDGA4 vs Shopify revenue divergence -28%
50
ICE i
I4·C5·E6
400
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers are repeatedly clicking things on the site that don't respond
High dead-click volume across both devices indicates UI elements that look clickable but aren't, frustrating shoppers before they can convert.
What's happening

Clarity recorded 440 dead clicks and 55 rage clicks across the site in 30 days.

  • Dead Clicks (site)440 high volume

Likely cause Non-interactive elements styled to look clickable (e.g. static badges or disabled buttons); confirm by reviewing top dead-click page recordings.

Do this — in order
  1. Review top dead-click session recordings in Clarity
    Identify which specific elements shoppers expect to be clickable.
    ~2 h · analytics · Evolut (LP)
  2. Fix or remove non-functional clickable-looking elements
    Directly resolves the friction once hotspots are identified.
    ~1 day · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
440 total dead clicks (175 mobile, 265 desktop)55 total rage clicks (26 mobile, 29 desktop)
50
ICE i
I5·C4·E6
401
Data-supportediSev 1 · cosmeticiJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Mobile cart-to-checkout retention is 39%, just under the 40% floor, a small but easy-to-close gap worth about $19/month.
What's happening

Mobile Add to Cart→Checkout retention is 39%, just below the 40% floor.

  • Add to Cart → Begin Checkout39% vs 40–60%

Likely cause The slide-out cart drawer's checkout button may lack prominence or trust signals, causing hesitation before checkout starts.

Do this — in order
  1. Make the checkout button the single most prominent element in the drawer
    Increase size/contrast so it's the obvious next step after adding to cart.
    ~30 min · theme edit · Client dev
  2. Add a shipping/returns trust line inside the cart drawer
    Reassures shoppers before they commit to checkout.
    ~30 min · copy · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart → Begin Checkout retention 39% vs 40–60% bandMobile recoverable $19/month
50
ICE i
I3·C4·E8
402
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers repeatedly click things that don't respond
High dead-click volume with low scroll depth signals broken or confusing UI elements suppressing engagement across the funnel.
What's happening

188 dead clicks and 33% average scroll depth suggest shoppers hit non-functional page elements site-wide.

  • Sitewide dead clicks188 high count
  • Sitewide avg scroll depth33% low engagement

Likely cause Non-clickable images or text styled as buttons, or slow-loading interactive elements, likely cause dead clicks; confirm via heatmap review.

Do this — in order
  1. Review top 10 Clarity dead-click heatmaps
    Identify which elements shoppers mistake for clickable controls.
    ~2 h · analytics · Evolut (LP)
  2. Restyle non-interactive elements that look clickable
    Remove button-like styling from static text/images causing dead clicks.
    ~1 day · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
188 dead clicks sitewide (141 desktop, 47 mobile)Average scroll depth only 33% sitewide
50
ICE i
I5·C4·E6
403
Data-supportediSev 2 · minoriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
A small but easy-to-fix leak just under the band floor, cheap to address inside the cart drawer (provisional pending tracking fix).
What's happening

Mobile Add to Cart → Begin Checkout sits at 39%, just under the 40% band floor.

  • Add to Cart → Begin Checkout39% vs 40–60%

Likely cause Likely a buried checkout button or missing shipping-cost clarity in the slide-out cart drawer; check drawer CTA visibility vs shipping-threshold messaging.

Do this — in order
  1. Make the checkout button sticky at the top of the cart drawer
    Ensure the primary CTA is visible without scrolling in the drawer.
    ~2 h · theme edit · Client dev
  2. Add a free-shipping progress bar to the drawer
    Clarify shipping cost/threshold before the shopper reaches checkout.
    ~2 h · copy · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart → Begin Checkout retention 39% vs 40–60% bandRecoverable ≈$26/moMobile sessions: 3,071
50
ICE i
I3·C5·E7
404
Data-supportediSev 2 · minoriInstrumentianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most desktop carts never reach checkout
A 100% carry-over is not physically plausible and undermines confidence in every downstream desktop number.
What's happening

Desktop Add to Cart → Begin Checkout shows 100% retention, above the plausible 40–60% band.

  • Add to Cart → Begin Checkout100% vs 40–60% band
  • Begin Checkout → Purchase23% vs 40–60% band

Likely cause The begin_checkout event may fire automatically whenever add_to_cart fires (duplicate trigger), or add_to_cart may be undercounted; check GA4 DebugView for duplicate event pairs to tell which.

Do this — in order
  1. Audit GA4 begin_checkout trigger for duplication with add_to_cart
    Confirms whether the two events are firing together incorrectly.
    ~2 h · analytics · Evolut (analytics)
  2. Verify the drawer's Checkout button fires a distinct event from Add to Cart
    Ensures the two funnel steps are measured independently.
    ~30 min · analytics · Evolut (analytics)
  3. Cross-check Shopify checkout counts against GA4 for desktop
    Validates whether the 100% figure is a measurement artifact.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
desktop Add to Cart→Begin Checkout retention 100% vs band 40–60%desktop sessions 1,354
405
Data-supportediSev 1 · cosmeticiJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
A real, though small, below-band leak in the cart drawer itself, distinct from the upstream ATC leak.
What's happening

39% of mobile cart-adds proceed to checkout, just under the 40–60% band floor.

  • Add to Cart → Begin Checkout39% vs 40–60% band
  • Begin Checkout → Purchase47% vs 40–60% band

Likely cause The drawer likely lacks a prominent checkout CTA or reassurance (shipping/returns), causing hesitation before leaving it.

Do this — in order
  1. Make the checkout CTA sticky in the cart drawer
    Keeps the primary action visible without scrolling inside the drawer.
    ~30 min · theme edit · Client dev
  2. Show shipping cost and returns note in the drawer
    Answers common cost objections before the shopper exits to checkout.
    ~30 min · copy · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart→Begin Checkout 39% vs band 40–60%Recoverable $29/monthCart experience is a slide-out drawer with no separate /cart page
50
ICE i
I3·C4·E8
406
Data-supportediSev 1 · cosmeticiJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Small but easy-to-fix gap just below the band floor in the cart drawer, the last step before checkout begins.
What's happening

Mobile shoppers who add to cart proceed to checkout only 39% of the time, just under the 40–60% band.

  • Add to Cart → Begin Checkout39% just below 40–60% band
  • Begin Checkout → Purchase43% within band

Likely cause The cart drawer may lack a prominent checkout CTA or visible shipping/returns info, causing hesitation before checkout starts.

Do this — in order
  1. Add a sticky checkout button in cart drawer
    Make the checkout CTA impossible to miss inside the drawer.
    ~2 h · theme edit · Client dev
  2. Show shipping/returns info in drawer
    Displaying policy details upfront reduces checkout hesitation.
    ~30 min · copy · Client dev
  3. Add express-checkout wallet buttons in drawer
    Shop Pay/PayPal buttons cut steps to begin checkout.
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
mobile Add to Cart→Begin Checkout retention 39% vs 40–60% bandrecoverable $32/momobile sessions 3139
50
ICE i
I2·C5·E8
407
Data-supportediSev 2 · minoriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
This step sits just under its band floor and is the second mobile leak recoverable amount identified in the snapshot.
What's happening

Mobile add-to-cart rate is 4%, just under the 5–10% band floor, right on the product page.

  • Session Start → View Product80% vs 20–45% band
  • View Product → Add to Cart4% vs 5–10% band

Likely cause Product page may lack a clear value prop or fast-loading imagery on mobile; distinguish via price/CTA clarity vs page-speed testing, since no behavioral data exists yet.

Do this — in order
  1. Simplify mobile product page above the fold
    Lead with price, core benefit, and a single Add to Cart CTA.
    ~1 day · LP build · Evolut (LP)
  2. Compress mobile product images
    Faster load reduces bounce before shoppers reach the CTA.
    ~2 h · theme edit · Evolut (LP)
  3. Add sticky Add to Cart bar on mobile PDP
    Keeps CTA visible while shoppers scroll reviews/specs.
    ~2 h · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
mobile View Product→Add to Cart retention 4% vs band 5–10%mobile recoverable revenue $457/mo
50
ICE i
I5·C4·E6
408
Data-supportediSev 2 · minoriInvestigateibehaviorali
Desktop shoppers are clicking on things that don't respond
What's happening

Desktop shows 22 rage clicks and 221 dead clicks, signaling unresponsive page elements frustrating shoppers.

  • Rage Clicks (desktop)22 elevated
  • Dead Clicks (desktop)221 elevated

Likely cause Likely a non-clickable image or button styled as interactive, or a slow-loading element being repeatedly clicked; confirm via rage-click session recordings.

Do this — in order
  1. Pull session recordings for top rage-click URLs
    Identifies the exact broken or unresponsive element.
    ~2 h · analytics · Evolut (LP)
  2. Fix or remove the non-functional styled element
    Removes a silent friction point once identified.
    ~2 h · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
Desktop rage clicks 22Desktop dead clicks 221Desktop avg scroll 39%
47
ICE i
I4·C4·E6
409
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers aren't engaging with page content before leaving
Widespread dead clicks and shallow scroll suggest visitors aren't finding or engaging with key content, likely suppressing downstream conversion.
What's happening

Visitors average only 31% scroll depth and generate 526 dead clicks, signalling confusion or non-interactive elements.

  • Avg Scroll Depth31% low engagement
  • Dead Clicks526 high across devices

Likely cause Elements look clickable but aren't (e.g. static badges/accordions), or key content sits below the fold given the shallow scroll.

Do this — in order
  1. Audit top pages for non-functional clickable-looking elements
    526 dead clicks suggest taps on badges, icons, or static text.
    ~2 h · theme edit · Evolut (LP)
  2. Move key CTA and trust content above the fold
    31% average scroll means most below-fold content goes unseen.
    ~2 h · theme edit · Evolut (LP)
  3. Tag the worst-performing page in Clarity for review
    Pinpoint exact dead-click elements once the page is identified.
    ~1 day · analytics · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
526 total dead clicks (mobile 303, desktop 223)Average scroll depth 31% (mobile 24%, desktop 38%)Rage clicks 25 total (desktop 22, mobile 3)
47
ICE i
I5·C3·E6
410
Data-supportediSev 2 · minoriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Sitting at the band floor signals weak mobile product-page persuasion, compounding the downstream checkout leak.
What's happening

Mobile product pages convert only 5% of viewers to cart adds, the lowest edge of the healthy 5–10% range.

  • Session → View Product (mobile)69% above 20–45% band
  • View Product → Add to Cart (mobile)5% floor of 5–10% band

Likely cause Weak mobile PDP persuasion (reviews/pricing clarity) or slow load time suppressing add-to-cart; compare Clarity recordings against page speed data.

Do this — in order
  1. Add reviews and trust badges near Add to Cart
    Surface social proof directly above the mobile add-to-cart button.
    ~2 h · theme edit · Evolut (LP)
  2. Audit mobile PDP load speed
    Slow-loading images or scripts may cause visitors to leave before adding to cart.
    ~2 h · analytics · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
mobile View Product→Add to Cart 5%, at the floor of the 5–10% bandmobile sitewide conversion 0.54% vs 1.5–3.5% band
47
ICE i
I5·C3·E6
411
TriangulatediSev 2 · minoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Sits right at the band floor with low scroll depth, suggesting the add-to-cart decision point isn't being reached or seen clearly.
What's happening

Mobile View→Add to Cart converts at 5%, the band floor, with only 25% average scroll depth.

  • Session → View Product70% above 20–45% band
  • View → Add to Cart5% at floor of 5–10% band
  • Add to Cart → Checkout65% above 40–60% band

Likely cause The add-to-cart CTA may sit below the 25% average scroll fold, or price/value isn't clear before shoppers lose interest.

Do this — in order
  1. Move add-to-cart button above the fold
    Low 25% scroll depth means most never reach a CTA placed lower on the page
    ~2 h · theme edit · Evolut (LP)
  2. Add a sticky mobile add-to-cart bar
    Keep the CTA visible regardless of scroll position
    ~2 h · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 5%, at the floor of the 5–10% bandMobile recoverablePerMonth $22Mobile average scroll depth 25%
47
ICE i
I3·C5·E6
412
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers are clicking things on the site that don't respond, and barely scrolling
High dead-click volume plus shallow scroll depth suggest broken or unresponsive page elements are suppressing engagement before shoppers can convert.
What's happening

366 dead clicks and only 30% average scroll depth suggest shoppers hit unresponsive elements before engaging further.

  • Dead Clicks (mobile)228 high vs 2 rage clicks
  • Avg Scroll Depth (mobile)25% low engagement

Likely cause Likely non-functional UI elements (accordions, swatches) read as dead clicks, or thin above-fold content causing early exit.

Do this — in order
  1. Watch top Clarity recordings with dead clicks
    Identify exactly which elements users repeatedly click without response.
    ~2 h · analytics · Evolut (LP)
  2. Fix or remove unresponsive UI elements found
    Make clicked links, swatches or accordions functional to cut friction.
    ~1 day · theme edit · Evolut (LP)
  3. Move key content above the fold
    25–36% scroll depth means most page content goes unseen.
    ~2 h · copy · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
366 dead clicks sitewide (228 mobile, 138 desktop)Avg scroll depth 30% overall (25% mobile, 36% desktop)Clarity worst page not yet identified
47
ICE i
I5·C4·E5
413
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers are clicking on things that don't respond, site-wide
High dead-click volume on both devices suggests non-functional or confusing UI elements, though the specific page isn't yet identified.
What's happening

427 dead clicks recorded sitewide with the worst-performing page not yet identified.

  • Dead clicks (mobile)247 high
  • Dead clicks (desktop)180 high
  • Avg scroll depth29% low engagement

Likely cause Elements that look clickable (badges, accordions, images) aren't wired to actions; confirm via per-page dead-click breakdown once worst-page data populates.

Do this — in order
  1. Pull Clarity dead-click heatmaps per page
    Identify which specific elements/pages drive the 427 dead clicks.
    ~2 h · analytics · Evolut (LP)
  2. Fix or remove the non-functional UI elements found
    Convert dead-click hotspots into working links/buttons.
    ~1 day · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
427 total dead clicks in Clarity (247 mobile, 180 desktop)Average scroll depth only 29% sitewideRage clicks: 15 total
47
ICE i
I5·C4·E5
414
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers are clicking on things that don't work hundreds of times a month
509 dead clicks and 38 rage clicks in 30 days point to broken or confusing UI elements across both devices.
What's happening

Shoppers clicked on non-functional elements 509 times and rage-clicked 38 times in 30 days, signaling broken UI.

  • Dead Clicks (mobile)287 non-functional clicks/mo
  • Dead Clicks (desktop)222 non-functional clicks/mo
  • Avg Scroll Depth29% sitewide, low engagement

Likely cause Likely decorative or disabled UI elements (badges, swatches, accordions) are being tapped as if interactive; audit non-CTA elements across top pages.

Do this — in order
  1. Map dead-click hot spots by page
    Use Clarity heatmaps to find exactly which elements shoppers mistake for interactive.
    ~2 h · analytics · Evolut (LP)
  2. Convert decorative elements to real links/buttons
    Make clicked icons, badges, or accordions actually function or remove hover styling.
    ~1 day · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
509 total dead clicks (mobile 287, desktop 222)38 total rage clicks (mobile 26, desktop 12)Avg scroll depth 29% sitewide
47
ICE i
I5·C5·E4
415
Data-supportediSev 2 · minoriInvestigateianalyticsi
Refunds are eating a meaningful slice of revenue
A 5.6% refund rate is elevated for supplements and may point to product mismatch or order/checkout errors worth investigating.
What's happening

Refunds equal 5.6% of revenue ($123.15 of $2,208.37), higher than typical supplement benchmarks.

  • Refund Rate5.6% vs <3% typical

Likely cause Could stem from product/expectation mismatch or duplicate/erroneous checkout charges; distinguish by tagging refund reason codes.

Do this — in order
  1. Tag refund reasons in Shopify admin
    Categorize refunds to see if driven by product or checkout issues.
    ~30 min · analytics · Evolut (LP)
  2. Review the 10 most recent refunded orders
    Check for a common SKU, shipping delay, or duplicate-charge pattern.
    ~2 h · analytics · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
Refunds $123.15 on $2,208.37 revenue (5.6%)Shopify orders: 75
47
ICE i
I4·C3·E7
416
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers are clicking things on the site that don't respond
Nearly 200 rage clicks and over 1,000 dead clicks signal real on-page friction that likely compounds the checkout and cart-drawer leaks.
What's happening

Desktop shows the bulk of dead clicks (715) and rage clicks (166), indicating unresponsive or confusing page elements.

  • Desktop dead clicks715 majority of sitewide total
  • Mobile dead clicks293 lower but notable

Likely cause Elements that look clickable but aren't (e.g. static images/badges) or slow-loading buttons on key pages; reviewing Clarity recordings on top pages would confirm which.

Do this — in order
  1. Review Clarity recordings on top-traffic pages
    Identify exactly which elements trigger dead and rage clicks.
    ~2 h · analytics · Evolut (LP)
  2. Fix or restyle non-functional clickable-looking elements
    Remove ambiguity that causes repeated frustrated clicks.
    ~1 day · theme edit · Evolut (LP)
  3. Move key CTA/content higher on the page
    29% average scroll means most visitors miss lower content.
    ~2 h · copy · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
1,008 dead clicks sitewide (293 mobile, 715 desktop) in 30 days188 rage clicks sitewide (22 mobile, 166 desktop)Average scroll depth 29% overall (21% mobile, 38% desktop)
47
ICE i
I5·C4·E5
417
Data-supportediSev 2 · minoriHypothesizeianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile view-to-cart sits at the very floor of its band (5% vs 5–10%), a small ($9/mo) but real leak worth a low-effort product-page fix.
What's happening

Mobile View Product→Add to Cart is 5%, exactly at the band floor of 5–10%.

  • View Product → Add to Cart (Mobile)5% at band floor 5–10%
  • Session Start → View Product (Mobile)88% vs 20–45% band, implausibly high

Likely cause Product page may lack a clear value prop or price/serving clarity near the Add to Cart button; the 88% view rate is also implausible and may reflect tracking or bot inflation.

Do this — in order
  1. Add reviews/trust badges above the fold on product pages
    Builds confidence right where hesitation happens before Add to Cart.
    ~2 h · theme edit · Evolut (LP)
  2. State cost-per-serving near the Add to Cart button
    Clarifies value for a supplement buyer comparing options.
    ~30 min · copy · Evolut (LP)
  3. Check mobile session traffic sources for bot inflation
    An 88% view rate vs a 20–45% band suggests the denominator may be unreliable.
    ~30 min · analytics · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 5% (band floor 5–10%), $9/mo recoverableMobile Session→View Product retention 88% (band 20–45%) — unusually high
47
ICE i
I3·C4·E7
418
Data-supportediSev 2 · minoriInstrumentibehaviorali
You can't tell how many shoppers these click problems actually affect
Session counts of 0 alongside real click events mean Clarity's session tracking isn't reporting correctly, so click-friction findings can't be sized.
What's happening

Clarity reports 0 sessions on both devices even though rage and dead clicks were recorded, an instrumentation gap.

  • Clarity sessions (mobile)0 despite 35 rage / 296 dead clicks
  • Clarity sessions (desktop)0 despite 98 rage / 484 dead clicks

Likely cause Clarity's session-count field isn't wired into this reporting pipeline, or the Clarity snippet is misconfigured to log events without sessions.

Do this — in order
  1. Confirm Clarity snippet is installed on all templates
    Missing session counts often mean partial installation.
    ~30 min · analytics · Evolut (analytics)
  2. Reconnect Clarity session reporting to the dashboard feed
    Ensures future click-friction findings can be sized against traffic.
    ~2 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Clarity mobile sessions recorded: 0 despite 35 rage clicks and 296 dead clicksClarity desktop sessions recorded: 0 despite 98 rage clicks and 484 dead clicks
419
TriangulatediSev 2 · minoriHypothesizeianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile add-to-cart rate sits at the very bottom of its band, the smallest but still real leak in the mobile funnel.
What's happening

Mobile view-to-cart conversion is 5%, the floor of the 5–10% band, on 4,762 sessions.

  • View Product → Add to Cart5% at floor of 5–10% band

Likely cause Weak add-to-cart visibility or unclear product value on mobile product pages versus genuinely low purchase intent traffic; check scroll depth (avg 21% on mobile) to see if shoppers reach the CTA.

Do this — in order
  1. Move the Add to Cart button above the fold on mobile
    Avg mobile scroll depth is only 21%, so many never reach it.
    ~2 h · theme edit · Evolut (LP)
  2. Add a sticky add-to-cart bar on mobile PDPs
    Keeps the CTA visible regardless of scroll position.
    ~2 h · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product→Add to Cart retention 5% vs 5–10% band (at floor)$38/month recoverable revenue
47
ICE i
I4·C4·E6
420
TriangulatediSev 2 · minoriInvestigateianalytics + behaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile product-page visitors never add to cart
Mobile ATC rate sits at the very floor of the 5-10% band, hinting at weak PDP persuasion.
What's happening

Mobile View→Add to Cart sits at 5%, the bottom edge of the 5–10% band.

  • View Product → Add to Cart5% floor of 5-10% band

Likely cause Likely weak PDP trust/CTA visibility, or the 284 mobile dead clicks show shoppers tapping non-interactive elements expecting action.

Do this — in order
  1. Move Add to Cart button above the fold
    Ensure the CTA is visible without scrolling on mobile PDPs.
    ~2 h · theme edit · Evolut (LP)
  2. Add reviews or trust badges near the CTA
    Boosts confidence at the exact decision point on product pages.
    ~2 h · theme edit · Evolut (LP)
  3. Investigate dead-click elements on top mobile PDPs
    284 mobile dead clicks suggest taps on images or badges expecting interaction.
    ~2 h · analytics · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Mobile View Product → Add to Cart retention 5% (floor of 5-10% band)Recoverable ~$37/month284 dead clicks on mobile (Clarity)Tracking verdict RED - treat as provisional
47
ICE i
I4·C4·E6
421
Data-supportediSev 2 · minoriInvestigateibehaviorali
Visitors are clicking on things that don't work, sitewide
High dead-click counts and low scroll depth point to broken or misleading UI elements suppressing engagement across the whole site.
What's happening

419 dead clicks and 32% average scroll depth suggest visitors hit non-functional elements sitewide.

  • Dead clicks (mobile/desktop)169 / 250 high sitewide
  • Avg scroll depth32% low engagement

Likely cause Non-clickable elements styled as buttons (badges, disabled swatches) or slow-loading interactive components; review Clarity recordings to confirm which.

Do this — in order
  1. Review Clarity recordings for top dead-click elements
    Identify which UI pieces users tap that don't respond.
    ~2 h · analytics · Evolut (LP)
  2. Fix or remove non-functional buttons/badges
    Convert dead-click hotspots into working links or remove them.
    ~1 day · theme edit · Evolut (LP)
  3. Compress above-fold assets to speed load
    Address low scroll depth possibly caused by slow-loading top content.
    ~2 h · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
419 total dead clicks (169 mobile, 250 desktop)Average scroll depth 32% (21% mobile, 43% desktop)55 rage clicks sitewide
47
ICE i
I5·C4·E5
422
Data-supportediSev 2 · minoriInvestigateibehaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most product-page visitors never add to cart
High dead- and rage-click counts point to broken or confusing page elements suppressing engagement before shoppers ever reach add-to-cart.
What's happening

295 dead clicks and 51 rage clicks sitewide suggest unresponsive elements frustrating shoppers pre-purchase.

  • Desktop dead clicks164 high friction signal
  • Mobile dead clicks131 high friction signal

Likely cause Non-functional elements styled as clickable (e.g., size guides, accordions) or mistaken clicks on static images; session recordings will confirm which.

Do this — in order
  1. Review top 10 Clarity recordings for dead clicks
    Pinpoint exact elements causing dead/rage clicks
    ~2 h · analytics · Evolut (LP)
  2. Fix or remove non-interactive elements styled as clickable
    Removes false affordances causing dead clicks
    ~2 h · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
295 total dead clicks (131 mobile, 164 desktop)51 total rage clicks (22 mobile, 29 desktop)Average scroll depth only 32% overall (21% mobile, 44% desktop)
47
ICE i
I5·C3·E6
423
Data-supportediSev 2 · minoriJust Do Itianalyticsi
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most mobile carts never reach checkout
Mobile cart-to-checkout conversion is 38%, just under the 40–60% floor, costing an estimated $61/month.
What's happening

Mobile cart-to-checkout conversion is 38%, just under the 40–60% floor, losing ~$61/month.

  • Add to Cart → Begin Checkout38% vs 40–60% band

Likely cause The slide-out cart drawer likely lacks a prominent checkout CTA or reassurance copy, causing hesitation; verify via drawer session recordings.

Do this — in order
  1. Add a sticky, high-contrast Checkout button in the cart drawer
    Increases visibility of the next step directly inside the drawer.
    ~2 h · theme edit · Client dev
  2. Show shipping and returns info inside the drawer
    Answers common objections without leaving the drawer.
    ~30 min · copy · Client dev
  3. Add express checkout buttons inside the drawer
    Shortens the path from cart drawer straight to payment.
    ~2 h · theme edit · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Mobile Add to Cart → Begin Checkout retention 38% vs 40–60% band$61/month recoverable revenue
47
ICE i
I3·C4·E7
424
Data-supportediSev 2 · minoriInvestigateibehaviorali
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most product-page visitors never add to cart
72 dead clicks and just 32% average scroll depth suggest shoppers are clicking non-functional elements and disengaging before reaching add-to-cart.
What's happening

72 dead clicks and 32% average scroll depth point to broken or ignored on-page elements sitewide.

  • Dead Clicks (sitewide)72 high, indicates non-responsive elements
  • Rage Clicks (sitewide)25 elevated, frustration signal
  • Avg Scroll Depth32% low engagement with page content

Likely cause Elements styled as clickable (badges, swatches) with no handler, or broken JS bindings, cause dead clicks; verify via session recordings vs a code audit.

Do this — in order
  1. Review top 10 Clarity recordings on PDP
    Pinpoints exact elements causing dead/rage clicks before any code changes.
    ~2 h · analytics · Evolut (LP)
  2. Fix or restyle non-functional clickable elements
    Convert dead-click hotspots into working links or static, non-clickable styling.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Sitewide dead clicks: 72 in 30 daysSitewide rage clicks: 25Average scroll depth: 32%Desktop dead clicks 59, rage clicks 25, avg scroll 43%
47
ICE i
I5·C4·E5
425
Data-supportediSev 2 · minoriInvestigateianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most desktop carts never reach checkout
An 89% cart-to-checkout carry-over is far above the 40–60% band, suggesting duplicate begin_checkout events rather than genuine behavior.
What's happening

Desktop Add to Cart→Begin Checkout sits at 89%, roughly 30pts above the band ceiling.

  • Add to Cart → Begin Checkout89% vs 40–60% band
  • Begin Checkout → Purchase22% vs 40–60% band

Likely cause Either begin_checkout fires multiple times per session (event duplication) or a returning-cart flow auto-advances shoppers; check GA4 event counts vs unique sessions.

Do this — in order
  1. Compare GA4 begin_checkout event count to unique sessions
    Reveals whether the event fires more than once per checkout.
    ~30 min · analytics · Client dev
  2. Cross-check Shopify checkout starts vs GA4 count
    Confirms the true cart-to-checkout carry-over rate.
    ~2 h · analytics · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
desktop Add to Cart→Begin Checkout retention 89% vs 40–60% banddesktop sessions 1386 (low volume)
47
ICE i
I4·C4·E6
426
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers are clicking on things that don't respond, sitewide
466 dead clicks and 23 rage clicks sitewide signal broken or non-responsive UI elements that could be suppressing multiple funnel steps, but the exact page is unidentified.
What's happening

466 dead clicks and 23 rage clicks sitewide suggest unresponsive UI elements, but the exact page isn't yet known.

  • Mobile dead clicks270 high volume
  • Desktop dead clicks196 high volume
  • Rage clicks (sitewide)23 elevated

Likely cause Dead/rage clicks suggest non-interactive elements styled as clickable (e.g., disabled buttons, slow-loading swatches); confirm via session recordings on top entry pages.

Do this — in order
  1. Filter Clarity recordings by dead-click events
    Identify the exact page/element behind 466 dead clicks before building fixes
    ~2 h · analytics · Evolut (LP)
  2. Populate the worst-page field in Clarity setup
    Currently blank, blocking root-cause targeting of UI friction
    ~30 min · analytics · Evolut (LP)
  3. Cross-check rage-click pages against mobile PDP
    Rage clicks may cluster at the same Add to Cart button already flagged as a leak
    ~2 h · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
sitewide dead clicks: 466 (270 mobile + 196 desktop)sitewide rage clicks: 23worstPage not identified ('—')
43
ICE i
I5·C4·E4
427
Data-supportediSev 2 · minoriInvestigateibehaviorali
Hundreds of monthly clicks hit dead, unresponsive page elements
501 dead clicks in 30 days shows shoppers repeatedly tapping elements that don't respond, a sign of confusing or broken UI likely contributing to drop-off.
What's happening

501 dead clicks and 25 rage clicks in 30 days point to UI elements that look clickable but aren't responding.

  • Dead clicks (mobile)280 30-day total
  • Dead clicks (desktop)221 30-day total
  • Rage clicks (desktop)22 30-day total

Likely cause Non-functional buttons or decorative elements that mimic controls (e.g. fake swatches, disabled filters) are the likely trigger; reviewing recordings on top-traffic pages will confirm which.

Do this — in order
  1. Watch 10 Clarity recordings showing dead clicks
    Pinpoint the exact elements and pages causing non-responsive taps.
    ~2 h · analytics · Evolut (LP)
  2. Fix or remove the non-functional UI elements found
    Remove or wire up decorative elements that look clickable but do nothing.
    ~1 day · theme edit · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
501 dead clicks sitewide over 30 days (280 mobile, 221 desktop)25 rage clicks sitewide (22 desktop, 3 mobile)clarity worstPage unidentified (—)
40
ICE i
I5·C3·E4
428
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers keep clicking things on the site that don't respond
825 dead clicks and 134 rage clicks indicate site-wide friction that likely suppresses both add-to-cart and checkout rates across devices.
What's happening

Shoppers rage-click 134 times and dead-click 825 times sitewide, signaling broken or confusing UI elements.

  • Sitewide Dead Clicks825 mobile 303 / desktop 522
  • Sitewide Rage Clicks134 mobile 26 / desktop 108

Likely cause Elements that look clickable (images, badges) aren't interactive, or slow responses trigger repeat clicks; distinguish via session recordings on top pages.

Do this — in order
  1. Watch top 10 Clarity recordings on PDP and cart drawer
    Pinpoint exact elements causing dead/rage clicks before fixing them.
    ~2 h · analytics · Evolut (LP)
  2. Fix or remove non-functional clickable-looking elements found
    Convert dead-click hotspots into working links or remove clickable styling.
    ~1 day · theme edit · Evolut (LP)
  3. Re-check load/interaction speed on worst-offending templates
    Slow responses can cause repeated rage-clicks.
    ~2 h · analytics · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
Sitewide deadClicks 825 (mobile 303 / desktop 522)Sitewide rageClicks 134 (mobile 26 / desktop 108)avgScrollPct 29% sitewide (mobile 21% / desktop 37%)
40
ICE i
I5·C3·E4
429
Data-supportediSev 2 · minoriInvestigateibehaviorali
⚡ Clarity: JS errors 11.8% (mobile) — the most likely single cause, and the cheapest to rule out.
Most desktop product-page visitors never add to cart
High dead/rage-click volume relative to sessions suggests broken or confusing UI elements interfering with browsing before add-to-cart, worse on desktop.
What's happening

Desktop shows 705 dead clicks and 165 rage clicks against only 38% average scroll depth.

  • Desktop dead clicks (30d)705 vs 165 rage clicks
  • Desktop avg scroll depth38% low for product pages

Likely cause Likely non-functional elements styled as buttons (e.g. fake add-to-cart or accordions) causing dead clicks, or slow-loading scripts causing rage clicks; session replay will confirm which.

Do this — in order
  1. Review top Clarity recordings with dead clicks
    Identify the specific element(s) users repeatedly click without response.
    ~2 h · analytics · Evolut (LP)
  2. Fix or remove non-functional UI elements found
    Convert dead/rage-click hotspots into working links or buttons.
    ~1 day · theme edit · Evolut (LP)
Success Step retention ≥ 5% (band floor)
Evidence & numbers
Desktop dead clicks: 705, rage clicks: 165 (30 days)Desktop avg scroll depth: 38%Mobile dead clicks: 288, avg scroll: 21%
40
ICE i
I4·C3·E5
430
Data-supportediSev 2 · minoriInstrumentibehaviorali
Behavioral analytics session counts don't match the click data being recorded
A behavioral tool reporting zero sessions while logging hundreds of clicks means its session counting is broken, undermining confidence in click-based findings.
What's happening

Clarity reports 0 sessions on both devices despite recording hundreds of dead/rage clicks, indicating broken session counting.

  • Clarity Mobile Sessions0 vs 315 dead clicks logged
  • Clarity Desktop Sessions0 vs 782 dead clicks logged

Likely cause The Clarity session-count field likely isn't populated in this export/API pull, a config bug rather than an actual traffic issue.

Do this — in order
  1. Re-check Clarity project session count field
    Confirm the dashboard shows nonzero sessions matching GA4 sessions.
    ~30 min · analytics · Evolut (analytics)
  2. Re-export Clarity data feed
    Refresh or reconnect the Clarity integration used for this snapshot.
    ~30 min · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Clarity mobile sessions: 0 despite 315 dead clicks recordedClarity desktop sessions: 0 despite 782 dead clicks recorded
431
Data-supportediSev 1 · cosmeticiInvestigateianalyticsi
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most desktop carts never reach checkout
An 87% cart-to-checkout rate is unusually high and could mean Add to Cart events are undercounted, muddying where desktop shoppers really drop off.
What's happening

Desktop Add to Cart → Begin Checkout is 87%, far above the 40–60% band ceiling, an unusual jump.

  • Add to Cart → Begin Checkout87% vs 40–60% band ceiling

Likely cause Add-to-cart events may be undercounted (e.g. a buy-now button skipping the cart event) versus checkout genuinely converting at an unusually high rate.

Do this — in order
  1. Audit the Add to Cart event on desktop buy-now buttons
    Confirms whether buy-now flows bypass the add-to-cart tag, inflating this ratio.
    ~30 min · analytics · Client dev
  2. Cross-check GA4 add-to-cart count against Shopify cart data
    Validates whether the discrepancy is measurement or real behavior.
    ~30 min · analytics · Client dev
Success Step retention ≥ 40% (band floor)
Evidence & numbers
Desktop Add to Cart → Begin Checkout retention is 87% vs 40–60% band ceiling1,390 desktop sessions/moOverall tracking verdict is GREEN, yet this ratio sits well outside the expected range
40
ICE i
I4·C3·E5
432
Data-supportediSev 2 · minoriInvestigateibehaviorali
Shoppers are clicking things on the site that don't do anything
High dead-click volume signals broken or confusing interactive elements, but the specific page isn't captured, so this needs investigation before a fix can be prescribed.
What's happening

382 dead clicks sitewide (246 mobile, 136 desktop) indicate shoppers clicking non-responsive elements, but the page is unidentified.

  • Mobile dead clicks246 high volume
  • Desktop dead clicks136 high volume

Likely cause Non-interactive elements styled to look clickable (e.g. images, disabled buttons) are likely collecting clicks; needs page-level Clarity review to confirm.

Do this — in order
  1. Enable page-level Clarity tagging
    Capture which URL each dead click occurs on to target the fix
    ~30 min · analytics · Evolut (LP)
  2. Review top dead-click session recordings
    Watch 10-15 sessions to identify the specific element causing non-response
    ~2 h · analytics · Evolut (LP)
Success Beats the current baseline in an A/B test
Evidence & numbers
382 total dead clicks (mobile 246, desktop 136)worstPage not identified in current Clarity setup
37
ICE i
I4·C3·E4
433
Expert opinioniSev 0iInstrumentiheuristici
⚡ Clarity: Dead clicks (desktop) — the most likely single cause, and the cheapest to rule out.
Most checkouts never finish
The Begin Checkout → Purchase retention is implausibly low — below half its band floor on a store whose GA4↔Shopify tracking is already suspect. Treat this as a measurement fault first (duplicate or missing purchase events, consent-mode gaps, checkout not tagged across domains), not a real funnel collapse: diagnose the event before acting, because the number itself cannot be trusted yet.
What's happening

The Begin Checkout → Purchase retention sits below half its typical range on a store whose GA4↔Shopify tracking is already suspect.

Likely cause Most likely a tracking artefact — missing/duplicate events or consent-mode gaps — not a genuine funnel failure.

Do this — in order
  1. Instrument the Begin Checkout → Purchase event
    Confirm it fires exactly once per real transition.
    ~2 h · analytics · Evolut (analytics)
  2. Check consent-mode gaps
    Verify consented conversions aren't being dropped.
    ~1 h · analytics · Evolut (analytics)
  3. Confirm cross-domain checkout tagging
    Ensure the checkout domain carries the GA4 session.
    ~1 h · analytics · Evolut (analytics)
Success GA4 ↔ Shopify revenue within ±20%
Evidence & numbers
Desktop Begin Checkout→Purchase 7% vs 40–60% bandDesktop sitewide CR 0.14% vs 1.5–3.5% band76 orders/month recoverable at this step23 abandoned checkouts (Shopify)
434
Expert opinioniSev 0iInstrumentiheuristici
Revenue reports can't be trusted for any funnel decision
Tracking verdict is RED with a -31% GA4/Shopify revenue gap; every funnel number below is provisional until this is fixed.
What's happening

GA4 undercounts revenue by 31% vs Shopify, so all downstream funnel percentages are unreliable.

  • GA4 vs Shopify Revenue$1,391 vs $2,007 -31% divergence
  • Desktop Add to Cart → Begin Checkout80% vs 40–60% band (implausible)

Likely cause placeholder

Evidence & numbers
GA4 revenue $1391 vs Shopify revenue $2007 (-31% divergence)Desktop Add to Cart→Begin Checkout retention 80% vs 40-60% band (implausibly high)
435
Expert opinioniSev 0iInstrumentiheuristici
placeholder