Thank you for confirming!

Basic question, but I assume Frequency Rules in AJO are applied at a profile level as this is the general way everything is viewed, but wanted to confirm.  I'm looking to cap contacts to per email address and didn't know if this was possible this way.

Thank you for your reply.  Based on this comment how would you recommend I solve for the following use case.Profile A and Profile B share an email address. Both qualify int he audience for Journey 1 which is being sent in incremental waves.  I want to ensure that the email address is only contacted ...

Gotcha, that might work!  Let me play around with that. Thank you!

Thank you for your response, unfortunately I need to do this for a batch audience.  I was continuing to dig into the documentation and saw that was an option for streaming audiences.  Is there any way to do the same for batch?

Hi, I am working in a system where the same email address can be associated with multiple profiles.  The profiles need to be distinct, however for the purposes of this email send I do not want the same email address to be contacted multiple times, even if each profile would qualify independently.  P...

Thanks Somen, I will dig in on those.  Follow up question, once a field is set as identity, it appears that even saying to no longer use it as identity doesn't prevent the stitching from occurring, is there a way to revert to previous state and at least prevent new incoming profiles from being added...

Another question, how does AEP handle multiple identity fields?  If there are 3 fields, 1 matches and 2 do not does it still collapse them based on the lone field or does it recognize there's more that don't match and keep them separate?  Thanks

Thank you for your response, this is exactly what my testing is bearing out.  With regards to your comment if a customer unsubscribes their email on one account and it is not recognized across all accounts would that not potentially lead to legal issues for the various international privacy laws?  R...

I have a use case where the Primary Identity Namespace is a unique ID representing a customer's account. However a customer can have multiple accounts, all with the same email address associated to them, and as a result there are multiple profiles with the same email account. When a customer opts ou...