Description
See what happened at checkout. Frictions is a WooCommerce checkout session replay plugin for reviewing eligible visits inside WordPress. Watch protected checkout recordings, find observed errors and inspect the steps around them.
Supports Classic checkout and Checkout Blocks. No Frictions account, paid recording allowance or trial deadline.
Find the steps worth investigating
Review validation errors, field interactions and steps before a visit ended or a linked order was placed. Compare mobile/desktop visits. No observed order is not proof of abandonment.
Included in Free
- Protected visual replay: recorded page layout, supported styling, visible page text, selections, local images and fonts. Text-field masking is On by default.
- Find recordings: replay-reference search, sorting, quick date ranges and visible filters for device, browser, checkout layout, outcome, issue, duration and watch status.
- Review tools: bookmarks, watched state, page selection, bulk review actions and explanations of incomplete recordings.
- Local order shortcuts where a valid association exists.
- Setup and diagnostics, including a real-recording check and the latest receipt among retained shopper recordings.
- Controls: pause, delete, retention and storage budget.
New recordings preserve the checkout page’s supported visual appearance, including layout, colors, typography and approved local logo/product images. Visible page text, selected labels and checkbox/radio states remain visible in either masking mode. Text-field masking defaults On; owners can turn it Off to include ordinary typed values. Page text and selections may already contain personal information, even with text-field masking On. Payment regions, passwords, security fields and explicitly private regions stay protected in either mode; payment-like card and IBAN text is omitted. Replay is inert and makes no external asset requests. Visual capture requires CSS Typed OM computed sizing; other browsers use a labelled structural fallback. Unsupported assets, SVG/canvas, shadow DOM and some CSS effects may not reproduce; this is not pixel-perfect video. Older recordings remain structural because their original appearance was never captured.
Set up recording your way
Local image copies require PHP GD; without it, image regions stay masked while supported layout and local fonts remain available.
Recording starts disabled. Choose a mode and use Save and start recording, or save your setup without starting. No separate consent plugin is required for the built-in choices:
- Built-in prompt: visitors allow or decline; no other banner plugin needed.
- Consent integration: supported CookieYes, Cookiebot or custom bridge.
- Owner-controlled: explicitly acknowledged recording without asking first, with visitor opt-out.
Built-in controls cover Frictions only. Consent modes require affirmative permission. Owner-controlled is not visitor consent or a compliance exemption. Refusal, opt-out, GPC and Do Not Track stop capture in every mode. Existing settings are preserved.
A refusal saved in built-in or owner-controlled mode remains effective when switching between those two modes. Only the visitor’s explicit Allow recording or Enable recording action clears that refusal. Enabling owner-controlled recording does not grant built-in consent, and a built-in permission still requires renewal after a textbox-masking change.
Recording privacy is an optional inline link, off by default. Enable it in Settings or place [frictions_privacy_link] manually. Hiding it never grants consent: the built-in prompt still appears when needed. Owner-controlled panels never open automatically. Consent integrations keep their own controls.
Free and optional Pro
Separate Pro adds guided review, saved views, notes, developer briefs and opt-in WordPress-mail notifications. First licence activation is required; activated tools continue after ordinary support expiry.
Fictional previews unlock nothing and make no Frictions request. Hide sidebar examples with Pro previews. Both editions retain safety limits.
Privacy and local storage
Replay stays in private WordPress tables: random IDs, protected page structure and appearance, visible page text and selections, local asset copies, coarse device/browser categories, events/timing and eligible order associations. The supplied recorder omits ordinary textbox values when masking is On. A modified browser client can mislabel text as visible content; the server cannot establish its origin or guarantee removal of all personal data. Data is compressed, not database-encrypted. Secure hosting, access and backups; no anonymity or compliance guarantee.
Defaults: 7 days, 256 MiB; configurable 1–365 days/16–10,240 MiB. Capture pauses at the budget; bookmarks expire. Each recording is limited to 32 MiB uncompressed, one hour active and 30 minutes idle. These limits do not measure total hosting space.
Order associations expire within the selected retention from their creation and never later than their replay. Shorter retention caps existing replay and association expiry; increasing it does not extend them. Upgrade also caps older associations. Separate short-lived replay-deletion safeguards prevent delayed uploads from restoring removed recordings.
Order accepted means WooCommerce accepted an order, not that money was collected. Order marked completed reflects WooCommerce’s completed status, not independent settlement proof. Payment confirmed reflects a WooCommerce payment-complete signal. Later eligible signals update retained, associated recordings; historical outcomes are not backfilled.
Withdrawal/opt-out stops capture and requests deletion, with retries on other site pages without recording them. Completion needs the matching WooCommerce session and a request reaching the store; offline visits, cleared storage or ended sessions cannot guarantee it. Accepted withdrawal revokes access before deletion; failures remain retryable.
Expired replays are unavailable. Cleanup and Action Scheduler order delivery need working workers. Backups/exports are not erased. WordPress privacy tools cover associated accounts/orders, including registered abandoned checkouts; anonymous unassociated visits need a replay reference.
WordPress privacy exports list associated replay references in the native report and include one frictions/<recording-id>.json file per retained recording inside the download ZIP. Replay data is written incrementally instead of assembling all decoded chunks in memory. Pending delivery and related review data remain included. If retained data changes or export storage fails, restart the export; an incomplete download is not reported as successful.
Full privacy, browser-storage and access details: bundled privacy-and-controls.txt.
Optional external service
Setup and Settings → Communication offer separate unchecked opt-ins, independent of recording:
- Compatibility: domain, WordPress/WooCommerce/PHP/Frictions Free versions and language, on save and at most weekly.
- Email: chosen email for Frictions tips/releases; email-only signup omits installation/domain details. New subscriptions require confirmation. Articles/offers are separate preferences; existing preferences are preserved.
Endpoint: https://frictions.com/newsletter-api/v1/frictions-welcome/
Requests include a random connection ID, credential and consent version; the service receives times/network address. No replay, checkout, order, customer data or plugin list is sent. Viewing/skipping or choosing neither sends nothing. Check status requests an update, not delivery proof.
Stop in Communication; retry unconfirmed withdrawal. Stopping a signup created here cancels it or unsubscribes all its Frictions newsletter topics. Existing subscriptions need their own unsubscribe link; account mail is unaffected. Uninstall makes no remote request: stop first or unsubscribe by email.
Compatibility details expire after 90 days without reports. Further retention details: privacy-and-controls.txt and privacy policy. Service terms. Consent providers may contact their own services.
Related plugins from Plugins.shop
Optional tools from the same publisher:
- Cartdini — Add checkout questions and keep answers with the order.
- OrderFloor — Set minimum orders, quantity limits and pack rules with shopper notices.
- Logged.ai — Review supported site/WooCommerce changes when investigating checkout problems.
Separate plugins, not requirements or automatic integrations. Check each listing’s features and requirements.
Source and builds
PHP: root and includes/. Browser scripts: assets/. TypeScript, instructions and pinned lockfile: source/. With Node 24.21.0, run npm ci --ignore-scripts then npm run build in source/ to reproduce the three bundles. No remote executable-code loader.
Installation
- Use PHP 8.1 or later and WordPress 7.0 or later. Activate WooCommerce 11.0 or later, then Frictions. Your chosen WooCommerce release may require newer WordPress or PHP versions.
- Review retention/storage, save a recording mode, then deliberately enable capture.
- Run Verify a real recording in a separate shopper browser; it does not override permission.
- Test refusal, withdrawal and checkout/theme/gateway/cache compatibility. Check scheduling and hosting capacity.
Samples are fictional. Administrators/non-production sites are excluded by default; development needs explicit opt-in. Network activation is unsupported.
Back up and replace files without uninstalling to preserve settings. Update Free first; separate Pro workflows require their own compatibility check. Former hosted 0.2.0 data/subscriptions need separate handling.
FAQ
Does PHP 8.1 compatibility mean it is recommended for a new store?
No. Compatibility requirements are separate from upstream security maintenance. Use an actively maintained PHP, WordPress and WooCommerce release supported by your host and other plugins. PHP 8.1 is end-of-life upstream; compatibility does not provide security updates or certify every theme, gateway or version combination.
Is CookieYes required?
No. The built-in prompt needs neither a banner plugin nor hosted account. Standalone CookieYes 3.5.8 needs getCkyConsent(), completed action and analytics consent; Cookiebot needs statistics consent. Older integrations need the required API or custom bridge (default denied). A banner or Google Consent Mode alone is not permission.
Does it record the whole website?
No. Capture covers the supported same-site permalink checkout, excluding order-pay, thank-you, account, other pages and off-site payments. Plain ?page_id= checkout URLs and third-party checkout builders are unsupported. The privacy-only helper does not record other pages.
Why does a recording say No order observed?
Association needs proof on that exact Classic/Blocks request, not a shared account/session. Missing proof, drafts and expired/revoked recordings are not guessed. Guest-to-login changes fail closed. Queued outcomes need Action Scheduler; this label alone does not mean checkout failed.
What happens on deactivation or uninstall?
Deactivation stops recording and jobs; unexpired data remains. Cleanup cannot run while inactive: delete beforehand if needed. Reactivation resumes cleanup and can restore previously enabled recording on the same site when its saved setup and checks still pass. Previously paused sites stay paused. Changed or incomplete setups need review before recording resumes. Free uninstall removes participating sites’ local/registered Pro data; networks above 1,000 sites need administrator handling. Pro-only uninstall keeps Free recordings. No remote deletion, billing cancellation or backup erasure occurs.
Screenshots








Changelog
1.2.20
- Improve bounded final-upload packing for queued checkout snapshots across reloads and navigation.
- Send large visual batches earlier while the uploader is idle, without increasing snapshot sampling or bypassing retry and backpressure safeguards.
- Preserve existing consent, text masking, payment protection and delivery limits. Missing data is not marked complete.
- Match the separate Pro companion version; existing recordings and settings remain unchanged.
1.2.19
- Reuse validated earlier snapshots within a bounded final upload so queued checkout changes do not repeat the same large appearance difference after a reload.
- Validate and reconcile dependent final chunks in order, preserving existing upload limits, text masking, withdrawal and truthful incomplete coverage.
- Pair with the separate Pro update that explains when a developer brief’s recording was deleted or expired.
1.2.18
- Preserve saved visitor refusals when switching between built-in and owner-controlled recording, without carrying permission into the built-in prompt.
- Write associated replay data incrementally into WordPress privacy-export ZIPs, preserving chunks, pending delivery and related review data without loading every decoded chunk at once.
- Close unused denied-response bodies without changing recording eligibility, retry rules or delivery limits.
- Correct verification instructions and complete the bundled release history.
- Pair with the separate Pro update that removes obsolete saved-view success messages when a new edit starts.
1.2.17
- Retry a bounded snapshot-difference representation when its compressed final upload fits but the smaller uncompressed full representation does not. This preserves eligible checkout endings without raising delivery limits.
- Keep fine style changes compact before falling back to whole style arrays, while preserving existing per-snapshot and total final-upload limits.
- Share the bounded final-upload operation budget across queued chunks, preserving the stop event when equivalent compact snapshot changes fit the existing limits.
- Keep validated final snapshot changes compact when delayed uploads must wait for an earlier chunk. Missing data remains unconfirmed; delivery limits and privacy protections are unchanged.
- Clarify that a saved recording preference does not override browser privacy signals or site recording checks.
- Pair with the separate Pro update for Saved views status messages and Investigations error recovery. Existing privacy settings remain unchanged.
1.2.16
- Keep unchanged style entries when Blocks checkout inserts or changes styles, reducing final-upload size on early departures and reloads.
- Retain bounded snapshot differences when many checkout styles or elements change, without retransmitting unchanged appearance assets in the final upload.
- Preserve the same bounded differences during server-side validation and final-data storage; missing data still cannot be marked complete.
- Use the registered WooCommerce Blocks checkout store instead of its asynchronous global store bridge.
- Correct the bundled privacy guide’s outdated Pro version information. Consent, masking, payment protection and delivery limits remain unchanged.
1.2.15
- Keep exit updates compact against acknowledged snapshots and send foreground activity more frequently instead of relying on large ordinary uploads during navigation.
- Retain validated final snapshot differences without storing overwritten patch values or expanding the pending delivery budget.
- Track explicitly observed quiet intervals for playback and inactivity skipping; missing or historical coverage stays unconfirmed.
- Reconcile repeated Blocks validation signals and declare the correct WooCommerce Blocks dependency.
- Allow setup changes to be saved without starting recording.
1.2.14
- Attempt bounded final checkout delivery on normal navigation with authenticated, sequence-checked segment finalization; unreceived data stays unconfirmed.
- Distinguish confirmed segment delivery, unconfirmed endings, inactivity and navigation gaps without treating an accepted order as complete footage.
- Avoid false Blocks validation signals from background validity checks; keep visible checkout errors.
- Show unavailable recording status instead of an incorrect paused state when settings cannot load.
- Keep existing privacy choices, masking and immediate withdrawal protections; update the bundled setup guidance.
1.2.13
- Lower the PHP requirement to 8.1 after compatibility testing. WordPress 7.0 and WooCommerce 11.0 minimums remain unchanged; individual WooCommerce releases retain their own requirements.
- Preserve recording, masking, privacy choices, retention and existing data. Current screenshots retain their actual 1.2.12 capture labels.
1.2.12
- Refresh the directory screenshots and bundled Pro examples with genuine current-version interface captures and fictional data.
- Align screenshot captions and example descriptions with the shown workflows. Recording, privacy choices, retention and replay behavior are unchanged from 1.2.11.
1.2.11
- Apply selected retention to order associations, reconcile older expiry and hide expired order-to-replay links.
- Recognize later WooCommerce completion and payment-complete signals without treating cash-on-delivery processing as collected payment.
- Validate stored event payloads, private verification state and optional theme font data before use.
- Clarify textbox masking’s client-side trust boundary while retaining visible text, selections and protected payment regions.
1.2.10
- Open replays at the top of the workspace so the heading and playback controls are visible, including when choosing Next replay.
- Keep Back to list returning to the previous list position and make unavailable-replay messages visible.
1.2.9
- Preserve appropriate recording state on same-site reactivation and avoid unnecessary pauses when recording setup is unchanged.
- Clearly explain unavailable replays and retain existing recordings, masking choices and playback preferences.
- Improve replay loading and fullscreen feedback; remove unsupported security-policy warnings without relaxing replay isolation.
1.2.8
- Refresh the bundled Pro examples and directory screenshots with genuine captures and matching version-labelled captions.
- Clarify which review tools are included in Free and which require the separate Pro add-on.
- Keep capture, masking, saved settings and replay playback unchanged from 1.2.7.
1.2.7
- Add replay-reference search, explicit sorting, quick date ranges and removable active-filter chips.
- Add page selection and bulk watched/bookmark actions with atomic expiry and revocation checks.
- Show retained shopper receipt time and explain incomplete recordings without assuming checkout abandonment or payment failure.
- Keep recording, privacy, masking and browser playback choices unchanged.
1.2.6
- Enable Skip inactivity by default and remember explicit On or Off choices in this browser for each site and administrator account.
- Preserve full-screen activation setup, saved recording choices and the paint-safe replay player.
1.2.5
- Fix white flashing during replay frame changes without relaxing the replay sandbox.
- Place Evidence, Team notes and Developer brief below the player, with a taller checkout viewing area.
- Preserve saved recording and masking choices and existing recordings.
1.2.4
- Wait for replay data and the checkout frame before starting or resuming the playback clock.
- Move the replay cursor without repeatedly reloading the page, and keep the current frame visible while the next frame loads.
- Fix Team notes preview tabs overlapping the replay controls on desktop.
- Preserve saved recording and masking choices, existing recordings and replay isolation.
1.2.3
- Batch ordinary checkout activity every 15 seconds to reduce repeated upload requests.
- Pace queued uploads after temporary host throttling instead of sending a rapid catch-up burst. Respect Retry-After and preserve bounded retries.
- Keep saved recording modes, masking choices, privacy-link settings and existing recordings unchanged.
1.2.2
- Recover from temporary recording-start failures with bounded retries and request timeouts instead of locking the tab out.
- Refresh recording lists when returning to the page and provide an explicit refresh action.
- Simplify first setup and add default-On text-field masking controls. Payment and security fields remain protected when masking is Off.
1.2.1
- Remove the synthetic setup demonstration. Review your recording mode, then verify a real logged-out shopper visit.
- Retry temporary upload throttling without discarding the rejected batch. Respect Retry-After and retain bounded memory-only buffering.
- Keep permanent storage limits, privacy controls and administrator exclusions in place. Older recordings remain structural.
1.2.0
- New recordings preserve supported checkout-page appearance with approved public text and local image/font copies.
- Keep customer values and payment regions masked, and replay isolated from scripts and external requests.
- Preserve older structural recordings and explicitly label visual fallbacks.
- Retain default-Off privacy-link choices and existing recording/withdrawal controls.
1.1.8
- Replace floating privacy controls with an inline link and expandable choices.
- Add an automatic-link visibility setting and manual-placement shortcode.
- Preserve permission, refusal, withdrawal and the 1.1.7 security protections.
Full release history: bundled changelog.txt.
