

Checkout journey card: the synthetic cart to payment test built from the shop's own pages, with the payment methods it confirms and the step that failed
PingView is for agencies and freelancers who look after WordPress sites and WooCommerce shops for other people. A management plugin looks at the shop from the inside; PingView checks from outside, from several locations, whether a customer can open the site and buy today, and emails you before the client notices.
What it checks
Alerts go to email out of the box; Slack, Microsoft Teams, Discord, webhooks and SMS are set up once in your PingView account and apply to every site.
For agencies
One plugin family, three platforms: PingView has the same plugin for WordPress, PrestaShop and Magento 2, and every client site reports into the same panel. Add a site with one field, the address alerts should go to, and PingView creates the account and the monitor. No API key to copy, no code on your visitors’ page loads. Deactivating the plugin does not stop monitoring, and disconnecting removes only the local credentials.
How it works
The monitoring runs on PingView’s servers. Nothing is added to the site’s frontend and nothing runs during a visitor’s request.
This plugin depends on the PingView external monitoring service (https://pingview.app). The service creates or connects a monitor, checks the configured website from external locations, sends downtime alerts, and returns monitoring information for the WordPress admin dashboard. The plugin cannot provide monitoring functionality without this service.
What the service is and what it is used for:
PingView is an external website monitoring service provided by PingView. It checks website availability, performance, certificates, and incidents from external locations and provides the results shown by this plugin.
What data is sent and when:
– During new account setup: the administrator’s email address, WordPress site URL, site name, plugin version, and a source identifier stating that the request came from the WordPress plugin.
– When connecting an existing account: the API token entered by the administrator. The token is sent in an authorization header so PingView can validate the account and list or create its monitors.
– When a monitor is created: the site URL, generated monitor name, monitor type, check interval, response-time threshold, and selected monitoring locations.
– When loading or refreshing the dashboard: the stored monitor identifier and API token, used to retrieve current monitoring status.
– After setup, PingView’s external servers request the monitored site URL at the configured interval to measure availability and related monitoring signals.
When data is transmitted:
– When the administrator submits either setup form.
– When the PingView admin dashboard is opened or manually refreshed.
– Continuously after setup, when PingView performs external checks of the configured site according to the monitor’s settings.
Service provider:
PingView
Terms of Service:
https://pingview.app/en/terms-of-service
Privacy Policy:
https://pingview.app/en/privacy-policy