...
Identify v3 (Powered by Auth0) includes robust Google Analytics tracking. The following events are included in the data layer.
Location | Event Name | Project | Schema / Message | Use Case |
Login | successful_login | Commerce |
| User has signed in successfully and landed on store |
Login | error | Auth0 | errorType: "signin_error," "errorMessage": "{message}" | User has encountered an error, password or API |
Sign-in Page | n/a | Auth0 | When a customer views sign in page | |
Forgot password page | n/a | Auth0 | Customer view ‘forgot password’ page | |
Forgot Password | forgot_password_submitted | Auth0 |
| User has sent a password reset email |
Sign up | signup_selection | Auth0 |
| User has selected 'sign up' |
Sign up | signup_success | Auth0 |
| User has created an account in auth0 (email/password) |
Sign up | create_profile | Commerce |
| User has created a customer |
Sign up | successful_login | Commerce |
| User has been authenticated and logged in successfully and landed on store |
Sign up | error | Auth0 | errorType: "auth0_signup_error," "errorMessage": "{message}" | User has encountered an error, user exists or API |
Customer profile page | n/a | AW Cloud UI | Customer views create customer profile page | |
Customer Matching | signup_success | Auth0 |
| User has created an account in auth0 (email/password) |
Customer Matching | create_profile | Commerce |
| User has created a customer |
Customer Matching | customer_match | Commerce | { "event": "awc_customer_match", "type", "#"} | User has matched to a customer in RTP |
Customer match (1) page | n/a | AW Cloud UI | Customer views ‘verification needed’ page after match | |
Customer match (many) page | n/a | AW Cloud UI | Customer view ‘call resort’ after being matched to multiple customers in RTP | |
Account Lookup | account_lookup | Auth0 |
| User has selected 'account lookup with pass number' on sign in screen |
Account Lookup | account_found | Auth0 |
| User entered a pass that is associated with an account |
Account Lookup | account_notfound | Auth0 | { "event": "error", "errorType": "account not found", "errorMessage": "{error message}" } | User entered a pass that is not associated with an account |
Pass Account Create | signup | Auth0 | signupMethod: "pass_media" | User has entered a valid pass number |
Pass Account Create | verify_account_view | Auth0 | signupMethod: "pass_media" | User has been sent an email to verify their identity before finishing account create with pass flow |
Pass Account Create | resend_email | Auth0 | signupMethod: "pass_media" | User has resent invite |
Pass Account Create | signup_error | Auth0 | signupMethod: "pass_media", "message": "no_email" | User has encountered an error related to customer not having an email profile on file in RTP |
Pass Account Create | signup_error | Auth0 | signupMethod: "pass_media", "message": "account_exists" | User has encountered an error related to customer having an existing account |
Pass Account Create | signup_error | Auth0 | signupMethod: "pass_media", "message": "invalid_value" | User has encountered an error related to a wrongly input pass number |
Pass Account Create | create_profile | Commerce |
| User has accepted invite, added a password, and has completed their profile |
Pass Account Create | successful_login | Commerce |
| User has accepted invite, added a password, and has completed their profile, and signed in/landed on store |
Add password | n/a | Auth0 | Page View | When a guest lands on the add password screen |
Implementation
Once Aspenware has received your onboarding information, they will send you a timeline for your implementation and be in contact as the process progresses.
...