Go to Main Contents

:: Industry developments

What exactly should the company collect on the Portal page?

When a company deploys Portal authentication, the user register page is a common design problem for which fields to collect. More users complain about poor experience, less collection and less business needs and security

Your position:Home > Content Centre > Industry News > > Text

When a company deploys Portal certification, the user register page is a common design question for which fields to collect. More users complain about poor experiences, less collection of business needs and security compliance requirements.

First, you have to distinguish between two scenarios: internal employee certification and visitor certification."Authentication"——This person is not a company employee, and his network privileges are at what level. So the employee Portal page usually requires only one account password or a cell phone number for secondary validation. The fewer fields, the faster certification speed, the higher acceptance of employees.

Visitors are completely unknown to the company, and Portal pages require more information. The basic cell number can be used to verify and send a authentication code, but only the cell phone number is far from sufficient when it is safely traced.——Many company visitors collect cell numbers, and the security incidents are traced with a bunch of cell phone numbers, which ultimately all involve operator prepaid card sections and are completely impossible to match with the specific visitor.

The user information collected by an enterprise on the Portal page is personal and requires that users be clearly informed of the use they are making to collect it, as required by relevant regulations, and authorized by the user. If a mobile phone number is collected on the Portal page for authentication, but the back desk uses this cell phone number for marketing or recording information, which is over-exploitation and compliance risk. It is recommended that privacy policies and usage provisions be added at the Portal design stage to provide clear information about the purpose, duration and extent of collection of information to users.

With regard to the number of fields, there is a practical experience: for each additional mandatory field on Portal certification pages, users’ certification completion rates are reduced by several percentage points. The more domains are available for non-mandatory authentication sites such as visitors, the lower the proportion of users willing to voluntarily complete certifications. Many businesses have made Portal pages as complex as registration forms to gather more information, and instead of filling in 4G networks, visitors lose control over their network. It is better to distinguish between mandatory entries and selected entries, such as mobile phone numbers, and other messages as optional entries, so that users can fill out better than complete authentication without filling them.

Finally, let us talk about the strictness of field authentication. The mobile numbers on Portal pages are used for many types of text message identification codes, but text messages have delayed and failed, especially in areas with bad signals. If SMS authentication codes are used as the only means of verification, a large number of users at peaks can line up to authenticate them simultaneously, and the user cannot wait for the code.

Access Program I'll be right back. Telephone counselling