Shoppers add to cart, then leave
A funnel shows the step where carts are abandoned, and recordings show what happened just before.
See funnelsEcommerce
Heatmaps, session recordings and A/B testing for online stores
See where shoppers drop off between the product page and payment, watch the visits behind the numbers, and test the fix before you roll it out.
Cuttl helps online stores find where shoppers give up and why. Funnels show which step between product page and payment loses the most people. Recordings and heatmaps show what went wrong on that step. Then you A/B test a fix and measure it in orders, revenue per visitor and average order value.
Where online stores lose sales
Most stores lose sales to the same few problems, and each one shows up in the data.
The checkout form loses people field by field
See the field people hesitate on or quit at. Typed values are never recorded.
See form analytics
A button or coupon box is quietly broken
Rage clicks, dead clicks and errors, ranked by how many shoppers they affect.
See issues
Phones convert worse than desktop
Filter heatmaps and recordings by device to see what mobile shoppers miss.
See heatmaps
Product pages get views but few add-to-carts
Scroll maps show whether people reach the price, reviews and delivery details.
What is a heatmap?
Slow pages on sale days
Core Web Vitals from real shoppers, next to the pages they leave.
See site healthSpot the drop, test the fix, ship the winner
Find the leak in your checkout funnel
Build a funnel from product page to order confirmation. Funnels run on data you already have, so a new funnel shows past visits too.
- Drop-off at each step, by device, channel, campaign or country
- One click from any step to the recordings of people who left there
- Field-level drop-off on checkout and account forms
See why shoppers stop
Recordings replay real visits with idle time skipped. The timeline marks rage clicks, errors and the moment someone converts or leaves.
- Recordings sorted by what’s worth watching
- Console errors and failed requests next to the visit
- Visits with frustration, errors, feedback or an order are always kept, even when recordings are sampled
- Form inputs are masked by default, and IP addresses are never stored
Test the fix and measure it in orders and revenue
Turn the problem you found into an A/B test, with the evidence attached. Change text, layout, images and buttons in the visual editor, or use your own CSS and JavaScript.
- Revenue per visitor, average order value and profit per visitor as test metrics
- Guardrails alert you or turn off a variant if it hurts orders
- Heatmaps and recordings for each variant
- Flicker-free, so shoppers don’t see the original page switch to the variant
Know the fix worked, then roll it out
Roll a clear winner out to everyone with a small holdout. Cuttl keeps watching the original issue, marks it fixed once the clean visits can’t be chance, and reopens it if the problem comes back.
- Rollouts with a holdout and ramp history
- Fixes checked automatically, and reopened if they return
- Change Impact for changes too small to test, like a new delivery banner
Built for how stores work
Thousands of product pages, one viewURLs are grouped by template, so every product page adds up into one heatmap.
Campaign traffic, kept apartFilter by channel, campaign, UTM or landing page to compare sale traffic with regular visitors.
Bots out of your numbersBot and AI-agent traffic is kept apart from real shoppers in reports.
Smaller stores can measure changes tooWhen a test would take too long, Change Impact compares before and after instead.Your first week with Cuttl
Add the snippet
Paste one script into your store’s page head, or add it through Google Tag Manager.
Set your goals
Mark add-to-cart, checkout started and order placed as goals, then build a funnel from them.
Find the biggest drop
Open the step that loses the most shoppers and watch the recordings behind it.
Test one fix
Draft an A/B test from that issue and measure it in orders and revenue per visitor.
Ecommerce questions
Checkout optimization means finding and removing whatever stops shoppers from finishing a purchase, such as surprise delivery costs, long forms or broken buttons. Funnels, recordings and form analytics show which of those problems your own store has.
The cause differs by store. Common ones are costs that appear late, forced account creation, a form field that rejects valid input, or a payment step that fails on phones. A checkout funnel with recordings of the people who left shows which one applies to you.
Yes. Cuttl groups URLs by template, so all product pages can be read as one heatmap, and you can still open a single product page on its own.
You can test any page where the Cuttl snippet runs, using the visual editor or your own code. Some platforms host the checkout on their own pages and limit which scripts can run there; in that case, test the steps before it, such as the cart and delivery information.
Orders and other goals, revenue per visitor, average order value and profit per visitor, plus clicks, form submits, bounce and scroll depth. Guardrails can alert you or turn off a variant that hurts a key metric.
No. Form inputs are masked by default, so typed values are never recorded, and Cuttl doesn’t store IP addresses. It also respects your consent settings before recording.
Heatmaps, recordings and funnels work at any traffic level. If an A/B test would take too long, the pre-test planner tells you, and Change Impact can compare before and after instead.
Comparing tools? See Cuttl vs Contentsquare and Cuttl vs Microsoft Clarity.
Find your store’s biggest drop-off this week
Add one script to your store and your first funnels, heatmaps and recordings start filling in from the next visit.