Hi Erika,

You can probably build a second workflow based on an Experience ID Change Event triggered by interactions created and constrained by conditions related to your first workflow if you don’t want to receive emails for each transaction created in your directory.

Hi Erika,

In addition to ​@vgayraud ‘s solution above, you could include additional tasks within the same workflow to distribute emails tied to the transactions right after they are imported. I am assuming you are using a file import based on your mention of the “Add Contacts and Transactions to XMD” task.

Your workflow would look something like the following flow:

1. Extract file task (Extract from SFTP, Extract from Qualtrics File Service, etc)
2. Load contacts and transactions to XM Directory task
3. Create a sample task (for each distribution group if needed)
   1. If you want to only distribute survey invites to certain segments of the imported contacts, or if you want to have different email templates for certain segments, this task can be used to create a segment for each group with filters. If you have multiple groups to send different emails, you would need multiple sample tasks in the workflow (one for each distribution group).
   2. If all imported contacts should receive the same email, then this task would not be necessary.
   3. If using this task, you would want to select the output from Step 2 above as the data source.
4. Send a survey via email task
   1. If using samples described in Step 3 to create segmented distribution groups, you would need to have one of these email tasks for each sample task.
   2. If not using samples and instead sending to the same distribution to all imported contacts, then the source for this task should be the transaction batch created in Step 2.

Here is what the configuration would look like for a distribution that does not use samples.

Thank you so much guys!