Depending on the data quality of your contact database, you may have different contact with the same email address. From Gabelhorn V1, SAM will ensure that your not spamming your subscribers and will make sure to not several
send : Add a new deduplication step : when sending an email campaign, filter out contact that have the same email address
SAM: Add a new deduplication step : when sending an email campaign, filter out contact that have the same email address
What are we trying to solve here ?
Our customer have a lot of contacts in SecuTix and the email address is not guaranteed to be unique in SecuTix (expect if it is also used as login) but not having means that we can have a situation where we have 2 contacts (or more) with the same email address. The problem with this situation is that if you send an email campaign with the target that contains contacts with same email addresses, then this email address will receive 2 emails... which does not make sense.
So the goal of this user story is to solve this problem by implementing an addtionnal check in SAM where we will make sure that in a situation as described above only 1 email will be sent.
How are processed the advantages with this new fitlering rule ?
Advantages will be linked to all contacts even the what we call duplicate in this particular case. the duplicate will not receive the email, only one email will be sent for each email address.
What about advantage with code in the email ?
Here we need to discuss in the team a bit more. My understanding is that right now the batch is working the following way :
- Link advantages to contact
- Filter out contact that should not receive an email
- Create and send shipments (only to remainging contacts after the filtering)
The question is at step 1. what is happening in the case of the invitation code ? For now my guess is that we are generating the codes but as we will not send them to some contacts they will not receive it. which is ok, let's discuss this during the next daily.
