Automated Ruler Analytics Lead Source Alerts
Every hour, WebRun opens Ruler Analytics, reads tracked calls and form submissions by source, compares the count against the normal pace for that time of day, and the moment a source spikes or drops sharply it posts the alert to Telegram with the numbers, texting the marketing lead through Twilio when the swing is severe enough to need same hour attention.
How do I get alerted to a sudden lead source spike or drop in Ruler Analytics?
WebRun checks your Ruler Analytics call and form tracking every hour, comparing each lead source against its normal pace. The moment one spikes or drops sharply, it posts the alert to Telegram with the numbers, and texts the marketing lead through Twilio if the swing is severe, so a lead source problem gets noticed the same hour.
- Lead source problems get caught within the hour instead of at month end
- Severe swings reach the marketing lead by text, not just an unread channel post
- Tracking issues that look like a lead drought get caught fast
Built for Marketing teams · Lead generation teams · Agencies · Marketing operations
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.ruleranalytics.comin a real browser with your saved login - no setup, no API keys. -
1
Ruler Analytics - check lead source volume
- Open Ruler Analytics and read tracked calls and form submissions by source
- Compare each source's count to its normal pace for the time of day
- Flag any source that spiked or dropped sharply
Done when Every lead source has been compared against its normal pace this hour.
-
2
Telegram - post the swing alert
WebRun opens Telegram to post the swing alert. - Post the flagged source, the direction, and the size of the swing
- Include whether it was a spike or a drop
- Send only when a source moves meaningfully
Done when The marketing channel has an alert for every flagged source.
-
3
Twilio - text the marketing lead for severe swings
WebRun opens Twilio to text the marketing lead for severe swings. - Text the marketing lead only when a swing is severe, such as a source going silent
- Name the source and what changed
- Skip the text for smaller swings already covered on Telegram
Done when The marketing lead has been texted for any severe swing.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
What counts as a severe swing worth a text?
You set the bar, such as a source that normally sends steady leads going completely silent for an hour. Smaller swings stay on Telegram only.
Does WebRun pause or redirect ad spend?
No. It only detects and reports the swing. Adjusting spend or investigating a tracking issue stays with your marketing lead.
Could a tracking issue cause a false alert?
It is possible, which is exactly why WebRun flags it fast. A sudden drop to zero from a source that normally performs is often a tracking problem worth checking immediately.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.