ClickClueGet ClickClue Free
Menu
← All guides

LEGACY INTEGRATIONS

WooCommerce recording boundaries and legacy tools.

Use the optional legacy checkout tools already included in Pro, with their existing data and settings.

Pro7 min readFree and Pro 1.2.7 guidance

Free + Pro guide (1.2.7 PDF)

In this guide 7 sections

Start with the public product-page question

#

ClickClue can help review eligible public product-page visits without enabling the legacy checkout integration. A size guide, product option or hard-to-find information can be investigated using replay; Pro adds supported heatmaps, journeys and form observations.

Cart and checkout are excluded by default. Deliberate inclusion requires full page-text masking, and account, order-pay and order-confirmation pages remain excluded. The legacy tools below have their own settings and consent requirements.

Use the WooCommerce product-page walkthrough before treating checkout signals as the starting point. Recorded interactions do not establish lost revenue or a completed purchase.

Where to find the legacy tools

#

By default, ClickClue excludes cart, checkout, account, order-pay and order-confirmation pages from recording. Cart and checkout can be included only with the explicit advanced setting and Mask all page text enabled. Account and payment-specific pages remain excluded. Check both Classic and Blocks checkout with your own theme before changing this policy.

ClickClue focuses on WordPress replay, heatmaps and visitor interactions. The optional tools below remain in Legacy checkout for existing installations. Recorded data, access and configured services are preserved. Enable only the integrations you need and test them with your own checkout before using their observations.

In Free 1.2.4, cart and checkout are excluded from recording by default, including configured WooCommerce pages and plain permalinks. Include cart and checkout pages requires Mask all page text. Account, order-pay and order-confirmation pages remain excluded. Review this choice after updating; checkout observations depend on eligible capture and are not guaranteed for every gateway or extension.

What the integration observes

#

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.

Read the ordered funnel

#

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. Recording without asking first does not grant the visitor consent required for this checkout association.

These observations do not calculate recovered revenue or prove why a customer left.

A missing step can reflect excluded pages, masking scope, missing events or a changed sampling population. Check those settings before comparing a funnel from before and after an update; do not treat missing recording coverage as a change in sales.

Turn an error into an investigation

#
  1. Open Legacy checkout → Checkout issue inbox and select a category. Read the affected-recording counts and suggested checks.
  2. Choose Watch latest example to open a replay with two seconds of context, or View matching recordings to review the group.
  3. Download an investigation brief when you need a text summary of counts, example references, suggested checks and your category note. Review it before sharing.
  4. After making and testing a store change, select Mark a fix. A later matching signal changes Monitoring to Observed again.

Measure investigation time

#

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.

Interpret before and after carefully

#

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.