PingView plugins

Store monitoring inside the admin you already have open

Three plugins, one panel, the same twenty-card contract. Install it in your store, give an email address, and you can see straight away whether the store is selling. Nothing is added to your customers' requests.

Pick your platform
your-store.com/wp-admin

PingView

your-store.com

Operational

Status

Operational

Uptime, 24h

99.98%

Response time

284 ms

Needs attention

All clear

Availability

24h agonow
Last 24 hours
99.98%
Last 7 days
99.91%

Checked from 5 locations

  • PLWrocław118 ms
  • DEFrankfurt173 ms
  • GBWorcester140 ms
  • USNewark248 ms
  • ITMilan296 ms

The SSL certificate expires in 26 days. Renew it before the browser starts warning your customers.

Example: the plugin panel in the WordPress dashboard. On PrestaShop and Magento the same cards sit in the back office and in the admin. Location and card names are real; the numbers are illustrative.

Three stores, one panel

Your store is not on the list?

Shopify, Shoper, IdoSell and custom-built stores are monitored from the outside, with no plugin at all. The panel then lives in PingView instead of in the store admin; everything else works the same.

Store monitoring without a plugin

Six questions the panel answers without a single click

The plugin computes nothing on its own. It renders what the PingView backend computed, in the place you happen to be.

Is the store up right now?
One word in the header: operational, degraded, partial, offline or maintenance. Exactly the state your team sees in PingView and your customer sees on the status page.
Is it my store or my connection?
The result from every probe separately: Wroclaw, Frankfurt, Worcester, Newark, Milan. Four see the store and one does not, so this is not a store outage.
How long was the store down this week?
Uptime for 24 hours and for 7 days, plus an hour-by-hour chart. No spreadsheet arithmetic, and no argument with the host about whether the outage happened at all.
Is the checkout actually taking orders?
A synthetic purchase path walks the cart and the checkout and asserts that the steps really happened. A homepage can answer 200 long after the payment step has died.
What should I fix first?
A list of things to do, most urgent first: an expiring certificate, a missing security header, a page that got slower. Sentences to tick off instead of a chart to interpret.
Who finds out while I am asleep?
Email works out of the box. Then you route incidents to the channel your team already watches: Slack, Microsoft Teams, Discord, a webhook or SMS.

The plugin computes nothing on your server

A store that is down cannot report that it is down. So the checks run from outside, and the plugin is only a window onto the result.

No code on customer requests

Not a line of the plugin runs when a customer opens a page. Nothing is added to the store's response time and nothing lands on the storefront.

Checks from five countries

The probes run on our servers in Poland, Germany, the United Kingdom, the United States and Italy. An outage at your host does not touch them.

Disconnecting does not stop the monitoring

Disconnecting removes the credentials stored in the store. The monitor keeps running, the history stays, the alerts still arrive.

The same contract on every platform

Twenty cards each of the three plugins has to render. This is not a marketing wish list: the build of every plugin fails if a single card disappears. Below you also get the three places where one platform does less than its siblings.

Plugin panel cards and their availability on the three platforms
Panel cardWordPressPrestaShopMagento 2
Store state in one wordOperational, degraded, partial, offline or maintenance in the panel header.
Four numbers up frontStatus, 24h uptime, response time and what needs attention.
What to fixSentences to tick off, most urgent first, computed by the backend.
Uptime, 24h and 7 daysPercentages plus an hour-by-hour chart.
What exactly is checkedThe interval, the locations and the conditions that raise an alert.
Watched store addressesCart, checkout, a category and a product, discovered from your store.
Alert channelsEmail, Slack, Teams, Discord, webhook and SMS, with a link to the settings.
Each probe on its ownStatus and latency per location, so an outage is told apart from a bad link.
Certificate and domainDays to SSL and domain expiry, plus a plain-HTTP warning.
Security headersThe Mozilla Observatory grade and the headers you are missing.
Lighthouse and Core Web VitalsPerformance, accessibility, best practices and SEO, measured from outside.
Purchase pathA synthetic run through the cart and the checkout, with its assertions.no verification state
Recent incidentsWhen they started, how long they lasted and how they ended.
Is the store's schedule aliveA diagnosis of the store's cron plus a heartbeat monitor on our side.cron line on your hostingcron line on your hosting
Status badgeA preview and a snippet to paste, next to the public status page.
Repoint after an address changeWhen the store changes domain, the monitor follows it.automaticone clickone click
Account and teamWhich PingView account this store reports into.
Monitoring outside the storeA plain statement that the checks do not run on your server.
Into the full productA link to the account with history, reports and status pages.
Disconnect the storeRemoves the local credentials; the monitor keeps running.