# Notifications

The **Notifications** tab provides a comprehensive overview of all notifications generated for this household within the selected date range. It combines high-level distribution charts with a detailed daily heatmap and interaction tracking, making it easy to audit what was sent and how the end user responded.

<figure><img src="/files/iChZGrt4OLjBgvEbTFyO" alt=""><figcaption></figcaption></figure>

## Distribution Charts

The top section displays three donut charts that summarise the notification activity for the selected period.

### Notifications by Rule

Shows the percentage breakdown of notifications grouped by the rule that triggered them. Each segment represents a different rule, for example:

* Daily energy report
* High excess energy available
* Peer Comparison: Total Energy Consumption
* Typical high consumption hours
* Monthly Energy Report
* Car is charging with grid power
* New top consuming device

This chart helps identify which rules are most active for the household.

### Notifications by Delivery Status

Shows the proportion of notifications in each delivery state. Possible statuses include:

* **Delivered** — The notification was successfully sent to the end user.
* **Pending** — The notification is queued for delivery.
* **Failed** — The notification could not be delivered.

A household showing 100 % Delivered indicates that all notifications within the selected date range were successfully sent.

### Notifications by Interaction Type

Shows how the end user interacted with the delivered notifications. Interaction types include:

| Interaction      | Description                                                         |
| ---------------- | ------------------------------------------------------------------- |
| **Openapp**      | The user tapped the notification and opened the app.                |
| **Viewed**       | The notification was displayed and seen by the user.                |
| **Dismiss**      | The user actively dismissed the notification.                       |
| **Stopdelivery** | The user opted out of receiving further notifications of this type. |

This chart is useful for gauging engagement and identifying notification fatigue.

## Notification Heatmap

<figure><img src="/files/1Cgu3HScdqJxWP0mYbf4" alt=""><figcaption></figcaption></figure>

Below the donut charts, a heatmap table displays the number of notifications per rule per day. The table is filtered by the **Delivery Status** selected in the page header (e.g., `DELIVERED`).

* **Rows** represent individual rules (e.g., "Daily energy report", "High excess energy available").
* **Columns** represent individual days within the selected date range.
* **Cells** contain the count of notifications sent for that rule on that day. Cells are shaded in green, with darker shades indicating higher counts.
* The **Sum\[rules]** row at the top shows the total number of notifications across all rules for each day.
* The **Sum\[days]** column on the right shows the total number of notifications for each rule across the entire period.

This view makes it easy to spot patterns — for example, rules that fire daily versus those that trigger only on specific days.

## Interactions

<figure><img src="/files/CTaPe8psxMQZniwqWSGH" alt=""><figcaption></figcaption></figure>

The **Interactions** section displays a time-series line chart tracking how the end user responded to notifications over the selected date range. Four series are plotted:

* **OPENAPP** — Percentage of notifications where the user opened the app.
* **VIEWED** — Percentage of notifications that were viewed.
* **DISMISS** — Percentage of notifications that were dismissed.
* **STOPDELIVERY** — Percentage of notifications where the user requested to stop delivery.

The y-axis shows the interaction rate as a percentage (0–100 %) and the x-axis shows individual dates. This chart helps monitor engagement trends — for instance, a rising dismiss rate may indicate notification fatigue and signal that rule frequency or content should be adjusted.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.moost.io/platform-manual/buildings/notifications.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.