Diagnose Conversion Drop

Investigates funnel drop-offs, performance issues, and UX blockers for ecommerce sites.

Published by @gtmagents·0 agent reads / 30d·0 saves·

Command: diagnose-conversion-drop

Inputs

  • window – lookback window (7d, 14d, 30d, campaign).
  • segments – comma-separated segments (device, channel, geography, campaign).
  • focus – funnel stage (landing, pdp, cart, checkout, post-purchase).
  • include-voc – true/false to ingest VOC/CSAT comments.
  • format – dashboard | memo | worksheet.

Workflow

  1. Data Aggregation – collect analytics, attribution, heatmap, replay, and performance metrics.
  2. Segment Analysis – compare segments vs baseline, highlight anomalies.
  3. Root Cause Mapping – correlate issues to UX, inventory, promo, or tech factors.
  4. Experiment & Fix List – prioritize remediations with impact/effort.
  5. Packaging – deliver requested format with visuals and recommended owners.

Outputs

  • Funnel diagnostic report with charts/tables per stage.
  • Prioritized issue + experiment backlog with severity.
  • Alert summary for site performance/checkout reliability.

Agent/Skill Invocations

  • conversion-ops-lead – drives diagnostics + recommendations.
  • growth-merchandising-director – reviews merchandising/promo impacts.
  • conversion-diagnostic-kit skill – ensures structured analysis.
  • site-performance-watch skill – layers in performance telemetry.

More on the bench

SKILL0

Vendor Management

Evaluate, compare, and manage vendor relationships. Trigger with "evaluate this vendor", "compare vendors", "vendor review", "should we renew", "RFP", or when the user is making procurement or vendor decisions.

sales-gtm-revops+1
0
SKILL0

Qbr Builder

Create Quarterly Business Reviews with account health scores, usage analytics, ROI analysis, expansion opportunities, and risk mitigation

customer-success+1
0
SKILL0

Escalation

Structure and package support escalations for engineering, product, or leadership with full context, reproduction steps, and business impact. Use when an issue needs to go beyond support, when writing an escalation brief, or when assessing whether an issue warrants escalation.

customer-success+2
0