Your first recording.
Your next useful clue.

Before you start

Use WordPress 6.6 or newer and PHP 8.1 or newer. Start on a staging copy with a database backup. ClickClue stores recordings in your WordPress database; it does not need a cloud recording account.

• Activate the plugin separately on each site. Network activation is not supported.
• Use transactional InnoDB tables on MySQL/MariaDB. Allow space beyond the replay payload limit for database indexes and backups.
• Use synthetic details and sample form submissions for your first test.

Install the free plugin

1. For a new installation, use the ClickClue directory package. For an existing installation, use the matching upgrade ZIP for its current plugin directory.
2. In WordPress, choose Plugins → Add New Plugin → Upload Plugin. Select the ZIP, install it and activate ClickClue.
3. Open ClickClue → Settings & privacy. New installations start with recording paused, 10% sampling, seven-day retention, a 250 MiB payload budget and page-text masking enabled.

Record an eligible visit

1. Publish your website-specific privacy policy and select it in WordPress Settings → Privacy. The built-in replay prompt needs that published link.
2. Choose Prepare test settings to fill the form with recording enabled and 100% sampling. Review the consent prompt, excluded paths and private selectors, then choose Save settings. Preparing alone does not save.
3. Clear your page cache. At 100% sampling, every consenting, eligible tab can be selected while recording is enabled.
4. Copy the test link into a signed-out private window. Signed-in users, including administrators, are excluded.
5. Choose one public page and a question, such as whether someone can find the size guide. Grant replay permission, scroll to the details and try the relevant link using synthetic details. The test panel should confirm an upload.
6. Return to WordPress. Choose Check for my recording, then Review latest recording. Inspect masking and playback. Bookmark the recording and add a note describing the useful moment, what you observed and what you will check.
7. Restore normal sampling or pause recording after the test.

An optional walkthrough in both editions

Choose Start tutorial at the top of the ClickClue dashboard. Free covers recording and review; Pro continues into grouped evidence, saved investigations, assignments and descriptive comparisons. Pause or resume whenever you like. The walkthrough never changes recording settings, grants consent or connects a service.

Progress is a checklist you mark yourself, saved in the current browser for your WordPress account and edition. It is not a verified setup result. Reset tutorial progress clears only that checklist. You can use every feature without completing it.

Add the Pro preview

Install the matching Pro add-on alongside ClickClue Free. Update Free first, then Pro. The current release adds Clues, heatmaps, structural form insights, journeys, comparisons and optional feedback without requiring WooCommerce. Earlier checkout integrations remain documented separately.

The preview does not require a purchase or a licence key. Annual launch bundles cover 1, 5 or 25 sites with the same Pro features. Preview transition details will be announced before availability changes. Installed previews remain usable and never become paid subscriptions automatically.

Explore page heatmaps and forms

Understand the defaults

The small consent loader runs first. The capture engine loads only after permission, sampling and server authorisation pass. Form values are always masked. Page text is masked by default.

Do Not Track and Global Privacy Control stop recording. Signed-in users and administration, login, account, order-pay and order-confirmation paths are excluded. Browser navigation into an excluded path also stops active capture.

• Images are excluded by default. An administrator can explicitly approve public, static WordPress library images; only prepared copies of those images can appear in new recordings. Private regions still take priority.
• Canvas, SVG, audio, video, embedded frames, hidden inputs and editable regions remain excluded. External fonts and CSS background images are not fetched.
• URL queries and fragments are removed. Recorded links and arbitrary asset URLs are stripped.
• Replay reconstructs the page. Dynamic or complex layouts can differ from the original; inspect a sample visit on your actual theme.

Organise approved public images

Replay images is off by default. Explicitly approve individual public static WordPress attachments and organise them into named collections. The catalogue holds up to 256 approvals. Add or move images in groups of up to 16; browse 12 previews per page. Moving between collections does not alter consent.

A recording saves only used copies, bounded to 64 images and 2 MiB within its existing payload allowance. Images are prepared locally without metadata; only supported same-origin local URLs are matched. Private and masked regions always take priority. No arbitrary image URL is fetched.

Removing approval or switching image copies off removes affected retained copies. Downloaded exports and backups need separate handling. Updated approvals require current consent. External fonts, CSS backgrounds, SVG, video and embedded content stay excluded.

Publish your notice and keep consent evidence

In WordPress Settings → Privacy, select a published page with your operator identity, privacy contact, replay purpose, legal basis, recipients, retention, transfers and visitor rights. Adapt the ClickClue suggested text there. The built-in prompt links to this page and blocks capture if it is missing. Allow replay and No thanks have equal visual prominence.

From 0.6.2, affirmative choices include a decision time and notice revision. An older positive choice or a changed notice/retention/masking/edition requires a fresh choice; a valid refusal stays refused. Update both ZIPs and clear page/CDN caches so the current loader and revision reach visitors.

New recordings store the server receipt time, matching revision and retention deadline, deleted with the recording. Increasing retention later does not extend that deadline. A notice change also stops uploads with earlier authorisation. Existing sessions keep blank receipt fields; no historical consent is invented. Keep dated copies of each notice and any CMP ledger under your justified retention policy. A browser flag or technical receipt alone does not prove that consent was informed and valid.

Finish your website-specific privacy setup

This is a configuration guide, not a compliance certificate. Establish your controller/processor roles, applicable national cookie rules, access controls, processor agreements and international-transfer arrangements. Assess whether a DPIA and a DPO are required for your actual processing before collecting real visits.

Document how you receive and answer access, erasure, objection and other rights requests, normally within one month. The current-visit withdrawal token is not an identity search across every visit. Do not collect new identity data just to make anonymous visits identifiable.

Review cleanup, backups, exports and enabled email/AI/agency services separately. Maintain an incident response process, including authority notification within 72 hours when required and notification to affected people when the applicable threshold is met. Keep your local legal review and decisions with the installation record.

Exclude sensitive regions

Add data-tw-block to a private element or enter its CSS selector in Settings & privacy. Existing data-private and .rr-block regions are also excluded.

Structural classes and IDs may remain for layout. Exclude elements whose attributes contain personal information. Inspect dynamic content, account widgets and order details in a synthetic recording before real use.

<div data-tw-block>Private customer information</div>

Connect your consent manager (optional)

Keep the built-in prompt until your consent manager is wired and tested. Turning the prompt off does not remove the consent requirement. Call grant only after the visitor agrees, and withdraw whenever that choice changes.

• Do not call grant on page load for every visitor.
• Test accept, decline, later withdrawal, cleared storage and the next page visit. A current notice revision is required by the start endpoint.
• Archive your CMP notice and consent records. Change the tracewell_consent_notice_revision filter value whenever your CMP replay purpose or notice changes, then clear caches.
• The earlier window.Tracewell API and tracewell:consent event remain supported for existing installations.

// Call after the visitor grants replay consent.
window.ClickClue?.grantConsent();

// Call when replay consent is withdrawn.
window.ClickClue?.withdrawConsent();

Stop capture and confirm deletion

Replay privacy lets the visitor stop and delete the current authorised recording. Capture stops immediately. A separate confirmation reports whether saved data was deleted.

A failed deletion keeps a tab-local retry token when session storage is available. Use Retry deletion; reloading that tab or reconnecting also retries. New capture stays off while deletion is unresolved. A former capture token can request deletion for up to 30 days after expiry, but cannot upload. Older recordings follow retention and administrator deletion.

Understand retention and backups

Find the right recording

You can save up to 20 filter combinations per account on each site. In Pro, category filters narrow the list to matching checkout signals.

1. Open the recording list and filter by path or device. Add a UTC date range when you need a specific period.
2. Choose watched/unwatched or bookmarked recordings. These states belong to your WordPress account.
3. Name a useful combination and choose Save these filters. Select it later from Saved filters, or use Clear filters to reset.

Work through the replay

• Use play/pause, seeking and playback speed to inspect a moment.
• Skip inactivity, move to the previous/next event or jump to the first error.
• Space toggles playback and arrow keys move five seconds when a form control is not focused.
• A successfully loaded replay is marked watched for accounts with review permission. A failed load leaves it unwatched.

Keep useful context

Bookmark a recording and add a concise session note: what you observed, what you want to check and the change you plan to test. Notes are visible to authorised reviewers; they are not a private notebook.

Each recording can hold up to 20 notes of up to 1,000 characters each. The note’s author or an administrator can delete it. Avoid customer names, payment information, passwords and pasted order details. An administrator can delete the recording in either edition. With the separate Pro add-on, administrators can also export permitted recording data; treat downloaded copies with the same care as the original.

Understand recording completeness

The player shows whether delivery was confirmed through the latest checkpoint, is still unconfirmed, or was interrupted. Confirmation does not prove the visitor’s entire visit was captured.

The recorder retries identical batches and recovers from temporary disconnection using a bounded memory-only queue. Navigation and browser back/forward restoration preserve their own stream checkpoints. Closing the browser can destroy unsent events; do not interpret a missing ending as visitor abandonment.

Computed layout tracking prioritises visible changes and is bounded to2,048 elements and32 open shadow roots. A complex page can exceed that budget. Private boundaries still apply and unsupported content remains excluded.

How this fits the product direction

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.

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.

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

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.

Select the page layout first

A layout fingerprint is a structural grouping aid. It is not a screenshot, a security identifier or a guarantee that every dynamic layout is identical.

1. Open Heatmaps & forms and choose your date/device scope.
2. Choose a page path, layout fingerprint and viewport group. Refresh after recording a new synthetic visit.
3. Read the recording counts alongside the result. Do not combine different layouts to claim a single page-wide result.

Read click and scroll observations

The heatmap shows coarsened positions from the top to the bottom of the page. Larger cells represent more clicks. A table gives the displayed cells’ counts and distinct recording counts.

Scroll reach counts observed depth thresholds. It does not establish that someone read or understood the content. Private regions are excluded. The grid remains available for older recordings without measured layout dimensions. The overlay is a reconstruction, not a screenshot; blocked media, fonts and dynamic layout differences can affect its appearance.

1. Choose Open recorded page overlay to reconstruct a matching masked page.
2. Switch between Click density and Scroll reach.
3. Use the page-position slider to inspect the relevant part of the page.

Inspect fields without their values

Fields use structural positions such as Form 1 · field 2, rather than entered values or labels. The table reports focus, validation signals and submit attempts.

No submit observed counts focused fields in recordings inactive for at least five minutes without a same-form submit. Missing signals, navigation and custom form behaviour can affect it; this is not a confirmed abandonment count.

When form structure changes, select the corresponding new layout. Test AJAX forms and custom validation in your own theme before relying on the observations.

Name structural elements and compare periods

Whole-range element and form reports let reviewers name an important button or structural field in administration. These aliases are owner-provided context, not text collected from a visitor.

Compare chosen UTC periods and device categories, keeping layout identifiers separate. Open supporting recordings before making an interpretation. Input values remain excluded and focus duration is not typing duration.

Review a clue in context

A clue is a lead, not proof of a broken button. Legitimate interactions can meet these conditions. The review status applies to this observation, not an entire website.

1. Open Clues and choose an observation. Watch opens shortly before its recorded moment.
2. Inspect what happened before and after. Three clicks within one second can create a repeated-click clue; an eligible button with no observed response for about 1.5 seconds can create a possible unresponsive-click clue.
3. Mark the observation New, Reviewing, Resolved or Ignored. Note the evidence and the next thing you will check.

Follow an ordered path

Journeys shows page paths within a retained recording. Save up to twenty funnels, each with two to eight ordered steps matching page paths, clues or form observations. A path prefix includes its child paths.

Use a recorded layout ID when structural field positions matter. Journeys do not identify a person across separate visits or devices.

Compare two periods fairly

The instant Compare screen analyzes batches of up to 200 retained recordings. Use Whole-range reports for all eligible recordings in the period. Consent, sampling, retention and bounded observations affect coverage. Changes in rates do not establish that a website edit caused the difference. Older recordings do not receive invented new observations.

1. Choose two separate UTC date ranges.
2. Use matching page, device and layout filters where appropriate.
3. Read the sample counts and denominators before interpreting rates.
4. Inspect representative replays from both periods before drawing a conclusion.

Build a whole-period report

Use Whole-range reports for all eligible retained recordings in the chosen UTC period. Progress and the observation cutoff remain visible while bounded jobs process the indexes. WP-Cron continues work; manual advancement also works on low-traffic sites. Refresh to include later arrivals.

Counts exclude deleted and expired recordings. A report cannot reconstruct observations that were never captured. Legacy instant Discovery views still show their sample limits; heatmap aggregation follows its separate existing path.

Temporary jobs expire after one hour and are limited to two per reviewer and eight per site. Each job can hold up to100,000 recording memberships and500,000 derived facts; reaching a bound is labelled partial. Narrow the period to complete a larger investigation. Each recording retains up to300 indexed observations.

Follow up a recurring clue

Whole-range reports groups repeated observations by kind, page, layout, device and structural target. Review affected visits, frequency, trend and replay moments. Set an owner and review state, and record an edit date when relevant.

Before/after comparisons describe observations. They cannot establish that your edit caused a change. Layout changes, sampling, consent and different traffic can all affect the result.

Configure meaningful goals

Use Goals to create fixed named success observations and select supported form adapters. Manual integration must call the goal only from your actual successful-completion callback. Never pass form values, email addresses, customer IDs or other identifying content.

An integration-reported completion is separate from a submit attempt and does not prove delivery, payment or a business result. Configuring enabled goals changes the consent scope. Use timed funnel steps and the product, enquiry and sign-up templates to inspect the journey before completion.

Create a short optional campaign

Visitor feedback supports multiple campaigns. Choose up to three rating or fixed-choice questions, an optional conditional follow-up, public paths, a UTC schedule and browser-session frequency controls. Preview the flow and publish your site-specific privacy notice before enabling it.

A campaign requires current replay consent and an eligible sampled recording. Signed-in, private, account and checkout pages stay excluded. No free-text responses are collected. Never ask for identifying or sensitive information.

Review feedback with its context

Filter results by date, page and device. Responses remain linked to the exact saved question revision and current recording. Legacy single-question results remain available. Pausing stops new responses; deletion, withdrawal and retention remove linked responses.

A browser-session quiet-period marker is stored only after consent, cleared on withdrawal and does not identify people across visits. Responses are voluntary and cannot represent every visitor.

Assign roles in WordPress

1. Sign in as a WordPress administrator and open Users → All Users.
2. Edit the existing account that needs access. Under Role, choose ClickClue analyst or ClickClue reviewer.
3. Select Update User. Ask the person to sign in with their own account and confirm the expected ClickClue access.

Invite someone to one recording

An invitation is not a public replay link. It expires, binds to one account and recording, and stops working when the recording is deleted.

1. As an administrator, open a recording and expand Invite someone to this replay.
2. Choose an existing WordPress account and an expiry of 1–168 hours. Create the invitation.
3. Copy the link and share it with that person through your own approved channel. Creating the link does not send an email.
4. The recipient must sign in as the chosen account. Revoke access from Workspace → Active replay invitations when it is no longer needed.

Review access and changes

Workspace displays the latest 30 entries from a bounded log of up to 100 administrative actions. It includes the actor ID, action, target reference and time, not replay contents. This is a recent activity aid, not a tamper-proof compliance archive.

Work in shared investigations

Create private or team collections, add retained recordings, assign an eligible WordPress account and choose a review status. Add a discussion at a replay timestamp to keep evidence and context together. Assignment does not grant access or send a message.

Private collections belong to their owner and administrators. Team sharing still requires a ClickClue-capable WordPress role. Deleted or expired recordings lose their linked collection membership and discussion. Avoid putting sensitive visitor details in notes.

Connect a remote site

Connections use HTTPS and do not follow redirects with credentials. Use the final canonical site address. Application passwords are encrypted on the central server using its WordPress salts.

1. Install and activate compatible ClickClue Free and Pro packages on the remote HTTPS site.
2. Create a dedicated ClickClue reviewer account there. Generate a WordPress application password in that user’s profile.
3. On your central site, open Workspace → Your sites → Connect another WordPress site.
4. Enter the remote site address, reviewer username and application password. Select Connect site.

Understand the overview

The overview includes the local site and up to 25 remote connections. It reports capture state, retained recording counts, issue counts and other summary information. Remote summaries may be cached for five minutes.

Open WordPress takes you to that site’s workspace. Each site keeps its own recordings, access controls, sampling and storage settings. The overview does not pool storage or increase a single site’s capacity.

• Download client report exports a CSV of site summaries with their observation time.
• It does not export recording payloads, customer identities or a branded PDF.
• Review the report’s site names and contents before sending it to a client.

End a connection

Disconnect removes the saved connection from the central workspace. Revoke its application password at the remote WordPress account when access should end completely. A changed site address, password, certificate or security rule may require reconnecting.

Save and export an investigation report

Investigations saves filter recipes combining clues, journeys and feedback. Report totals and exports share their retained population and coverage. Reopening a report reloads live eligible evidence instead of preserving hidden copies of removed recordings.

CSV and JSON exports require the appropriate administrative access. Keep exported files private; the plugin cannot recall files already downloaded. Connected-site summaries remain aggregate health overviews rather than a central store of remote recordings.

Configure the legacy checkout digest

This preview’s digest covers the legacy checkout categories. Digests contain fixed category counts and a link to the site’s admin area, without recording payloads or session notes. Digests are deduplicated to at most once per 24-hour interval after acceptance. Notifications start disabled.

1. Configure and test your WordPress mail transport.
2. Open Legacy checkout → Legacy checkout notifications & AI and enable the daily email digest. Enter an authorised recipient and a minimum affected-recording threshold.
3. Save workspace settings. Saving does not itself send an email. The scheduled digest runs through WordPress cron.
4. Check the mail status and verify actual inbox delivery. Transport acceptance alone does not prove delivery.

Summarise legacy checkout evidence

This preview summarises legacy checkout evidence only. It does not summarise ordinary click and scroll activity or the visual replay. A recording without checkout signals has no evidence for this tool.

The request sends fixed event categories, counts and relative timing. It excludes DOM content, page paths, notes, raw order IDs and customer details. Usage is charged to the connected API account; the plugin caps requests at 20 per UTC day.

Outputs must cite existing evidence references, but a cited interpretation can still be wrong. ClickClue does not automatically change a store or establish a diagnosis.

Requests use store:false. That setting is not a promise of zero provider retention; check your account’s data controls.

1. In Legacy checkout → Legacy checkout notifications & AI, enter your OpenAI API key and a Responses-compatible model. Enable manual AI summaries and save.
2. Open a recording with legacy checkout signals. Expand Legacy checkout AI summary and read the processing description. Choose Summarise checkout with OpenAI only when you want to send that evidence.
3. Review the interpretation and use its evidence buttons to inspect the corresponding signals.

Remove credentials

Remove OpenAI key disables further processing. Disable email to stop future digests. Keys and application passwords are encrypted with authenticated encryption and WordPress salts; changing those salts can require reconnecting.

Local recording in either edition

Choose the edition by its analysis and collaboration tools. More traffic does not require Pro. Sampling, retention, storage and your host determine how many recordings you can keep.

A recording lasts at most 30 minutes and holds at most 8 MiB of payloads. Capture pauses when the chosen storage budget is reached. These controls provide no hosting space and do not guarantee server capacity.

Choose a budget from measured recordings

Settings & privacy shows recent recording sizes and estimates how many additional recordings may fit in the remaining payload budget. It uses up to 200 recent recordings with no upload in the last minute; a small sample is provisional and visits can resume and grow.

Both editions start with seven-day retention and 250 MiB. An administrator can choose 1–365 days and 1–10,240 MiB after checking hosting space and justified retention. Updating preserves saved settings; it does not allocate server storage.

Lowering the payload budget does not delete recordings. Capture stays paused until space is available. Budgets exclude database indexes, backups and hosting logs. MiB means 1,048,576 bytes.

Preserved version 0.5.1 reference

Version 0.5.1 allowed Free 200 starts / 7 days / 50 MB and Pro 5,000 starts / 30 days / 500 MB. These figures describe that historical release only. Follow the current installation and consent guides for setup; notice and consent requirements changed in version 0.6.2.

Current installation steps · Current consent setup

Choose a useful sample

Estimate eligible, consenting visits and apply the sampling percentage. Sampled recordings are not the same as total traffic. A very low sample can miss less common interaction problems.

After a synthetic test at 100%, select a sampling rate your host and storage budget can sustain. Review measured recording capacity in Settings & privacy; estimates are not a traffic forecast.

Retention and deletion

Scheduled cleanup uses WordPress cron, with bounded cleanup during dashboard access and session creation. Configure a reliable cron trigger on low-traffic sites. Failed cleanup appears in health checks.

Deleting a recording removes its chunks, issue index, analytics metrics, session review state, notes, invitations and payment association together. Failed database transactions are reported for retry. Bulk deletion stops if progress cannot be confirmed.

The last 100 administrative audit entries, saved filter preferences and connection settings have a separate configuration lifecycle. Deactivation keeps stored data. The optional Delete data when uninstalling setting removes plugin tables and configuration.

Downloaded exports, backups and hosting logs are outside recording deletion. Plan their retention separately and take care not to restore previously deleted recordings from a backup.

From Tracewell to ClickClue

ClickClue is the new product name. Version 0.5.1 changes the visible name and documentation while retaining the original plugin folders, database keys, consent choices and integration identifiers for upgrade compatibility.

The upgrade packages retain the internal WordPress folders tracewell and tracewell-pro so replacement preserves the existing installation. Do not rename these folders or activate a second ClickClue copy alongside them.

Replace the installed packages

1. Back up your WordPress database and plugin files. Test on a staging copy first.
2. Obtain the current matched installer ZIPs through your release or account delivery. Use the Free package for your existing plugin directory; include Pro only if it is installed.
3. Upload the Free ZIP through Plugins → Add New Plugin → Upload Plugin. Review WordPress’s replacement comparison, then replace the existing plugin.
4. Replace Pro after Free. Keep both packages on the same release.
5. Clear page/asset caches. Check your settings and record a signed-out synthetic visit. Confirm masking, playback and the interactions you intend to review.

Updating to 0.9.0

Back up your site, update Free first and then matching Pro without uninstalling, and clear page/CDN caches. Keep the existing installation directory. Free0.9.0 works on its own; Pro0.9.0 requires Free0.9.0 or newer.

Existing settings, recordings, image approvals, legacy answers and saved funnels are migrated. New tables hold transport checkpoints, report membership and team/campaign records. Valid consent remains when scope is unchanged; enabled goals, campaigns and image approval changes require current positive consent. Previous refusals remain respected.

Use a signed-out test visit on your own theme and integrations to check masking, approved images, completion goals and withdrawal before relying on new reports.

Updating to 0.8.1

Back up your database and plugin files. Replace Free first, then matching Pro 0.8.1 if installed. Use the package for each existing plugin directory and do not uninstall to update. Clear page and asset caches, then check a signed-out sample visit.

Updating from 0.8.0 to 0.8.1 preserves valid existing replay choices, recordings and saved settings. Upgrading from a release before 0.8.0 still requires fresh positive replay consent; refusals remain respected.

This release includes local tutorial help and clearer approved-image privacy guidance. Recording stays paused or enabled according to your saved settings. On multisite, uninstall cleanup follows each site’s own saved deletion preference.

Compatibility introduced in 0.8.0

Version 0.8.0 introduced the approved-image option and a new replay notice. An upgrade from a release before 0.8.0 requires fresh positive replay consent, while existing refusals remain respected. Use the current matched installers and keep the existing plugin folders, recordings and settings; do not uninstall to update.

Both editions have no monthly recording quota. Free keeps replay, saved filters, bookmarks, notes and every privacy control. Pro adds analysis, visitor feedback and collaboration in the separate add-on.

Approved image capture starts off. Existing recordings do not gain images or new observations retrospectively. New optional feedback remains off until deliberately published. Existing survey settings are preserved; updating does not enroll a visitor or enable an external service.

Use fit-width or fit-window, zoom, the event timeline and fullscreen where supported. Review your actual pages with masked text and private regions before increasing recording.

Configure approved images

Compatibility introduced in 0.6.10

Version 0.6.10 clarified the review workspace and prepared verified Pro update delivery. Use the current matching packages above. Later versions remove its edition-based monthly allowances and share retention/storage controls across Free and Pro.

The dashboard opens on Recordings, with Pro page analysis under Heatmaps & forms. Checkout tools and their saved data are preserved under Legacy checkout; configured legacy email and AI services are not automatically disabled.

Both editions start new installations at seven-day retention and 250 MiB. Upgrading preserves your chosen settings and storage budget. Review Settings & privacy before increasing sampling, retention or storage.

The Pro updater supports verified ClickClue package delivery. Commercial activation and automatic delivery still need a connected service. If a rotated key or copied site prevents reconnecting, the administrator can confirm Forget local licence; it clears this installation’s saved licence details without releasing any remote seat. Installed Pro preview features remain usable.

Compatibility introduced in 0.6.9

Version 0.6.9 brings the 0.6.8 privacy and reliability fixes together with recovery when you return using the browser Back button while a recording start is still pending. Use the current matched installer ZIPs, replacing Free first, then Pro if installed. Do not uninstall or rename their folders.

Clear page/CDN caches and check a signed-out sample visit. Your recordings, settings, storage budgets, bookmarks and notes remain in place. Version 0.6.8 privacy choices stay valid; older positive choices may need a fresh consent decision.

On multisite, newly saved filters are separate for each site. Old filters did not record which site they belonged to, so they remain available on the main site; recreate any filters you need on secondary sites.

Compatibility introduced in 0.6.3

Version 0.6.3 improved setup and consent recovery. Install the current matching packages above, replacing Free first, then Pro, and clear page/CDN caches. Existing data, folder names, consent API aliases and storage budgets remain compatible.

Recording health now flags a missing published privacy policy. The test panel refreshes after a failed start followed by refusal, and identifies origin-verification failures. Test real capture on hosted staging: a browser-based WordPress sandbox can omit the Origin header. Keep origin protection enabled.

Compatibility introduced in 0.6.2

The 0.6.2 release introduced the notice and consent changes below. Install the current matching Free and Pro packages, replacing Free first, then Pro. Existing recordings, roles, notes and storage budgets remain compatible. Do not uninstall or rename folders.

Publish and select your store-specific privacy policy in WordPress Settings → Privacy. The built-in prompt now needs its published link. Clear page and CDN caches after updating: older loader revisions cannot start or upload recordings under the new notice.

Older positive browser choices require fresh permission; a valid refusal remains refused. New recordings have a notice revision, server receipt and fixed retention deadline. Existing records have no invented historical consent. See the consent guide for CMP revision handling and evidence.

Configure the notice and consent evidence

Compatibility introduced in 0.6.1

Version 0.6.1 used the same Free-first, then Pro replacement flow. Use the current matching packages above. The optional tutorial is available at the top of the dashboard after updating; it does not change capture settings, consent or connected services.

Existing 0.5.1 and 0.6.0 installations retain their recording identifiers, stored data, consent API aliases and chosen payload budget. Clear page caches after replacing the ZIPs. Tutorial checklist progress is local to the browser, account and edition; resetting it never deletes recordings.

Compatibility introduced in 0.6.0

Version 0.6.0 kept the same WordPress ZIP replacement flow: Free first, then Pro. Folders, database identifiers, existing replays, review notes and consent API aliases remain compatible. Follow the current replacement steps in this guide.

Storage budgets are preserved at the earlier edition’s effective ceiling. Review Settings & privacy before raising them. Older recordings keep their normal replay and position grid; new measured heatmap events enable the page overlay. The preview still has no connected payment or commercial delivery service.

Recover from an unsuccessful update

Pause capture if the updated site behaves unexpectedly. Keep a copy of the error and your previous package/database backup. Restore the matching plugin files from your known-good backup, then verify the database and settings on staging before resuming.

The preview supports manual ZIP updates. Follow the steps above while commercial automatic updates are unavailable.

No recording appears

1. Confirm recording is enabled and your sample rate is suitable. Clear page caches after changes.
2. Use a signed-out private window on an included page. Administrators and other signed-in users are excluded.
3. Grant consent. Check whether Do Not Track or Global Privacy Control is active; these choices are respected.
4. Open the test link from Settings & privacy and read its local status. Look for storage-budget, asset-loading or authorisation errors.
5. Confirm the test panel reports an upload. Back in WordPress, clear date/path/device filters and refresh the list.

The replay looks different

Keep text masking and private-region exclusions enabled. Use fit-width or fit-window, then adjust zoom. Approved public images can restore product context; everything outside the approved selection remains excluded.

Replay does not fetch missing external fonts, background images, video or embedded frames. Dynamic builders, animations and browser-specific styles can still differ. Reproduce the specific page state with synthetic content and include your theme, browser, viewport and reproduction steps in a support brief.

A checkout or payment signal is missing

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.

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.

Use the evidence carefully

After reviewing individual recordings, Pro can group repeated observations so you can inspect their supporting evidence together. In Whole-range reports, select a date range and Grouped clues, then run the local analysis. Read the population and any partial-coverage warning before choosing a replay.

Older recordings cannot be upgraded into missing observations. Review your Pro observation settings, current notice and consent, clear cached pages and record a new consenting test visit when coverage is missing. A clue is an observation for human review; it is not a diagnosis.

Use Save page investigation to open a report draft with its actual page, viewport, layout and report period. Nothing is saved until you choose Save report. Run it against retained data; saved filters do not preserve expired evidence.

Keep using Free

Free includes recording, playback, bookmarks, notes and saved recording filters. Neither edition has an edition-based recording-start quota. Sampling, retention, bounded payloads and your hosting capacity still govern capture.

Use the evidence carefully

From a saved investigation choose Compare this page, then select separate before and after UTC ranges and the relevant layout groups. Read the sample counts and missing coverage alongside each percentage. A layout or traffic change can alter the population.

Comparisons are descriptive. They do not establish causation, recovered revenue, conversion lift or that a fix worked for every visitor. Collect suitable new consenting visits if a period has insufficient observations; do not treat missing data as zero friction.

Use the evidence carefully

Collection evidence, discussions and live reports remain subject to deletion and retention. Authorised users can see shared notes; keep personal and payment information out. Private investigations start visible only to their owner and administrators.

1. In a replay, open Add to an investigation. Choose an existing collection or create a named private investigation with that replay.
2. Choose Open investigation and assign to set a next check, eligible WordPress account and work status. Deliberately choose team sharing if required. No link grants new access.
3. Use saved Investigation reports for a repeatable question; Review grouped clues connects the saved scope to group assignments and edit dates. Compare this page opens a descriptive comparison.
4. Administrators may opt into weekly or monthly Scheduled reports for an eligible WordPress account. The email contains only a private WordPress link, never replay, note or clue details. The live report checks access and current retention when opened. Saving does not send an email; disable the schedule to stop future emails.

Local guidance and optional commercial services

Optional Pro suggestions appear after relevant review actions. Dismiss a suggestion to keep it hidden in this browser for your site and WordPress account. Local guidance preferences can restore them. Intent, bounded local usage counts and dismissals are not sent to ClickClue, contain no note text or visitor identifiers and do not change recording settings. When browser storage is blocked, choices last only for the current visit.

The installed Pro add-on remains usable locally. A commercial licence provides entitled private delivery, updates and support when the commercial service is available. Reading this guide does not connect a licence, begin a subscription or enable email.