MENU
A financial services customer states that families often share email addresses across multiple checking, savings, loan, and credit accounts. The customer needs to allow individual accounts to use the same email address in Marketing Cloud but maintain separate subscriber attributes.
Which component should be discussed with the customer to allow for this use case?
Suggested Answer: A, C, D
Get Premium CRT-250 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
29 comments · newest first
BR
Brett
10 months ago
Not sure if this will really solve the issue though.
LE
Levi
11 months ago
Contact ID might work too, but Subscriber Key seems better.
FR
France
11 months ago
Wait, can you really have multiple accounts with the same email?
CA
Candida
11 months ago
Definitely need to use Subscriber Key for this!
GL
Glendora
11 months ago
I agree, Subscriber Key is the way to go.
VA
Valene
11 months ago
I feel like Member Record was mentioned in our study materials, but I can't recall how it fits into this specific case.
NO
Noel
12 months ago
Data Extensions could be useful for storing additional attributes, but I don't think they directly address the email sharing issue.
DU
Dudley
12 months ago
I'm not entirely sure, but I think Contact ID might also be relevant in some scenarios. We had a practice question about that, right?
DO
Doyle
1 year ago
I remember we talked about how Subscriber Key can help differentiate between accounts using the same email. It seems like the right choice here.
WI
William
1 year ago
The Member Record seems like it might be relevant, but I'm not sure how it would apply in this specific use case. I'll need to review the details more carefully.
MA
Marsha
1 year ago
Data Extensions could be the answer here. That would let the customer store the separate subscriber attributes for each account, right? I'm not 100% sure, but it's worth considering.
AB
Abraham
1 year ago
Okay, I think I've got it. The Subscriber Key is the way to go here. That will allow the customer to maintain separate subscriber attributes while using the same email address across multiple accounts.
FI
Filiberto
1 year ago
Hmm, I'm a bit confused. I was thinking the Contact ID might be the right component, but now I'm not so sure. I'll need to think this through a bit more.
YU
Yuki
1 year ago
This seems like a tricky one. I'm not sure if I fully understand the use case, but I think the Subscriber Key might be the way to go here.
WE
Werner
2 years ago
Ooh, this is a tough one. I bet the marketing team is having a field day with all these email addresses! Maybe they can use them to send out coupons for family discounts or something.
EV
Eve
1 year ago
C) Member Record
TW
Twanna
1 year ago
I think using Data Extensions would be the best way to handle this situation.
LA
Laine
1 year ago
D) Data Extensions
VA
Vallie
1 year ago
B) Contact ID
TA
Tammi
1 year ago
A) Subscriber Key
VE
Veronica
1 year ago
A) Subscriber Key
IZ
Izetta
2 years ago
Subscriber Key seems like the obvious choice to me. That's what it's designed for, right? Keeping subscriber data separate even with shared email addresses.
DE
Delmy
1 year ago
I agree, Subscriber Key is the way to go for this use case.
OC
Octavio
2 years ago
Yes, you are correct. Subscriber Key is the best option for maintaining separate subscriber attributes.
FA
Fannie
2 years ago
I'm not sure. Maybe we should also consider Data Extensions for this use case.
HO
Howard
2 years ago
Hmm, I'm not sure. This sounds like a tricky one. Maybe Contact ID would work, but I'm curious to hear what the other candidates think.
AN
Andra
2 years ago
I think Option D, Data Extensions, is the way to go here. That'll let the customer maintain separate subscriber attributes while still using the same email address.
RE
Rebecka
2 years ago
I agree with Junita. Subscriber Key would allow individual accounts to use the same email address but maintain separate attributes.
JU
Junita
2 years ago
I think we should discuss Subscriber Key with the customer.