ClickClueGet ClickClue Free
Menu
← All guides

TROUBLESHOOTING

Find out why a recording or replay is missing.

Work through the common reasons a replay, page observation or connection is missing.

Free + Pro7 min readFree and Pro 1.2.7 guidance

Free + Pro guide (1.2.7 PDF)

In this guide 8 sections

No recording appears

#

Separate startup from delivery. In 1.2.6, optional public font styles do not delay starting capture, and recorder loading overlaps authorization after admission. The selected recording basis and server approval are still required. The local test status and an acknowledged upload show different stages of that process.

  1. Confirm setup is finished, including the explicit storage and visitor-control choices. Check recording is enabled and sampling is suitable. Setup saves 100% sampling until you change it. Clear page/CDN caches after changes.
  2. Use a signed-out private window on an included public page. Administrators and other signed-in users are excluded. Cart and checkout are excluded by default; do not use them as your first capture test.
  3. Check the saved mode. ClickClue’s banner needs a published privacy policy and visitor acceptance. An external banner must send the replay-consent signal. Without-asking mode needs the explicit owner setting, and still respects valid refusals, Do Not Track and Global Privacy Control.
  4. Open the test link from setup or Settings → Test & diagnostics and read its local status. Look for storage-budget, asset-loading, excluded-page or authorisation errors.
  5. Confirm an upload was actually acknowledged; enabled settings alone are not an upload. Back in WordPress, clear date/path/device filters and refresh the list. Check the latest recording’s page and time to identify your test. Final upload unconfirmed is not proof of a complete visit.

Starts, saved visits and short durations

#

Recording attempts counts recording starts this month. Saved recordings counts visits that delivered a replayable page. A start can appear before its first upload, or remain without a saved replay if delivery stops. View details in the awaiting-page notice and open Test a recording to inspect the current tab.

Use the upload label beside a recording to inspect its last received data and checkpoint status. A status of 0:00 can mean only the initial page arrived; it does not prove the visitor left immediately. Update to the current version, refresh and inspect a new signed-out visit. Existing missing events cannot be recovered.

If the test panel reports a host response such as 429, the host is throttling requests. Let the recorder retry, check the host’s request logs and ask about the affected ClickClue endpoint. Avoid repeatedly reloading the test or disabling the site’s protection broadly. A server cannot diagnose an upload it never received.

A visitor cannot find the stop control

#

The floating Replay privacy button is off unless selected. Check the placement saved in setup or Settings. If you chose your own control, provide a same-page #clickclue-privacy footer/menu link or connect the local openPrivacy() API where ClickClue runs.

Test while signed out on an included page with recording enabled. Open the control, stop capture and wait for deletion confirmation. A saved custom-control declaration does not verify the link, and stopping capture alone is not a confirmed deletion. Use Retry deletion when shown.

The replay looks different

#

Review the page-text masking choice and keep private-region exclusions in place. Enable Capture public design assets to include eligible public images, backgrounds and fonts. Use fit-width or fit-window, then adjust zoom. Existing recordings cannot recover omitted assets.

Replay uses saved eligible public design assets. Only the public Google Fonts stylesheets already used by the page and their font binaries may be copied from the fixed provider; other remote-only assets are excluded. Video, canvas and embedded frames remain excluded. Dynamic builders, animations and browser-specific styles can still differ. Reproduce the page with synthetic content when reporting a problem.

Use matching current Free and Pro versions, reload open administration tabs and clear page/CDN caches after updating. A validated saved font may use a data-font fallback if the host allows it. Do not weaken Content Security Policy or permit live-site scripts to repair a replay. Image-click evidence missing from an older visit cannot be backfilled.

A checkout or payment signal is missing

#

Free 1.2.4 excludes cart and checkout by default. Include cart and checkout pages requires Mask all page text. Account, order-pay and order-confirmation pages remain excluded. These rules can reduce coverage in an existing checkout funnel after updating.

Confirm WooCommerce and both ClickClue packages are active. Test the relevant classic or Blocks checkout with synthetic data and a gateway in test mode.

A form submit does not confirm payment. Server-confirmed markers need a consenting, linked recording and a paid event. Redirects, browser privacy choices, missing linkage or third-party extensions can affect coverage. Owner-policy recording does not unlock that consent-gated association.

Legacy checkout email, AI or a remote site fails

#
  • Email: verify WP-Cron and WordPress mail delivery, the recipient and the threshold. Check the reported transport status.
  • AI: confirm opt-in, a valid key, model access and available API budget. Check whether the daily request cap was reached.
  • Agency: use the final HTTPS address, a dedicated reviewer and a valid application password. Check security rules and certificate validity.
  • Deletion: use Retry deletion and check database health. Do not treat stopped capture as a confirmed deletion.

Prepare a useful report

#

Write down the expected behaviour, actual result, versions, page, theme, relevant extensions, reproduction steps and the exact non-sensitive error. A recording ID can be useful inside an authorised support exchange.

Do not send API keys, passwords, full recordings, payment information or real customer details. Use synthetic data and review any exported brief before sharing.

Choose the next check from the symptom

#
What you observeCheck nextWhat it does not establish
No saved recordingUse a signed-out test; check the recording mode, opt-outs, exclusions, sampling and storage.That every visitor is missing.
An image is blank in replayCompare the signed-out live page with a matching new test and review public-design capture.That the image failed for the original visitor.
A visit ends unexpectedlyInspect its upload/checkpoint status and the activity that was actually saved.That every intended moment reached the server.
No form submit is observedReproduce the form interaction with synthetic data and inspect the live response.A confirmed abandoned enquiry or failed email.

For a missing image, use the one-image diagnostic record. For mobile form feedback, follow the two-case form test.