| 开发者 | pingbell |
|---|---|
| 更新时间 | 2026年9月26日 08:57 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
order.created) — the order count and the revenue.action.wc_pingbell_new_customer_order) — an order from someone who had not bought before. WooCommerce has no event for this, so nothing in your store fires it: PingBell tells a first order from a repeat one on its own side, from the orders it receives, and the counter fills from there. It would carry the order's id and nothing else.action.woocommerce_order_status_completed).action.woocommerce_add_to_cart.
External service
This plugin talks to the PingBell service (https://pingbell.io — terms, privacy). What goes where:
X-WC-Webhook-Signature), through its own webhook mechanism. This is WooCommerce's standard order webhook, and WooCommerce puts the whole order in it — including the customer's name, email and billing and shipping addresses. The plugin does not choose or trim that content. The new-customer and completed-order webhooks carry only the order's id. Older manual API-key connections send to https://app.pingbell.io. While the PingBell page is open in your admin, your server asks https://my.pingbell.io for the board and its numbers, and pairs or unpairs a screen when you ask it to.Not to design your board: that works the moment you activate the plugin, with sample numbers. Signing in, which creates a free account for you, is what brings your real numbers in and rings your phone. Putting the board on a TV, or sharing it by link, takes a plan.
The board in your WordPress admin is free, with no time limit, and so is connecting your store. A free account holds one board and carries a small PingBell mark. Showing a board on a TV or any other screen takes a plan, and the first time you subscribe there is a 14-day free trial.
No. The plugin does nothing when an order is placed, paid or changed. WooCommerce sends the order to PingBell in the background, the way it sends any webhook, and PingBell does the counting. The one time your orders are read is when you connect, to send your last 30 days and your lifetime totals, and that happens in the background in small batches. On a very large store it takes a while, and the Screens & connect tab shows how far it has got.
Nothing until you sign in. Then your store name, currency and timezone, your design, and a one-time summary of your history as totals, with no customer's name, email or address in it. After that, WooCommerce sends each new order through its standard order webhook, which does carry the customer's details, as it does for any webhook. See External service above.
Nothing in your store fires a "first order" event. PingBell tells a first order from a repeat one on its own side, from the orders it receives, and the counter fills as they come in.
PingBell stops trusting the store, the plugin removes the webhooks it created, and your boards, counters and history stay in your PingBell account. Reconnecting picks them back up.
Every WooCommerce webhook in your store that delivers to PingBell is removed, even ones an older version made, and even if WooCommerce is deactivated at the time. Every setting the plugin stored goes with it. Nothing was ever written to your orders. Deactivating does nothing on purpose: a host deactivating plugins during an update is not a request to disconnect.
Signing in sets up New orders (order.created), New customers (action.wc_pingbell_new_customer_order) and Completed orders (action.woocommerce_order_status_completed). The manual API-key connection can point a counter at any WooCommerce topic, including action.woocommerce_add_to_cart.
https://hooks.pingbell.io/log?id=PINGBELL_ID, signed with a secret (X-WC-Webhook-Signature) so a forged request cannot inflate your counters. Older manual API-key connections use https://app.pingbell.io/log?id=PINGBELL_ID.
order.status_completed as a webhook topic — it stores an empty one and saves without complaint — so that connection was silent. The plugin now uses the matching action hook (action.woocommerce_order_status_completed) and refuses any topic WooCommerce would not accept instead of creating a webhook that cannot work. Reconnect to replace an affected webhook.