LEGACY INTEGRATIONS
Legacy WooCommerce integration
Existing checkout tools in this preview, while checkout diagnostics move toward the separate Frictions product.
In this guide 6 sections
ClickClue focuses on WordPress replay, heatmaps and visitor interactions. Checkout-specific diagnostics are planned for Frictions.com, a separate plugin. The tools below remain in Legacy checkout for existing installations. Recorded data, access and configured services are preserved. They are not part of the main ClickClue setup walkthrough, and this is not a release of Frictions.
Classic checkout uses known frontend events. Checkout Blocks uses cart events and visible error notices. Fixed categories include shipping, coupon, validation and general checkout errors; raw notices, payment details and order IDs are not included in those markers.
Embedded payment frames are excluded. Test your actual theme, checkout extensions and payment gateway in staging.
Legacy checkout → Checkout funnel shows recorded visits, add-to-cart, checkout view, checkout submit and confirmed paid. Each step counts recordings that reached the steps in order. The displayed conversion and drop-off figures refer to this consenting, sampled, retained set.
A submit is an attempt. Only a linked WooCommerce server paid event can add payment confirmation. The association uses a short-lived capture cookie and a keyed order hash rather than storing a raw order ID in ClickClue. Missing linkage, navigation, sampling or retention can leave an order outside the funnel.
These observations do not calculate recovered revenue or prove why a customer left.
- Open Legacy checkout → Checkout issue inbox and select a category. Read the affected-recording counts and suggested checks.
- Choose Watch latest example to open a replay with two seconds of context, or View matching recordings to review the group.
- Download an investigation brief when you need a text summary of counts, example references, suggested checks and your category note. Review it before sharing.
- After making and testing a store change, select Mark a fix. A later matching signal changes Monitoring to Observed again.
Open Legacy checkout → Legacy checkout investigation pilot in Pro to time matched staging tasks against your usual workflow. Record completed and incomplete tasks, confidence and interruptions. Results stay in the current browser for this WordPress account; export CSV before clearing storage. No study data is sent to ClickClue.
Comparisons use equal windows around a fix marker, up to seven days each and limited to retained recordings. Small samples show counts instead of percentages. A single visit may span both windows.
The change history records WordPress update hooks, not every possible deployment. Timing alone does not establish that an update caused an error.