Catch a Lytics audience segment anomaly early
Every hour, WebRun opens Lytics, checks each key audience segment's size against its recent trend, posts a Slack alert the moment a segment grows or shrinks unusually fast, and mirrors the same alert to Telegram so the data team sees it even outside working hours.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I catch a sudden Lytics audience segment size change?
Every hour, WebRun checks each key Lytics audience segment's size against its recent trend, posts a Slack alert the moment one moves well outside normal, and mirrors the same alert to Telegram for the data team. A broken tracking rule or a sudden behavior shift gets caught within the hour instead of surfacing days later in a campaign report.
- Segment anomalies get flagged within the hour they start
- The data team sees the alert whether or not Slack is open
- Broken tracking rules get caught before they skew a campaign
Built for data and marketing operations teams · CDP administrators · growth marketers · personalization teams
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.lytics.comin a real browser with your saved login - no setup, no API keys. -
1
Lytics - check segment sizes
lytics.com
WebRun opens Lytics to check segment sizes. - Open Lytics and review each key audience segment
- Read its current size and compare it against the recent trend
- Note any segment that has moved well outside its normal range
Done when Every key segment's size is checked against its recent trend.
-
2
Slack - post the anomaly alert
slack.com How to Automate Slack
WebRun opens Slack to post the anomaly alert. - Post a Slack alert naming any segment that moved outside its normal range
- Include the current size next to the recent trend
- Post nothing when every segment is within its normal range
Done when The team has a Slack alert for any segment anomaly.
-
3
Telegram - mirror the alert
telegram.org How to Automate Telegram
WebRun opens Telegram to mirror the alert. - Mirror the same alert to the data team's Telegram channel
- Keep the wording identical to the Slack post
- Send nothing when there is no anomaly to report
Done when The data team has the same alert available in Telegram.
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
Does it change or rebuild the segment?
No. WebRun only reports the size change. Investigating or adjusting the segment's definition stays with your data team.
Why post to both Slack and Telegram?
So the alert reaches the data team wherever they are watching, since not everyone keeps Slack open outside working hours.
What counts as an unusual size change?
A jump or drop clearly outside that segment's own recent trend, not a fixed percentage applied the same way to every segment.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.