Setting Up Ecommerce Alerts: What to Monitor
Ecommerce alerts are only valuable if someone acts on them. And someone will only act on them if they trust that the alerts signal real problems - not noise.
Alert fatigue is one of the biggest challenges when configuring ecommerce alerts. Set too many store monitoring alerts and your team learns to ignore them. Set too few and you miss critical issues. Set them without context and they arrive at 3 AM for a metric shift that is completely normal for a Tuesday night.
This guide covers how to design ecommerce alerts and store monitoring alerts that your team will actually use: which metrics to alert on, how to set thresholds intelligently, how to tier your alerts by severity, and how to route them to the right people at the right time.
See it in action
Want to automate this for your store?
VortexIQ's AI agents can audit, fix, and monitor your ecommerce store automatically.
This piece is part of our complete guide: Ecommerce Monitoring & Anomaly Detection: The Complete Guide.
In This Guide
The Alert Fatigue Problem
Before getting into specific store monitoring alerts, it is worth understanding why most ecommerce alert setups fail.
The typical progression looks like this:
- A major incident causes significant revenue loss because nobody noticed it in time
- The team sets up alerts - lots of them - to make sure this never happens again
- Alerts start firing constantly for normal metric fluctuations
- The team starts ignoring alerts because most of them are false positives
- A real incident occurs and the alert fires, but nobody acts on it because alerts have become background noise
- Revenue loss. Back to step 1.
This cycle repeats across ecommerce teams everywhere. The solution is not more alerts or fewer alerts. It is smarter alerts - designed with three principles:
Principle 1: Every alert must be actionable. If there is nothing a person can do when they receive an alert, it should not be an alert. It should be a report.
Principle 2: Context matters as much as the metric. An alert for "revenue down 15%" means nothing without knowing whether that is unusual. An alert for "revenue is 15% below what is expected at this time on this day given current traffic levels" is meaningful.
Principle 3: Alert volume should be low. If your team receives more than 3-5 critical alerts per week, the system is misconfigured. Most weeks should have zero critical alerts.
The Three-Tier Alert System
The most effective ecommerce alerts structures use a tiered store monitoring alerts system that separates genuinely urgent issues from important-but-not-urgent ones.
Tier 1: Critical Alerts (Immediate Response Required)
These critical ecommerce alerts signal issues that are costing significant revenue right now and require an immediate response regardless of time of day.
For more on this topic, see: guardrails.
Criteria for Tier 1: Revenue impact above GBP 500/hour, or complete functional failure of a core store process.
Delivery: SMS, phone call, or push notification - not just email. Must reach the on-call person regardless of whether they are at their desk.
Response time target: 30 minutes or less.
What qualifies as Tier 1: - Site completely down or checkout non-functional - Revenue more than 30% below hourly contextual baseline for two or more consecutive periods - Payment gateway failure (payment step completion below 50% of baseline) - Checkout completion rate below 40% of baseline across all devices - Active fraud pattern detected
Tier 2: Warning Alerts (Investigate Within 1-2 Hours)
These store monitoring alerts signal developing problems that need investigation during business hours - or outside hours if the store does significant overnight trading.
Criteria for Tier 2: Revenue impact of GBP 100-500/hour, or a significant metric deviation that may indicate a developing problem.
Delivery: Email, Slack message, or in-app notification.
Response time target: 1-2 hours during business hours.
What qualifies as Tier 2: - Revenue 15-30% below hourly contextual baseline - Mobile or desktop conversion rate 20%+ below baseline - Checkout abandonment rate 25%+ above baseline - Inventory discrepancy detected on top 20 SKUs - Ad platform ROAS below target by more than 25% for 2+ hours - Page load time on checkout above 4 seconds - Support ticket volume 2x above hourly baseline
Tier 3: Informational Alerts (Review During Daily Check)
These informational ecommerce alerts capture trends and issues that matter strategically but do not require immediate action from your store monitoring alerts system. They should surface in your daily operational review, not land in your inbox as urgent notifications.
Criteria for Tier 3: Revenue impact below GBP 100/hour, or gradual trends that need monitoring but are not urgent.
Delivery: Daily digest email or dashboard flag.
Response time target: Review within 24 hours.
What qualifies as Tier 3: - Revenue 5-15% below daily baseline - Minor conversion rate softness (5-10% below baseline) - Inventory approaching low threshold (2-3 weeks supply at current velocity) - Organic traffic shift in either direction - Email campaign underperformance vs benchmark - Gradual increase in cart abandonment rate over multiple days
Revenue Alerts: What to Track and How
Revenue-focused ecommerce alerts are the most commercially important category of store monitoring alerts. Getting them right means catching financial impact as early as possible.
Hourly Revenue vs Contextual Baseline
The most powerful revenue alert. Rather than alerting when revenue drops below a fixed threshold, compare actual hourly revenue against a dynamically calculated expected value for that specific hour.
Why contextual baselines outperform fixed thresholds: - Your store generates different revenue at 10 AM vs 8 PM - Mondays and Saturdays have different revenue patterns - November and July have different revenue profiles - A 20% drop from GBP 1,000 expected is very different from a 20% drop from GBP 10,000 expected
Ecommerce monitoring that uses AI builds these contextual baselines automatically. For stores without AI monitoring, a reasonable approximation is to compare against the same hour last week - imperfect but better than a static threshold.
Alert trigger: Revenue more than 20% below contextual baseline for two consecutive hourly periods.
Conversion Rate Alerts
Set separate alerts for overall conversion rate, mobile conversion rate, and desktop conversion rate. Device-specific alerts are particularly valuable because mobile checkout issues often affect mobile conversion without visibly moving the overall number (if desktop traffic is higher).
Alert trigger: Conversion rate more than 15% below contextual baseline for one hour, or more than 10% below for three consecutive hours.
Checkout Funnel Alerts
Alert on each step of your checkout funnel separately. An alert on "checkout completion rate" tells you something went wrong somewhere. An alert on "payment step completion rate specifically" tells you exactly where to look.
Recommended checkout monitoring points: - Add to cart rate - Cart to checkout initiation rate - Checkout step 1 (contact/address) completion rate - Checkout step 2 (shipping) completion rate - Payment step completion rate - Order confirmation rate
Alert trigger: Any individual step more than 15% below its contextual baseline.
Inventory Alerts: Beyond Low-Stock Notifications
Most ecommerce platforms provide basic low-inventory notifications. A proper inventory alerting system goes further.
Velocity-Based Stockout Prediction
Rather than alerting when stock is already low, alert when the current sales velocity will exhaust stock within a defined window.
Alert logic: If current sales velocity continues, this SKU will reach zero stock in X days.
Recommended thresholds: - Critical alert: Less than 3 days supply at current velocity - Warning alert: Less than 7 days supply at current velocity - Informational: Less than 14 days supply at current velocity
This approach catches stockout risk during high-velocity periods (promotions, viral social moments, seasonal demand spikes) when standard low-stock thresholds are much less useful.
Inventory Discrepancy Alerts
Alert when your ecommerce platform's reported stock levels diverge from expected levels based on order activity.
Alert logic: Inventory changed by X units, but order activity only accounts for Y units. Discrepancy: Z units. Likely sync failure or manual adjustment.
Alert trigger: Discrepancy above 5 units on any SKU with a velocity above 10 units/day.
Marketing Alerts: Spend and Returns
Marketing ecommerce alerts protect your ad budget and catch campaign issues before they become expensive. These store monitoring alerts are often overlooked but critical.
ROAS (Return on Ad Spend) Alerts
Alert when a campaign's ROAS falls significantly below target. This catches broken landing pages, ad creative fatigue, and audience targeting problems early.
Alert trigger: Campaign ROAS below 50% of target ROAS for two consecutive hours during active hours.
Important: Set at the campaign level, not just account level. Account-level ROAS can mask individual campaign problems if other campaigns are performing well.
Spend Anomaly Alerts
Alert when campaign spend is significantly above or below expected delivery.
- Overspend alert: Campaign spending more than 20% above daily budget target (may indicate budget settings changed or audience too broad)
- Underspend alert: Campaign spending less than 50% of daily budget target (may indicate ad disapproval, audience too narrow, or campaign paused)
Traffic Source Alerts
Alert when a significant traffic source drops materially - this catches organic ranking drops, ad campaign pauses, and email delivery issues.
Alert trigger: Traffic from a primary channel (organic search, paid, email) drops more than 25% below the rolling 7-day average for that channel at that time.
Operations Alerts: Fulfilment and Customer Experience
Operational store monitoring alerts catch problems that do not show up in revenue metrics immediately but will damage customer satisfaction and trigger refunds if not addressed.
Fulfilment Delay Alerts
Alert when orders are not being fulfilled within your standard SLA window.
Alert trigger: Orders placed more than X hours ago without a fulfilment event (configurable based on your SLA).
Return Rate Alerts
A spike in returns for a specific product often indicates a quality issue, description mismatch, or packaging problem that needs immediate investigation.
Alert trigger: Return rate for any product more than 2x its 30-day average return rate, sustained over 24 hours.
Support Volume Alerts
A spike in inbound support contacts is one of the best early warning signals for operational problems.
Alert trigger: Support contact volume more than 2x the rolling hourly baseline, or more than 5 contacts about the same topic (order status, specific product, specific issue) within one hour.
The Complete Alert Configuration Matrix
Alert Tier Metric Threshold Frequency Delivery Revenue anomaly (critical) 1 Hourly revenue >30% below contextual baseline Real-time SMS + push Checkout failure 1 Payment completion rate <50% of baseline Real-time SMS + push Site down 1 Availability Any downtime >2 min Real-time SMS + push Revenue anomaly (warning) 2 Hourly revenue 15-30% below baseline Hourly Slack + email Mobile conversion drop 2 Mobile CVR >20% below baseline Hourly Slack ROAS alert 2 Campaign ROAS <50% of target, 2+ hours Hourly Email Inventory critical 2 Days supply <3 days at current velocity Every 4 hours Slack Support spike 2 Ticket volume >2x baseline Hourly Slack Revenue soft 3 Daily revenue 5-15% below daily baseline Daily digest Email Inventory warning 3 Days supply <7 days at current velocity Daily digest Email Traffic shift 3 Channel traffic >25% from 7-day average Daily digest Email Return rate 3 Product return % >2x 30-day average Daily digest Email
Frequently Asked Questions
How many ecommerce alerts should I set up?
Fewer than you think. A well-designed ecommerce alert system should generate no more than 3-5 Tier 1 (critical) alerts per month under normal operating conditions. If you are getting critical alerts multiple times per week, either your thresholds are too aggressive or you have genuine recurring operational issues to resolve. Start with 5-8 core alerts covering revenue, checkout, and inventory. Add more only when you have validated that the existing alerts are working correctly.
What is the most important ecommerce alert to set up first?
Checkout completion rate by device. This single metric catches the most common and expensive type of ecommerce incident - a broken checkout experience that prevents customers from completing purchases. Set a Tier 1 alert for payment step completion rate dropping below 50% of baseline, and a Tier 2 alert for overall checkout completion rate dropping below 70% of baseline. These two alerts will catch the majority of critical technical incidents.
Should revenue alerts use fixed thresholds or contextual baselines?
Contextual baselines produce far fewer false positives and catch more genuine anomalies. A fixed threshold of "alert if revenue drops below GBP 5,000 per hour" generates false alarms at 2 AM when that hourly revenue is perfectly normal and misses a real problem at 2 PM when GBP 5,000 represents a 40% shortfall. Use contextual baselines wherever possible. VortexIQ's Nerve Centre builds these automatically from your historical data.
How do I prevent alert fatigue in my ecommerce team?
Three practices prevent alert fatigue: strict tiering (so Tier 1 alerts are genuinely rare and urgent), contextual thresholds (so alerts only fire when something is genuinely unusual for that time and context), and regular review and calibration (remove or adjust alerts that consistently fire without leading to meaningful action). Track your alert-to-action ratio - what percentage of alerts result in an action being taken? If it is below 70%, your thresholds need adjustment.
Can I set up ecommerce alerts without a dedicated monitoring platform?
Yes, but with significant limitations. Google Analytics 4 supports custom alerts on web traffic and conversion metrics. Shopify provides basic notifications. Ad platforms have their own built-in alert tools. However, these operate in silos - you cannot correlate a revenue alert with an ad platform event or an inventory alert. A dedicated ecommerce monitoring platform connects all these sources and provides the cross-channel intelligence that individual tools cannot.
Related Articles
- Ecommerce Monitoring & Anomaly Detection: The Complete Guide
- Ecommerce Monitoring: Beyond Basic Uptime Checks
- Anomaly Detection: How AI Spots Revenue-Killing Issues
- Revenue Impact Analysis: Quantifying Store Issues
- Shopify Store Monitoring: Complete Guide
Ready to take action?
Run a Free AI Audit on Your Store
VortexIQ scans your ecommerce store across 85+ checks — SEO, performance, analytics, ads — and gives you a prioritised fix plan in under 30 seconds.