5 min read

How to Set Up Custom Alerts in Mixpanel

You're shipping a new feature and need to know immediately if signups tank or a critical flow breaks. Without alerts, you're constantly checking dashboards. Mixpanel's custom alerts watch your data 24/7 and notify you when something changes—you don't have to.

Create an Alert on Your Events

Alerts in Mixpanel live inside the Events board. You set a condition, Mixpanel monitors it, and sends a notification when the threshold is crossed.

Step 1: Navigate to your event

Go to Analytics > Events and find the event you want to monitor (e.g., user_signup, payment_completed). You'll see a graph showing event count over time.

javascript
// First, instrument the event in your app
mixpanel.track('user_signup', {
  source: 'homepage',
  plan_type: 'premium',
  signup_method: 'google_oauth'
});
Alerts need data. Track the event with relevant properties so you can segment alerts later.

Step 2: Click the alert button

On the event graph, click the bell icon. Mixpanel opens an alert configuration panel where you'll choose your trigger condition.

Step 3: Set your condition

Choose Drops below or Exceeds and enter a threshold (e.g., 10 events, 50 events). Select a time window: Last 5 minutes, Last hour, or Last day. Be specific—too sensitive triggers noise, too loose misses real problems.

javascript
// Example threshold logic:
// Alert Type: Drops below
// Threshold: 10 events
// Time window: Last hour
// This fires when user_signup count < 10 in any 1-hour window
Set thresholds based on your typical event volume. If you average 50 signups/hour, 10 is a realistic drop.

Step 4: Configure notifications

Select Email, Slack, or both. For Slack, Mixpanel will ask for workspace access and you'll choose the channel. Save and enable the alert.

Watch out: Alerts only trigger on NEW data after creation. Historical data won't retroactively fire alerts. Set them up proactively, not after a problem.

Segment Alerts for Precision

You don't want alerts on all traffic. Narrow them to specific cohorts or properties for signal-rich notifications.

Step 1: Add a segment filter

When creating an alert, use Segment by. Choose a property like plan_type, country, or device_type. This limits the alert to only users matching that property.

javascript
// Track with rich properties for segmentation flexibility
mixpanel.track('checkout_completed', {
  plan_type: 'enterprise',
  mrr: 5000,
  country: 'US',
  annual_contract: true
});

// In Mixpanel UI, alert on enterprise customers only:
// Segment by: plan_type = 'enterprise'
// This prevents noise from small test or free-tier checkouts
Properties enable you to set alerts per segment without creating duplicate tracking code.

Step 2: Validate segment volume

Before saving, check the segment's baseline volume. If a segment averages 5 events/day, a threshold of 10 is meaningless. Start with segments that have predictable daily volume.

Tip: Low-volume segments fire randomly. Ensure your segment has consistent baseline activity (at least 50+ events/day) before setting a threshold.

Monitor and Tune Your Alerts

Alerts decay in usefulness if thresholds don't evolve with your product. Review alert history and adjust quarterly.

Step 1: Check alert history

Go to Settings > Alerts to see all past triggers. This shows whether thresholds are realistic or if you're getting too many false positives.

javascript
// Query event volume to validate your threshold
const url = new URL('https://mixpanel.com/api/2.0/segmentation');
url.searchParams.append('from_date', '2026-01-01');
url.searchParams.append('to_date', '2026-03-26');
url.searchParams.append('event', 'user_signup');

fetch(url, {
  headers: {
    'Authorization': `Bearer ${SERVICE_ACCOUNT_TOKEN}`
  }
})
.then(res => res.json())
.then(data => console.log('Daily volume:', data.data));
Use the Segmentation API to understand baseline metrics and validate thresholds.

Step 2: Update thresholds as you scale

As your app grows, event volume climbs. A threshold that caught problems in January might be too low by June. Review quarterly and adjust upward with growth.

Tip: Alert on leading indicators (signups, trial starts, feature adoption) not lagging metrics (churn, downgrade). You'll get actionable early warnings.

Common Pitfalls

  • Threshold too sensitive: You'll ignore notifications because they fire constantly. Test on a week of historical data to find the right baseline.
  • Forgetting to instrument events: Alerts need data. If you don't track checkout_started, you can't alert when checkouts drop.
  • Silencing notifications: If you're muting alerts, your threshold is wrong. Lower it or narrow the segment instead of disabling.
  • Email-only notifications: Email gets buried. Use Slack so alerts reach your team in real time, not in a digest tomorrow.

Wrapping Up

Custom alerts turn Mixpanel from a dashboard you check into a monitoring system that reaches out to you. Set them on leading indicators, validate thresholds on real data, and keep them narrow enough to act on. If you want to automate alert setup and correlation across your entire product stack, Product Analyst can help.

Track these metrics automatically

Product Analyst connects to your stack and surfaces the insights that matter.

Try Product Analyst — Free