Install. Connect consent.
Check your first recording.

Capture covers the configured checkout only. It excludes order-pay, confirmation, account and off-site payment pages. Other checkout builders, plain ?page_id= checkout URLs and network activation are unsupported.

Test your theme, gateways, consent banner and cache/security configuration before recording shopper visits. Read the dated release-test evidence.

Select Other banner — developer setup. Connect the following function to your consent manager’s confirmed analytics choice and change callbacks. Pass true only for an affirmative analytics choice; pass false for refusal, withdrawal or an unknown choice.

function syncFrictionsConsent(analyticsAllowed) {
  const granted = analyticsAllowed === true;
  window.FrictionsConsent = { granted };
  window.dispatchEvent(new CustomEvent('frictions:consent', {
    detail: { granted }
  }));
}

This is an integration function, not a complete consent banner. Your developer must call it with the real choice on page load and whenever that choice changes. Never grant consent by default. Setting the object also makes the choice available if the recorder loads after the callback.

Withdrawal stops capture and requests deletion of that visit’s stored replay. It does not restart on the same loaded page; a later visit can become eligible after a new affirmative choice. The deletion request must reach your store to complete.

Enabled means eligible future visits may be captured. Clear list filters, then use the first-recording check. Make sure the shopper is logged out of WordPress, has a nonempty cart, reaches the configured checkout and makes an affirmative analytics choice. Browser privacy signals, missing consent, an unsupported checkout or a full storage budget can prevent capture.

The browser reported a choice, but stored replay data has not been confirmed. Keep checkout open, review Frictions diagnostics and check whether cache or security rules block its same-site WordPress requests. Do not cache checkout or authenticated admin responses. If the check expires, start a fresh check.

Non-production environments are excluded by default. A developer can explicitly enable development recording with define('FRICTIONS_DEVELOPMENT', true); in that environment’s WordPress configuration. Resulting recordings are marked as test traffic. Consent, supported checkout and access protections still apply; use isolated test payments and mail.

This is expected. The player reconstructs approved geometry, safe labels and timing. It excludes product content, arbitrary page text, images, entered values and payment frames. It is a structural replay, not a video or a copy of your theme.

Check filters and retention first. Expired, deleted and withdrawn recordings are unavailable. Order association also requires an unambiguous eligible WooCommerce session; Frictions does not guess between ambiguous tabs, drafts or unsupported visits.

Check that both Free and Pro are active on this individual site and show compatible versions: Free 1.1.3 and Pro 1.1.2. Open Pro licence and complete this site’s first valid activation; existing connections can use Check licence now after upgrading. Some actions require management access. Administrators receive separate frictions_view and frictions_manage capabilities; delegate them deliberately through your usual role-management process.

If Frictions reports unreadable saved settings, review the visible values and consent integration, then explicitly save the form. Capture uses paused defaults while that stored configuration is unreadable. A failed save stays an error; keep your draft and retry after the storage problem is resolved. Do not assume consent or recording was changed from a button click alone.

Recording deletion, consent withdrawal, expiry or staff access may have changed while the report was loading. Reload the investigation to get a fresh, authorized result. A busy or changing store may need another attempt; Frictions does not keep retrying indefinitely.

Keep Free and Pro compatible and check the displayed compatibility or package error. Download the current pair from the official download page and your eligible account. If WordPress deactivated Pro before rejecting the update, reactivate the retained Pro files, then retry with the supported pair. Do not uninstall to repair an update.

In Frictions Settings, choose Download diagnostics. It provides version, checkout, consent and storage checks without replay contents or credentials. Open a support request with the issue, reproduction steps and relevant versions. Never send passwords, payment details or shopper recordings.

Use the labelled Pro previews and relevant suggestions inside Frictions to see genuine example screens with fictional data, compare what Free includes and what Pro adds, and choose a task to resume after installation and a valid first activation. Viewing a preview does not enable recording, sending or Pro access. Hide or restore suggestions and preview navigation in the browser-local discovery preferences.

The field guide covers the current recorder and Pro workflows. Preview examples never replace your own checkout and consent test.

Updating from 0.4.2? That release could pause recording during an upgrade. Versions 0.4.3 and later preserve the current recording and setup choices. Check Recording status after updating; resume only if you intend to record and consent is configured. An update does not turn paused recording on.

Deactivation preserves local data. Uninstalling Free permanently removes its local recordings, settings and registered Pro data. Uninstalling Pro alone removes Pro workflow data while leaving Free recordings available. Neither action cancels billing or erases independent hosting backups or exported files.

The former 0.2.0 architecture used a hosted service. Moving to the local edition does not automatically import, cancel or erase historical remote recordings or subscriptions; handle those separately.