Verify

  • Updated

Verify validates the email addresses your visitors enter within the access journey. If the email address is not valid, you can choose to block access to the WiFi for that visitor. This ensures the data you gather from your visitors is more accurate and provides you with valid email addresses for follow up communications such as NPS surveys. To enable this feature please contact your account manager.

License required: Capture or Engage + Verify

See the benefits of Verifying your visitors' email addresses as they log in

Add Verify to an access journey

To use Verify you must select Enable Verify email verification on the access journey.

1. Click Onboarding > Access journeys and select which access journey to add Verify to.

2. Click Options and select Enable Verify email verification.

Verify.png

3. If you want to block access to the Wi-Fi for visitors who enter an invalid email address, select Block email addresses that are reported as undeliverable by Verify.

The visitor receives an error when they try to enter an invalid email address and they cannot gain access to the Wi-Fi until they enter a valid email address.

Neverbounce_access.jpg

 

If you don't block access this allows the visitor to log in to the Wi-Fi with an invalid email

address but marks the email address as invalid on the CRM/WiFi Users record.

4. Save and Publish the access journey. For more information, refer to Access journey.

CRM/WiFi Users record

If a user logs in when Verify is active, the CRM/WiFi Users record shows if an email address is valid or not.

Neverbounce_crm.jpg

 

Verify - Email status definitions

The following 5 status definitions are used when email addresses are verified by the Verify feature.

Email Status Definition OK to Send?
Valid

The email address is verified and is an existing address that accepts mail.

Yes

Invalid

The email is verified as non-existent or not accepting mail, leading to bounces.

No

Disposable

The email is temporary, often a fake account used to avoid using a personal email (e.g. Mailinator, Guerilla Mail etc.).

No

Catch-all (Unverifiable)

Email validity can't be confirmed; it is a domain-wide setting that accepts any email for that domain.

Maybe

Unknown

The email's status is impossible to determine after multiple checks or the server can't be reached.

No

Additional Context for Catch-all Results

Handling "Catch-all" emails depends heavily on your data quality and infrastructure:

The percentage of ‘Catch-alls’ is directly correlated to the amount of ‘Invalid’ emails within a set of data. The higher the invalid rate, the more likely the ‘Catch-alls’ are to bounce. If you have a fairly clean list, the ‘Catch-alls’ have a better chance of being ‘valid’ results. ‘Catch-alls’ tend to bounce at half the rate of your original invalid percentage.

SAFE - If you have a dedicated email server with your own IPs, catch-all emails may be safe for sending dependent on the overall health of your list.

DON’T SEND – If you use a third-party email provider that requires a bounce rate below 4%, these emails are not safe for sending.

Share online:
Was this article helpful?
1 out of 2 found this helpful