I use a sendable Data Extension as an entry source for a journey. This DE contains SubscriberKey and EmailAddress, and we've configured the data extension settings so that SubscriberKey in the DE relates to SubscriberKey in SFMC (it was required).
My understanding is that when we send an email through this journey, a subscriber will be created, and they will appear in the "All Subscribers" list in Email Studio.
My question is: Will this subscriber also appear in "All Contacts" in Contact Builder with a ContactKey identical to the SubscriberKey from the DE used for sending? If so, why the SubscriberKey is not just called ContactKey?
I'm asking because we are implementing mobile push notifications and SMS in our project. We need to ensure that the same ContactKey is associated with the email, device ID (for push), and mobile number (for SMS) to avoid duplicating contacts. What is the best approach to achieve unified contact management under a single ContactKey across multiple communication channels in SFMC?
Thanks!