Your Mixpanel alerts: ignored.
Your Lighthouse alerts: acted on.
Connect Lighthouse to your existing Mixpanel data.Mixpanel's anomaly algorithm fires on things that don't matter, and tells you nothing useful when it does. Get alerting built the way it should work: full context, tunable conditions, and every advantage native Mixpanel alerts don't have.
- Connects to existing Mixpanel account
- No migration
- Free forever for small teams
- No credit card
Installs
Israel
Installs triggered
Mixpanel Alert: Country change
Condition: not within forecasted range [122.97005462646484, 372.08203125] (current: 376)
Report: Installs: breakdown by GEO
Mixpanel is triggered!
Description: Installs are below the 7-day rolling average by more than 30%
Severity: S2
Segment: Israel
Value: 309
Compared Value: 1,443
Threshold: 1,010
View in Mixpanel
Three steps. No engineering.
- 01
Connect with a service account
Read-only credentials. Lighthouse never changes anything in Mixpanel.
- 02
Point at your Insight report
Paste the report ID. Lighthouse reads its structure automatically.
- 03
Build the metric in Lighthouse
Describe the condition in plain English, no SQL required.
Same Mixpanel data. Completely different signal quality.
- Alert frequency
Lighthouse
Any interval: 15 min, hourly, or any custom scheduleMixpanel native
Hourly or daily only, no way to catch a crash in 15 minutes- Aggregation window
Lighthouse
Any custom window: last 3 hours, last 8 hours, trailing 45 minutes, whatever fits the metricMixpanel native
Fixed to hourly or daily grouping, no way to look at a custom window- Message customization
Lighthouse
Fully custom message with dynamic values: segment, value, threshold, linksMixpanel native
Fixed system template; your team gets raw numbers with no context- Alert conditions
Lighthouse
Define exact logic: % drop vs. 7-day avg, absolute change, rolling averages, multi-dimensional rules, any combinationMixpanel native
Locked to Mixpanel's black-box forecast. Ranges like [122.97, 372.08] are unreadable and impossible to tune.- Triggered segment
Lighthouse
Shows the exact segment that fired: "Israel", immediately actionableMixpanel native
Shows aggregate only; you have to dig into the report to find which country- Minimum volume filter
Lighthouse
Set a baseline minimum so small markets never spam your channel. Only meaningful signals get through.Mixpanel native
No way to filter by volume: a market with 3 installs dropping to 2 fires the same alert as your biggest market dropping 79%- In-alert actions
Lighthouse
Hit / Resolve / Acknowledge + one-click metric history. Triage without leaving Slack.Mixpanel native
Links only: Edit alert · History. No team accountability, no audit trail.- What you can monitor
Lighthouse
Any metric: install funnels, D7/D30 retention, conversion rates, custom queriesMixpanel native
Insights reports only: funnels, retention cohorts, and conversion flows cannot be alerted on- Segments + overall in one metric
Lighthouse
Every segmented metric automatically includes an $overall row: one definition covers every segment and the aggregateMixpanel native
Separate alert rules needed for per-segment and total: double the setup, double the maintenance- Future-proof as your stack grows
Lighthouse
Point existing metrics at the new source. Alert logic, conditions, and history carry over, no rebuild needed.Mixpanel native
When you add Snowflake or BigQuery, your Mixpanel alerts are obsolete; you're starting from zero
| Capability | Lighthouse | Mixpanel native |
|---|---|---|
| Alert frequency | Any interval: 15 min, hourly, or any custom schedule | Hourly or daily only, no way to catch a crash in 15 minutes |
| Aggregation window | Any custom window: last 3 hours, last 8 hours, trailing 45 minutes, whatever fits the metric | Fixed to hourly or daily grouping, no way to look at a custom window |
| Message customization | Fully custom message with dynamic values: segment, value, threshold, links | Fixed system template; your team gets raw numbers with no context |
| Alert conditions | Define exact logic: % drop vs. 7-day avg, absolute change, rolling averages, multi-dimensional rules, any combination | Locked to Mixpanel's black-box forecast. Ranges like [122.97, 372.08] are unreadable and impossible to tune. |
| Triggered segment | Shows the exact segment that fired: "Israel", immediately actionable | Shows aggregate only; you have to dig into the report to find which country |
| Minimum volume filter | Set a baseline minimum so small markets never spam your channel. Only meaningful signals get through. | No way to filter by volume: a market with 3 installs dropping to 2 fires the same alert as your biggest market dropping 79% |
| In-alert actions | Hit / Resolve / Acknowledge + one-click metric history. Triage without leaving Slack. | Links only: Edit alert · History. No team accountability, no audit trail. |
| What you can monitor | Any metric: install funnels, D7/D30 retention, conversion rates, custom queries | Insights reports only: funnels, retention cohorts, and conversion flows cannot be alerted on |
| Segments + overall in one metric | Every segmented metric automatically includes an $overall row: one definition covers every segment and the aggregate | Separate alert rules needed for per-segment and total: double the setup, double the maintenance |
| Future-proof as your stack grows | Point existing metrics at the new source. Alert logic, conditions, and history carry over, no rebuild needed. | When you add Snowflake or BigQuery, your Mixpanel alerts are obsolete; you're starting from zero |
Common questions
Will this be another dashboard my team has to check?
Does Lighthouse replace Mixpanel?
Why is Mixpanel's native alerting limited?
What does the minimum volume filter do?
Can Lighthouse alert on Mixpanel funnels and retention?
What happens when we add a data warehouse later?
How long does setup take?

Your Mixpanel data deserves better alerts.
Connect in minutes. Set your first signal-aware alert today.
No migration · Read-only access · Free forever for small teams