What's New in Alerts

Last Updated: November 18, 2026

We’ve updated how Alerts work in EarthRanger Web. You can now choose exactly which changes should send an Alert, and limit Alerts to Events in a specific area, so you get fewer messages and more signal. Read on for what’s new and what to check in your existing Alerts.

Fewer Alerts, more signal

Alerts work best when each one means something. With this update, you choose exactly which changes should send an Alert, so the ones you receive are the ones that need your attention. You spend less time sorting what matters from what doesn’t, and you can trust an Alert is worth opening.

Heads up: your existing Alerts will change

After the update, your existing Alerts are sent only when a matching Event is first reported. They no longer send when an existing Event is edited.

This matters most if you rely on Alerts for updates, for example:

  • An Alert with no Conditions that used to be sent every time a matching Event was saved.
  • An Alert with Conditions that used to be sent when a field used in a Condition changed.

If either of these describes your setup, take a few minutes to review those Alerts and choose which changes you want to be notified about (steps below). Nothing is deleted: your Notification Methods, Event Types, Conditions and schedules stay exactly as they are.

If you manage Alerts for other people on your site, ask them to review theirs too.

What's new

Triggers

A new Triggers section sits above Conditions when you create or edit an Alert. Every Alert starts with Event Created, and you can add Triggers for changes to specific fields on the Event Types you selected, such as Update to: Battery Level (%). The Alert is sent when any of its Triggers occurs.

Triggers and Conditions work together

Triggers and Conditions answer two different questions. Triggers decide when: they are the moments EarthRanger checks an Event, such as when it is created or when a specific field is updated. Conditions decide what: they are the requirements the Event must meet before an Alert is sent. An Alert is sent when any Trigger occurs and all Conditions are met.

For example, here are a few ways to use them:

Goal

Trigger (when)

Condition (what)

Be notified only when a carcass’s cause of death is not natural

Event Created

Cause of Death Is One Of the unnatural causes

Be alerted when a camera trap battery is low

Update to: Battery Level (%)

Battery Level (%) ≤ 5

Know when an Event moves up in priority

Update to: Priority

None

Be alerted about a low battery on a new camera trap report or on a later change

Event Created and Update to: Battery Level (%)

Battery Level (%) ≤ 5

Notify different people depending on where an Event happens

Event Created

Geographic Feature or Feature Group Is One Of the areas you select

With more than one Trigger, the Alert is sent when any one of them occurs. With Conditions, all of them must be met.

Send Alerts based on where an Event happens

You can now limit an Alert to Events inside a Geographic Feature or Feature Group, so different people can be notified depending on where something happened. To set it up, add a Condition for the area you care about.

Helpful tips in the window

Information icons next to Triggers and Conditions explain how each works, right where you are setting them up.

For the full setup steps, see Setting Up Personalized Alerts for Specific Events.

Keep your update Alerts working

To keep getting Alerts when an existing Event changes, add a Trigger for each field you want to watch.

  1. Open Alerts from the Menu or from Settings.
  2. In the Alerts list, select the pencil icon next to the Alert you want to update.
  3. Go to Triggers and select the +.
  4. Choose the field to watch, for example Battery Level (%).
  5. Check your Conditions. They still apply, so the Event must meet all of them for the Alert to be sent.
  6. Select Save.

Repeat for each Alert that should react to updates. If an Alert only needs to tell you when a new Event is reported, no change is needed.

Note: An Alert with no Triggers is never sent, so keep at least one in place.

Important: You can receive up to 20 Alerts per day. A Trigger on a field that changes often can use them up quickly, so pair it with a Condition to keep only the Alerts that matter.

Before and after

Your Alert

Before the update

After the update

To be notified of updates again

No Conditions

Sent every time a matching Event was saved

Sent when a matching Event is created

Add a Trigger for each change you want to be notified about. The Alert is sent when any one of them occurs.

With Conditions

Sent when a field used in a Condition changed

Sent when a matching Event is created

Add a Trigger for the field used in each Condition. The Alert is sent when any one of them occurs and all Conditions are met.