> ## Documentation Index > Fetch the complete documentation index at: https://docs.summerengine.com/llms.txt > Use this file to discover all available pages before exploring further. # Alerts: flag a drop in your game's numbers > Set rules that flag a day when play sessions or store page views drop, or launches per store page view fall, and see which days fired in the last 28 days. **Early access.** Rules are checked each time you open the page, and saved in your browser only. Summer does not email you about them yet. Until you have numbers on Summer Games, this page shows example data, marked **Example data**. Open **Alerts** at [summerengine.com/studio/grow/alerts](https://summerengine.com/studio/grow/alerts). ## Add a rule | Field | Options | | - | - | | **Name** | Up to 50 characters, such as "Play sessions dropped". | | **When** | **Daily play sessions drop**, **Daily store page views drop**, or **Launches per store page view fall**. | | **Threshold (%)** | How big a drop counts: 5-90% for the first two, 1-100% for launches per view. | | **Games** | All your games, or one game. | Below the form, Studio writes the rule out in a sentence, for example: "A day's play sessions are more than 30% below the mean of the 7 days before". Click **Add rule**. Days with very few counts are left out, so a quiet day does not fire a rule. ## Read your rules **Your rules, and the days they fired (last 28 days)** lists each rule with an on and off switch and the days it fired. Turn a rule off to keep it without checking it, or delete it. When a rule fires, open [Analytics](/grow/analytics) and find the day in the daily table. ## With your agent Ask "did anything drop this week?". The Studio assistant reads your numbers and flags drops of 20% or more, biggest first. See [Use the agent](/grow/use-the-agent). *** Does this not help you? [Reach out on Discord!](https://discord.gg/summerengine) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.