| 开发者 | cartrevival |
|---|---|
| 更新时间 | 2026年11月12日 03:27 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
navigator.sendBeacon(), so nothing ever blocks navigationadmin-ajax.php anywherecartrevival folder to /wp-content/plugins/, or install through Plugins → Add New.No. The always-loaded core is about 2 KB gzipped (2.2 KB measured), deferred and never render-blocking. Exit intent, field capture, push opt-in and tab alerts live in separate small modules that download only at the moment their trigger fires. Tracking beacons are fire-and-forget, so the browser never waits on them, and a page view with an empty cart performs no database writes at all. A build-time size gate fails any release whose core exceeds 4 KB, so this number cannot quietly rot.
Yes. Anonymous shoppers are tracked from their first add-to-cart using a first-party cookie and WooCommerce's own session. As soon as they type an email or phone number at checkout, that cart becomes recoverable.
After a period of inactivity you choose, from 15 to 240 minutes, defaulting to 60. Activity means a page view, a cart change or typing at checkout. Each cart schedules its own check, so nothing scans your database on a timer.
CartRevival matches the order back to the cart by session, cookie, customer account, email or phone, cancels any pending reminders, and records the revenue. A cart that converts without a reminder is never counted as recovered — your recovery numbers stay honest.
No. Every reminder reserves a unique slot in the send log before it is scheduled, and the send job claims that slot atomically. Two workers racing on the same cart cannot both send.
Yes. Both the classic shortcode checkout and the newer block checkout are supported, including capturing details entered in block checkout fields.
Yes. HPOS compatibility is declared, and CartRevival works with it on or off.
Yes, including exit intent. CartRevival detects an intent to leave on touch devices through scroll-up velocity and the back gesture.
CartRevival registers with WordPress's personal data exporter and eraser, includes a one-click unsubscribe link in every message, and lets you disable IP address and page URL collection entirely. Phone numbers can require explicit consent. Nothing is deleted on uninstall unless you opt in.
Yes, fully. The plugin's own admin screens and messages are translated, and recovery emails follow the shopper's language, not your site's: someone browsing in Arabic gets an entirely Arabic email, right-to-left, including the button and the footer. You can also write your own Arabic version of each recovery step. An email is never sent half in one language and half in another.
No. The free plugin has no cart quota, no registration, no account and no licence check. It never contacts a licensing server to decide what you are allowed to do. The optional PRO add-on is sold separately and is not required for anything described here.
Yes. The capture popups ship their own self-contained styles, and the plugin adds nothing to your theme's templates. Both the classic shortcode checkout and the WooCommerce block checkout are supported.
Nothing is deleted unless you tick the box for it under Settings. Delete the plugin with that box unticked and your carts and history stay in the database; tick it first and everything the plugin created is removed cleanly on uninstall.
Yes. CartRevival never blocks a cached page. If a cache serves a stale security token, the script quietly fetches a fresh one and retries.
WhatsApp reminders are free. Connect your WhatsApp number at 6rsh.com (free), then pick an approved message template under CartRevival → Recovery → WhatsApp. If the 6rsh WooCommerce plugin is already connected on your site, CartRevival uses that connection automatically.
cartrevival_carts_table_columns, cartrevival_carts_table_column, cartrevival_carts_query_orderby).