Spot a broken event before the whole team trusts bad data
Every Monday, WebRun opens Segment, reads last week's event volume for each source, compares it with the week before, notes any event name that appeared or vanished, writes the review into your Notion data page, and WhatsApps you about any sharp drop.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I catch broken event tracking in Segment before it skews reports?
WebRun opens Segment every Monday, reads last week's event volume for every source, and compares it with the week before. It writes a dated review into Notion listing volume changes, brand new event names and events that stopped firing, then WhatsApps you about any sharp drop worth investigating.
- A broken event is caught the Monday after it ships, not at quarter end
- New event names get reviewed instead of appearing unannounced
- Eight weeks of volume history live in one Notion page
Built for data teams · analytics engineers · growth teams · product managers
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.segment.comin a real browser with your saved login - no setup, no API keys. -
1
Segment - read event volume by source
segment.com
WebRun opens Segment to read event volume by source. - Open Segment and set the reporting window to the last full week
- Read total event volume per source and per event name
- Compare with the previous week and note events that disappeared, events that are brand new, and any volume that moved more than 30 percent
Done when Every source has a week-over-week volume comparison and a list of changed event names.
-
2
Notion - write up the weekly review
notion.so How to Automate Notion
WebRun opens Notion to write up the weekly review. - Add a dated entry to your data quality page in Notion
- Table the volume per source with the week-over-week change
- List new event names under a heading for review, and list vanished events under a heading for investigation
Done when Notion holds a dated review with volumes, new events and vanished events.
-
3
WhatsApp - flag sharp drops to you
whatsapp.com How to Automate WhatsApp
WebRun opens WhatsApp to flag sharp drops to you. - WhatsApp yourself only when a source dropped sharply or an established event stopped firing entirely
- Name the source, the event and the size of the drop in one line
- Include a pointer to the Notion entry rather than repeating the whole table
Done when You have been told about any drop worth investigating today.
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
Will it change a source or destination setting?
No. WebRun reads volume figures and event names only. It never enables or disables a source, never edits a destination, and never touches a tracking plan. Every change stays a deliberate human action.
How does it know a drop is a real problem?
It compares each source and event name against the previous week and flags moves beyond the threshold you set, defaulting to 30 percent. An established event that fires zero times is always flagged, since that is the classic sign of a shipped bug.
Why write it to Notion rather than just message me?
Because the dated history is what makes drift obvious. One week's numbers mean little, but a Notion page with eight weeks of volume shows exactly which release broke which event.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.