...
A batch to remove or anonymize non-validated contacts can be run by setting the parameter in green below to the desired sunset or legal duration
Use cases
How will this work for Guest checkout?
No verification mail is sent to Guests. The email will be stored as "unverified" in the contacts base and cannot be used to log in the Ticketshop
How will this work for quick checkout / on-sale processes?
The verification mail will send at first login from the customer. No verification is required at the time of the checkout / on sale process
- When a user has both a B2C (final customer) and a B2B (relay) account with the same email address, will the validation be valid for all accounts?
- No. Validation is per account, not per email address. This means that each account will need a separate validation
- On sales channels requiring opt-in validation will the end user receive one or two validation emails?
- The end user will receive two separate mails as these are two separate and independent processes
- When creating an emergency account in TIXNGO that will be injected back in S360, will the account be already validated?
- Yes. A TIXNGO imported account will be considered as validated
External Identity Provider (Customer SSO)
- What happens in the case of a customer who uses a third party SSO?
- This functionality only applies to Secutix managed accounts.
- For SSO linked account we assume that the email confirmation was done with the original IDP, i.e. the third party SSO owner. Thus in S360 we store a "email validated = true" flag by default for federated identities (third party SSO managed).
- If customers use a third-party SSO on some of their ticketshops but not all then the functionality could be ON, right? Can we confirm there is no impact on sales channels with external SSO active?
- Same answer as above
- Can the email validation be activated only for some sales channels?
- No. The email validation feature is activated at institution level
Migration
- How will we proceed to the activation of this function ?
- New institution will have this setting activated by default
- Existing customers will need to plan a migration sometime during the one year sunset period starting in September 2024. This means we will force email validation for everybody by September 2025 to be GDPR compliant
- Please contact your CSM to plan this migration ahead of the end of the sunset period
- It is important to know that existing customer's end users will have to validate their email has soon as they perform a new action after the migration such as printing their ticket for their next event
- Would it be possible to mark all existing contacts as “confirmed e-mail address” – as they are currently considered “confirmed” in SecuTix ?
- This is not allowed as it defeats the whole purposes of confirming the mails
- Asking customers to anonymize their contacts, as required by law, can be challenging for some of them. If they do not send an email, will only the active customer get the new e-mail validation process to follow when doing an action on the ticketshop ?
- Yes. Only customers trying to log in the ticketshop will get the email validation message
- What happens to contacts whose e-mail address is not validated ?
- They remain labeled as "not verified" and cannot log to the ticketshop
- Will they be automatically anonymized after a certain period of time ?
- No. You have to regularly run the Removal / anonymization of inactive contacts batch