To build a trigger-based journey that sends "Getting started" emails when an opportunity is marked

as "Won," the appropriate trigger to use is the Dataverse record change trigger. This trigger is

specifically designed to initiate actions based on changes in Microsoft Dataverse records, which are

integral to Dynamics 365.

Here’s the detailed reasoning:

Dataverse Record Change Trigger:

The Dataverse record change trigger is used to initiate journeys when there is a change in a record

within Dataverse, such as an opportunity's status.

Since the requirement is to send a "Getting started" email once an opportunity status changes to

"Won," this trigger can detect the status update in real-time.

Using this trigger, you can specify the criteria for the journey to start, such as filtering for

opportunities with a status of "Won," thus automating the email sending based on this condition.

Why Not Other Triggers?

Custom trigger with lead profile data and Custom trigger with contact profile data: These are

generally used for initiating journeys based on custom events or data points outside of standard

Dataverse records, which isn’t applicable here as the journey is triggered by an opportunity status

change, a native Dataverse record.

Email Link Clicked Interaction Trigger: This trigger is used to follow up after an email link is clicked,

which does not align with the scenario. The journey must start based on an opportunity status

change, not email interaction.

Microsoft Dynamics 365 Reference:

Create and manage trigger-based journeys

Work with Dataverse triggers in journeys

By using the Dataverse record change trigger, you ensure that the journey aligns directly with the

sales process and automatically sends the "Getting started" email when an opportunity reaches the

"Won" status, as requested by the global sales lead.