Pick the biggest evidence-backed conversion opportunity worth A/B testing, using existing reports, metrics, audits and experiment learning.
| Context | What to provide |
|---|---|
| Required context | Store identity and existing reports, test results, or owner requests. |
| Optional context | Existing roadmap and tickets, active tests, owner decisions, goals, capacity, and constraints. |
Execution requirements: Evidence access and supported result output. Tracker updates need authorized writes outside Glue's read-only review runner.
Local runs link the complete shared-schema report.json with a readable result summary. Glue manages its JSON results.
How to use
- Invoke
$plan-shopify-optimizationwith goals and constraints; include the current tracker when available. - Review eligible experiments, the selected opportunity, investigation gaps and separate direct fixes. Missing analytics lowers confidence and launch readiness without preventing worthwhile experiment proposals. Tracker changes require their own applicable authorization.
Examples
Use $plan-shopify-optimization to find the biggest supported A/B-test opportunity from these storefront reports without rerunning the audit.
Use $plan-shopify-optimization to review this week's funnel evidence, audits and experiment results; rank worthwhile A/B tests and explain what evidence is missing if none is ready. Preserve existing decisions.