Monitoring

Slack alerts

The channel the team already watches, with the event linked back to the screen that explains it.

Per eventLinked backNever blocks

Slack is where a team notices things together, which makes it the natural home for the events worth a shared glance rather than an individual interruption. Connect a workspace, choose a channel, and route any of the twelve event types to it.

Its defaults are broader than email deliberately. Lifecycle events, an experiment starting, ending or being deployed, go to Slack but not to anybody’s inbox: a channel is the right place for "this is now live", and an email about it is noise.

Each message carries the event and a link back to the exact console screen it refers to, so the first click lands on the significance page rather than on a dashboard somebody then has to navigate.

Like email, delivery runs after the event is committed and outside its transaction, and a failure is logged rather than raised. The action is the product; the notification is commentary about it, and commentary must never be able to undo the thing it describes.

Better experiments, better conversions

Test on all visitors with the world’s lightest script and make confident decisions powered by real-time reporting.