May 8, 2026 · 5 min read · Revenue, Slack, How-to
How to get Slack alerts when revenue drops
Revenue drops are the alerts that matter most — and the ones teams find out about too late. Most data teams discover a revenue drop when someone checks a dashboard, or worse, when finance closes the month and the numbers don't match.
This guide covers how to set up real-time Slack alerts for revenue drops from your data warehouse, so your team knows within minutes, not days.
Why revenue drops go undetected
The problem isn't the data. Most companies with a data warehouse have their revenue data there — transactions in Snowflake, MRR in BigQuery, order totals in Redshift or Postgres. The data exists. What's missing is a layer that watches it continuously and tells you when something moves.
Dashboards are reactive. They require someone to open them, remember to check, and notice a change against a visual baseline they're holding in their memory. At 10pm on a Tuesday, nobody's checking a Looker dashboard.
The fix isn't a better dashboard. It's monitoring — a system that watches revenue continuously and sends a Slack alert the moment it drops outside its normal range.
What you need
- ·A data warehouse (Snowflake, BigQuery, Redshift, or Postgres) containing revenue, transaction, or MRR data
- ·Slack
- ·A tool that connects the two and understands what "normal" looks like
The third item is where most homegrown approaches break down. A static alert — "alert if revenue drops more than 20%" — fires every weekend, every holiday, every time a campaign runs. Teams tune out the noise. The real drop gets buried.
What you need is adaptive baselines: a system that compares today's revenue to the relevant historical period. Tuesday at 4pm compared to the last 4 Tuesdays at 4pm. Not compared to yesterday, not compared to an arbitrary threshold.
Setting up revenue alerts with Lighthouse
Lighthouse connects to your warehouse with read-only credentials and sends Slack alerts when metrics move. Here's the full setup.
Step 1: Connect your warehouse
Add read-only credentials in Lighthouse. Depending on your warehouse:
- ·Snowflake: create a read-only role with SELECT on relevant schemas
- ·BigQuery: create a service account with BigQuery Data Viewer and BigQuery Job User roles
- ·Redshift: create a user with SELECT on the schemas you want to monitor
- ·Postgres: create a user with GRANT SELECT ON ALL TABLES IN SCHEMA
Lighthouse only needs read access. Setup takes about 3 minutes.
Step 2: Describe your revenue metric
Once connected, Lighthouse shows your schema. Pick the table that contains your revenue or transaction data and describe what you want to monitor in plain English:
"Total transaction revenue in the last hour, compared to the same hour last week."
or
"Daily revenue, compared to the 4-week average for the same day of week."
or for subscription businesses:
"MRR from active subscriptions, compared to last week."
Lighthouse reads your schema and generates the SQL automatically. You review and approve it. No manual query writing.
Step 3: Set alert conditions
Configure when Lighthouse should alert:
- ·Drop threshold: alert if revenue falls more than X% vs baseline
- ·Compare period: same hour last week, same day last week, 4-week rolling average
- ·Frequency: check every 15 minutes, hourly, or daily
- ·Severity: S1 for critical drops, S2 for moderate changes
Lighthouse builds adaptive baselines automatically — it learns your day-of-week and time-of-day patterns so Monday morning doesn't trigger a false alarm.
Step 4: Route to a Slack channel
Authorize the Lighthouse Slack app and pick which channel to send revenue alerts to. Most teams route to #finance-alerts or #revenue-ops. You can create separate monitors for different revenue streams and route them to different channels.
What the alert looks like
When revenue drops outside its normal range, Lighthouse sends something like:
S1 — Revenue drop detected Daily revenue is $47,200 — down 23% vs the 4-week average of $61,400 for the same day of week. Segment: All · Compare: Last 4 Tuesdays · Threshold: >15% drop [Acknowledge] [Mark as known issue]
Your team has the full picture without opening anything. They know what dropped, by how much, and relative to what.
Revenue metrics worth monitoring
Here are the revenue-related metrics teams most commonly alert on:
Transaction volume
- ·Total transaction count, last hour
- ·Payment success rate (drops signal processor issues)
- ·Average order value by segment
Revenue
- ·Daily or hourly revenue vs same period last week
- ·Revenue by product line or geography
- ·Refund rate (a spike here erodes net revenue)
Subscription / MRR
- ·MRR from active subscriptions
- ·New MRR from trials converting
- ·Churned MRR this week
- ·Billing failure rate (unrecovered revenue)
E-commerce
- ·Cart-to-checkout conversion rate
- ·Checkout-to-purchase conversion rate
- ·Return rate by category
Common gotchas
Comparing to yesterday breaks on weekends. If you alert when Tuesday revenue is lower than Monday, you'll fire every single Tuesday. Use same-day-last-week or 4-week rolling average.
Static thresholds go stale. If your business is growing 10% month-over-month, a threshold that was calibrated 3 months ago now fires constantly — or misses drops entirely. Adaptive baselines solve this automatically.
Midnight UTC alerts. Many businesses have a natural revenue dip between midnight and 6am. If you're comparing hour-over-hour, you'll get alerts every night. Ensure your compare period accounts for time-of-day patterns.
Lighthouse handles all of this automatically. Start for free — connect your warehouse and create your first revenue alert in under 10 minutes.