0

So, I need to be able to send out an email that could include an individual with different purchases. I set-up a SubscriberKey that is unique and links to the Subscriber Key and not the email address.

That was my understanding of how I can send an email multiple times to the same email address. Below is my data extension set-up:

enter image description here

I've added test data to the DE with my personal and work email twice with each one having a unique SubscriberKey. I should receive 4 emails, 2 to each email address. However, I only receive 1 email for each email address.

I know this has to be something simple that I'm overlooking. Any ideas?

2
  • 2
    How do you send your emails? If from Journey Builder, then those won’t be deduplicated... if from Email Studio, there is an option in the flow to turn on/off deduplication by email address
    – zuzannamj
    Feb 26 '20 at 19:56
  • In Journey Builder that runs daily. Each day a new set of contacts are uploaded and on some days a user might show up twice but each time the contact has a unique Subscriber_Key which is set to be the Primary Key. Feb 26 '20 at 20:18
1

Consider the below scenario,

"A bank want to send a monthly balance statement to all its customers. But, imagine all 4 members in a family share a COMMON email address! [see example below] Where in 2 families with both having 4 members, but have a common email address per Family." enter image description here

So you can leverage the concept called COMPOSITE KEY [in simple combination of Primary Keys]!

enter image description here

So with this approach, by disabling the De-duplicate option as below, enter image description here

I was successfully able to get 4 emails for each email-address! In practical all 4 emails with have separate Balance and FirstName as below. enter image description here

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.