Skip to content

Commit 885087b

Browse files
authored
Updates from feedback
1 parent 4770952 commit 885087b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/communication-services/quickstarts/email/handle-email-events.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -88,9 +88,9 @@ To generate and receive Email events, take the steps in the following sections.
8888

8989
### Trigger Email events
9090

91-
To view event triggers, we need to generate some events.
91+
To view event triggers, we need to generate some events. To trigger an event, [send email](../email/send-email.md) using the Email domain resource attached to the Communication Services resource.
9292

93-
- `Email Delivery Report Received` events are generated when the Email is status is in terminal state, i.e. Delivered, Failed, FilteredSpam, Quarantined. To trigger an event, send an email using the Email domain resource attached to the Communication Services resource.
93+
- `Email Delivery Report Received` events are generated when the Email status is in terminal state, i.e. Delivered, Failed, FilteredSpam, Quarantined.
9494
- `Email Engagement Tracking Report Received` events are generated when the email sent is either opened or a link within the email is clicked. To trigger an event, you need to turn on the `User Interaction Tracking` option on the Email domain resource
9595

9696
Check out the full list of [events that Communication Services supports](../../../event-grid/event-schema-communication-services.md).

0 commit comments

Comments
 (0)