> For the complete documentation index, see [llms.txt](https://docs.relevant-digital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.relevant-digital.com/hb-analytics/alarms-and-notifications/hba-vs-ari-alarms.md).

# HBA vs ARI alarms

Choose alarms based on the metric you need and how quickly you must respond.

### Quick recommendation

* Use **HB Analytics (HBA) alarms** for technical or operational issues. They trigger within the hour.
* Use **Ad Revenue Insights (ARI) alarms** for daily performance monitoring and longer-term trends.
* Use the module that provides the metric you need when a metric exists in only one.

### Choose the right alarm

1. **Need an urgent response?** Use HBA alarms.
2. **Monitoring daily revenue or other consolidated data?** Use ARI alarms.
3. **Need a metric from only one module?** Create the alarm in that module.

### Understand the data timing

ARI imports data daily. Some source data requires consolidation before reliable analysis is possible. ARI alarms based on API data therefore have a one-day delay.

This delay suits stable, long-term monitoring. HBA alarms are better for detecting technical changes quickly.

### Set up your alarm

Follow the relevant guide:

* [Set up an HB Analytics alarm](/hb-analytics/alarms-and-notifications/setting-up-your-hb-analytic-alarms.md).
* [Set up an Ad Revenue Insights alarm](/ad-revenue-insights/alarms-and-notifications/setting-up-your-ad-revenue-insights-alarms.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.relevant-digital.com/hb-analytics/alarms-and-notifications/hba-vs-ari-alarms.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.