A phone number attribute allows customer to enter and validate a phone number easily.
Example configuration in the Admin Console:
In the customer journey:
Configure when creating the attribute
The following settings can only be changed until the attribute is added (saved for the first time) to the identity store. You will find these settings disabled when you return to edit existing attributes.
Attribute type: Defined when selecting the attribute type before any further settings are displayed.
Attribute path: The storage path that's created for the attribute in the Identity Store. Used in combination with the Attribute name to lead Lifecycle Event Hooks to the right place.
Attribute name: The name of the attribute in the Identity Store. Used in combination with the Attribute path to provide access for Lifecycle Event Hooks.
Indexing: Custom attributes can be made searchable by setting up an indexing option.
Search (Unique): Set indexing to unique if you want the attribute to be searchable AND the value of your string to be unique for each account. (Each customer has to provide a unique input e.g. card IDs.)
None: The attribute will not be searchable in the account search menu.
You can add a maximum of 5 indexed attributes to an identity store. Indexing can't be revoked once added.
Configure any time (with caution)
We advise caution when managing account attributes: editing the identity store schema can have adverse effects on your customer experience.
Enable attribute: Switch the attribute on or off: if disabled,
it will be hidden from self-service and the Admin Console
it will not appear in the customer journey at a Pre-Progressive Pofiling event
customer data will not be mapped from social profiles
customer data will not be available for Lifecycle Event Hooks
Name claim: This is the corresponding Native Claim that will govern this attribute. It obtains the related customer data from an external provider and maps the value to the attribute.
Attribute display name: The name of the input field displayed for customers.
Make the attribute mandatory: Choose whether to make this attribute mandatory or not. If made mandatory, a customer has to enter a value at self-service registration or the next login.
Mandatory attributes are added to the login workflow with a progressive profiling step: customers are shown fields they need to fill out to continue their journey.
Adapt the default progressive profiling experience to your needs with the new Pre-Progressive Profiling event we've added to supported lifecycle events.
Show attribute during registration: Choose whether to display this attribute during self-service registration or not.
Show attribute in My Account: Choose whether to show this attribute in a customer's self-service account or an admin user's My Account portal.
Show attribute in Admin Console: Choose whether to display this attribute for the customer account at administrative account handling.