People visit the product page, yet orders do not grow. Is the page the problem? Perhaps buyers cannot choose a size, discover shipping costs too late, or encounter an error while paying. All three can appear as “low conversion,” but each needs a different response.
10 parts · 3 checkpoints · 1 free / 9 member parts →
Locate the step where buyers stop before choosing this week’s change. Conversion rate optimization (CRO) follows a purchase journey: seeing the product, understanding it, adding it to a cart, starting checkout, paying, and receiving the order. Advertising brings people to the starting point. Refunds and support feedback later help you assess whether those orders fulfilled the page’s promise.
This lesson is for a store team planning its weekly work. It helps assign an issue to the page, merchandising, technical, payment, support, or email owner and agree when to review it. If a funnel is new to you, picture a series of purchase steps. Some people continue at each step; others leave. Comparing two neighboring steps often gives you a clearer investigation than staring at total orders.
Consider a buyer who adds an item to cart and leaves after seeing the delivery charge. Replacing the main product image may do little for that problem. Conversely, a simpler payment button will not explain a size choice that buyers never understood. Observe the actual path, repeated questions, and error records before proposing a change.
Define the denominator as well. An add-to-cart rate can use sessions or visitors, so percentages using different definitions are not directly comparable. The worksheet below keeps page, market, device, traffic source, and dates aligned, then checks purchase, after-sales quality, and profit together. Its figures are classroom examples rather than store performance claims.
Use the three checks below to prepare your investigation. They organize the question; the later exercises assess the evidence, proposed action, and team responsible for it.
What this lesson answers
- When conversion weakens this week, how do you first locate whether the breakpoint is page clarity, event tracking, payment and checkout, abandonment, or the post-purchase promise?
- Why should you avoid changing the page, discount, and traffic together and calling the combined result CRO?
- Which market, device, source, page-version, and date fields make one conversion evidence row comparable?
- When add-to-cart rises but refunds, support, or contribution profit worsen, how do you pause scale and repair the promise?
- How should you QA the GA4 view_item, add_to_cart, begin_checkout, and purchase events before trusting a funnel result?
- How does a Klaviyo abandonment flow separate Added to Cart from Started Checkout and verify its exclusion rules?
- When should mobile CTA, above-the-fold proof, and safe-area issues go to the page owner instead of another experiment?
- When scanner findings, heatmaps, support questions, and refund counter-signals conflict, how do you write the next reversible weekly action?
What should this week’s review resolve?
Define the issue: which page and step, who encountered it, and what record they left. By the end, you should be able to assign an owner, agree on a review date, and say what would make the team stop.
Free account to read · Parts 2-10 · 9 parts
Member practice: investigation, ownership, and review
This part includes
- Investigate page and behavior evidence
- Work through complete cases and decisions
- Edit, copy, and restore a review record
1 self-check question
An account is free; sign in to read this part.
Checking your membership…
No checkpoint finished in this lesson yet. Start with “Go to the exercise”.
Common questions
- How is operations growth CRO different from the dedicated CRO series?
The dedicated CRO series goes deeper into page roles, heatmaps, A/B testing, and checkout friction. This lesson only answers the weekly prioritization question: from orders, support, refunds, reviews, site search, and scanner findings, which signal looks like the real breakpoint, and should the next move be page repair, tracking QA, ad-page match, post-purchase counter-evidence, or a lifecycle email route?
- Where should the conversion route table send a breakpoint?
The conversion route table should send the breakpoint to the next execution route, such as page role map, heatmaps and recordings, GA4 event QA, ad-page match, fulfillment and returns, post-purchase counter-evidence, or abandoned lifecycle. Do not package every breakpoint as an A/B test.