Click-Through and validation processes

Follow

This article shows some practical examples dealing with Click-Through and account validation processes. Currently the following validation modes are supported:

  • Email
  • Validation code via SMS

In the following examples we discuss the Email validation, but most of the cases apply to the Validation code via SMS as well.
Please note that you can find an example of code-based validation in the following article: Validating an end-user's mobile phone number with a confirmation code.

If you are not familiar with Access Templates and Control Panel settings, please visit the following page: Access Templates and Sign-Up Options before proceeding with this article.

 

Example #1: Email validation set before the first access

In this case we consider a Venue associated with an access template via Click-Through. Additional fields and Email validation are not set.

First access

The email-based validation is enabled, so the Email address field is required the first time, even if it is not specified as Additional fields.

Then the Splash Portal asks the end-user to complete the validation process.


Next accesses

The Email address field is asked until the validation process is completed. After this action is done, the field is not asked any more.

 

Example #2: Email validation set after the first access

In this case we consider a Venue with an access template via Click-Through with no Additional fields or validation set. So users can sign up without providing any data.
Later, at a certain time, the Email validation is enabled.
Please understand how the Splash Portal works in this situation.

First access

As already mentioned, no Additional fields or validation methods are enabled at the beginning, so end-users are able to sign-up without providing any data.

 

Change of configuration

After the first access the Account validation mode is set to Email. This action can be done through the Control Panel, by modifying the active Access Template

Second access

Now the email-based validation is active, but no email address is specified in the end-users' accounts previously registered.
If the end-user opens the Splash Portal with the same device used during the first access, then Cloud4Wi is able to detect it by recognizing the device's MAC address, and retrieving the details of the end-user, even if he is not authenticated yet.
The validation requires the Email address field to be specified and as a result, this field is now required by the Splash Portal.



Next accesses

The Email address field is asked until the validation process is completed. After this action is done, the field will not be asked any more.

Have more questions? Submit a request

Comments