| 开发者 | userelements |
|---|---|
| 更新时间 | 2026年6月24日 15:46 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
wp_mail() — the same delivery path WooCommerce uses — so they work with any SMTP or transactional email plugin you already have.
Variable fallbacks prevent awkward blanks: {{customer.first_name|there}} outputs "there" when a guest has no stored name.
Audience conditions — send to the right customers
Avoid sending every message to everyone. Add conditions to each automation:
CartCue is a WooCommerce abandoned cart recovery and sales automation plugin. It lets you create automated plays triggered by WooCommerce events — abandoned carts, paid orders, failed payments, new customers, inactive customers, and more — and takes actions like sending a personalized email, generating a coupon, or changing an order status.
When a shopper enters their email address at checkout and leaves before completing the order, CartCue captures the cart and schedules a recovery email. You can send the email immediately or after a delay (e.g., 1 hour, 24 hours). The email includes the cart contents, total, and a one-click recovery link that restores their cart automatically.
Yes. CartCue recovers guest carts as long as the shopper has entered their email address at checkout. You can also configure plays to send only to registered customers if you prefer.
No. The free version is fully functional with no subscription or credit card required. CartCue Pro is a per-site purchase, not a monthly recurring fee that scales with your revenue or contact count.
Yes. CartCue sends email through wp_mail(), the standard WordPress email function. It is compatible with WP Mail SMTP, Postmark, Mailgun, SendGrid, FluentSMTP, and any other SMTP or transactional email plugin.
Yes. CartCue is fully compatible with WooCommerce High-Performance Order Storage (HPOS / custom order tables).
Yes. CartCue emails support variables for customer first name, last name, email, order number, order total, order items, cart total, cart recovery link, coupon code, store name, and store URL. You can use fallback values for missing data — for example {{customer.first_name|there}} outputs "there" for guests with no stored name.
Yes. The free version includes a Create Coupon action that creates a coupon with your chosen discount and inserts it into the email. For a unique, one-time coupon code generated per customer, upgrade to CartCue Pro.
CartCue is lighter, faster to set up, and does not require an external CRM account or a monthly subscription. It is focused on WooCommerce-native automations that store owners need most: abandoned cart recovery, win-back, post-purchase follow-ups, and payment recovery. Advanced marketing CRM features are not included by design.
Yes. Each CartCue play supports follow-up steps with individual time delays. The free version includes up to 2 follow-up steps per play. CartCue Pro supports unlimited steps.
Yes. CartCue embeds a tracking pixel for opens and wraps links for click tracking. Open rate, click rate, and per-play performance are visible in the Reports dashboard.
Yes. The Customer Win-Back trigger fires daily for registered customers who have not placed an order in a set number of days (configurable). You can target customers inactive for 30, 60, 90 days or any value you choose.
Yes. All automation logs, cart data, email tracking, and customer consent records are stored in your WordPress database. No customer data is sent to CartCue or any external server.
The free version works with standard WooCommerce orders. CartCue Pro adds dedicated triggers for WooCommerce Subscriptions renewal, cancellation, pause, and reactivation events.
Log export (CSV) is available in CartCue Pro. The free version provides in-dashboard reporting with the activity log view.
CartCue requires WooCommerce 8.0 or higher. It has been tested up to WooCommerce 9.9.
apCollectInlineActions is exposed globally and the email builder syncs before collecting inline actions for the test payload.create_shared_coupon, separate from the Pro unique-coupon action (create_coupon), preventing schema collisions when license state changes; legacy saves with create_coupon still resolve correctly.wp_unslash() that could strip intentional backslashes./cartcue-track/click/) returning 404 when rewrite rules were stale after install or update — rules now register before flush on activation, auto-flush on frontend loads via a versioned option, and a URI fallback handler records clicks even before rewrites refresh.status = 0) back to opted-in — grant() now blocks historical/migration sources from resurrecting suppressed addresses; checkout opt-in can still restore consent.id="ap-test-btn" in the unified play editor — header and live-preview send buttons no longer collide; test-send handlers use a shared class.renderStylesPanel reference error.admin.js and audience-estimate.js on the same container.admin.js bindings.updateBlockPreview() was targeting the removed card layout and skipped persist() on most edits.wp_unslash() after the actions array is already unslashed; corrupted builder JSON now shows an admin error instead of silently saving empty content.{{customer.first_name|there}} outputs fallback when variable is empty.