...
Some guests may have forgotten which email the they used to sign - up with originally. If this feature is enabled, Resorts resorts can allow a guest guests to look up their email by inputting their pass number, as seen below. To enable this function, Aspenware will set the setting: "passMediaLookupEnabled": true, "customerIdLookupEnabled": true. Once . Aspenware will configure Auth0 to enable this function so that once the user selects ‘Lookup email by pass number,' they will be directed to another page to input their pass number, seen as shown below.
...
Create Account with Pass
...
The rewards module in RTP|One is connected to Aspenware Identity v3. If a resort wants to enable a rewards program and enroll guests, an enrollment checkbox will appear on the create customer profile screen. This will then communicate directly with RTP and create an enrollment status of ‘true’ in the module. Please note that the resort must setup their own Rewards module in RTP before Aspenware would enable this feature on the sign-up flow.
Google Analytics
We will track the following google analytics events based on the page location and user action indicated.
...
Title
...
Description
...
Location
...
Type (Page/Event)
...
Sign-in Page
...
When a customer views sign in page
...
Auth0
...
Page View
...
Forgot password page
...
Customer view ‘forgot password’ page
...
Auth0
...
Page View
...
forgot_password_select
...
Customer selected ‘forgot password’
...
Auth0
...
Event
...
forgot_password_submitted
...
Customer sent email to themselves to reset password
...
Auth0
...
Event
...
signin_attempt
...
Customer selects ‘continue’ from sign in
...
Auth0
...
Event
...
signin_error
...
Customer experiences a sign in error, such as password didn’t match, account exists, etc.
...
Auth0
...
Event
...
successful_login
...
Customer has been authenticated and directed to shop successfully
...
AW Cloud UI & Commerce
...
Event
...
signup_selection
...
Customer selects ‘sign up’ in auth0
...
Auth0
...
Event
...
Sign-up Page
...
Customer views sign up page
...
Auth0
...
Page View
...
signup_attempt
...
Customer selects ‘continue’ after input email/password when creating a new account
...
Auth0
...
Event
...
signup_success
...
Customer is successful in creating new account in auth0
...
Auth0
...
Event
...
auth0_account_error
...
Error occurred during sign up in auth0 such as email in use, API error.
...
Auth0
...
Event
...
Customer profile page
...
Customer views create customer profile page
...
AW Cloud UI
...
Page View
...
customer_match
...
Customer submits create profile and is matched to an existing customer in RTP (1 or many)
...
AW Cloud UI
...
Event
...
Customer match (1) page
...
Customer views ‘verification needed’ page after match
...
AW Cloud UI
...
Page View
...
Customer match (many) page
...
Customer view ‘call resort’ after being matched to multiple customers in RTP
...
AW Cloud UI
...
Page View
...
create_profile
...
Customer is successful in creating new customer
...
AW Cloud UI
...
Event
...
Update_Customer_Profile_Error
...
Customer experienced an error at creating a new customer
...
AW Cloud UI
...
Event
...
account_lookup
...
Customer selects ‘look up account with pass’
...
Auth0
...
Event
...
account_found
...
Customer inputs a valid pass and found an account
...
Auth0
...
Event
...
account_notfound
...
Customer input an invalid pass or no account found
...
Auth0
...
Event
...
signupwithpass_invitesent
...
Customer inputs correct pass, has email on file, and has no auth profile
...
Auth0
...
Event
...
Property: error_accountexists
...
Customer inputs a valid pass but account exists
...
Auth0
...
Event
...
Property: error_incorrectnumber
...
Customer inputs a invalid pass number and nothing found.
...
Auth0
...
Event
...
error_noemail
...
Customer inputs a valid pass but no email profile exists to verify
...
Auth0
...
Event
...
Add password
...
When a guest lands on the add password screen
...
...
have added Google Analytics tracking to Identity v3. For more information on the specific additions to the data layer, see
Monitoring & Alerting
Aspenware has set up performance monitoring through Application Insights. Internal teams at Aspenware will be alerted if there are any performance degradations (e.g. 10 sign-in failures within 5 minutes). Aspenware will assess performance on a regular basis to determine trends and consult with Auth0 to determine continual improvements in the system to ensure the delivery of optimal performance for resort partners.
...
All existing (and new) 3rd party applications from Identity v2 are may be added to Identity v3. There are additional requirements and collaboration required between the resort and Aspenware to set up, as listed below:
Steps for Onboarding 3rd Party Applications
Resort completes the application section on the onboarding form and sends to Aspenware.
Application Description
Application type
Callback URL
Logout URL
withScheme
Aspenware sets up Auth0 applications for the Resort 3rd party application.
Aspenware will provide resort with connection name and scope to put in their application(s) code-base.
Resort Dev team to set up application using Auth0 guidelines
Resort Dev team to test
The documentation for setup can be found /wiki/spaces/PLA/pages/3188031491See the Identify v3 (Powered by Auth0) Configuration Guide for details about setup of this feature.
Theming
Aspenware will theme the resort Auth0 pages based on the criteria submitted via Theme Designer. If the resort is a current Aspenware customer, most of the information can be utilized from Identity v2, but some new information will be required.
...