Avoid duplicate emails in email invite automation.

In the process point 3, have you added any filter criteria to send only to respondents where some embedded data is equal to something?

Moreover, this use case should be based on customer rather than purchase number. So, customer basic data should be created in first import and then all other purchasing data should be considered as transaction data and while distribution new transations should be distributed. 

Hi @rondev , thanks for your response. Yes, we are using some filter criterias. Like surveySentflag=True, isdeleted=false, emailoptout=false and survey participants = (6 different logic values here). 

Since you are saying we need to upload other informations as transaction data. If we will upload all data as transactional information instead of contact then how we will pull those information in the survey embedded field. Because transaction data cannot be pulled easily into the survey. And can you please share some screenshot to understand how I can manage that distribution?

With respect to current process, are we then turning any flag to fals, so that, that contact is not picked in the next cycle.

Transaction data  can be pulled easily in survey and it gets pulled just like embedded data, It is just we need to make sure that they are uploaded as transaction data via import automation or XM directory task.

Is there any way to turn flag as negative just after sending invite or we will need to do pass this value from APP only?

Also regarding transaction data. I tried this. I passed the value as transaction data and created same embedded field in survey. But those fields were blank. Can you please share the process to handle this?