Setting up your HB Analytic Alarms

Setting Up HB Analytics Alarm

HB Analytics alarms let you monitor any metric in real time and get notified when something goes wrong — a bidder dropping off, revenue falling below a threshold, timeouts spiking, and so on. Alarms trigger within the hour, making them the right tool for catching technical issues fast.

​ HB Analytics alarms vs. Ad Revenue Insights alarms Use HB Analytics alarms when you need fast, within-the-hour alerts on technical metrics. Ad Revenue Insights alarms run on daily imported data — better suited for longer-term revenue monitoring, but not for catching issues in real time.

1

Creating a New Alarm

Go to Alarms in the top menu and expand the Alarms dropdown to see your active alarms.

Here you can see and manage the existing alarms.

2

Add new alarm

Click + New HB Analytics Alarm Choose Custom alarm to get full control. Presets are available for common use cases.

3

Name your Alarm

Give it a clear name — this is what other users will see if you share it.

4

Set the date range

Alarms use dynamic time periods, not fixed dates. Choose a period like Per Day so the alarm evaluates a full day of data each time it runs.

Good to know: HB Analytics uses real-time data. Shorter time periods catch problems faster.

5

Choose what to monitor

Select the dimensions and metrics you want to track. A few things to keep in mind:

• If you want to monitor a metric per bidder with different thresholds per bidder, create one alarm per bidder rather than one alarm covering all.

• Use filters to narrow down to the specific bidders, sites, or placements you care about.

6

Set up your trigger condition

There are two types of triggers — choose the one that fits your use case:

Trigger type

When to use

Alarm button

Absolute value

You have a fixed threshold (e.g. revenue drops below €1,000)

Left ALARM button

% change

Levels vary a lot between dimensions and a relative drop makes more sense (e.g. a bidder drops 30% day-on-day)

Right ALARM button (requires Compare date range)

To use % triggers, enable Compare date range first, then use the right-hand ALARM button.

Once you press an ALARM button, set your condition (e.g. Less than → 10%) and click OK.

Multiple conditions use AND logic. For example: trigger only when CPM is low AND ad requests are above a threshold. OR logic isn't supported — create separate alarms instead (e.g. one for low revenue, one for high timeout %).

7

Save and set visibility

Choose Private (only you) or shared (visible to your organisation), then click Save.

Understanding the Alarms Panel

Once saved, your alarm appears in the list. Here's what the columns mean:

Understanding the Checks Panel

Each alarm can generate multiple checks — one per failing dimension combination. For example, an alarm on revenue per bidder might create separate checks for each bidder that fails the condition.

Email Notifications

Go to Generic settings to configure who gets notified:

• Edit global alarm recipients — email addresses for all shared (non-private) alarms.

• Edit my alarm recipients — email addresses for your private alarms

Slack notifications

Email notifications remain available for alarm recipients. When the Using the Relevant Yield Slack Integration is enabled, alarms can also send notifications to Slack. When editing alarm recipients, connect your Slack workspace and select Slack recipients. See Using the Relevant Yield Slack Integration for setup details.

Filtering Checks by Status

Use the Show checks dropdown to filter the checks panel:

• Unacknowledged — active errors not yet reviewed

• Acknowledged — errors you've marked as seen

• Recently recovered — checks that recovered in the last 7 days