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.
- Audit GA4 purchase event in GTM preview modeConfirm it fires once per order with correct value/currency parameters.
- Check consent-mode and cookie-banner configurationNull consentRatePct suggests consent signals may be suppressing GA4 hits entirely.
- Reconcile 10 sample orders between GA4 and ShopifyPinpoint exactly where GA4 loses the purchase event.
Evidence & numbers
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.
- Compare GA4 purchase hits against Shopify order IDsIdentify which orders GA4 is missing to isolate the firing issue
- Check consent banner impact on purchase tag firingConfirm analytics consent isn't silently blocking the purchase event
- Add Shopify order webhook as a server-side backup feedRemoves reliance on client-side GA4 tag for revenue truth
Evidence & numbers
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.
- Audit GA4 purchase event firingConfirm the event fires exactly once per completed order and matches Shopify order IDs.
- Check consent-mode and tag-blocking impactVerify whether GA4 tags are blocked pre-consent, undercounting purchases.
- Build a daily GA4-vs-Shopify reconciliation checkCatch future divergence early before it skews CRO decisions.
Evidence & numbers
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.
- Audit GA4 purchase events against Shopify order webhooksReveals whether events are missing, duplicated, or blocked.
- Implement server-side GA4 tagging for ShopifyRemoves reliance on client-side JS that can fail or be blocked by ad blockers.
- Check consent mode default settingsIf consent isn't granted by default, GA4 under-reports vs Shopify's native count.
Evidence & numbers
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.
- Audit GA4 purchase event against Shopify order webhookConfirms whether events are missing, duplicated, or blocked by consent mode.
- Add Shopify order ID as a dedupe key in GA4Prevents double-counting or dropped purchases from refreshes.
- Implement server-side purchase trackingCaptures orders missed by client-side tags due to ad blockers or script errors.
Evidence & numbers
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.
- Audit GA4 purchase event firingCompare triggered events to confirmed Shopify orders to find where tracking drops
- Check consent banner default stateA default-denied consent state can silently block GA4 purchase events
- Add server-side GA4 tagging via Conversions APIServer-side capture avoids ad-blockers and consent gaps causing dropped events
Evidence & numbers
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.
- Audit GA4 purchase event firing on order confirmationConfirm the purchase event fires for every completed order, not a subset.
- Add Shopify server-side conversions feedReduces reliance on client-side tags blocked by ad blockers or consent tools.
- Build a daily GA4 vs Shopify revenue reconciliation checkCatches future divergence before funnel data is trusted again.
Evidence & numbers
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.
- Audit GA4 purchase event firing on order confirmation pageConfirm it fires once per order with correct transaction_id to stop drops or double-counts.
- Reconcile GA4 vs Shopify order counts daily for 7 daysPinpoints whether the gap comes from missing sessions, blockers, or dedup suppression.
- Add Shopify-native or server-side GA4 trackingReduces reliance on client-side script that can be blocked or delayed.
Evidence & numbers
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.
- Audit GA4 purchase event firing on order confirmation pageConfirm it fires once per order and matches Shopify's 90 orders.
- Check consent-mode/cookie banner for blocked tagsconsentRatePct is null — verify consent isn't suppressing purchase events.
- Deduplicate GTM triggers firing the purchase tagMultiple containers/triggers can cause under- or over-counting.
Evidence & numbers
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.
- Audit GA4 purchase event firing across all payment pathsConfirm the event fires for Shop Pay, express wallets, and standard checkout equally.
- Check GA4 consent mode configurationNull consentRatePct suggests consent signals may be unset, silently dropping purchase hits.
- Reconcile GA4 vs Shopify order IDs for a sample weekPinpoint exactly which order types are missing from GA4 to confirm root cause.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GA4 purchase event firingConfirm the purchase event fires reliably on the order confirmation page for all traffic.
- Add server-side tracking via Shopify appReduce data loss from ad-blockers/consent by sending purchase events server-side.
- Set weekly GA4-vs-Shopify revenue reconciliationCatch future divergence early before it skews decisions.
Evidence & numbers
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.
- Audit GA4 purchase event against Shopify order webhookConfirms whether GA4 is missing or double-counting transactions.
- Verify gtag/GTM fires on order confirmation for all devicesMobile-only misfires are a common cause of large divergence.
- Add server-side purchase tracking as backup feedBypasses client-side/consent blocking if that's the root cause.
Evidence & numbers
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.
- Audit GA4 purchase event on order confirmation pageConfirm it fires once per order with correct transaction_id and value.
- Cross-check GA4 vs Shopify order counts, not just revenueReveals whether the gap is missing orders or mismatched values.
- Implement server-side tagging (Conversions API)Reduces client-side tracking loss from ad blockers and consent gaps.
Evidence & numbers
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.
- Audit GA4 purchase event firingConfirm the purchase event fires exactly once per Shopify order, not zero or twice.
- Check consent-mode banner defaultsVerify the consent banner isn't blocking GA4 tags for a portion of shoppers pre-purchase.
- Set up a daily GA4-vs-Shopify revenue diff alertCatch future tracking divergence before it distorts CRO decisions.
Evidence & numbers
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.
- Audit GA4 purchase event firingConfirm the purchase event fires exactly once per completed order.
- Match GA4 DebugView order IDs to Shopify ordersFind missing or duplicated events causing the gap.
- Check consent banner and ad-blocker impactVerify consent mode isn't suppressing GA4 before purchase fires.
Evidence & numbers
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.
- Audit GA4 purchase event firing in real timeUse DebugView to confirm the purchase event fires on every completed Shopify order.
- Reconcile GA4 transaction IDs against Shopify ordersMatch IDs to isolate whether events are missing, duplicated, or delayed.
- Add server-side tracking as a fallbackReduces dependence on a client-side tag that can be blocked or delayed.
Evidence & numbers
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.
- Audit GA4 purchase event firingConfirm the purchase event fires on the order confirmation page and isn't blocked by consent mode.
- Verify Shopify-to-GA4 integration setupCheck for a missing, duplicated, or misconfigured e-commerce pixel causing the revenue gap.
- Reconcile consent banner default stateConfirm analytics consent isn't defaulting to denied, which would suppress GA4 events.
Evidence & numbers
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.
- Audit GA4 purchase event against Shopify order webhookCompare order IDs to find missing or duplicated purchase events.
- Verify GA4 purchase event fires once on thank-you pageDuplicate firing on refresh or multi-domain checkout skews revenue.
- Reconcile consent mode settingsNull consent rate suggests Consent Mode may be blocking some purchase pings.
Evidence & numbers
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.
- Audit GA4 event tags in GTMCheck for duplicate begin_checkout/purchase triggers inflating or dropping counts.
- Reconcile GA4 purchase events against Shopify ordersMatch order IDs to find missing or duplicated purchase events.
- Switch to Shopify's native GA4 integrationReduces client-side/ad-blocker loss that likely drives the revenue gap.
Evidence & numbers
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.
- Audit GA4 e-commerce tags for duplicate firingCheck begin_checkout/purchase tags in GTM preview mode
- Reconcile GA4 purchase count vs Shopify order IDsFind missing or duplicated purchase events causing the gap
- Add server-side or consent-mode fallback taggingRecovers data lost to consent-blocked browsers
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GA4 purchase event firingConfirm it fires once per order and order IDs match Shopify.
- Check consent mode configurationNull consent rate suggests consent signals may be suppressing tags.
- Reconcile GA4 with Shopify via native/server-side integrationClose the gap using Shopify's GA4 app or server-side GTM.
Evidence & numbers
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.
- Check consent-mode defaults blocking GA4 tagsnull consent rate suggests consent banner may suppress tracking
- Audit GA4 purchase event firing on order confirmationconfirm transaction_id dedupe and event fires once per order
- Reconcile Shopify order webhook against GA4 nightlycatch future divergence before it skews decisions
Evidence & numbers
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.
- Turn on Shopify abandoned-checkout audit firstCompare Shopify order IDs against GA4 purchase hits to quantify exactly which orders are missing.
- Check consent banner timing against tag firingconsentRatePct is null, suggesting consent mode may be suppressing GA4 tags before purchase fires.
- Verify purchase event only fires once per orderDuplicate or missing pixel firing on the thank-you page is a common cause of this size of gap.
Evidence & numbers
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.
- Audit GA4 purchase event against Shopify ordersMatch order IDs to find missing or duplicate purchase events.
- Check consent-mode settings before purchase firesConfirm the consent banner isn't blocking the GA4 tag on checkout completion.
- Move to server-side GA4 taggingReduces data loss from ad-blockers and browser tracking prevention.
Evidence & numbers
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.
- Audit GA4 purchase event firing on order confirmationConfirm it fires once per order and matches Shopify order IDs.
- Reconcile daily GA4 vs Shopify revenue for 7 daysValidates any fix before funnel percentages are trusted again.
- Implement server-side GA4 tagging via Shopify appReduces client-side blocking loss causing undercount.
Evidence & numbers
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.
- Audit GA4 purchase event on the order confirmation pageConfirm the tag fires reliably for every completed order
- Cross-check GA4 transaction IDs against Shopify order IDsPinpoints exactly which orders are missing from GA4
- Set up server-side tracking via GA4 Measurement ProtocolRemoves reliance on client-side tags that ad-blockers can drop
Evidence & numbers
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.
- Verify GA4 purchase event fires on every Shopify order confirmationCompare order IDs in Shopify to GA4 purchase hits to find the gap source
- Check consent mode and cookie-banner settings blocking GA4consentRatePct is null, suggesting consent signals aren't being captured at all
- Enable Shopify's native GA4 integration or server-side taggingRemoves dependence on client-side script that can be blocked or dropped
Evidence & numbers
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.
- Audit GA4 purchase event firing on order confirmation pageConfirms whether the event tag fires reliably for every completed order.
- Check consent banner for blocking tracking scriptsConsent-mode defaults can silently suppress GA4 events pre-consent.
- Implement server-side event tracking as backupCaptures purchases missed by client-side tags due to ad-blockers or script errors.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GA4 purchase event on the order confirmation pageConfirm the purchase tag fires every time, not just on some browsers.
- Install Shopify's native GA4 integration or server-side taggingReduces client-side event loss from ad-blockers and ITP.
- Reconcile GA4 vs Shopify revenue weekly until gap is under 10%Catches future tracking drift before it skews decisions.
Evidence & numbers
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.
- Add a sticky Add-to-Cart bar on mobile PDPKeeps the CTA visible given average scroll depth is only 23%.
- Review mobile dead-click recordings in ClarityFind which of the 269 dead-click elements shoppers expect to work.
- Surface reviews/trust badges above the fold on mobile PDPBuilds confidence before the scroll cutoff shoppers rarely pass.
Evidence & numbers
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.
- Audit GA4 purchase event firing against Shopify ordersConfirms whether events are missing, duplicated, or blocked on completion.
- Check consent mode and tag triggers in GTMNull consent rate suggests consent banner may be suppressing GA4 hits.
- Reconcile GA4 vs Shopify order IDs weeklyCatches future drift early before it skews CRO decisions again.
Evidence & numbers
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.
- Audit GA4 purchase event firingVerify the GA4 purchase tag fires correctly on the order confirmation page for every completed order.
- Reconcile GA4 vs Shopify order countsCompare daily order IDs between platforms to pinpoint where revenue is lost in tracking.
- Fix or reinstall GA4 Shopify integrationReinstall the official GA4/Shopify app or correct GTM container settings.
Evidence & numbers
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.
- Audit GA4 purchase events against Shopify order webhookCompare per-order event counts to pinpoint where GA4 drops transactions.
- Check consent-mode or cookie banner blocking the GA4 tagNull consentRatePct suggests consent signal isn't even being captured.
- Implement server-side GA4 purchase tracking via Shopify webhookRemoves reliance on client-side tag firing, closing the gap long-term.
Evidence & numbers
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.
- Audit GA4 purchase event firingConfirm the purchase event fires on the order-confirmation page for all sessions, not just consented ones.
- Check consent banner impact on taggingconsentRatePct is null, suggesting consent mode may be blocking event collection entirely.
- Reconcile GA4 vs Shopify order IDsMatch a sample of orders to find exactly where events drop out of GA4.
Evidence & numbers
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.
- Audit GA4 purchase event firingVerify the purchase event fires exactly once per Shopify order via GTM preview.
- Reconcile order IDs between GA4 and ShopifyMatch order IDs to find missing or duplicated purchase events causing the gap.
- Implement server-side conversion trackingSend purchase events server-side to cut loss from ad-blockers/consent mode.
Evidence & numbers
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.
- Audit GA4 purchase event firing on the order confirmation pageConfirm the e-commerce purchase event fires for every order type, including express-checkout.
- Check whether the cookie/consent banner blocks GA4 tagsconsentRatePct is null, suggesting tags may never fire for some visitors.
- Reconcile GTM container events against Shopify checkout extensibility scriptsLook for duplicate or missing event triggers causing the gap.
Evidence & numbers
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.
- Audit GA4 purchase event firing on the order confirmation pageConfirm the event fires once per order and the count matches Shopify's order total.
- Check consent mode and tag-blocking on checkoutNull consent rate suggests the consent banner may be blocking GA4 tags before purchase.
- Set up a weekly GA4-vs-Shopify revenue reconciliation checkCatch future tracking drift before it skews CRO decisions.
Evidence & numbers
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
- Audit GA4 purchase event firingCompare GA4 order IDs against Shopify orders to find missing conversions.
- Check consent-mode/cookie banner blockingconsentRatePct is null — verify the banner isn't suppressing purchase pings.
- Re-validate thank-you page purchase tagEnsure GTM/GA4 fires reliably on the order confirmation page.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Compare GA4 order count to Shopify order countFastest way to tell if events are missing vs values being wrong.
- Audit GA4 purchase event on order confirmation pageConfirm it fires once per order with correct value/currency.
- Move to server-side or native Shopify GA4 integrationCuts client-side tracking loss from ad-blockers and script issues.
Evidence & numbers
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.
- Audit GA4 purchase event firingConfirm the purchase tag fires on every order confirmation page.
- Reconcile GA4 transaction IDs against Shopify ordersPinpoint exactly which orders GA4 is missing.
- Implement consent mode loggingCapture consent state per session to explain revenue variance.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GTM tags for add_to_cart, begin_checkout, purchase eventsCheck for duplicate or missing fires causing the 104% and -27% anomalies.
- Reconcile GA4 purchase count against Shopify order countConfirms whether purchase events are deduplicated correctly per order.
- Enable Shopify's native GA4/server-side integrationReduces client-side event loss driving the revenue gap.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Compare GA4 and Shopify order IDs for gapsPinpoint whether events are missing, duplicated, or delayed.
- Check consent banner isn't blocking purchase pingsNull consent rate suggests CMP may be dropping events.
- Deploy server-side Shopify-to-GA4 forwardingFills gaps lost to ad blockers or client-side script failures.
Evidence & numbers
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.
- Audit purchase event firing on order confirmation pageConfirm it fires exactly once per order and matches Shopify order IDs.
- Configure and verify consent mode settingsconsentRatePct is null, meaning consent tracking isn't set up and may be dropping events.
- Reconcile GA4 vs Shopify orders daily for two weeksBuild an order-ID match report to confirm the fix before trusting funnel data.
Evidence & numbers
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.
- Audit GA4 tags with GTM preview modeCheck for duplicate or missing add_to_cart/purchase triggers causing the 108% and revenue gap.
- Reconcile GA4 vs Shopify orders by IDMatch individual orders to isolate exactly which events are lost or duplicated.
- Implement server-side or Enhanced Conversions taggingReduces client-side event loss from ad blockers and browser privacy limits.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Reconcile GA4 purchase events against Shopify order IDsFind exactly which orders aren't firing or are double-counted in GA4
- Check consent-mode and purchase-event deduplication settingsConsent gaps or duplicate client/server events are the most common cause of this gap size
- Implement server-side purchase tracking via Shopify webhookRemoves reliance on client-side JS that can fail or be blocked
Evidence & numbers
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.
- Verify GA4 purchase event fires on order confirmationEvent may not trigger due to redirect timing or tag misconfiguration
- Check consent mode banner default stateNull consent rate suggests consent mode isn't configured, blocking GA4 data
- Reconcile 30-day order list between GA4 and ShopifyPinpoint exact missing or duplicate transactions causing the gap
Evidence & numbers
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.
- Audit GA4 purchase event firingConfirm purchase event fires once per order and isn't blocked by consent mode or client-side errors
- Cross-check order IDs GA4 vs ShopifyPull a day-level order ID match to isolate where events are lost or duplicated
- Add server-side or GA4 e-commerce via Shopify appReduce reliance on client-side tags prone to ad-blockers and script failures
Evidence & numbers
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.
- Audit GA4 purchase event count vs Shopify ordersConfirm every completed order fires exactly one GA4 purchase event.
- Check consent mode suppressing GA4 tagsBlocked consent can hide purchases from GA4 while Shopify still records the sale.
- Review GTM triggers for duplicate/conditional firingMisconfigured triggers can double count or drop purchase events.
Evidence & numbers
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.
- Audit GA4 purchase event firing41% revenue gap suggests duplicate or missing purchase events in GA4
- Verify consent mode and pixel placementNull consent rate suggests GA4 isn't capturing accepted-consent sessions
- Reconcile GA4 vs Shopify revenue weeklyCatch future divergence before trusting any funnel number
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GA4 purchase event firing on order confirmationConfirm it fires once per order and matches Shopify order IDs.
- Compare GA4 vs Shopify order counts directlyIsolates whether the gap is missing events or wrong values.
- Move to server-side or native Shopify GA4 integrationCuts client-side tracking loss from ad blockers and consent gaps.
Evidence & numbers
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.
- Audit GA4 purchase events against Shopify order IDsPinpoint exactly which orders GA4 is missing or double-counting.
- Verify consent-mode defaults aren't blocking the purchase tagA default-denied consent state silently drops GA4 purchase events.
- Add Shopify webhook-based conversion trackingServer-side order data isn't affected by browser/ad-blocker issues.
Evidence & numbers
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.
- Audit GA4 purchase event firingConfirm the ecommerce purchase event fires on the order confirmation page across devices.
- Check consent banner impact on taggingVerify the consent banner isn't blocking GA4 tags before purchase completes.
- Reconcile GA4 with Shopify via server-side trackingAdd Shopify's GA4 app or a server-side Conversions API to close the gap.
Evidence & numbers
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.
- Audit GA4 purchase event firing in GTMConfirm it fires once per order and matches Shopify order IDs.
- Implement Google consent mode v2Null consent rate suggests consent signals aren't reaching GA4, undercounting revenue.
- Set up a weekly GA4 vs Shopify reconciliation checkCatch divergence early before decisions are made on bad data.
Evidence & numbers
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.
- Audit GA4 purchase event firing on order confirmationCompare dataLayer triggers vs Shopify order data to find dropped or duplicated events.
- Verify consent banner isn't blocking GA4 tagsNull consent rate suggests consent mode may be stripping hits before they're recorded.
- Add server-side GA4 tagging via Shopify webhooksRemoves reliance on client-side JS that can fail, be blocked, or double-fire.
Evidence & numbers
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.
- Audit GA4 purchase event firingConfirm the purchase event fires reliably on every order confirmation page.
- Implement consent mode defaultsMissing consent signals may be silently dropping hits on both devices.
- Cross-check Shopify order count vs GA4 purchase eventsValidate server-side counts match Shopify's 84 orders to locate the gap.
Evidence & numbers
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.
- Audit GA4 purchase event against Shopify order IDsFind exactly which orders are missing or duplicated in GA4.
- Check consent banner impact on GA4 tag firingconsentRatePct is null, suggesting the tag may be blocked for many visitors.
- Fire purchase event server-side from Thank You pageReduces client-side event loss that likely causes the 46% gap.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit the GA4 purchase event payloadConfirm value, currency and transaction_id match Shopify order totals for every order.
- Check for duplicate or blocked GA4 triggersVerify the purchase event fires exactly once and isn't blocked by consent mode.
- Reconcile Shopify order webhook against GA4 hitsSpot-check 10 recent orders line-by-line between the two systems.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GA4 purchase event firing vs Shopify ordersMatch order IDs/timestamps to find exactly which purchases GA4 misses
- Implement Consent Mode v2 with default stateNull consent rate suggests the banner isn't reporting to GA4, silently dropping revenue
- Move to server-side GTM taggingCuts ad-blocker and consent-related event loss that likely causes the 34% gap
Evidence & numbers
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.
- Audit GA4 purchase event firingConfirm the purchase event fires on every completed order to match Shopify's order count.
- Compare GA4 vs Shopify order counts dailyPinpoint exact days/orders where GA4 misses events to isolate the cause.
- Validate consent mode configurationCheck whether the consent banner blocks GA4 tags for a subset of sessions.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Compare GA4 DebugView purchase events against Shopify order IDsPinpoints whether events are missing, duplicated, or delayed.
- Audit consent banner and consent-mode configurationconsentRatePct is null, suggesting consent signals aren't being captured or passed to GA4.
- Implement server-side purchase tracking via GA4/Shopify appRemoves reliance on client-side JS that can be blocked or fail silently.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GA4 purchase event firing on order confirmationConfirm the event fires once per order and isn't blocked by consent defaults
- Compare GA4 vs Shopify order counts day-by-dayPinpoint exact dates or pages where GA4 events drop to isolate the tag issue
- Implement server-side GA4 tracking via ShopifyRemoves reliance on a client-side tag that can be blocked or delayed
Evidence & numbers
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.
- Audit GA4 purchase and begin_checkout tagsConfirm each fires exactly once and isn't blocked by consent mode.
- Reconcile GA4 with Shopify orders dailySet up a recurring report to catch revenue drift early.
- Walk a live test order in GA4 DebugViewPinpoint exactly where GA4 events diverge from the real checkout.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GA4 purchase event firing in DebugViewCheck for duplicate or missing purchase events against real orders
- Verify consent mode and tag firing rulesConsent gating can silently drop a chunk of purchase events
- Cross-check GA4 order IDs vs Shopify order IDsIdentify exactly which orders are missing or duplicated in GA4
Evidence & numbers
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.
- Audit GTM tags for duplicate purchase/ATC eventsDuplicate fires would explain desktop retention exceeding 100% and revenue mismatch.
- Verify GA4 consent mode is configured correctlyBlocked consent signals can undercount GA4 revenue versus Shopify.
- Reconcile GA4 DebugView events against Shopify ordersConfirms exactly where events are lost or duplicated.
Evidence & numbers
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.
- Audit GA4 e-commerce tags for duplicate firingUse GTM preview mode to check add_to_cart/begin_checkout firing twice per action.
- Reconcile GA4 purchase event against Shopify order webhookConfirm purchase fires exactly once per completed order.
- Check consent-mode gating on purchase pixelVerify the purchase tag isn't blocked before conversion completes.
Evidence & numbers
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.
- Move Add to Cart button above the fold on mobile PDPWith 3,071 mobile sessions and only 3% adding to cart, the CTA likely needs no scrolling to reach.
- Add trust badges and clear price near the CTAReduce hesitation at the decision point to lift add-to-cart rate.
- Run a mobile PDP page-speed auditSlow load times commonly suppress mobile add-to-cart; rule this out before further redesign.
Evidence & numbers
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.
- Add a sticky add-to-cart bar on mobile PDPsKeeps the CTA visible while scrolling, cutting drop-off before add-to-cart.
- Audit mobile PDP load and interactivity speedSlow time-to-interactive can silently kill add-to-cart taps.
- Move price and CTA above the fold on mobile PDPReduces scroll friction between viewing and adding to cart.
Evidence & numbers
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.
- Audit GA4 purchase event firingConfirm the event fires once per order and matches Shopify order IDs.
- Check consent banner and ad-blocker impactVerify consent mode isn't suppressing GA4 tags before purchase fires.
- Implement Shopify server-side GA4 taggingCapture events lost to client-side blocking and reconcile with Shopify.
Evidence & numbers
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.
- Audit GA4 purchase event on the thank-you pageConfirm it fires exactly once per order and matches Shopify order IDs.
- Compare daily GA4 vs Shopify order counts for a weekReveals whether the gap is a flat % or spikes by day/device.
- Check consent mode setup on checkout pagesNull consentRatePct suggests consent signals may not be firing at all.
Evidence & numbers
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.
- Audit GA4 purchase event on order confirmationConfirm it fires once per order with correct transaction_id and value.
- Check consent mode banner is feeding GA4 correctlyNull consent rate suggests consent signals aren't reaching GA4.
- Implement server-side tracking (GTM server/Conversions API)Reduces client-side loss from ad blockers and consent gaps.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Add a sticky mobile Add-to-Cart bar with priceKeeps the buy button reachable since most shoppers scroll only 23% of the page.
- Fix unresponsive PDP buttons causing dead clicks270 mobile dead clicks indicate elements shoppers tap aren't responding.
- Move key value props and CTA above the foldLow scroll depth means content below the fold is rarely seen.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GA4 purchase event firingConfirm the purchase event fires exactly once per Shopify order on the thank-you page.
- Check consent mode tag suppressionconsentRatePct is null — verify Consent Mode isn't blocking conversion tags for most visitors.
- Reconcile GA4 vs Shopify order IDsMatch order IDs day-by-day over 30 days to isolate exactly which events are missed.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GA4 purchase event firing in GTM previewConfirm the ecommerce purchase tag fires on every completed order, not just some.
- Reconcile GA4 order IDs against Shopify's order listIdentify exactly which orders are missing from GA4 to isolate the broken trigger.
- Implement Shopify-native or server-side GA4 integrationReduces event loss from ad blockers, consent gating, or client-side script failures.
Evidence & numbers
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.
- Audit GA4 purchase event firing on order confirmation pageConfirm the purchase tag fires reliably against Shopify's 74 real orders.
- Deploy server-side tracking via GA4 Measurement ProtocolCaptures orders missed by blocked client-side pixels, closing the revenue gap.
- Instrument consent-rate reportingconsentRatePct is null; measure it to see if consent banners suppress tags.
Evidence & numbers
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.
- Audit GA4 purchase event for duplication or drop-offCompare event firing on order-confirmation page against Shopify order count
- Verify Shopify-to-GA4 integration/consent mode setupNull consent rate suggests consent signals may be blocking tracking
- Reconcile revenue weekly until variance is under 5%Prevents decisions being made on unreliable funnel data
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GA4 purchase event firing on confirmation pageConfirm the event fires for 100% of completed Shopify orders via debug mode.
- Check consent banner blocking Analytics pre-purchaseIf consent defaults to denied, purchases from those sessions never reach GA4.
- Install Shopify's server-side Conversions API appServer-side pass-through avoids client-side blocking losses.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GA4 purchase event firing on every completed order.Confirms whether the tag fires on all completions or only some, explaining the gap.
- Add consent-mode logging to measure opt-out rate.Null consent rate hides how much traffic GA4 never measures at all.
- Implement Shopify-native or server-side purchase event.Removes reliance on client-side tags broken by ad-blockers or consent denial.
Evidence & numbers
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.
- Cross-check consent-mode configurationVerify the consent banner isn't blocking conversion pings before GA4 loads.
- Audit GA4 purchase event firingUse GTM preview to confirm purchase fires exactly once per Shopify order.
- Add a server-side purchase backup eventSend Shopify webhook order data to GA4 via Measurement Protocol as a fallback.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GA4 purchase event firing on order confirmation pageConfirm the event fires for every completed order, not just some sessions
- Check consent-mode settings for analytics blockingConsent banners can suppress purchase events before GA4 ever receives them
- Add server-side purchase tracking via Shopify webhook to GA4Removes reliance on client-side JS that may fail after payment
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GA4 purchase event firing per orderMatch GA4 purchase hits to Shopify order IDs to find missing or duplicate fires.
- Check consent-mode impact on purchase trackingconsentRatePct is null; confirm the cookie banner isn't blocking the purchase pixel.
- Reconcile GA4 vs Shopify revenue daily for 7 daysConfirms the fix closes the 31% gap before trusting funnel %s.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GA4 purchase event against Shopify order webhookConfirms whether GA4 is under-firing or double-counting purchases.
- Reinstall Clarity snippet with session ID captureSession count of 0 despite click activity means Clarity isn't tagging sessions correctly.
- Add Shopify order count as a cross-check dashboardGives a trustworthy fallback while GA4 is being fixed.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GA4 purchase event firingCompare GA4 order count to the 21 Shopify orders to quantify the gap.
- Verify consent mode configurationNull consent rate suggests Consent Mode may be blocking or modeling events.
- Implement server-side/Conversions API trackingReduces reliance on client-side JS and closes the revenue gap.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GA4 purchase event firingCompare Shopify order IDs against GA4 purchase hits to find where events drop.
- Verify GTM purchase trigger fires once per orderDuplicate or missing triggers on the order-confirmation page cause revenue mismatch.
- Check consent-mode/ad-blocker impact on trackingNull consentRatePct suggests consent mode may be blocking hits.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GTM tags for duplicate event firingCheck begin_checkout/purchase triggers for double counts causing the 105% retention.
- Reconcile GA4 vs Shopify order IDs dailyPinpoint exactly where events are lost or duplicated.
- Implement server-side conversion taggingRecover client-side loss from ad blockers/consent gaps driving the revenue gap.
Evidence & numbers
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.
- Audit GA4 purchase event firing on every checkout completion pathConfirm the purchase event fires once per order, including express/wallet checkouts.
- Reconcile GA4 vs Shopify order counts daily for one weekPinpoint which order types (discounted, subscription, express) are missing from GA4.
- Add server-side or native Shopify GA4 taggingReduces client-side ad-blocker and consent losses causing undercounting.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GA4 purchase and add_to_cart tags in GTMCheck for duplicate or missing triggers causing the 52% revenue gap.
- Step through checkout in GA4 DebugViewConfirms whether add_to_cart or purchase events fire twice on desktop.
- Reconcile GA4 vs Shopify revenue daily for a weekConfirms the fix before trusting funnel numbers again.
Evidence & numbers
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.
- Audit GA4 purchase event firingCompare GA4 purchase count to Shopify order count to isolate missing events.
- Implement Shopify's native GA4/Conversions API integrationServer-side tracking recovers events lost to ad-blockers or consent gaps.
- Add GTM preview QA checklist for checkout eventsPrevents future silent tag failures on purchase/begin_checkout events.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Add a sticky Add to Cart bar on mobile PDPsKeeps the primary action visible without scrolling, directly targeting the 3% conversion gap.
- Move price and CTA above the fold on mobileReduces scroll needed before a shopper can act.
- Audit mobile PDP load speed for image/script delaysSlow renders can suppress taps on the add-to-cart button.
Evidence & numbers
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.
- Audit GA4 Purchase event firing per orderConfirm it fires exactly once and isn't blocked by ad blockers or consent tools.
- Add server-side purchase tracking via Shopify webhookPushes order data to GA4 Measurement Protocol as a backstop to client-side loss.
- Review consent banner impact on tracked sessionsconsentRatePct is null — confirm consent mode isn't silently dropping events.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GA4 purchase event firingCompare GTM tag conditions against Shopify's checkout-completion webhook to find dropped events.
- Deduplicate the purchase eventEnsure GA4 doesn't double-fire or miss the event on redirect-based checkout completion.
- Reconcile revenue daily for two weeksCross-check GA4 vs Shopify revenue until divergence stays under 5%.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GA4 purchase tag firing on order confirmationCheck for consent-mode blocking since consentRatePct is null
- Reconcile order IDs between Shopify and GA4Identify which specific orders GA4 is missing to isolate the failure point
- Add Shopify's server-side Conversions API feedReduces reliance on client-side tags that consent tools or ad-blockers can drop
Evidence & numbers
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.
- Audit GA4 purchase & begin_checkout tags in GTMConfirm each fires once per order and matches Shopify order IDs to close the $634 gap.
- Add server-side GA4 tagging via Shopify webhooksRemoves ad-blocker/consent loss that likely causes client-side GA4 undercounting.
- Re-baseline all funnel bands after fixCurrent mobile/desktop retention numbers are provisional until tracking is trustworthy.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GA4 purchase event firing on the order confirmation pageConfirms whether the tag loads after redirect or is blocked by ad blockers/consent tools.
- Compare GA4 DebugView events against Shopify order webhooksPinpoints exactly where events are dropped or duplicated.
- Reinstall GA4 via Shopify's native integration or server-side taggingRemoves reliance on a client-side tag that may be blocked.
Evidence & numbers
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.
- Audit GA4 purchase event firing against Shopify ordersCompare order IDs event-by-event to find missing or duplicate GA4 purchase events.
- Implement server-side or Shopify-native purchase trackingUse Shopify's Web Pixel or Conversions API so purchase data doesn't rely on client-side JS.
- Add consent-mode fallback for ad-blocker lossEnsure GA4 tags fire regardless of consent-banner default state.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GTM tags for duplicate begin_checkout/purchase firing113% desktop retention means an event is firing more than once per session.
- Cross-check GA4 consent mode against Shopify checkout eventsConsent gaps commonly explain a ~37% revenue undercount in GA4.
- Reconcile GA4 purchase event value with Shopify order totalsConfirms whether the gap is event volume or event value mapping.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GA4 purchase & begin_checkout tagsCompare GTM trigger firing vs Shopify webhook to find duplicate/missing events causing the 36% gap.
- Deduplicate checkout event on drawer buttonSlide-out cart drawer's checkout button may fire begin_checkout twice, inflating desktop step to 105%.
- Add server-side purchase event via Shopify webhookServer-side tracking bypasses ad-blockers/consent gaps that likely cause GA4 undercount.
Evidence & numbers
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.
- Surface price and shipping cost above the foldRemoves late cost surprises that commonly stall mobile Add to Cart.
- Simplify variant/subscription selector on PDPConfusing options block a quick one-tap add to cart on mobile.
- Add a sticky mobile Add-to-Cart barKeeps the CTA visible while scrolling, cutting drop-off before ATC.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GA4 purchase event on order confirmation pageConfirm it fires once per order with correct transaction_id and value.
- Check consent banner and consent mode configurationNull consent rate suggests tracking may be blocked for some visitors.
- Reconcile GA4 vs Shopify order counts daily for 2 weeksConfirms the fix and establishes a trustworthy baseline for future calls.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit GA4 add_to_cart and purchase tag firingDuplicate triggers likely explain the impossible 104% desktop rate
- Reconcile GA4 order IDs against Shopify ordersIdentify exactly which events are missing or duplicated
- Implement Shopify's native/server-side GA4 taggingRemoves reliance on client-side tags prone to blocking or dupes
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Verify Clarity tag fires on PDP, drawer, and checkoutConfirms the script is installed site-wide, not just on some templates.
- Check consent banner isn't blocking the Clarity scriptConsent gating can silently suppress all session recordings.
Evidence & numbers
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.
- Verify the Clarity snippet is installed site-wideConfirms the tag fires on every template, not just some pages.
- Check the consent banner isn't blocking ClarityConsent tools can silently suppress the recording script from firing.
- Test Clarity capture in an incognito sessionConfirms recordings populate within minutes of a live visit.
Evidence & numbers
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.
- Verify Clarity script is installed site-wideConfirm the tracking snippet loads on both mobile and desktop templates.
- Check consent banner isn't blocking ClarityCookie consent settings may prevent session recording from firing.
- Re-run Clarity for 7 days and review recordingsGathers real session replays to confirm PDP and checkout hypotheses.
Evidence & numbers
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.
- Confirm Clarity snippet loads on live siteCheck page source/network tab for the Clarity script firing.
- Check CSP/consent settings for blocksA content-security-policy or consent gate may silently block Clarity.
- Reinstall Clarity via Shopify app embedEnsures the snippet persists across theme updates.
Evidence & numbers
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.
- Compare GA4 DebugView to 10 live test ordersConfirms whether purchase events fire once per order or not at all
- Audit consent-mode default state on checkout pagesConsent gating before user action can silently block GA4 purchase tags
- Reconcile GA4 vs Shopify order IDs for the last 30 daysPinpoints exactly which orders are missing or duplicated in GA4
Evidence & numbers
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
- Move Add-to-Cart button above the fold on mobile PDP252 dead clicks suggest shoppers can't find or tap the current CTA
- Review Clarity recordings on the mobile PDPPinpoint exactly which non-functional elements are absorbing taps
- Shorten mobile PDP above the CTAOnly 24% avg scroll means most shoppers never reach key content
Evidence & numbers
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.
- Audit GA4 purchase event firing on order confirmationConfirms whether the purchase event tag actually fires after checkout.
- Check consent-mode settings blocking GA4 tagsCookie banner defaults can silently suppress purchase tracking.
- Reconcile GA4 against Shopify via server-side trackingA server-side or CAPI setup removes browser-blocking as a variable.
Evidence & numbers
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.
- Add a sticky Add to Cart bar on mobile PDPKeeps the CTA visible without requiring scroll past 23% of the page.
- Audit PDP elements causing dead clicks263 dead clicks suggest buttons or images aren't triggering expected actions.
- Move price and CTA higher on the PDPLow scroll depth means most content below the fold is never seen.
Evidence & numbers
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.
- Verify Clarity script fires on every page templateConfirms tag isn't blocked or missing on key templates like PDP or checkout.
- Check Clarity project sampling and device filtersA misconfigured filter could be excluding all sessions from device reporting.
- Re-pull rage/dead click rates once session counts are fixedEnsures future UX decisions are based on a real session denominator.
Evidence & numbers
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.
- Move the Add to Cart button above the fold on mobile PDPAvg scroll is only 23%, so most shoppers never reach a below-fold button.
- Review Clarity recordings for the 260 mobile dead clicksDead clicks often mean a tappable-looking element isn't functioning.
- Add a sticky mobile Add to Cart barKeeps the action reachable regardless of scroll depth.
Evidence & numbers
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.
- Move add-to-cart button above the fold on mobile PDPAvg scroll of only 23% means a lower CTA is rarely seen.
- Fix unresponsive elements causing 251 mobile dead clicksReview Clarity recordings to locate the broken tap target.
- Add a sticky add-to-cart bar on mobile PDPKeeps the CTA visible regardless of scroll position.
Evidence & numbers
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.
- Check add-to-cart button tap targets and JS bindings294 dead clicks indicate taps aren't registering on mobile PDP.
- Add sticky add-to-cart bar on mobile PDPAverage scroll is only 22%, so CTA visibility is likely the gap.
- Simplify variant/quantity selection stepsFewer taps needed before the add-to-cart action can fire.
Evidence & numbers
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.
- Move Add to Cart button above the fold on mobile PDP22% avg scroll means most shoppers never reach a lower-placed button.
- Add a sticky mobile Add-to-Cart barKeeps the CTA visible through scroll, reducing dead-click confusion.
- Review PDP dead-click hotspots in session recordings293 dead clicks indicate taps on elements shoppers expect to be interactive.
Evidence & numbers
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.
- Move Add to Cart button and key benefits above the foldMobile scroll depth is only 22%, so most page content below it goes unseen.
- Fix dead-click elements near the product gallery/CTA285 mobile dead clicks suggest shoppers tap elements that don't respond.
- Add a sticky mobile Add to Cart barKeeps the CTA visible while scrolling, reducing exits before adding to cart.
Evidence & numbers
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.
- Move checkout button above the fold in drawerEnsure the primary CTA is visible without scrolling on mobile.
- Add express checkout buttons inside the drawerShop Pay/PayPal buttons reduce steps from cart to purchase.
- Add shipping/returns reassurance copy near CTAShort trust text next to the checkout button addresses hesitation.
Evidence & numbers
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.
- Add a sticky high-contrast checkout button inside the drawerMakes the next step obvious without scrolling the drawer on mobile
- Add trust badges and returns info inside the drawerReassures shoppers before they decide to proceed
- Review Clarity recordings for dead-click hotspots in the drawer363 mobile dead clicks likely mark an unresponsive tap target
Evidence & numbers
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.
- Audit GA4 purchase events against Shopify order IDsCompare order counts to find duplicate or missing purchase fires.
- Verify tracking on Shop Pay/PayPal redirect flowsExternal payment redirects often drop GA4 client IDs, undercounting purchases.
- Add Shopify-native or server-side GA4 pixelServer-side tagging avoids ad-blocker and redirect losses causing the 33% gap.
Evidence & numbers
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).
- Add shipping threshold and returns line inside drawerBuilds confidence to proceed without leaving the drawer
- Make checkout button sticky and full-width in drawerEnsures the CTA is visible without scrolling on mobile
- Fix dead-click elements inside the drawer225 mobile dead clicks suggest tappable-looking elements aren't responding
Evidence & numbers
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.
- Audit GA4 purchase event firing logicConfirm the purchase event fires exactly once per completed Shopify order.
- Check consent-mode tag gating on checkoutVerify cookie consent isn't blocking GA4 tags before purchase completes.
- Reconcile transaction IDs GA4 vs ShopifyMatch order IDs across both systems to find missing or duplicate hits.
Evidence & numbers
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.
- Move Add to Cart button above the foldAvg scroll is only 21%, so most never reach the current button
- Review Clarity recordings for the 131 mobile dead clicksIdentify unresponsive elements blocking add-to-cart
- Simplify mobile product page layoutShorten path to the add-to-cart action
Evidence & numbers
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.
- Add sticky Add to Cart bar on mobile PDPKeeps CTA visible since most users never scroll past 22%.
- Move price and CTA above the foldSurface the buy button before long-form benefit copy.
- Fix unresponsive PDP tap targets39 mobile dead clicks suggest an element isn't functioning correctly.
Evidence & numbers
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.
- Verify Clarity snippet is installed sitewideConfirm the tracking script is present in theme.liquid on all templates.
- Check consent banner isn't blocking ClarityConfirm the analytics consent category fires before Clarity loads.
- Re-test after 48 hours for session captureConfirm sessions and rage-click counts populate before trusting data.
Evidence & numbers
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.
- Pin Add to Cart button above the foldKeeps the primary CTA visible without scrolling on mobile PDP.
- Reduce variant selector to one tapFewer taps before add-to-cart lowers PDP friction.
- Add stock/review count near CTASocial proof beside the button can nudge hesitant mobile shoppers.
Evidence & numbers
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.
- Verify the Clarity snippet is present on all live templatesConfirms whether the tracking code was ever deployed correctly.
- Check consent/cookie banner isn't blocking the Clarity scriptConsent gating is a common cause of zero-session reporting.
- Re-check Clarity dashboard 24h after the fixConfirms sessions are now populating before relying on it again.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Fix or enlarge the mobile Add to Cart tap target269 monthly dead clicks suggest shoppers tap it without effect.
- Move Add to Cart button above the fold on mobile PDPAverage mobile scroll depth is only 23%, many never reach it lower down.
- Manually test variant/size selectors on real mobile devicesConfirm selectors aren't silently failing and blocking the add-to-cart action.
Evidence & numbers
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.
- Add a sticky mobile Add to Cart bar81% reach the PDP but only 3% add to cart — keep the CTA visible without scrolling.
- Review Clarity recordings on top dead-click elements262 dead clicks imply shoppers are tapping non-functional elements near the buy box.
- Move key value content above the fold23% average scroll means most page content is never seen.
Evidence & numbers
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.
- Make the Add-to-Cart button sticky on mobile PDP23% avg scroll means most shoppers never reach a static ATC button.
- Fix unresponsive tap targets on the product page268 dead clicks indicate elements that look tappable but don't respond.
- Move price, variant picker and ATC above the foldMatches the low scroll behavior so key actions are seen immediately.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Move Add to Cart button above the fold on mobile PDP22% avg scroll means most shoppers never reach a lower CTA.
- Add a sticky mobile Add-to-Cart barKeeps the CTA accessible regardless of scroll position, lifting ATC rate directly.
- Fix mobile PDP elements generating 291 dead clicksIdentify non-clickable images or badges shoppers mistake for buttons and link or remove them.
Evidence & numbers
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.
- Add prominent Checkout button atop cart drawerReduce taps needed to reach checkout from the slide-out cart.
- Show shipping/trust info inside drawerReassure shoppers on cost and security before they leave the drawer.
- Enable Shop Pay/PayPal express buttons in drawerLet mobile shoppers skip the full checkout flow.
Evidence & numbers
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.
- Pin a prominent Checkout button in the cart drawerEnsures the CTA is visible without scrolling on mobile.
- Add trust badges and shipping/returns info inside the drawerReduces last-second hesitation before checkout.
- Add Shop Pay/Apple Pay buttons inside the drawerLets shoppers skip to one-tap checkout.
Evidence & numbers
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.
- Make checkout button sticky and high-contrast in cart drawerDrawer sits above a /cart page — CTA visibility directly drives this step
- Add express wallets (Shop Pay, Apple Pay) inside drawerRemoves steps for mobile shoppers most prone to drop-off
- Show shipping threshold and trust badges in drawerBuilds confidence before the checkout tap, closing the 27% vs 40–60% gap
Evidence & numbers
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.
- Add a sticky, high-contrast checkout button in the drawerImproves tap visibility for the drawer's primary action on small screens.
- Add one-tap express checkout button inside the drawerShop Pay/Apple Pay in-drawer removes an extra step for mobile users.
- Surface free-shipping threshold text in the drawerReduces mid-drawer drop-off from shipping-cost uncertainty.
Evidence & numbers
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.
- Make the drawer's checkout button sticky and full-widthEnsures the single next step is always visible on small screens
- Add a one-line shipping/returns reassurance in the drawerReduces hesitation right before the checkout tap
- Fix unresponsive drawer icons/buttons331 mobile dead clicks indicate elements that look clickable but aren't
Evidence & numbers
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.
- Make checkout button sticky and dominantEnsure the CTA sits above the fold with no competing links.
- Add express-pay buttons inside the drawerShop Pay, Apple Pay, PayPal buttons cut steps to checkout.
- Show shipping cost and returns noteSurface shipping/returns info in-drawer to reduce checkout hesitation.
Evidence & numbers
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.
- Make the checkout button sticky and above the fold in the drawerEnsures the primary action is visible without scrolling on mobile.
- Add a shipping/returns trust line beside the checkout buttonReduces last-second hesitation before leaving the drawer.
- Add express checkout wallet buttons inside the drawerLets shoppers skip to payment without opening the checkout page.
Evidence & numbers
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.
- Move Add to Cart button above the fold on mobile PDP188 mobile dead clicks suggest shoppers tap non-functional areas expecting action.
- Simplify mobile PDP copy and pricing displayClarify the value proposition to reduce hesitation before adding to cart.
- Increase Add to Cart button size/contrast on mobileImproves tap target given the 4% ATC rate on high mobile traffic.
Evidence & numbers
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.
- Compare GA4 purchase event IDs against Shopify order IDsReveals whether events are missing, duplicated, or mistimed.
- Check consent mode and ad-blocker impact on purchase trackingConsent gaps commonly explain a 20-30% undercount.
- Add server-side purchase event as backup sourceReduces reliance on client-side JS that can fail silently.
Evidence & numbers
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.
- Add sticky 'Add to Cart' bar on mobile PDPKeep CTA visible without scrolling to capture low-scroll visitors.
- Move key benefits/price above the foldOnly 21% avg scroll means most content goes unseen.
- Fix dead-click elements on mobile PDP169 dead clicks suggest tappable-looking elements aren't functioning.
Evidence & numbers
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.
- Make the add-to-cart button sticky and full-width on mobile PDPRemoves scrolling/tapping friction implied by 165 dead clicks.
- Increase tap-target size and spacing around variant selectorsDead clicks often mean shoppers are missing or mis-tapping controls.
- Move key benefit bullets and price above the foldMobile average scroll is only 21%, so most content below the fold goes unseen.
Evidence & numbers
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%.
- Move Add to Cart button above the fold21% avg scroll means most shoppers never reach a lower CTA.
- Increase mobile Add to Cart button size and contrast139 dead clicks suggest shoppers are tapping unresponsive elements nearby.
- Add a sticky Add to Cart bar on mobile PDPKeeps the CTA visible regardless of scroll depth.
Evidence & numbers
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.
- Make the add-to-cart button sticky and full-width on mobile128 dead clicks suggest shoppers can't find or trigger it easily
- Simplify the variant/size selector on product pagesReduces friction near where dead clicks likely cluster
- Add price and trust copy directly above the ATC buttonReduces hesitation right before the action shoppers are missing
Evidence & numbers
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.
- Make Add to Cart button sticky on mobile PDPPuts the CTA above the fold regardless of scroll depth, directly targeting the leak.
- Review Clarity recordings at dead-click hotspots on PDP120 mobile dead clicks likely mark the exact broken element.
- Shorten mobile PDP above the fold to surface price and CTA sooner22% avg scroll means most shoppers never see content below the top.
Evidence & numbers
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.
- Move price and Add to Cart button above the fold23% scroll depth means most shoppers never reach the current CTA.
- Add a sticky mobile add-to-cart barKeeps the CTA reachable as shoppers scroll product details.
- Compress and lazy-load mobile product imagesFaster load reduces early drop-off from a sluggish page.
Evidence & numbers
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.
- Verify Clarity snippet loads on the live siteZero sessions suggests the script may be missing or blocked.
- Check Clarity project filters and sampling rulesA misconfigured filter can silently exclude all sessions.
- Re-verify Clarity data after 48h once fixedConfirms behavioral data flows before trusting future UX diagnoses.
Evidence & numbers
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.
- Verify Clarity snippet fires on the live themeConfirm the tracking script loads in browser console and reports to the Clarity dashboard.
- Check consent banner isn't blocking ClaritySome CMPs block third-party recorders until consent is explicitly given.
- Recheck session counts after 48 hoursConfirm sessions populate before trusting any future behavioral findings.
Evidence & numbers
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.
- Watch Clarity replays of top dead-click sessionsPinpoint the exact page and element causing the non-interactive click attempts
- Make flagged elements clickable or strip their button-like stylingRemoves the false affordance currently frustrating shoppers
- Move key trust content above the ~24-38% scroll lineEnsures reviews/benefits are seen before visitors disengage
Evidence & numbers
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.
- Make the Add to Cart button sticky on mobile PDPKeeps the CTA visible despite only 24% average scroll depth.
- Review dead-click hotspots on mobile product pages254 dead clicks suggest shoppers tap non-interactive elements expecting action.
- Shorten above-fold product copy to surface CTA soonerLow scroll depth means the buy button may be missed before shoppers leave.
Evidence & numbers
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.
- Move Add to Cart button and price above the fold on mobileOnly 24% average scroll means most shoppers never reach a lower-placed CTA.
- Review the 262 mobile dead clicks in Clarity recordingsIdentify which non-responsive element shoppers tap before leaving without adding to cart.
- Simplify the variant/size selector on mobile PDPReduces friction if dead clicks cluster on selector controls.
Evidence & numbers
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.
- Make Add to Cart button sticky on mobile PDPAvg scroll is only 24%, so most shoppers never reach a static button
- Fix unresponsive PDP elements causing dead clicks270 mobile dead clicks suggest buttons or swatches that look clickable but aren't
- Move key product value content above the fold76% of mobile visitors never scroll past the first screen
Evidence & numbers
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.
- Add a sticky add-to-cart bar on mobile product pagesKeeps the CTA visible given only 24% average scroll depth.
- Audit the 264 mobile dead-click elements in Clarity recordingsIdentify which product-page elements shoppers tap but get no response from.
- Move price, reviews, and add-to-cart above the foldSurfaces key purchase info without requiring scroll.
Evidence & numbers
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.
- Review mobile Clarity recordings on PDPPinpoint the exact element causing 256 dead clicks before changing anything.
- Simplify the mobile variant selectorReplace dropdowns with tap-friendly swatches to reduce taps to add to cart.
- Make Add to Cart sticky on mobile PDPKeep the ATC button visible while scrolling to cut friction.
Evidence & numbers
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.
- Check Add to Cart button responsiveness on mobile PDPHigh dead-click count suggests taps may not be registering.
- Simplify PDP variant and quantity selectorsRedesign elements users tap without effect to reduce dead clicks.
Evidence & numbers
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.
- Add a prominent sticky checkout button in the drawerMake the checkout CTA the largest, highest-contrast element in the slide-out cart.
- Show shipping and returns info inside the drawerReduce hesitation by stating shipping cost/returns policy directly in the cart drawer.
- Enable express wallet buttons in the drawerLet mobile shoppers pay with Shop Pay/Apple Pay directly from the drawer without a full checkout page.
Evidence & numbers
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.
- Move Add to Cart button above the fold21% average scroll means most visitors never reach a low CTA.
- Shorten hero and benefits copy on PDPReduce scrolling needed to reach the purchase decision.
- Add a sticky Add to Cart bar on mobile PDPKeeps the CTA visible regardless of scroll position.
Evidence & numbers
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.
- Make the checkout button sticky and prominent in drawer327 monthly dead clicks suggest users are missing the CTA.
- Add trust badges and shipping info inside the drawerReassures shoppers before they'd otherwise leave.
- Add express checkout buttons in the drawerCuts steps for mobile shoppers reaching payment.
Evidence & numbers
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.
- Add a sticky, high-contrast checkout button inside the drawerMakes the primary CTA impossible to miss so fewer shoppers exit unconverted.
- Show shipping cost and returns info inside the drawerRemoves the need to click away to find shipping/returns, a common abandonment trigger.
- Add Shop Pay/Apple Pay express buttons to the drawerCuts steps to checkout for the mobile shoppers most prone to abandoning.
Evidence & numbers
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.
- Make the checkout button sticky in the drawerEnsure the CTA sits above the fold without scrolling on mobile.
- Show shipping threshold and returns copy in-drawerReduce hesitation by surfacing trust info inline before checkout.
- Add express wallet buttons inside the drawerLet shoppers skip straight to Apple Pay/Shop Pay from the cart.
Evidence & numbers
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.
- Move the checkout button above the fold in the drawerEnsure the CTA is visible without scrolling inside the cart drawer.
- Enable express wallet buttons in the drawerLet mobile shoppers pay via Shop Pay/Apple Pay directly from the drawer.
- Add shipping and returns reassurance under cart itemsState the free-shipping threshold and return policy in the drawer.
Evidence & numbers
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.
- Add a sticky, prominent checkout button in the drawerMobile users need one-tap access without scrolling the drawer.
- Add express checkout buttons inside the drawerShop Pay/PayPal shortcuts shorten the path to purchase on mobile.
- Show shipping threshold and returns note in the drawerBuilds trust and removes hesitation before checkout starts.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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%).
- Add sticky checkout button to cart drawerMake the checkout CTA always visible above the fold in the drawer.
- Add trust badges and shipping info in drawerShow returns policy and shipping threshold inside the drawer to reduce hesitation.
- Add express checkout buttons in drawerLet mobile shoppers jump straight to Shop Pay/PayPal from the drawer.
Evidence & numbers
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.
- Make the drawer's Checkout button sticky and full-widthReduces steps needed to convert once the cart is open.
- Add shipping/returns trust copy inside the drawerRemoves hesitation from hidden costs or policy uncertainty.
- Add express checkout buttons inside the drawerLets mobile shoppers skip the full checkout form.
Evidence & numbers
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.
- Move Add to Cart button above the fold on mobile21% avg scroll means most shoppers never reach a lower CTA.
- Add key benefit bullets near price on mobile PDPGives shoppers a reason to buy without further scrolling.
- Fix unresponsive elements causing mobile dead clicks189 dead clicks suggest taps landing on non-functional elements.
Evidence & numbers
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.
- Make the checkout button sticky and prominent in drawerA low ATC→checkout rate suggests the CTA is easy to miss on mobile.
- Show shipping cost/threshold in the drawerRemoves surprise costs that stall checkout progression.
- Add express checkout wallets to the drawerLets shoppers skip full checkout form entry directly from the drawer.
Evidence & numbers
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.
- Move price and Add to Cart button above the foldLow 21% scroll depth means most never reach a lower CTA.
- Add reviews/trust badge near the CTABuilds confidence before the shopper decides to add to cart.
- Trim above-fold copy to lift effective scroll reachShorter content surfaces the CTA sooner for mobile scrollers.
Evidence & numbers
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.
- Check GTM trigger conditions for begin_checkout tagConfirm it only fires once per checkout attempt, not on every drawer open.
- Add event de-duplication via session or cart tokenPrevents inflated checkout counts from repeated triggers.
Evidence & numbers
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.
- Move Add to Cart button above the fold on mobile PDPReduces scrolling needed to act; avg mobile scroll is only 21%.
- Review Clarity recordings for PDP dead-click hotspotsIdentify which non-interactive elements shoppers are tapping.
Evidence & numbers
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.
- Move Add to Cart button above the fold on mobile PDP21% scroll depth means most visitors never reach the current CTA
- Add a sticky Add-to-Cart bar on mobileKeeps the CTA visible regardless of scroll position
- Investigate the 171 mobile dead clicks on PDP elementsDead clicks indicate shoppers tapping something non-functional
Evidence & numbers
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.
- Move Add to Cart button above the fold on mobile22% average scroll means most shoppers never reach a lower CTA.
- Review Clarity recordings for the 47 dead-click elementsIdentify which mobile PDP element shoppers tap without effect.
- Compress mobile PDP hero imagesFaster load reduces early exits before the CTA renders.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Pin Add to Cart button above the foldSticky mobile CTA keeps the button visible without scrolling.
- Compress PDP hero images for mobileFaster load reduces bounce before the CTA is seen.
- Simplify mobile PDP above-the-fold copySurface price and primary benefit immediately to prompt add-to-cart.
Evidence & numbers
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.
- Audit GTM triggers for add_to_cart and begin_checkoutConfirms each event fires once and only on the correct action.
- Cross-check Shopify checkout starts against GA4 eventsValidates the true desktop cart-to-checkout rate independent of tags.
Evidence & numbers
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.
- Verify the Clarity snippet is installed on all live templatesConfirms the script is actually present on PDP, cart and checkout pages.
- Check consent or tag-manager rules aren't blocking ClarityConsent gating can silently prevent session recording.
- Confirm the Clarity project ID matches the live storeA mismatched ID sends data to the wrong project, showing as zero sessions here.
Evidence & numbers
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.
- Add a sticky mobile add-to-cart barKeeps the CTA visible while scrolling long product pages, reducing drop-off before ATC.
- Compress mobile product-page hero imagesFaster load reduces bounce before shoppers reach the Add to Cart button.
- Move variant/size selector above the foldRemoves an extra scroll/tap step that stalls mobile add-to-cart intent.
Evidence & numbers
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.
- Add a sticky mobile Add-to-Cart barKeeps the CTA visible while scrolling product details, cutting drop-off before add-to-cart.
- Compress PDP hero images and video for mobileFaster loads reduce bounce before shoppers ever reach the Add to Cart button.
- Verify Clarity recording is active on PDPCaptures real mobile sessions to confirm whether CTA visibility or speed drives the drop.
Evidence & numbers
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.
- Move Add-to-Cart button above the foldPuts the CTA in immediate view so shoppers don't have to scroll to convert.
- Add price, reviews, and stock badge near CTABuilds instant confidence needed to tap add-to-cart on a small screen.
- Simplify variant selector to one tapRemoves extra steps that cause mobile shoppers to abandon before adding.
Evidence & numbers
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.
- Verify the Clarity snippet fires on all pagesUse GTM preview or view-source to confirm the tag is actually present.
- Check consent-mode isn't blocking Clarity from loadingEnsure Clarity isn't gated behind a consent category it shouldn't need.
- Reinstall Clarity via the Shopify appRules out a theme-code conflict causing silent script failure.
Evidence & numbers
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.
- Add sticky 'Add to Cart' bar on mobile PDPKeeps the CTA visible while scrolling to cut mobile-only drop-off.
- Compress hero images to speed mobile PDP loadFaster load reduces exits before the add-to-cart action.
- Show trust badges and reviews above the fold on mobileBuilds confidence needed for a quick add-to-cart decision.
Evidence & numbers
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.
- Pin a prominent Checkout button in the drawerImproves CTA visibility to reduce mobile drop-off after adding to cart.
- Add express checkout buttons inside the drawerShop Pay/Apple Pay let shoppers skip straight to payment from the drawer.
- Show shipping cost and returns policy in drawerRemoves cost/uncertainty as a reason to abandon before checkout.
Evidence & numbers
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.
- Verify the Clarity snippet fires on the live siteZero sessions despite real traffic suggests the tag isn't installed or is blocked
- Confirm the Clarity project ID matches the live themeA mismatched ID would silently send data nowhere useful
- Set up device-level Clarity segments once fixedEnables mobile vs desktop behavioral diagnosis of the funnel leaks above
Evidence & numbers
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.
- Verify Clarity snippet fires on all pagesConfirms the tracking script is actually installed sitewide.
- Check Clarity project sampling and filter settingsEnsures sessions aren't being excluded before capture.
- Re-check session counts after 48 hoursValidates the fix before relying on behavioral data again.
Evidence & numbers
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.
- Add accelerated checkout button to mobile cartShop Pay button lets shoppers skip steps straight to checkout.
- Show shipping estimate inside the cart drawerPrevents late cost surprises that stall mobile checkouts.
- Simplify mobile cart to one prominent checkout CTAReduces on-screen clutter and clarifies the next step.
Evidence & numbers
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.
- Move Add to Cart button above the fold on mobileWith only 25% avg scroll, a lower CTA goes largely unseen.
- Add a sticky add-to-cart bar on mobile PDPKeeps the purchase action visible regardless of scroll depth.
- Review top mobile dead-click elements near PDP CTA232 dead clicks suggest shoppers tap something expecting a response.
Evidence & numbers
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.
- Move Add to Cart above the fold on mobile PDP25% average scroll means most shoppers never reach a buried CTA.
- Add a sticky Add to Cart bar on mobile PDPKeeps the primary action reachable at any scroll position.
- Review Clarity recordings behind the 243 mobile dead clicksIdentify which non-clickable elements shoppers mistake for buttons.
Evidence & numbers
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.
- Verify Clarity session counting is enabled correctlyConfirms whether the 0-session figure is a config bug or an export omission.
- Identify and populate the worst-performing page fieldCurrently blank, preventing page-level prioritization of dead clicks.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Enlarge and reposition the mobile Add to Cart buttonHigh dead-click count near PDP suggests shoppers are missing or mis-tapping the current CTA.
- Add a sticky mobile Add-to-Cart barKeeps the CTA visible as users scroll past a 29% average scroll depth.
- Surface price-per-serving and key benefit near the CTAClarifies value without requiring more scrolling or reading.
Evidence & numbers
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.
- Review mobile PDP click maps in ClarityPinpoint exactly where the 287 dead clicks cluster near the Add to Cart area.
- Enlarge and anchor the Add to Cart buttonMake the CTA sticky so it's reachable without relying on the 23% average scroll.
- Simplify above-fold product infoSurface price, reviews and CTA higher so shoppers decide before they stop scrolling.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Verify Clarity install snippet fires on every pageA session counter stuck at 0 suggests partial or delayed script load.
- Cross-check Clarity session counts against GA4 sessionsConfirms whether the gap is a tagging bug or just a reporting delay.
Evidence & numbers
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.
- Move Add to Cart button and key benefits above the fold21% avg scroll means most mobile shoppers never see current placement
- Audit product page for elements causing dead clicks298 mobile dead clicks suggest shoppers tapping images/text expecting action
Evidence & numbers
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.
- Watch mobile session recordings on PDPLocate where the 324 dead clicks cluster to identify the broken tap target.
- Enlarge and anchor the mobile Add to Cart buttonMake it sticky/visible without scrolling once the root cause is confirmed.
Evidence & numbers
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.
- Make the checkout button sticky in the drawerKeep the CTA above the fold and always visible inside the slide-out drawer.
- Add a shipping/returns trust line to the drawerReduce hesitation by showing delivery time and return policy inside the drawer.
- Add express checkout buttons to the drawerShop Pay/PayPal buttons let shoppers skip the extra step toward checkout.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Watch 10 Clarity recordings on the top product pageIdentify exactly which elements shoppers are dead-clicking on.
- Move the add-to-cart button and trust badges above the foldScroll depth of 21-37% means most shoppers never see content placed lower.
- Make dead-clicked static elements inert or properly linkedReduces frustration behind the 191 rage clicks recorded.
Evidence & numbers
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.
- Move the Add to Cart button above the foldWith only 21% average scroll, the CTA must be visible immediately.
- Audit top dead-click elements on the PDPIdentify non-functional elements causing 314 mobile dead clicks.
- Compress above-fold PDP content on mobileShorten hero/trust content so CTA appears sooner in the scroll.
Evidence & numbers
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.
- Make checkout the drawer's single primary button.A buried or secondary checkout CTA is the top cause of drawer abandonment.
- Add express wallet buttons inside the drawer.Lets shoppers skip an extra step entirely, raising carry-over to checkout.
- Add trust badges and shipping/returns note in drawer.Reduces last-second doubt before shoppers commit to checkout.
Evidence & numbers
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.
- Make checkout button sticky in the mobile drawerKeeps the CTA visible without scrolling on small screens.
- Add delivery estimate and trust badges to drawerReduces last-second hesitation before advancing to checkout.
- Add express checkout buttons inside the drawerApple Pay/Shop Pay let mobile users skip manual steps entirely.
Evidence & numbers
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.
- Move the checkout button above the fold in the drawerMake the sticky CTA visible with no scrolling needed inside the drawer.
- Show free-shipping progress bar in the drawerMotivates completing checkout instead of closing the drawer.
- Add express checkout buttons inside the drawerShop Pay/PayPal buttons shorten the path from cart to purchase.
Evidence & numbers
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.
- Add a sticky, full-width checkout button in the drawerMake the primary CTA impossible to miss on small screens.
- Enable Shop Pay, Apple Pay and PayPal express buttonsLet mobile shoppers skip manual checkout entry entirely.
- Show free-shipping threshold progress in the drawerGive mobile shoppers a reason to proceed instead of abandoning.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Add a prominent checkout button atop the cart drawerMakes the next step obvious instead of leaving shoppers to close the drawer.
- Show shipping cost or free-shipping threshold in drawerHidden shipping costs are a leading cause of cart abandonment before checkout.
- Add trust badges (secure checkout, returns) inside drawerBuilds confidence to move from cart to checkout.
Evidence & numbers
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.
- Pin a full-width Checkout button at drawer topMake the primary CTA visible without scrolling on small screens.
- Add express checkout buttons directly in drawerShop Pay/Apple Pay buttons above the fold shortcut the tap-through to checkout.
- Show free-shipping progress bar in drawerGives shoppers a reason to proceed to checkout instead of closing the drawer.
Evidence & numbers
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.
- Make the checkout button sticky and full-width in the cart drawerRemoves scrolling/searching needed to proceed since there's no separate /cart page.
- Add express checkout wallet buttons inside the drawerLets shoppers skip the full checkout form entirely from the drawer.
- Surface shipping and returns trust copy directly in the drawerAddresses hesitation before the shopper commits to checkout.
Evidence & numbers
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.
- Make the checkout button the drawer's most prominent elementIncrease size/contrast of the checkout CTA inside the drawer.
- Add shipping and returns info inside the drawerAnswer cost/return questions before shoppers leave the drawer.
- Add express-checkout buttons directly in the drawerLet shoppers skip the standard checkout flow entirely.
Evidence & numbers
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.
- Add a prominent sticky checkout button in the drawerMake the primary action unmissable right after adding to cart.
- Show shipping and returns trust copy inside the drawerAnswers cost and policy doubts without forcing a page navigation.
- Add Shop Pay/Apple Pay express buttons in the drawerLets ready buyers skip checkout entirely, recovering impatient shoppers.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Move Add to Cart button above the fold on mobileAvg scroll is only 21%, so most shoppers never reach a lower CTA
- Audit and fix dead-click zones on product page225 mobile dead clicks suggest shoppers tap non-interactive elements expecting action
- Add sticky add-to-cart bar on scrollKeeps CTA visible as shopper scrolls past current 21% depth
Evidence & numbers
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.
- Move Add to Cart button above the fold on mobileAvg scroll is only 21%, so the CTA is probably unseen.
- Add a sticky add-to-cart bar on mobile PDPKeep the CTA visible regardless of scroll position.
- Tighten above-fold value proposition copyClarify the benefit before the shopper decides to scroll away.
Evidence & numbers
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.
- Move Add to Cart button above the fold21% average scroll means most shoppers never reach a lower CTA.
- Add a sticky add-to-cart bar on mobile PDPKeep the CTA accessible regardless of scroll position.
- Surface key benefits and price near the topGive shoppers a reason to buy before they stop scrolling.
Evidence & numbers
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.
- Add a sticky, high-contrast checkout button in the drawerMakes the next step unmissable, cutting pre-checkout drop-off.
- Show shipping threshold and returns policy in the drawerRemoves the uncertainty that stalls shoppers before checkout.
- Add Shop Pay/Apple Pay button inside the drawerOne-tap express checkout skips steps between cart and purchase.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Make the drawer checkout button sticky and full-widthIncreases visibility and reduces mis-taps in the cart drawer.
- Review Clarity recordings for dead-click hotspots in the drawerPinpoints which elements shoppers mistake for functional controls.
- Add an express checkout button inside the drawerLets ready-to-buy shoppers skip an extra step.
Evidence & numbers
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.
- Make checkout button sticky and full-width in the drawerIncreases visibility so shoppers don't need to scroll to proceed.
- Add trust badges and returns info inside the drawerReduces hesitation at the point of proceeding to checkout.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Audit begin_checkout and add_to_cart tag firing rulesDe-duplicate events firing on back-button navigation or re-renders.
- Cross-check GA4 event counts against Shopify checkout startsConfirm true counts before trusting this transition again.
Evidence & numbers
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.
- Move Add to Cart button and price above the fold22% average scroll means most mobile users never reach a below-fold CTA.
- Shorten hero and description content on mobile PDPGets shoppers to the buy box faster, reducing drop-off before Add to Cart.
- Add a sticky Add to Cart bar on mobile PDPKeeps the CTA visible regardless of scroll position.
Evidence & numbers
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.
- Add a sticky mobile Add-to-Cart barKeeps the CTA visible during scroll, removing a low-effort friction point.
- Move price, reviews and shipping above the foldMobile PDP may hide key decision info causing hesitation.
- Audit mobile PDP load speedSlow load disproportionately suppresses add-to-cart on mobile.
Evidence & numbers
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.
- Confirm Clarity script fires on the live themeCheck theme.liquid or tag manager for the snippet and console errors.
- Check Clarity project ID and date filtersEnsure the correct project and 30-day range are selected before re-checking.
Evidence & numbers
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.
- Move Add-to-Cart button above the foldA sticky, prominent mobile ATC button cuts friction to purchase intent.
- Add trust badges near priceGuarantees/reviews next to price reduce buying hesitation.
- Simplify PDP value proposition copyClearer benefit statement helps shoppers decide faster to add to cart.
Evidence & numbers
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.
- Add sticky mobile Add-to-Cart barKeeps the CTA visible while scrolling to reduce drop-off before adding to cart.
- Show reviews and guarantee badge above the foldBuilds trust immediately to counter hesitation on the mobile PDP.
- Simplify PDP layout to one primary CTARemoves competing links that distract from adding to cart.
Evidence & numbers
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.
- Add a sticky Add to Cart bar on mobile PDPKeeps the CTA visible while scrolling instead of only appearing once, above the fold.
- Surface reviews/trust badges above the foldBuilds credibility earlier in the scroll to support the add-to-cart decision.
- Simplify the variant/quantity selectorReduces taps between viewing and adding to cart on small screens.
Evidence & numbers
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.
- Verify the Clarity snippet fires on the live siteUse browser dev tools to confirm the script loads on real pages.
- Reinstall Clarity via Shopify app or theme.liquidRules out app conflicts or caching blocking the snippet.
- Confirm Clarity project ID matches the live domainA wrong ID sends zero data even with real traffic.
Evidence & numbers
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.
- Add a prominent sticky checkout button in the drawerMakes the next step obvious instead of requiring extra scrolling or taps
- Show shipping and returns info inside the drawerBuilds trust before checkout since there is no dedicated cart page
- Add Shop Pay/Apple Pay buttons to the drawerLets mobile shoppers skip a step straight from the drawer
Evidence & numbers
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.
- Verify Clarity snippet fires on all pagesCheck theme/GTM install and browser console for errors.
- Check consent banner isn't blocking ClarityConfirm the Clarity tag isn't gated behind an unconsented category.
Evidence & numbers
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.
- Move Add-to-Cart button above the fold on mobileOnly 24% scroll depth means most shoppers never reach a buried CTA.
- Review session recordings for top dead-click elements on PDP294 dead clicks suggest shoppers expect action from non-functional elements.
Evidence & numbers
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.
- Verify session totals directly in the Clarity dashboardConfirm true session volume behind the dead-click counts.
- Check the Clarity snippet is installed on every templateEnsures recording fires sitewide, not just on some pages.
Evidence & numbers
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.
- Move Add to Cart button above the fold on mobile PDP25% average scroll means most shoppers never reach a lower CTA
- Audit top dead-click elements on mobile product pages230 dead clicks suggest shoppers tapping non-interactive elements
- Trim above-fold PDP content to price, CTA, and one benefitReduces scroll needed to reach the purchase action
Evidence & numbers
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.
- Move Add to Cart button above the fold on mobile PDPLow 25% scroll depth means most shoppers never reach a lower CTA.
- Audit dead-click zones on the mobile product page243 dead clicks suggest shoppers are tapping non-interactive elements expecting action.
- Add a sticky add-to-cart bar on mobile PDPsKeeps the CTA reachable regardless of scroll position.
Evidence & numbers
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.
- Check Clarity project setup for session-count reportingVerify the snippet reports session totals, not just click events.
- Confirm Clarity sampling rate is not set to exclude session countsA misconfigured sample rate can zero out aggregate session metrics.
Evidence & numbers
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.
- Move Add-to-Cart button above the foldOnly 22% average scroll means most shoppers never reach a lower CTA.
- Review 294 mobile dead clicks via session recordingsIdentify which PDP element shoppers tap without effect.
- Simplify PDP layout to surface CTA soonerReduce content competing with the add-to-cart button.
Evidence & numbers
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.
- Add a sticky Add to Cart button on mobile PDPsKeep the CTA visible while scrolling to reduce lost intent from a 4% conversion rate.
- Audit PDP elements causing 288 dead clicksIdentify which images/text shoppers are tapping expecting interactivity.
Evidence & numbers
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.
- Move checkout button to top of the cart drawerEnsures the CTA is visible without scrolling on mobile.
- Add shipping threshold and returns note inside the drawerAnswers common objections before the shopper exits.
- Add express checkout buttons inside the drawerLets shoppers skip straight to payment from the cart.
Evidence & numbers
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.
- Move the checkout button above the fold in the drawerEnsure the CTA is visible without scrolling inside the slide-out cart.
- Show a shipping-threshold progress bar in the drawerReduce surprise costs that cause drawer abandonment.
- Add express checkout buttons inside the drawerLet shoppers jump straight to Apple Pay/Shop Pay from the cart drawer.
Evidence & numbers
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.
- Make the checkout button sticky and visible in the cart drawerThe drawer is the only path to checkout; remove scrolling needed to find it.
- Show shipping cost and returns info inside the drawerRemoves a common pre-checkout hesitation without needing a cart page.
- Add Shop Pay/PayPal express buttons inside the drawerLets shoppers skip straight to checkout in one tap.
Evidence & numbers
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.
- Pin checkout button to top of cart drawerEnsure the CTA is visible without scrolling on small screens
- Add shipping/returns trust line inside drawerReduce last-second hesitation before tapping checkout
- Surface Shop Pay/Apple Pay buttons in the drawerLet mobile users skip to express checkout directly from the drawer
Evidence & numbers
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.
- Move Add to Cart button above the fold on mobile PDP21% average scroll means most shoppers never reach a lower CTA.
- Add concise benefit bullets near the price at the topGives shoppers a reason to buy without needing to scroll.
- Fix unresponsive PDP elements causing dead clicks235 mobile dead clicks suggest buttons or images that don't respond.
Evidence & numbers
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.
- Make the checkout button sticky in the drawerEnsure the CTA is the obvious next step once the drawer opens.
- Add shipping and returns note in the drawerAnswer cost and return questions before shoppers close the drawer.
- Add express-pay buttons inside the drawerLet shoppers skip full checkout form entry.
Evidence & numbers
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.
- Make checkout button full-width and sticky in drawerIncrease visibility of the primary CTA inside the slide-out cart.
- Add shipping threshold/trust badges inside drawerReduce hesitation before checkout without needing a cart page.
- Add express checkout buttons in the drawerLet mobile shoppers skip steps directly from the drawer.
Evidence & numbers
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.
- Check if express/buy-now buttons skip the add_to_cart eventThese paths would inflate checkout starts relative to recorded cart adds.
- Deduplicate begin_checkout firing per session in tag managerPrevents one checkout visit from logging multiple events.
Evidence & numbers
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.
- Pin high-contrast Checkout button in drawerRemoves scrolling/searching for the CTA inside the drawer.
- Show shipping/returns trust line in drawerReduces hesitation from unknown shipping cost before checkout.
- Add express wallet buttons in drawerShop Pay/Apple Pay cut steps and may lift completion.
Evidence & numbers
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.
- Make the checkout button full-width and above the foldRemoves scrolling needed to find the primary action in the drawer.
- Add shipping threshold and returns copy inside the drawerAnswers common objections without leaving the drawer.
- Enable Shop Pay/PayPal express buttons in the drawerLets mobile users skip straight to one-tap checkout.
Evidence & numbers
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.
- Make checkout button sticky and prominent in drawerEnsure one clear CTA is visible without scrolling on mobile.
- Add trust badges and returns info inside drawerBuild confidence to proceed without leaving the drawer.
- Show free-shipping threshold progress in drawerMotivates completing checkout to hit the threshold.
Evidence & numbers
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.
- Add sticky Add to Cart bar on mobile product pagesKeeps the CTA visible while shoppers scroll long PDPs.
- Place reviews/trust badges next to Add to Cart buttonBuilds confidence at the exact mobile decision point.
- Simplify variant/size selector for one-tap addFewer taps before adding reduces mobile drop-off.
Evidence & numbers
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.
- Review Clarity recordings for top dead-click elementsIdentify which specific buttons/links fail to respond to prioritize fixes.
- Fix or remove non-functional UI elementsEliminate the dead/rage-click triggers found in recordings.
Evidence & numbers
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.
- Move Add-to-Cart button and key trust content above the foldLow scroll depth means most shoppers never see lower-page content.
- Review Clarity recordings for the highest dead-click elementsIdentify and fix non-functional accordions/images on product pages.
Evidence & numbers
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.
- Move Add to Cart button above the fold on mobileReduces scrolling needed given only 24% avg mobile scroll depth
- Simplify mobile pricing and subscription optionsClearer pricing reduces hesitation before adding to cart
- Compress mobile PDP images for faster loadFaster loads typically correlate with higher add-to-cart rates
Evidence & numbers
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.
- Pin Add to Cart button above the fold on mobile25% avg scroll depth means most users never reach a lower CTA.
- Add price and key benefit near the top of the pageSurface value proposition before users stop scrolling.
- Compress mobile hero images for faster loadSpeed up time-to-interactive to cut early mobile drop-off.
Evidence & numbers
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.
- Review mobile product-page recordings for dead-click elementsIdentify which tapped element isn't responding using Clarity session replays.
- Make the Add to Cart button sticky on mobile product pagesKeeps the CTA visible given only 25% average scroll depth.
- Check mobile page load speed and image weightSlow loads can suppress scroll and interaction before CTA is seen.
Evidence & numbers
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.
- Review Clarity recordings for mobile PDP dead-click hotspotsPinpoint exactly which tapped elements aren't registering
- Make the Add to Cart button sticky on mobile PDPKeeps the CTA visible while shoppers scroll product details
- Simplify the mobile variant/size selector UILikely source of dead clicks blocking the path to Add to Cart
Evidence & numbers
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.
- Configure Clarity to tag and report worst-performing page URLsWithout page tagging the dead-click source can't be diagnosed
- Audit the top-trafficked PDP for elements styled as buttons that aren't clickableCommon cause of dead clicks that silently suppress engagement
Evidence & numbers
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.
- Move Add to Cart button and benefit copy above the foldOnly 24% of mobile scroll depth is reached; put the CTA where it's seen.
- Add a sticky mobile add-to-cart barKeeps the CTA accessible without further scrolling.
- Trim above-fold image weight for faster PDP loadSpeeds time-to-CTA visibility on mobile.
Evidence & numbers
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.
- Make the checkout button full-width and sticky in the cart drawerImproves visibility of the next step since there's no separate cart page.
- Add trust badges and return policy inside the cart drawerBuilds confidence before committing to checkout.
Evidence & numbers
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.
- Add a prominent sticky Checkout button inside the cart drawerMakes the next step obvious without needing a separate cart page.
- Show shipping threshold and trust badges in the drawerAnswers cost/trust hesitations right where shoppers are deciding.
- Add express checkout buttons inside the drawerShortens the path from cart to purchase for mobile shoppers.
Evidence & numbers
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.
- Move price, reviews, and Add to Cart above the foldAvg scroll is only 21%, so most PDP content goes unseen.
- Add a sticky Add to Cart bar on mobile PDPKeeps the CTA reachable without scrolling.
- Check mobile PDP load speedSlow rendering could be causing early exits before scroll.
Evidence & numbers
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.
- Make checkout button sticky and full-width in mobile drawerEnsures the primary action is always visible without scrolling.
- Fix or remove elements generating dead clicks in the drawerNon-functional taps are actively costing conversions.
- Add secure-checkout and free-returns copy inside drawerBuilds confidence to proceed past add-to-cart.
Evidence & numbers
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.
- Move Add to Cart button and price above the fold21% average scroll means most visitors never reach the current CTA.
- Audit and fix dead-click elements on mobile PDP310 dead clicks suggest unresponsive elements frustrating shoppers.
- Add a sticky Add to Cart bar on mobile PDPKeeps the CTA accessible regardless of scroll position.
Evidence & numbers
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.
- Move Add to Cart button above the fold21% average scroll means most never reach a lower CTA.
- Add key benefit bullets near the priceSurfaces value props early so scroll depth matters less.
Evidence & numbers
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.
- Move the Add to Cart button above the fold on mobile PDPAvg mobile scroll is only 21%, so most visitors never reach a lower button.
- Simplify variant/size selection UI on the product pageReduce the 325 mobile dead clicks likely caused by confusing selectors.
Evidence & numbers
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.
- Audit GTM for duplicate begin_checkout triggers on desktopRule out double-firing before trusting this metric for decisions.
- Compare Shopify checkout-started count to GA4 begin_checkout countConfirms whether the 77% figure is real or a tracking artifact.
Evidence & numbers
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.
- Review recordings for the top dead/rage-click elementsPinpoint exact elements users try to click that don't respond.
- Fix or restyle the flagged non-interactive elementsRemoves friction once specific culprits are identified.
Evidence & numbers
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.
- Make the checkout button sticky in the cart drawerMobile users may not scroll far enough to see the CTA today.
- Show free-shipping progress bar in the drawerNudges shoppers to proceed instead of closing the drawer.
- Auto-open the drawer with checkout CTA visible on addImmediate next-step visibility reduces mobile drop-off.
Evidence & numbers
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.
- Review Clarity heatmaps for top dead-click elementsIdentify the specific components causing repeated failed clicks
- Move key CTAs and trust content above the fold29% average scroll means most page content is never seen
- Convert misleading static visuals into functional links or remove themReduces frustration clicks on elements that appear interactive
Evidence & numbers
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.
- Verify Clarity snippet fires on every page loadZero recorded sessions despite logged clicks points to a broken install.
- Check SPA route-change handling for session countingTheme's client-side navigation may not trigger Clarity's session-start event.
Evidence & numbers
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.
- Review top dead-click zones in Clarity recordingsPinpoint which fake buttons/images shoppers try to click
- Convert dead-click hotspots into working linksMake badges/images clickable or remove affordance cues
Evidence & numbers
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.
- Move Add to Cart button above foldWith only 21% average scroll, the CTA must be visible without scrolling.
- Fix the unresponsive dead-click element on PDP276 mobile dead clicks suggest a non-responsive image or swatch blocking taps.
Evidence & numbers
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.
- Move the Add to Cart button above the fold on mobile PDPPuts the primary action within immediate view without scrolling.
- Shorten above-fold copy so price and CTA are visible firstReduces the scroll needed to reach the purchase decision.
- Review Clarity recordings for dead-click hotspots on PDPIdentifies exactly which element shoppers are trying to tap.
Evidence & numbers
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.
- Verify Begin Checkout event fires only post add-to-cartCheck tag manager trigger conditions to rule out firing on page load
- Cross-check GA4 event counts against Shopify checkout startsConfirms whether the 100% carryover is a tagging artifact
Evidence & numbers
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.
- Make the checkout button full-width and sticky in the drawerReduce friction to proceed since there's no separate cart page.
- Show shipping threshold and returns info in the drawerAnswer objections without the shopper leaving the drawer.
- Add express checkout buttons to the drawerLet shoppers skip manual checkout entry entirely.
Evidence & numbers
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.
- Segment Clarity recordings by URL to find worst pageworstPage is currently unidentified; needed before any fix.
- Watch 10 rage-click recordings this weekIdentify the specific elements shoppers repeatedly click without effect.
Evidence & numbers
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.
- Make the drawer checkout button more prominentIncrease size and contrast so it's the obvious next step
- Add express wallet buttons inside the drawerShop Pay/Apple Pay reduce steps needed to begin checkout
- Add shipping and returns info inside the drawerReduces uncertainty that stalls checkout initiation
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Inspect GTM begin_checkout trigger for duplicate firingReloads or back-navigation may re-fire the event multiple times
- Add event deduplication logic to begin_checkout tagPrevents one checkout session from counting as several
- Cross-validate against Shopify checkout-started countConfirms the true add-to-cart-to-checkout rate before acting on it
Evidence & numbers
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.
- Log begin_checkout events per order IDConfirms whether the tag fires once or multiple times per checkout.
- Review GTM trigger conditions for duplicatesDuplicate bindings on the drawer checkout button commonly cause double firing.
Evidence & numbers
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.
- Audit GA4 begin_checkout trigger conditionsConfirm the event fires once per session, not on every drawer open.
- Cross-check Shopify admin checkout count vs GA4Validates whether the 87% carryover is real or a tracking duplicate.
Evidence & numbers
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.
- Make checkout button primary and sticky in drawerEnsures the CTA is the clear next step, not lost among cart items.
- Enable express checkout buttons in drawerShop Pay/PayPal buttons reduce steps to begin checkout.
- Add shipping and returns note inside drawerAnswers cost and return concerns before the shopper leaves the drawer.
Evidence & numbers
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.
- Make the Checkout button sticky and prominent in the drawerEnsures a single, unmissable CTA above the fold inside the drawer.
- Add a shipping/returns trust line in the drawerReduces last-second hesitation before proceeding to checkout.
- Enable express checkout buttons in the drawerShop Pay/PayPal buttons let shoppers skip straight to payment.
Evidence & numbers
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.
- Audit GA4 view_item event firing for duplicatesConfirms whether the 81% view rate is real or a tracking artifact before acting on it.
- Move Add to Cart button above the fold on mobile PDPReduces scrolling needed to convert an engaged viewer.
- Add reviews/trust copy next to the Add to Cart buttonAddresses hesitation at the point of decision.
Evidence & numbers
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.
- Add a sticky, prominent checkout button in the drawerMakes the next step obvious without scrolling within the drawer.
- Show free-shipping threshold or shipping cost in the drawerRemoves cost surprise that drives drawer abandonment.
- Add express checkout buttons inside the drawerLets shoppers skip to a wallet checkout directly from the drawer.
Evidence & numbers
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.
- Review session recordings to find top dead-click elementsPinpoint which buttons or images appear clickable but aren't
- Fix or remove identified non-functional UI elementsEliminates frustration points once specific elements are confirmed
- Strengthen above-fold content to lift scroll engagementLow 30% scroll depth suggests early disengagement from key content
Evidence & numbers
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.
- Move primary CTA and top benefit bullets above the foldMost mobile users never scroll past 24%, so key content must be visible immediately.
- Add a sticky Add-to-Cart bar on mobile PDPKeeps the buy action visible regardless of how far the user scrolls.
- Check PDP load speed and compress hero imageSlow-loading hero sections can suppress scroll and engagement on mobile.
Evidence & numbers
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.
- Review Clarity recordings for the 262 mobile dead clicksIdentify which elements shoppers tap expecting a response
- Add a sticky mobile Add-to-Cart barKeeps the CTA visible given only 24% average scroll depth
- Move key benefit copy above the foldSurfaces purchase-driving info before scroll drop-off at 24%
Evidence & numbers
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.
- Review Clarity recordings for top dead-click zonesPinpoint the exact elements generating the 498 dead clicks.
- Fix or remove the non-functional elements identifiedConverts dead zones into working links, buttons, or removes them.
Evidence & numbers
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.
- Review Clarity recordings on highest-traffic PDPsPinpoint exact elements generating dead and rage clicks before changing UI.
- Fix or remove the non-functional elements identifiedRemoves friction once session review flags the offending components.
- Test PDP and cart drawer load speedSlow scripts can make working elements appear unresponsive, inflating dead clicks.
Evidence & numbers
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.
- Move Add to Cart above the foldWith only 21% average scroll, price and CTA must be visible without scrolling.
- Audit the product page for dead-click elements328 dead clicks suggest shoppers tap images or badges expecting them to work.
Evidence & numbers
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.
- Compare Shopify checkout-started count to GA4 begin_checkout countReveals whether GA4 is over- or under-firing this event on desktop.
- Audit add_to_cart and begin_checkout tag firing in GTMCheck preview mode for duplicate or missing fires on desktop product/cart pages.
Evidence & numbers
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.
- Watch 10 Clarity recordings on product and cart pagesIdentify exactly which elements trigger dead/rage clicks before checkout.
- Remove clickable-looking styling from inert elementsStrip hover/cursor styling from badges/icons that aren't actually interactive.
Evidence & numbers
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.
- Review top 10 Clarity recordings with rage/dead clicksIdentify the exact broken elements driving frustration before prescribing a fix.
- Fix or remove identified non-responsive elementsOnce located, repair broken buttons/links or replace with working equivalents.
Evidence & numbers
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.
- Watch the top 10 Clarity rage-click recordings this weekIdentifies the exact broken elements driving the 229 rage clicks.
- Fix or remove any non-clickable elements styled as buttonsDirectly eliminates dead-click frustration once identified.
Evidence & numbers
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.
- Watch 10 Clarity recordings with rage clicksIdentify the exact element(s) shoppers repeatedly click without result.
- Fix or remove any non-functional buttons foundRestore expected click behavior on those elements.
Evidence & numbers
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.
- Review Clarity recordings for top dead-click elementsIdentify which non-clickable elements shoppers try to tap.
- Fix or restyle non-functional visual elementsConvert to real links/buttons or make clearly non-clickable.
- Re-check rage-click hotspots after the fixConfirm counts drop in the following reporting period.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Review top dead-click elements in session recordingsIdentify and fix or remove elements shoppers mistake for buttons
- Move key value props and CTA above the 32% scroll lineMost visitors never scroll past this point on either device
- Fix buttons in identified rage-click zones51 rage clicks indicate shoppers repeatedly clicking something broken
Evidence & numbers
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.
- Add persistent checkout button at top of drawerReduces steps needed to move from cart to checkout on mobile.
- Add free-shipping progress bar in drawerMotivates shoppers to proceed to checkout to unlock the threshold.
- Show trust badges for secure checkout and returnsReassures shoppers before they leave the cart for checkout.
Evidence & numbers
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.
- Review 10 Clarity recordings on top product pagesIdentifies exactly which elements trigger dead clicks
- Fix or remove the non-functional elements foundRestores expected interactivity and may lift add-to-cart
- Move key content (reviews, FAQ) higher on the pageImproves the low 31% scroll depth by front-loading engagement
Evidence & numbers
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.
- Review top Clarity recordings with dead clicksPinpoints exact elements shoppers mistake for buttons.
- Make or remove clickable-looking static elementsStops wasted clicks on badges/images that do nothing.
- Fix lazy-load delays causing perceived unresponsivenessReduces dead clicks caused by elements not yet interactive.
Evidence & numbers
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.
- Move Add-to-Cart and key benefits above the foldSurfaces the buy action before shoppers stop scrolling.
- Add a sticky mobile Add-to-Cart barKeeps the buy action reachable throughout the page.
- Review dead-click hotspots on mobile PDPIdentifies which elements shoppers mistake for Add-to-Cart.
Evidence & numbers
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.
- Add above-fold social proof (ratings, review count) on mobile PDPlifts trust at the floor-level ATC step
- Clarify pricing/subscription savings near Add to Cart buttonreduces hesitation before the cart click
- Compress mobile PDP hero and reviews above the foldshortens path to the add-to-cart decision
Evidence & numbers
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.
- Watch Clarity recordings for top dead-click elementsidentify exact elements shoppers try to click
- Fix or remove clickable-looking but inert elementsconverts friction points into functional links
Evidence & numbers
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.
- Watch recordings on top dead-click pagesIdentify exactly which elements users repeatedly click without response.
- Fix or remove non-functional UI elements foundRebind broken click handlers or remove decorative elements styled like buttons.
Evidence & numbers
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.
- Review 10 Clarity recordings showing dead clicksIdentify which specific elements users try to click.
- Restyle or activate the identified non-functional elementsRemove button affordance or make them actually clickable once found.
Evidence & numbers
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.
- Segment Clarity recordings by URL to find worst pageworstPage is currently unidentified and needed to target the fix
- Review flagged elements for fake-button stylingRemove or wire up elements that look clickable but aren't
- Re-check dead-click count after the fixConfirms the change actually reduced frustrated clicks
Evidence & numbers
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.
- Review top 10 Clarity dead-click session recordingsIdentify which elements shoppers expect to be clickable.
- Limit hover/cursor-pointer styling to real controlsRemoves visual ambiguity about what can be clicked.
Evidence & numbers
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.
- Watch top Clarity recordings with dead clicksPinpoint exactly which elements shoppers mistake for interactive controls
- Fix or remove button-like styling on non-clickable elementsReduces wasted taps and shopper frustration once hotspots are found
Evidence & numbers
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.'
- Watch 10-15 Clarity recordings with dead clicksIdentify the specific non-responsive elements causing failed taps.
- Remove or wire up non-functional visual elementsConvert decorative badges/images that look clickable into real links or remove them.
Evidence & numbers
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.
- Watch 10 Clarity recordings per deviceIdentify exactly which elements generate the dead and rage clicks.
- Fix or remove the worst offending elementsLikely candidates: fake buttons, disabled swatches, slow-loading widgets.
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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.
- Review top Clarity recordings with dead clicksPinpoint exact page elements shoppers try to click that don't respond.
- Fix or de-style non-functional visual elements site-wideConverts false affordances into real links/buttons or removes clickable-looking styling.
Evidence & numbers
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.
- Filter session recordings by dead-click volumeIdentify which specific template drives the 804 dead clicks.
- Review PDP and cart drawer for non-functional elementsCheck for disabled buttons or tooltips mistaken for clickable CTAs.
Evidence & numbers
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.
- Move Add-to-Cart button and price above the foldPuts the primary action within immediate view on mobile PDPs.
- Add a sticky Add-to-Cart bar on mobile PDPKeeps the CTA accessible regardless of scroll position.
- Add concise benefit bullets near the top of the PDPGives shoppers a reason to add to cart before they scroll away.
Evidence & numbers
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.
- Pull refund reason codes from ShopifyIdentify whether refunds cluster around quality, shipping, or expectation issues.
- Review product page claims against refund complaintsCheck for expectation mismatch driving returns.
Evidence & numbers
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.
- Pull refund reason codes from ShopifyIdentify the top two reasons driving the 8.4% refund rate.
- Compare refunded SKUs' PDP copy for overpromising claimsCheck if refunded orders share descriptions that set wrong expectations.
Evidence & numbers
$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.
- Pull refund reason codes for the last 20 orders.Identifies whether refunds are product-fit, shipping, or subscription-related.
- Clarify usage/results expectations on the PDP.Prevents mismatch-driven refunds if dissatisfaction is the main reason.
Evidence & numbers
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.
- Filter Clarity recordings by dead-click countIdentify the exact page and element causing the unresponsive clicks.
- Fix or remove the unresponsive elements foundRebind click handlers or remove decorative elements that look clickable.
Evidence & numbers
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.
- Pin the Add to Cart button in a sticky mobile barKeeps the CTA visible without requiring scroll on mobile
- Shorten above-fold product copy to surface price and CTA soonerMobile scroll depth of 21% means most copy below it goes unread
Evidence & numbers
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.
- Watch top Clarity recordings with dead clicksIdentify the exact element shoppers repeatedly click without response.
- Remove button-like styling from static elementsStop badges/icons that aren't links from looking clickable.
Evidence & numbers
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.
- Pull refund reason codes from Shopify adminIdentify whether refunds stem from billing errors, quality issues, or split-shipment partials.
- Check payment gateway for duplicate-charge bugRule out a technical double-charge issue inflating refund count above order count.
- Review support tickets tied to refunded ordersSurface product-quality or fulfillment complaints driving refunds.
Evidence & numbers
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.
- Check GA4 for duplicate view_item tags firing on product pagesDuplicate firing artificially inflates this step's retention rate.
- Cross-check mobile session counts against Shopify AnalyticsConfirms whether GA4 mobile sessions are undercounted, inflating the ratio.
Evidence & numbers
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.
- Verify Add-to-Cart GA4 event firing on desktopCompare GA4 add_to_cart counts vs Shopify cart creation events.
- Cross-check tag trigger conditions for ATCEnsure the trigger fires on all cart-drawer add actions, not just the PDP form.
Evidence & numbers
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.
- Audit begin_checkout event triggers in GTMCheck for duplicate firing on cart drawer interactions vs actual checkout page load.
- Deduplicate begin_checkout by session/order IDPrevents inflated retention numbers from skewing funnel analysis.
Evidence & numbers
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.
- Review top dead-click session recordings in ClarityIdentify which specific elements shoppers expect to be clickable.
- Fix or remove non-functional clickable-looking elementsDirectly resolves the friction once hotspots are identified.
Evidence & numbers
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.
- Make the checkout button the single most prominent element in the drawerIncrease size/contrast so it's the obvious next step after adding to cart.
- Add a shipping/returns trust line inside the cart drawerReassures shoppers before they commit to checkout.
Evidence & numbers
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.
- Review top 10 Clarity dead-click heatmapsIdentify which elements shoppers mistake for clickable controls.
- Restyle non-interactive elements that look clickableRemove button-like styling from static text/images causing dead clicks.
Evidence & numbers
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.
- Make the checkout button sticky at the top of the cart drawerEnsure the primary CTA is visible without scrolling in the drawer.
- Add a free-shipping progress bar to the drawerClarify shipping cost/threshold before the shopper reaches checkout.
Evidence & numbers
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.
- Audit GA4 begin_checkout trigger for duplication with add_to_cartConfirms whether the two events are firing together incorrectly.
- Verify the drawer's Checkout button fires a distinct event from Add to CartEnsures the two funnel steps are measured independently.
- Cross-check Shopify checkout counts against GA4 for desktopValidates whether the 100% figure is a measurement artifact.
Evidence & numbers
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.
- Make the checkout CTA sticky in the cart drawerKeeps the primary action visible without scrolling inside the drawer.
- Show shipping cost and returns note in the drawerAnswers common cost objections before the shopper exits to checkout.
Evidence & numbers
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.
- Add a sticky checkout button in cart drawerMake the checkout CTA impossible to miss inside the drawer.
- Show shipping/returns info in drawerDisplaying policy details upfront reduces checkout hesitation.
- Add express-checkout wallet buttons in drawerShop Pay/PayPal buttons cut steps to begin checkout.
Evidence & numbers
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.
- Simplify mobile product page above the foldLead with price, core benefit, and a single Add to Cart CTA.
- Compress mobile product imagesFaster load reduces bounce before shoppers reach the CTA.
- Add sticky Add to Cart bar on mobile PDPKeeps CTA visible while shoppers scroll reviews/specs.
Evidence & numbers
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.
- Pull session recordings for top rage-click URLsIdentifies the exact broken or unresponsive element.
- Fix or remove the non-functional styled elementRemoves a silent friction point once identified.
Evidence & numbers
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.
- Audit top pages for non-functional clickable-looking elements526 dead clicks suggest taps on badges, icons, or static text.
- Move key CTA and trust content above the fold31% average scroll means most below-fold content goes unseen.
- Tag the worst-performing page in Clarity for reviewPinpoint exact dead-click elements once the page is identified.
Evidence & numbers
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.
- Add reviews and trust badges near Add to CartSurface social proof directly above the mobile add-to-cart button.
- Audit mobile PDP load speedSlow-loading images or scripts may cause visitors to leave before adding to cart.
Evidence & numbers
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.
- Move add-to-cart button above the foldLow 25% scroll depth means most never reach a CTA placed lower on the page
- Add a sticky mobile add-to-cart barKeep the CTA visible regardless of scroll position
Evidence & numbers
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.
- Watch top Clarity recordings with dead clicksIdentify exactly which elements users repeatedly click without response.
- Fix or remove unresponsive UI elements foundMake clicked links, swatches or accordions functional to cut friction.
- Move key content above the fold25–36% scroll depth means most page content goes unseen.
Evidence & numbers
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.
- Pull Clarity dead-click heatmaps per pageIdentify which specific elements/pages drive the 427 dead clicks.
- Fix or remove the non-functional UI elements foundConvert dead-click hotspots into working links/buttons.
Evidence & numbers
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.
- Map dead-click hot spots by pageUse Clarity heatmaps to find exactly which elements shoppers mistake for interactive.
- Convert decorative elements to real links/buttonsMake clicked icons, badges, or accordions actually function or remove hover styling.
Evidence & numbers
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.
- Tag refund reasons in Shopify adminCategorize refunds to see if driven by product or checkout issues.
- Review the 10 most recent refunded ordersCheck for a common SKU, shipping delay, or duplicate-charge pattern.
Evidence & numbers
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.
- Review Clarity recordings on top-traffic pagesIdentify exactly which elements trigger dead and rage clicks.
- Fix or restyle non-functional clickable-looking elementsRemove ambiguity that causes repeated frustrated clicks.
- Move key CTA/content higher on the page29% average scroll means most visitors miss lower content.
Evidence & numbers
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.
- Add reviews/trust badges above the fold on product pagesBuilds confidence right where hesitation happens before Add to Cart.
- State cost-per-serving near the Add to Cart buttonClarifies value for a supplement buyer comparing options.
- Check mobile session traffic sources for bot inflationAn 88% view rate vs a 20–45% band suggests the denominator may be unreliable.
Evidence & numbers
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.
- Confirm Clarity snippet is installed on all templatesMissing session counts often mean partial installation.
- Reconnect Clarity session reporting to the dashboard feedEnsures future click-friction findings can be sized against traffic.
Evidence & numbers
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.
- Move the Add to Cart button above the fold on mobileAvg mobile scroll depth is only 21%, so many never reach it.
- Add a sticky add-to-cart bar on mobile PDPsKeeps the CTA visible regardless of scroll position.
Evidence & numbers
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.
- Move Add to Cart button above the foldEnsure the CTA is visible without scrolling on mobile PDPs.
- Add reviews or trust badges near the CTABoosts confidence at the exact decision point on product pages.
- Investigate dead-click elements on top mobile PDPs284 mobile dead clicks suggest taps on images or badges expecting interaction.
Evidence & numbers
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.
- Review Clarity recordings for top dead-click elementsIdentify which UI pieces users tap that don't respond.
- Fix or remove non-functional buttons/badgesConvert dead-click hotspots into working links or remove them.
- Compress above-fold assets to speed loadAddress low scroll depth possibly caused by slow-loading top content.
Evidence & numbers
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.
- Review top 10 Clarity recordings for dead clicksPinpoint exact elements causing dead/rage clicks
- Fix or remove non-interactive elements styled as clickableRemoves false affordances causing dead clicks
Evidence & numbers
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.
- Add a sticky, high-contrast Checkout button in the cart drawerIncreases visibility of the next step directly inside the drawer.
- Show shipping and returns info inside the drawerAnswers common objections without leaving the drawer.
- Add express checkout buttons inside the drawerShortens the path from cart drawer straight to payment.
Evidence & numbers
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.
- Review top 10 Clarity recordings on PDPPinpoints exact elements causing dead/rage clicks before any code changes.
- Fix or restyle non-functional clickable elementsConvert dead-click hotspots into working links or static, non-clickable styling.
Evidence & numbers
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.
- Compare GA4 begin_checkout event count to unique sessionsReveals whether the event fires more than once per checkout.
- Cross-check Shopify checkout starts vs GA4 countConfirms the true cart-to-checkout carry-over rate.
Evidence & numbers
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.
- Filter Clarity recordings by dead-click eventsIdentify the exact page/element behind 466 dead clicks before building fixes
- Populate the worst-page field in Clarity setupCurrently blank, blocking root-cause targeting of UI friction
- Cross-check rage-click pages against mobile PDPRage clicks may cluster at the same Add to Cart button already flagged as a leak
Evidence & numbers
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.
- Watch 10 Clarity recordings showing dead clicksPinpoint the exact elements and pages causing non-responsive taps.
- Fix or remove the non-functional UI elements foundRemove or wire up decorative elements that look clickable but do nothing.
Evidence & numbers
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.
- Watch top 10 Clarity recordings on PDP and cart drawerPinpoint exact elements causing dead/rage clicks before fixing them.
- Fix or remove non-functional clickable-looking elements foundConvert dead-click hotspots into working links or remove clickable styling.
- Re-check load/interaction speed on worst-offending templatesSlow responses can cause repeated rage-clicks.
Evidence & numbers
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.
- Review top Clarity recordings with dead clicksIdentify the specific element(s) users repeatedly click without response.
- Fix or remove non-functional UI elements foundConvert dead/rage-click hotspots into working links or buttons.
Evidence & numbers
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.
- Re-check Clarity project session count fieldConfirm the dashboard shows nonzero sessions matching GA4 sessions.
- Re-export Clarity data feedRefresh or reconnect the Clarity integration used for this snapshot.
Evidence & numbers
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.
- Audit the Add to Cart event on desktop buy-now buttonsConfirms whether buy-now flows bypass the add-to-cart tag, inflating this ratio.
- Cross-check GA4 add-to-cart count against Shopify cart dataValidates whether the discrepancy is measurement or real behavior.
Evidence & numbers
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.
- Enable page-level Clarity taggingCapture which URL each dead click occurs on to target the fix
- Review top dead-click session recordingsWatch 10-15 sessions to identify the specific element causing non-response
Evidence & numbers
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.
- Instrument the Begin Checkout → Purchase eventConfirm it fires exactly once per real transition.
- Check consent-mode gapsVerify consented conversions aren't being dropped.
- Confirm cross-domain checkout taggingEnsure the checkout domain carries the GA4 session.
Evidence & numbers
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