MageSentinel – Checkout Monitoring For WooCommerce Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
WooCommerce checkout monitoring for your store, in two parts. The first one is free and needs no account.
A health page in your admin. Under the MageSentinel menu you get a plain
reading of the things that quietly stop a WooCommerce store from taking money:
whether the cart and checkout pages are still set and published, whether any
payment method is enabled at all, whether a shipping zone exists, how many
fatal errors WooCommerce logged in the last day, whether Action Scheduler is
running on time, and whether a WooCommerce database update is waiting. Each row
links straight to the screen that fixes it. Greek for Greek admins, English
otherwise.
Email alerts, every 15 minutes. The same checks run on your site every 15 minutes.
When one turns red — no payment method, the checkout page unpublished,
maintenance mode left on, a pile of failed payments, or orders that stopped
coming in when your store normally has a steady flow — you get an email naming
the problem and the screen that fixes it, and another when it is fixed. One
email per problem, not one per hour. The email goes out through your site’s own
mail; nothing else leaves your server. Send it to any address, or switch it off.
A weekly summary email (optional, off until you switch it on): every Monday,
last week’s orders, revenue, average order and failed payments against the week
before, with the health checks as they stand. Built from your own orders and
sent through your site’s own mail.
These checks read your settings and counts from the inside. They cannot tell
whether a shopper can actually pay — a broken payment script, a theme update
that hides the button. That is what MageSentinel is for.
A connector for MageSentinel checkout monitoring (optional, paid, 14 days
free). MageSentinel walks your
storefront the way a customer does — finds a product, adds it to the cart, fills
the checkout — and tells you when that stops working. This plugin is the part
that runs inside WordPress, so the check can confirm what actually happened in
your database instead of guessing from the page.
The connector is off by default. Nothing is exposed until you switch it on
and paste a token from your MageSentinel dashboard. Once on, it lets
MageSentinel:
- read store health — WordPress, WooCommerce and PHP versions, active plugins,
enabled payment and shipping methods, order counts, scheduler state. Never
order contents, never customer data; - confirm the test order a check just placed;
- cancel that test order — only if “Test orders” is switched on, and only for an
order from amagesentinel+address, under an hour old and unpaid.
CAPTCHA on your checkout? MageSentinel never solves or gets around a
CAPTCHA. If your checkout asks for one, you can switch on Let MageSentinel’s
checks past your CAPTCHA: requests that carry this store’s own connector
token are then served without the CAPTCHA, through the CAPTCHA plugin’s own
allow-list. Every other visitor still gets it. Off by default. Supported: CAPTCHA
4WP (Advanced noCaptcha & invisible Captcha), reCAPTCHA for WooCommerce,
hCaptcha for WP and Simple CAPTCHA Alternative with Cloudflare Turnstile.
Test orders never reach anyone’s inbox: the plugin silences WooCommerce’s new,
cancelled, failed, on-hold and customer emails for its own orders.
Once MageSentinel is connected and checking in, it sends your alerts (email or
Slack), so the plugin’s own emails pause to spare you duplicates. If MageSentinel
stops checking in for three hours, they resume on their own.
External services
The health page, the email alerts and the weekly summary run entirely on your
site. Their emails go out through your site’s own wp_mail; the plugin sends
nothing to MageSentinel or anyone else for them, and the emails load nothing
from outside when they are opened. To check HTTPS, the certificate and the
security headers, the self-check requests your own site’s home page; it
contacts no other address. The sign-up and pricing links are plain links you
choose to follow.
The plugin connects to MageSentinel (https://magesentinel.com), a
third-party checkout-monitoring service, only after you switch the connector on
under Settings and paste a connector token from your MageSentinel account.
While the connector is off, or holds no token, none of the following happens.
- MageSentinel reads this site’s diagnostics. MageSentinel calls the
plugin’s REST endpoint (/wp-json/magesentinel/v1/) with your token in the
X-MageSentinel-Token header. It receives: the checks shown on the health
page; the site address, locale, timezone and currency; WordPress, WooCommerce
and PHP versions; the active theme and plugin names and versions; enabled
payment and shipping method names; order counts per hour, day and payment
method (no amounts); counts of products, stock states and fatal errors (only
the plugin or theme folder named, never the error text); free disk space;
cache and Action Scheduler state; plugins switched on or off and updates
applied in the last week. For the test orders MageSentinel itself placed (a
magesentinel+ billing address and the order key are required), it reads
their number, status, total, payment method and items, and may cancel them.
It never receives customer names, addresses, emails or payment details.
Requests without a valid token are refused. - Requests to start a test purchase. The plugin sends a request to
https://magesentinel.com/api/connector/checks, with a hash of your token and
your site address, in two cases: when you press Test purchase now (it
then asks for the progress until the purchase finishes), and two minutes
after WooCommerce, the active theme or a payment or shipping plugin is
updated, at most once every 15 minutes. Nothing else is sent.
Using the connector requires a MageSentinel account, a paid service with a free
trial.
- Terms of service: https://magesentinel.com/terms
- Privacy policy: https://magesentinel.com/privacy
- Data processing addendum: https://magesentinel.com/dpa
Privacy
The checkout figure on the overview counts shoppers who reach checkout with
something in the cart, once a day each. It stores only a daily count: the
“already counted” mark is a salted hash of the WooCommerce session, kept for
the current day and then dropped. No IP address, name or cookie of its own is
stored, and the count is never sent anywhere.
Deleting the plugin removes all its settings and stored data.
Screenshots
The overview: each thing that can stop checkout, its state, and a link to the
screen that fixes it.
The same numbers as a table, for readers who want the figures rather than the
picture.
Settings: the connector switch, the token field, and the test-order
permission.
The store at a glance: catalog, updates, payments by method and how many
shoppers reached checkout.
Tools → Site Health: the same checkout checks next to WordPress’s own.
