Checkout friction
Shows which checkout step loses you orders, how long shoppers sit on each one, and where mobile is worse than desktop.
Authored by Sid Chaudhary
Founder & CEO at Intempt
Agentic workflow
Coming soon1 step Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Find the stalling checkout step
Coming soonBlu builds a step
About this recipe
When to use it
"People abandon at checkout" isn't actionable. This drills into the checkout stage page by page to surface the specific field, payment method, or step where people actually give up.
What it delivers
Breaks checkout-stage drop-off down by individual page, surfacing which form fields, payment methods, or steps correlate with abandonment rather than reporting one blended checkout conversion rate.
How you prompt this
Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.
Tell Blu Agent what you want
“Shows which checkout step loses you orders, how long shoppers sit on each one, and where mobile is worse than desktop.”
recipe.md preview
Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.
Inputs & outputs
What the recipe needs before it runs, and what it leaves in your workspace.
Inputs
- Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.
Outputs
How the recipe runs
Blu follows the steps in order and shows you each one before anything goes live.
- 01Find the stalling checkout stepCreate a Funnel report called "Checkout Form Friction". Steps: 1. Event "Checkout created": "Started Checkout" 2. Event "View page" where Page URL contains "/checkout/shipping" or equivalent shipping step: "Reached Shipping" 3. Event "View page" where Page URL contains "/checkout/payment" or equivalent payment step: "Reached Payment" 4. Event "View page" where Page URL contains "/checkout/review" or equivalent review step: "Reached Review" 5. Event "Checkout completed" OR "Placed order": "Completed Order" Conversion window: 1 hour (in-session checkout completion) Breakdown: By "device_type" attribute on the Users object (mobile checkout typically 30% lower conversion than desktop) Compare: Previous period (prior 30 days) For each step, also surface: - Median and 75th-percentile time on the step page (long times suggest friction) - Drop-off rate vs. previous period - For users who reached but didn't pass each step: what was their last in-checkout action (helps identify the specific field/element that caused exit) Annotations: - Flag the step with the largest drop-off (the primary checkout bottleneck). - Flag any step where median time-on-page exceeds 90 seconds (typically signals form complexity, validation issues, or payment-method confusion). - Flag if mobile drop-off at any step is >15 percentage points worse than desktop (mobile-specific UX issue at that step). - Highlight the Abandoned checkout volume in the same period: these are recoverable users; pair this report with abandoned-cart recovery. Industry benchmarks: average ecommerce checkout completion rate is ~50%; top-quartile is 70%+. Step-level: shipping to payment typically 80%+ of the drop-off. Use case: every ecommerce team optimizes the checkout but most see only the top-line drop-off, not the per-step diagnosis. This recipe surfaces exactly where the friction lives. Taxonomy notes: - Checkout created and Checkout completed are canonical (Stripe-sourced). - Abandoned checkout (Shopify) is canonical and complementary. - Per-step pages are derived from View page.Page URL patterns since separate canonical events for each checkout substep don't exist.
Install Intempt and run it
- 1
Sign up
Create a free Intempt workspace.
- 2
Connect your data
Add the sources this recipe reads from.
- 3
Ask Blu
Type /checkout-form-friction in Blu once this recipe is live there.
- 4
Review and approve
Blu builds each step and waits for your OK before anything goes live.
Related recipes
Sid ChaudharyDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Sid ChaudharyPost demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Sid ChaudharyReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe 