An alert when a widget's engagement falls

A widget can load fine and still stop working for you. A redesign, a new banner or a slower page can leave shoppers ignoring it, and nothing tells you. AISA now opens an Engagement fell alert when that happens.

• Once a day, AISA compares the widget's engagement rate over the last 7 days with its usual level, the median of the 3 weeks before. The alert opens when the last 7 days are at or under half of that.
• It only judges a switched-on widget with at least 200 sessions that saw it in each of those 4 weeks.
• It never opens when a member switched the widget on or off or published a version, or when a test ran on it, in any of those weeks. Those changes would explain the drop. Such a widget is judged again once the change is more than 4 weeks old.
• The alert shows on the Alerts page with the site and the widget's name, and an Open widget button.
• Your organization's admins get one email per day, listing every engagement alert found that day. It shows no figures: the widget's page is where you read them.

The alert closes by itself when a later week is back to the level the alert opened against, when you switch the widget off, or when you delete it. The Resolved tab keeps it with the reason.

The REST endpoint GET /api/v1/alerts and the list_alerts tool of the MCP server list these alerts too, with the kind widget_engagement_fall and the resolution engagement_recovered. They carry no rate and no session count.