Contents
What are the default profile attributes in the Marketing Cloud?
By default, every account has three profile attributes: Full Name, Email, and UserDefined, which is intended as a generic attribute that you can use as needed. By default, every account also receives an HTML Email preference attribute that is set to Yes. You can’t modify these attributes.
What is a profile center?
Profile centers are default link available in the emails which we send via marketing cloud. This link redirects the user/subscriber to the webpage which contains information of that specific user. In the detailed webpage, subscriber sees all the attributes that are defined in your account and are not marked as hidden.
Why do you need a custom profile center?
Your custom profile center allows you to both manage information inside your Marketing Cloud account and use that information to conduct triggered sends as confirmation of more or changed information in a particular profile. The automation allows the user to keep their information up to date without involving more effort from your team.
What are the attributes of a user profile?
A globally unique identifier (GUID) that is the unique identifier for the user. Example: 12345678-9abc-def0-1234-56789abcde. Read only, Immutable. A list of other email addresses for the user. Example: [“[email protected]”, “[email protected]\\. NOTE: Accent characters are not allowed. The password for the local account during user creation.
How is the mail attribute populated in Azure AD?
mail attribute: It’s an attribute in Active Directory, the value of which represents the email address of a user. mailNickName attribute: It’s an attribute in Active Directory, the value of which represents the alias of a user in an Exchange organization.
How to use user profile attributes in Azure Active Directory?
Use this attribute to get a user with sign-in value without specifying the local account type. The unique username of the local account user in the directory. Use this attribute to create or get a user with a specific sign-in username. Specifying this in PersistedClaims alone during Patch operation will remove other types of signInNames.