| 开发者 | whoisakash |
|---|---|
| 更新时间 | 2026年10月25日 16:28 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
wp statbird rebuild, wp statbird score, wp statbird status.statbird_segment_changed, statbird_scored, statbird_snapshot_built, statbird_customer_refreshed.statbird_counted_statuses (which order statuses count as purchases).No. Nothing runs on your shop's pages. Reading orders and scoring happen in the background with WooCommerce's own task scheduler, in small batches.
Processing, completed and refunded orders. Refunds are subtracted, and an order that was refunded in full does not count as a purchase. Cancelled, failed and pending orders are ignored. Developers can change the list with the statbird_counted_statuses filter.
Guests are matched by email. If a guest later creates an account with the same email, their guest orders join their account.
Churn risk is the chance a customer does not order in the next 90 days. With enough history, a small model trained on your store decides it, using recency, frequency, spend and each customer's buying rhythm. Otherwise a simple rule compares how long it has been with their usual gap between orders. The Help screen explains every number.
No. AI is an optional extra. Groups, risk, value, cohorts, trends, patterns, the order card and exports all work without it.
Statbird's analysis stays on your site. It adds itself to WordPress's personal data export and erase tools, and removes all of its data when you delete the plugin. See "External services" for exactly what the optional AI features send.