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

# Email alerts for conversions

> Email the workspace owner when a visitor opens an exact URL path or sends an exact event name. You can create up to 10 alerts on Starter and above.

The Alerts tab emails the **workspace owner** when a visitor hits a trigger you choose. This is not the traffic-spike email. That one lives under **Settings → Reports**.

Open **Settings → Alerts**. Alerts need a Starter plan or above. You can create up to 10. You need permission to configure the site (editor, admin, or owner).

## Create an alert

Click **New alert**. The form is two blocks: **Trigger** (when this happens) and **Action** (send an email).

1. Give it a **Name**. This is what `{{goal.name}}` becomes in the email.
2. Choose the trigger type and the exact value.
3. Write the **Subject** and **Message**. Use **Insert variable** to drop in `{{visitor.country}}` and the other tokens.
4. Click **Create alert**.

## What actually fires it

The value is an **exact** match. There is no `*` wildcard here.

| Trigger in the form | Fires when | Value to type |
| - | - | - |
| A visitor opens a URL | A pageview arrives whose path equals the value | `/checkout/success` |
| A custom event is sent | A non-pageview event arrives whose name equals the value | `purchase` |

A URL trigger only looks at pageviews. `/checkout/success` does not match `/checkout/success/`. A visit to `/checkout/success?ref=1` still matches, because the path is `/checkout/success`.

A custom-event trigger matches the event name. That includes events you send yourself and the built-in names `payment`, `identify`, `external_link`, `file_download`, and `form_submission`.

Bots do not fire alerts. Heartbeat and engagement pings do not fire alerts. Each matching event sends one email (not a daily digest).

## Try an exact match

A visitor opens a URL
A custom event is sent

Value in the alert

## Email variables

These tokens work in the subject and the message. Unknown tokens are left as you typed them.

| Token | What the owner sees |
| - | - |
| `{{goal.name}}` | The alert's **Name** |
| `{{visitor.name}}` | A generated label for that visitor, such as `azure meadowlark` (not a real name) |
| `{{visitor.country}}` | The country code from the visit, or `an unknown location` |
| `{{visitor.device}}` | Device type, or `unknown device` |
| `{{visitor.browser}}` | Browser, or `unknown browser` |
| `{{visitor.referrer}}` | Referring hostname, or `direct` |
| `{{visitor.channel}}` | Channel, or `Direct` |

Line breaks in the message become separate paragraphs in the email.

## Send test and Remove

**Send test** emails **you** (the person who clicked), not the owner. The subject is prefixed with `[TEST]`. The body uses sample values (`United States`, `Chrome`, `google.com`), so a test is not a live visitor.

**Remove** stops future emails. It cannot be undone. Events that already matched are not replayed.

## Next steps

* [Email traffic reports](https://help.trfyx.com/reports.md) for a weekly recap or a site-wide spike.
* [Goals](https://help.trfyx.com/goals.md) if you also want the conversion on the dashboard, not only in email.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.