How to Use GA4 Custom Alerts to Monitor Traffic and Conversions
· 9 min · Google Analytics
Stop finding problems days late. Set up GA4 custom alerts to catch traffic drops, conversion issues, and tracking breaks in time to act.
Why GA4 custom alerts matter for monitoring GA4 is excellent at reporting what happened, but monitoring is about noticing what’s changing right now—before it becomes a revenue problem. Custom alerts turn your analytics into an early-warning system for:
• Sudden traffic drops (SEO issues, broken campaigns, site downtime) • Conversion declines (checkout errors, form failures, pricing changes) • Tracking breaks (missing events, consent misconfiguration) • Channel anomalies (paid spend running but sessions not landing)
In many organizations, the real cost isn’t the incident—it’s the delay in detection. A 24–72 hour lag is common when teams only check dashboards weekly.
What GA4 “custom alerts” really are GA4’s alerting feature is called Custom insights. You define a condition (for example, “purchase conversions drop by 30% day over day”), and GA4 notifies you when it happens.
Custom insights can be used in two ways:
• Monitoring (recommended): Always-on alerts that watch key metrics • Investigation: Temporary alerts for a campaign, launch, or experiment
What alerts can and can’t do in GA4 Custom insights are powerful, but they’re not a full incident-management platform.
They can:
• Monitor common GA4 metrics (users, sessions, conversions, revenue, event count) • Compare against a prior period (for example, previous day, previous week) • Send notifications in GA4 and optionally by email
They can’t reliably:
• Replace server uptime monitoring • Detect every data-quality issue (for example, subtle attribution shifts) • Guarantee real-time detection (processing delays can occur)
A practical approach is to use GA4 custom alerts for behavior and performance changes, and pair them with:
• Uptime monitoring (site availability) • Tag monitoring (tracking deployed correctly) • Ad platform alerts (spend and delivery)
What to monitor: a practical GA4 alert framework You’ll get the best results by monitoring a small set of business-critical signals rather than creating dozens of noisy alerts. Start with four categories.
1) Acquisition health (traffic and channel mix) Monitor whether people are still arriving—and from the right places.
Recommended alerts:
• Total sessions drop (sitewide) • Organic search sessions drop (SEO risk) • Paid sessions drop while spend is stable (landing or tagging issue) • Country/region sessions drop (geo targeting, CDN issues)
Realistic benchmark thresholds (adjust to your baseline):
• Sites with 10,000–100,000 sessions/day: alert at -15% day over day • Sites with 1,000–10,000 sessions/day: alert at -25% day over day • Sites with <1,000 sessions/day: alert at -35% day over day (higher natural volatility)
2) Conversion and revenue integrity If you only create one set of alerts, make it these.
Recommended alerts:
• Purchases drop (count) • Purchase revenue drop • Lead form submissions drop • Key funnel step events drop (add_to_cart, begin_checkout, generate_lead)
Realistic benchmark thresholds:
• Ecommerce with steady traffic: alert at -20% purchases day over day • Lead gen (B2B) with lower volume: alert at -30% leads week over week • Revenue: alert at -25% revenue day over day (revenue is more volatile than sessions)
3) Tracking and data quality signals These alerts catch “analytics is broken” moments.
Recommended alerts:
• Event count for a core event drops sharply (purchase, generate_lead) • Sessions normal but conversions near zero (checkout tracking broken) • Page_view drops while sessions remain stable (tag firing issues)
Practical threshold ideas:
• Alert if purchase event count < 3 by noon for high-volume stores (tune to your business) • Alert if conversions drop by 80% while sessions drop by <10% (strong tracking-break indicator)
4) Engagement and UX red flags Engagement metrics won’t always map directly to revenue, but they can signal usability issues.
Recommended alerts:
• Engaged sessions drop • Engagement rate drops on key landing pages • Average engagement time drops after a release
Benchmark thresholds:
• Alert at -10% to -15% engagement rate week over week on top landing pages • Alert at +20% in “session_start” but -20% in “view_item” (users landing but not browsing)
Step-by-step: how to set up GA4 custom alerts (custom insights) GA4 lets you create custom insights from multiple places, but the cleanest path is through the Insights area.
Create your first custom insight Open GA4 and select the correct property. Go to Reports. Find Insights (often located in the Reports snapshot area, depending on your UI). Click Create (or Create custom insight). Choose the Condition type: - Anomaly detection style: compare to a previous period (common) - Static threshold style: above/below a fixed number Select: - Metric (for example, Sessions, Purchases, Total revenue) - Dimension (optional, for example, Session default channel group) - Comparison period (for example, previous day, previous week) Set your threshold (percentage change or absolute va…