> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adriel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Alerts

> Rule-based monitoring for marketing data and platform connectivity, with email and in-app notifications.

**Alerts** let a user set up rules that watch their data and notify them when something changes. Common uses: catch a metric that spiked or dropped, detect an ad account that stopped delivering, flag a creative that violates a naming rule, or check that UTM parameters are set correctly.

Open **Alerts** from the main left navigation to see the list of all alerts in the workspace.

## The Alerts page

The Alerts page lists every alert set up in the workspace. Each row shows:

* **Status** — a toggle to pause or resume the alert.
* **Name** — the alert name.
* **Channels** — the data sources the alert applies to.
* **Applied to** — the level the alert runs at (Campaign, Ad set, Ad, or Ad account).
* **Condition** — a summary of the trigger condition.
* **Frequency** — how often the alert checks its condition.
* **Action** — the actions taken when the alert triggers (Trigger Alert, Send Email Notification).

Row actions:

* **Row action menu (three-dot icon)** — Duplicate, Edit, or Delete a single alert.
* **Bulk delete** — select multiple alerts with the checkboxes and click **Delete** at the top of the page.
* **Search** — filter the list by alert name.

## Create an alert

Click the **+** button in the top right of the Alerts page. Alert creation runs through five steps.

### Step 1: Select type

Pick one of six alert rule types:

* **Monitor metrics against a threshold** — trigger when a numeric metric (CTR, CPA, ROAS, etc.) exceeds or falls below a defined threshold.
* **Track metric changes over time** — trigger when a metric increases or decreases by a percentage compared to a baseline over a specific period.
* **Track ad account status** — trigger when an ad account is disabled, blocked, or disconnected on Adriel.
* **Check UTM Parameter Conditions** — trigger when UTM parameters are missing, contain specific keywords, or do not contain specific keywords.
* **Monitor ad content for specific keywords** — trigger when specific keywords are missing or included in ad headlines or descriptions.
* **Track ad or ad set approval status** — trigger when ads or ad sets are disapproved for compliance violations.

### Step 2: Name the alert

Enter a display name for the alert. This is what appears in the Alerts page and the Alert widget.

### Step 3: Define Conditions

<Note>
  Five of the six rule types share the same condition structure — only **Track ad account status** is simpler and just needs the data sources to track. The other five follow the flow below, with the trigger condition itself varying by rule type.
</Note>

<Steps>
  <Step title="Select the data source to apply the alert condition">
    Add one or more connected data sources.
  </Step>

  <Step title="Choose the level (breakdown) where the condition will be applied">
    Pick **Campaign**, **Ad Set**, or **Ad**. The condition runs against rows at this level.
  </Step>

  <Step title="Define the filter conditions to narrow down the data based on specific criteria">
    Optionally add filter conditions (channel, status, campaign name, etc.) so the alert only checks a subset of rows.
  </Step>

  <Step title="Set trigger conditions for alert">
    Set the condition that triggers the alert. Pick a metric, an operator (`>`, `<`, `=`, and so on), and a value. Click **+ Add condition** to add more; multiple conditions combine with AND.
  </Step>

  <Step title="Set the period to check condition fulfillment">
    Pick the time window the rule looks at (for example, **Today**, or a fixed lookback range).
  </Step>
</Steps>

For **Track ad account status**, the only field is the data sources to watch — the trigger is fixed (ad account disconnected, disabled, or blocked).

### Step 4: Set Frequency

<Steps>
  <Step title="Select how frequently the alert should be sent when the conditions are met">
    Pick the check cadence — for example, **Daily**, **Every Monday**, or **Upon Trigger** (as soon as the condition is met).
  </Step>

  <Step title="Limit how many alerts are sent, even if the conditions are met frequently">
    Pick an alert cap to prevent excessive notifications. For example, **Once per Day** ensures only one alert triggers per day even if the underlying condition matches many times.
  </Step>

  <Step title="Select timezone">
    Pick the timezone the check runs in (defaults to the workspace timezone).
  </Step>
</Steps>

### Step 5: Configure actions and delivery methods

Pick which actions to take when the alert triggers:

* **Trigger Alert** — surface the alert in the Alerts page and in any Alert widget on a dashboard.
* **Send Email** — send an email to configured recipients.

Save the alert and it starts checking on the configured schedule.

## The Alert widget

Add an **Alert widget** to any dashboard to surface active alerts on that dashboard. The widget lets a user pick which of the workspace's alerts to display — not every alert has to appear on every dashboard.

* Each alert row shows the alert name and a counter that increases as the alert triggers.
* Clicking an alert row opens a side panel with details:
  * The alert's channels and period.
  * The trigger conditions.
  * A history of every time the alert triggered.
* Each entry in the trigger history can be **marked as read individually**. Marking as read doesn't remove the historic record — it just decrements the notification count on the alert row.
* The side panel has a **Mark all as read** action to clear the notification count in one click.
* Alerts can be edited from the side panel via the **Edit** button.

## Permissions

* **View only** members can see alerts and the Alerts page.
* **View and edit** and **Admin** members can create, edit, duplicate, and delete alerts.

## Troubleshooting

<AccordionGroup>
  <Accordion title="An alert isn't triggering even though the condition matches">
    Confirm the alert is toggled on. Also check the frequency cap — an alert set to "Once per Day" won't fire again after the first trigger of the day, even if the condition still matches.
  </Accordion>

  <Accordion title="Email notifications aren't arriving">
    Confirm **Send Email** is toggled on in Step 5 and that recipient email addresses are added. Check spam folders.
  </Accordion>

  <Accordion title="The Alert widget shows nothing">
    The widget only shows alerts that have been added to it. Open the widget's settings and select the alerts to display, then save the dashboard.
  </Accordion>

  <Accordion title="The &#x22;Monitor metrics against a threshold&#x22; or &#x22;Track metric changes over time&#x22; rule types aren't available for some connectors">
    The **Monitor metrics against a threshold** and **Track metric changes over time** rule types are currently only available for Marketing, GA4, Semrush, and Google Campaign Manager 360 connectors. Other connectors — for example, The Trade Desk — only support the **Track ad account status** rule type.

    Adding a connector to the other rule types requires a roadmap request.
  </Accordion>
</AccordionGroup>