Create an alert
Click New alert. The form is two blocks: Trigger (when this happens) and Action (send an email).- Give it a Name. This is what
{{goal.name}}becomes in the email. - Choose the trigger type and the exact value.
- Write the Subject and Message. Use Insert variable to drop in
{{visitor.country}}and the other tokens. - Click Create alert.
What actually fires it
The value is an exact match. There is no* wildcard here.
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
Email variables
These tokens work in the subject and the message. Unknown tokens are left as you typed them.
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 for a weekly recap or a site-wide spike.
- Goals if you also want the conversion on the dashboard, not only in email.