on ‎2021 Jan 15 9:49 AM
Hello Gurus,
Our client has in his ECC system, many contacts for the same account have the same email address. So when we create a target group and we send an email campaign the same email address will receive the same email as many times as the number of the contacts with same email.
There's a note : https://launchpad.support.sap.com/#/notes/2448963 , but it's not working if the target group number is bigger than 2. Our scenario, we have 50K contacts and many contacts have the same email, so the Reduce randomly does not work as expected : It deletes some good contacts and leaves the duplicated ones.
Is there any other solution ?
Best regards
Request clarification before answering.
Hi Anas,
If I'm understanding you correctly. You don't want the contacts to be deleted in SMC but you want to select the SMC to select the 'best' contacts and only sent out e-mails to those contacts, correct?
If that is the case you indeed should work with the KBA you mentioned. You should recreate the 'Ranked Duplication' part.
Did you already enable using emails as a secondary distinction?
If no, you should enable this first via the segmentation configuration for the related segmentation profile.
If yes, could you provide more details where it is going unexpected?
The number one in the KBA is not referring to the amount of your target group. It is telling the system: 'out of your total target group reduce the group by only allowing only one contact per one e-mail adress' So the solution provided in the KBA should also work for your use case.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Anas,
as mentioned by Jef, I would also say that the approach in the KBA mentioned by you should work for you.
Regarding the Secondary distinction:
1. Go to your "Segmentation Configuration" app
2. Select "Segmentation Objects and Attributes"
3. Select the Segmentation Object on which your Segmentation Profile is based on (e.g. Contacts)
4. Scroll down to the part "Secondary Distinction Entities" (it is below the Attribute Groups section)
5. Create/Add a new Secondary Distinction and name it for example EMAIL and select the Data Source where your attribute is included (e.g. the email address for Contacts in the _SAP_CF_CE_CONTACT_IA_ERP_CUST (if you have custom fields))

6. Select your created Entry
7. Add a new Key/Position in the Secondary Distinction Entity and Search for the Attribute (e.g. SMTP_ADDR as the email address of the contact)

8. After these steps you should find that Entity in your segmentation if you choose to create a Segment by the "Reducing Randomly" operation.

Hope that helps.
BR Tobias
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
We created a target group TG1 using the "Reduce randomly", and then we created another target group "TG2" from the same segmentation tree. As the documentation says, we created two dependent target groups.
After launching the email campaign that uses TG2, we got this log :

And one of the contact's got two emails at once :

Is this issue caused by the dependent target groups ?
Best regards,
Anas
Hello Jef,
Thank you for your response.
1- Yes don't want to delete contacts in SMC even if they have the same email, because they belong to the same account. But we don't want to send email to the best contacts, we want to send emails just once per email adress :
Exemple : Contact 1 -> company@company.com / Contact 2 -> company@company.com / Contact 3 -> company@company.com
We want to send only one email to the email address "company@company.com" (whoever the contact selected is)
2- No we didn't enable "Secondary distinction". Could please explain what does this function do ?
3- "The number one in the KBA is not referring to the amount of your target group. It is telling the system: 'out of your total target group reduce the group by only allowing only one contact per one e-mail adress' So the solution provided in the KBA should also work for your use case" :
Actually this is not our case, if we use the "Reduce randomly" and we set the number as 1, we have only one contact as result. Please see screenshots below :


Best regards,
Anas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Anas,
As mentioned by Tobias you should enable it via the segmentation configuration. The secondary distinction is the function that will enable you to filter down to one unique e-mail adress. After you have set up the secondary distinction as Tobias mentioned you should be albe to segmentate as follow.
Looking at your screenshots you haven't done this and this is why you cannot choose 'per reference object'
1. Select the attribute 'Email'
2. Create segment - by reducing randomly - per reference object = reference email
3. Create
As you can see on the screenshot we had 5.175 contacts and after reducing based on unique email we only have 2.339 contacts. I

| User | Count |
|---|---|
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.