6 min read

How to Set Up Alerts for Time To Convert in Mixpanel

When your conversion funnel slows down, you want to know immediately—not in next week's dashboard review. Mixpanel lets you set alerts on funnel conversion time so changes surface while you can still react. Here's how to configure them.

Set Up Your Conversion Funnel

Alerts for time to convert require a funnel as your baseline. This is what Mixpanel uses to calculate conversion speed.

Step 1: Create a funnel in Mixpanel

Go to Funnels in the left sidebar and click Create New Funnel. Name it (e.g., 'Sign Up to Purchase'). Add your conversion steps in order: Sign Up → Product View → Checkout → Purchase. Make sure each step matches an event you're already tracking.

javascript
// Track funnel events from your app
mixpanel.track('Sign Up', { 
  source: 'organic',
  plan: 'free'
});
mixpanel.track('Product View', { 
  product_id: '123',
  category: 'analytics'
});
mixpanel.track('Checkout', { 
  cart_value: 99.99,
  items_count: 1
});
mixpanel.track('Purchase', { 
  revenue: 99.99,
  plan: 'pro'
});
Fire these events from your web or mobile app to populate the funnel

Step 2: Set the conversion time window

In funnel settings, configure the Time Window parameter. This is how long Mixpanel waits for subsequent events before treating a user as a dropout. For B2B products, 30-90 days is common. For e-commerce, 7-14 days is typical.

javascript
// Set user properties to help segment the funnel
mixpanel.people.set({
  'funnel_entry_date': new Date().toISOString(),
  'funnel_entry_step': 'Sign Up',
  'user_segment': 'free_trial',
  'signup_source': 'paid_ads'
});
Track user properties to segment funnel analysis later
Watch out: If your funnel steps are infrequent, use a wider time window (30+ days). A too-narrow window creates false dropouts.

Create an Alert on Conversion Time

Now you'll set up the actual alert to notify you when average time to convert changes significantly.

Step 1: Open your funnel and go to Alerts

Find your funnel under Funnels. At the top of the page, click the bell icon or Alerts button. Click Create Alert and select Funnel metric change.

javascript
// Use Mixpanel's JQL to query conversion times
const conversionQuery = `
data("events",{
  from_date:"2026-03-20",
  to_date:"2026-03-26",
  where:contains(["event"], ["Purchase"]),
  unit:"day"
}).groupby(["properties.funnel_step"],[count()])
`;
// Execute in Mixpanel UI or via API to see conversion progression
Query conversion data to understand your current baseline

Step 2: Choose Average Time to Convert as your metric

In the alert configuration, select Average Time to Convert (not conversion rate). Set the threshold to how much slower than baseline you'll tolerate (e.g., 'Alert if average time exceeds 7 days'). Choose your notification channel: Slack, Email, or Webhook.

javascript
// Track conversion time explicitly in your events
mixpanel.track('Funnel Progress', {
  'current_step': 'Purchase',
  'funnel_name': 'signup_to_purchase',
  'time_in_funnel_seconds': 604800,
  'funnel_step_number': 4,
  'total_funnel_steps': 4
});
Include time-to-step in your event properties for custom filtering

Step 3: Set check frequency and enable the alert

Configure how often Mixpanel evaluates the alert: Hourly for fast-moving products with high volume, Daily for most products. Save your alert. Mixpanel will send the first notification once it detects a change above your threshold.

javascript
// Log alert trigger events for debugging
mixpanel.track('Alert Triggered', {
  'alert_name': 'Time to Convert Slowdown',
  'current_avg_time_days': 8.5,
  'baseline_avg_time_days': 5.2,
  'percent_increase': 63.5,
  'affected_users': 247,
  'alert_severity': 'high'
});
Track when alerts fire to monitor your alert health
Tip: Add a segment filter to only alert when *specific users* convert slowly. For example: 'Alert only if mobile users' conversion time increases'.

Calibrate Your Alert to Minimize False Positives

Raw thresholds trigger too often. Use these techniques to get signal instead of noise.

Step 1: Calculate a realistic baseline from historical data

Look at your funnel's Historical Conversion Time chart in Mixpanel. Average the last 30 days. Your alert threshold should be 20-30% *above* this average. If your baseline is 5 days, alert at 7 days, not 4.

javascript
// Query last 30 days of conversion data
const thirtyDaysAgo = new Date();
thirtyDaysAgo.setDate(thirtyDaysAgo.getDate() - 30);

mixpanel.track('Baseline Calculation', {
  'query_start_date': thirtyDaysAgo.toISOString(),
  'query_end_date': new Date().toISOString(),
  'metric': 'avg_time_to_convert',
  'expected_baseline_days': 5.2
});
Review 30 days of historical data to set realistic thresholds

Step 2: Add a minimum volume filter to the alert

Don't alert on low-volume slowdowns. Go back to your alert settings and add a second condition: 'Only alert if funnel has at least X completions this period' (e.g., 100 conversions per day). A 20% slowdown on 1 user is noise. A 20% slowdown on 1000 users is actionable.

javascript
// Track daily funnel stats as a separate event
mixpanel.track('Daily Funnel Metrics', {
  'date': new Date().toDateString(),
  'total_conversions': 1247,
  'avg_time_to_convert_hours': 48,
  'step_with_highest_dropout': 'Checkout',
  'meets_alert_volume_threshold': true
});
Gate alerts on minimum volume to reduce noise

Step 3: Test the alert on historical data

Before going live, use Mixpanel's Alert Preview to see how many times it would have fired over the last 7-30 days. If it fires more than 1-2 times, increase your threshold. Aim for alerts that fire when something is genuinely wrong, not daily.

javascript
// Log alert calibration results
mixpanel.track('Alert Calibration Test', {
  'test_period_days': 30,
  'alert_threshold_days': 7,
  'times_would_have_fired': 1,
  'false_positive_ratio': 0.02,
  'recommendation': 'threshold_acceptable'
});
Use preview results to dial in the right threshold
Tip: Set a cooldown period between alerts (e.g., 'Don't alert more than once per 8 hours'). This prevents getting paged for transient glitches.

Common Pitfalls

  • Setting thresholds too aggressively—alerting at 10% above baseline creates daily false alarms that you'll learn to ignore
  • Not filtering by minimum volume—a 50% slowdown on 2 users isn't actionable; a 5% slowdown on 5000 users is
  • Using a funnel time window that's too short—real users convert outside your expected window, so your actual baseline is worse than the metric shows
  • Forgetting to track all funnel events—if Mixpanel doesn't see the events, conversion times will be artificially low

Wrapping Up

You've now got alerts that surface real funnel slowdowns instead of random noise. Monitor the first month of alerts to confirm your threshold is right. If you want to track conversion delays across multiple analytics tools and correlate them with your product changes, Product Analyst can help.

Track these metrics automatically

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

Try Product Analyst — Free