Session recordings
Watch a real visit end to end, at the speed it happened.
For exampleReplay the 47 sessions that reached delivery and left without paying.
Recordings, heatmaps and CRO
Watch where your checkout loses people, then run the fix as a test.
Replay real visits, see where attention goes, and find the step that costs you orders. Every finding comes with the sessions behind it, and turns into an experiment in one click.
- Where it lives
- The Behavior app
- Works with
- Shopify, WooCommerce, Magento — or any site you can add one script tag to
- What waits for you
- Which experiment ships
- Included in
- Every Self Service plan
01 / 04
In the app
The Behavior app, funnel surface.
Checkout funnel
8,420 sessions · last 30 days
Entered checkout
8,420
sessions, last 30 days
Biggest single drop
−33 pts
delivery → payment
Orders it costs
~118/mo
at your current basket
Where they stop
Share of shoppers reaching each step
| Cart | 100% |
| Address | 82% |
| Delivery options | 74% |
| Payment | 41% |
| Order placed | 38% |
02 / 04
What you can look at
Heatmaps
See where attention lands on a page, and where it never gets to.
For exampleShows attention pooling below the delivery block, not on it.
Funnels
Measure each step, so a drop belongs to one place rather than to checkout.
For example82% → 74% → 41%: the loss is between delivery and payment.
Journeys
Follow the path from arrival to order, including the loops back.
For exampleShoppers who scroll back to the product page convert 3× less often.
CRO experiments
Turn a finding into an A/B test against your current page, not a hunch.
For exampleMoves the delivery date above payment and runs it against the live version.
Every finding, sourced
Each conclusion links back to the sessions it came from.
For example“Delivery date is the blocker” opens the 8,420 sessions it was read from.
03 / 04
You can check any of it, whenever you want.
Every run keeps what it read, the rule it followed, and who approved it.
What Synton reads
- Recordings of shoppers scrolling back to look for a delivery date
- A heatmap that puts attention below the delivery block, not on it
- The same pattern across 8,420 sessions, on mobile and desktop
What Synton changes
- Move the delivery date above the payment options
- Run the change as an experiment against your current page
- Report the result with the sessions behind it
What you can check
- No finding is reported without the sessions behind it
- A receipt for every change: what it read, the rule it followed, who approved it
- Product changes undo in one click. Other changes keep a snapshot for manual recovery, and some cannot be undone at all
04 / 04
What it does not do
- It needs traffic. A page with a handful of visits a week will not produce a result you can trust.
- It cannot record a page it is not on. Recording needs the Synton script on your storefront.
- It does not deploy the winner for you. An experiment reports a result; publishing it is your call.
Synton products
See the other products
Insights
Stop guessing at your checkout.
Connect your store, let it record for a week, and see which step is actually costing you orders.
See where I lose people