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.
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 →
How it works
Three steps. No engineering.
Connect with a service account
Read-only credentials — Lighthouse never exports your raw data
Service Account Secret
Project ID
Point at your Insight report
Paste the report ID — Lighthouse reads its structure automatically
Insight Report ID
Build the metric in Lighthouse
Describe the condition in plain English — no SQL required
"Alert if installs drop more than 20% vs. the 7-day average, per country, minimum 1,000 installs"
Side by side
Same Mixpanel data.
Completely different signal quality.
Common questions
Will this be another dashboard my team has to check?
No — Lighthouse doesn't add a dashboard to your routine. It watches your Mixpanel metrics in the background and only shows up when something's actually wrong, in the Slack channel you already use. There's nothing new to check unless there's something worth knowing.
Does Lighthouse replace Mixpanel?
No — Lighthouse connects to Mixpanel via API and adds a monitoring layer on top. You keep using Mixpanel for exploration and analysis. Lighthouse handles the alerting, with far more control than Mixpanel's native alerts.
Why is Mixpanel's native alerting limited?
Mixpanel alerts are built around a single black-box anomaly algorithm with no way to tune conditions, filter by volume, or surface which segment triggered the alert. For teams with multi-market data, this creates constant false positives — and teams learn to ignore the channel.
What does the minimum volume filter do?
It lets you set a baseline minimum — for example, only alert on a segment if its 7-day average is above 1,000 installs. A country with 3 installs dropping to 2 looks like a 33% drop, but it's meaningless. The volume filter ensures small markets never spam your alerts channel.
Can Lighthouse alert on Mixpanel funnels and retention?
Yes. Lighthouse connects to the Mixpanel API and can monitor any metric you can define — not just Insights reports. Install-to-purchase funnels, D7/D30 retention by country, session conversion rates — all alertable.
What happens when we add a data warehouse later?
When you connect Snowflake, BigQuery, or Redshift, you can point existing Lighthouse metrics at the new source. Your alert conditions, thresholds, segment filters, and history all carry over. You're not starting from scratch.
How long does setup take?
Most teams are monitoring their first Mixpanel metric within 10 minutes. Connect with your Mixpanel API credentials, pick a report, define your condition, and set a Slack channel. No engineering required.
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