Linux 软件免费装
Banner图

Octopush SMS Automation & Cart Recovery

开发者 octopush
hamzachaudhry
更新时间 2026年4月3日 20:44
PHP版本: 7.4 及以上
WordPress版本: 6.9
版权: GPLv2 or later
版权网址: 版权信息

标签

marketing woocommerce abandoned cart sms octopush

下载

1.1.8 1.1.10 1.1.11 1.1.5 1.1.6 1.1.7 1.1.9

详情介绍:

This is the official WordPress plugin of Octopush (https://octopush.com/). It is developed and owned by Octopush and connects your WooCommerce store to the Octopush SMS service. It provides SMS automation, contact management, campaigns, abandoned cart recovery with popup and inline capture, and an optional live chat widget. Requirements Features Privacy & data The plugin sends data to Octopush (phone numbers, names, messages) when you send SMS or sync contacts. Abandoned cart capture is optional and configurable. Document your use of Octopush and this plugin in your privacy policy. Do not track users without consent; configuring and using the plugin implies consent for the Octopush service.

安装:

  1. Install and activate WooCommerce if you plan to use SMS automation or abandoned carts.
  2. Upload the plugin files to /wp-content/plugins/octopush-sms-automation-cart-recovery/ or install through the WordPress Plugins screen.
  3. Activate the plugin through the Plugins screen.
  4. Go to Octopush SMS Automation & Cart Recovery in the admin menu and open Settings. Enter your Octopush API key, sender, and other credentials. Save and test the connection.
  5. Configure SMS templates (Abandoned Carts, SMS Toward Customers, SMS Toward Shop Owner) and optional popup/inline customization under Octopush SMS Automation & Cart Recovery -> SMS Automation.

升级注意事项:

1.1.7 Developer credit and WordPress.org contributor listing update. 1.1.6 Listing text refresh: improved plugin short description for better storefront visibility. 1.1.5 Readme: corrected Octopush terms of service URL in External services. 1.1.4 WordPress.org review: main filename aligned with slug; readme documents Octopush central cron external service. 1.1.3 Rebrand release: new plugin name, slug, and text domain. 1.1.2 Abandoned cart SMS for France: mandatory STOP clause appended for +33 numbers. 1.1.1 Maintenance release. 1.1.0 Packaging cleanup: no .DS_Store or other dotfiles in the plugin ZIP; see PACKAGING.txt before uploading to WordPress.org or Plugin Check. 1.0.10 Internal cleanup for release packaging (remove hidden files such as .DS_Store). 1.0.9 Larger country dropdown arrow in abandoned cart and Store Owner Phone field. 1.0.8 Store Owner Phone dropdown in Settings now shows country flags in the list. 1.0.7 Store Owner Phone in Settings now has the same searchable country dropdown. Abandoned cart phone field improvements. 1.0.6 Settings: version moved above Connection Status & Balance. Phone field UI improvements. 1.0.5 Country dropdown in abandoned cart popup and inline field now shows country names and is searchable by name or code. 1.0.4 Plugin version is now shown on the Settings page for easier support and updates. 1.0.3 Automatically enable central cron on activation when available, and improve cleanup of non-abandoned carts after checkout. 1.0.2 Internal improvements and cron reliability fixes. 1.0.1 Initial release. Requires WordPress 5.8+, PHP 7.4+, and WooCommerce for full functionality.

常见问题:

Do I need an Octopush account?

Yes. You need an Octopush account and API credentials to send SMS. The plugin acts as an interface to the Octopush service.

Is abandoned cart capture optional?

Yes. You can enable or disable the time-based popup and the inline name/phone field on the cart page independently. Both are configurable under SMS Automation → Abandoned Carts → Popup & Inline Capture Customization.

How do abandoned cart alerts run? Do I need to set up cron?

Abandoned cart detection and SMS alerts run only when the external cron URL is called. There is no WordPress cron or traffic-based trigger. You must call the secret URL (shown in SMS Automation → Abandoned Carts under "External cron (required for automatic alerts)") every 5 minutes from your server’s crontab, your host’s cron tool, or a free service like cron-job.org. The URL is unique to your site and must be kept secret. Until this is set up, use the "Run abandoned cart check now" button for manual runs.

Where are contacts stored?

Contacts are stored in your WordPress database (custom table for Woo contacts). The plugin can sync WooCommerce-related contacts to Octopush when you link a list and run sync.

How does it scale for large stores?

For most stores you can use the defaults, but there are filters to safely tune performance, with enterprise-friendly defaults already applied:

  • Woo contacts loaded at once – filter octopush_pro_get_woo_contacts_limit (default 100000). Increase or decrease depending on your memory budget.
  • Backfill from existing orders – filter octopush_pro_backfill_woo_orders_limit (default 100000). Controls how many historic orders are scanned on first backfill.
  • Sync chunk size – filter octopush_pro_sync_chunk_size (default 100). Controls how many contacts are sent to Octopush per API call.
  • Abandoned cart contacts per page (admin) – filter octopush_pro_admin_abandoned_contacts_per_page (default 1000). Controls how many contacts are shown per page in the dashboard.
  • Reports rows per page – filter octopush_pro_reports_per_page (default 100). Controls how many log entries are shown per page.
  • Abandoned capture cooldown – filter octopush_pro_abandoned_capture_cooldown (default 5 seconds between captures per session). You can tune this for stricter anti‑spam.
  • Log & cart retention – filters octopush_pro_log_retention_days (default 365) and octopush_pro_cart_retention_days (default 730). Raise, lower, or disable (set to 0) depending on your compliance and storage needs.
Recommended starting points:
  • Small stores (≤10k customers) – keep defaults or modestly increase limits.
  • Medium stores (~10k–100k customers) – Woo contacts/backfill limits around 50_000, sync chunk size 50–100, reports 50–100 rows per page.
  • Large/enterprise (100k+ customers) – Woo contacts/backfill limits 100_000+ (or use batched exports), sync chunk size 100–250, and longer retention (365+ days) combined with external log archiving.

更新日志:

1.1.7 1.1.6 1.1.5 1.1.4 1.1.3 1.1.2 1.1.1 1.1.0 1.0.10 1.0.9 1.0.8 1.0.7 1.0.6 1.0.5 1.0.4 1.0.3 1.0.2 1.0.1