/
Aspenware GA4 Events

Aspenware GA4 Events

 

Events in the Purchase Flow

Event

Event Type

GA4 Standard or Aspenware Custom

Trigger

Schema Included

Example

Event

Event Type

GA4 Standard or Aspenware Custom

Trigger

Schema Included

Example

view_item_list

GA4 Standard Event

Fires when any category (PLP) page loads.

  • ecommerce

  • item(s)

 

image-20240807-220334.png

 

awc_view_pricing_calendar

GA4 Custom Event

Fires when large calendar page loads.

  • ecommerce

  • item(s)

 

select_item

GA4 Standard Event

Fires when a user clicks on a product card (either on the PLP, cross-sell or related products).

  • ecommerce

  • item(s)

 

image-20240807-220444.png

 

view_item

GA4 Standard Event

Fires when a user views a PDP. This can come from selecting a product card on the category page, selecting a date on a large pricing calendar, clicking a cross-sell, or related product item.

  • ecommerce

  • item(s)

 

 

add_to_cart

GA4 Standard Event

Fires when a user adds a product to their cart.

  • ecommerce

  • item(s)

 

 

view_cart

GA4 Standard Event

Fires when a user clicks “View Cart” on the slideout cart or on the cart icon in the header.

Also fires when the full page cart loads.

  • ecommerce

  • item(s)

 

 

remove_from_cart

GA4 Standard Event

Fires when a user clicks “remove” next to a product in the cart.

  • ecommerce

  • item(s)

 

 

begin_checkout

Standard Event

Fires when a user clicks “Checkout” from the slideout cart or the full-page cart used to indicate the user’s intention to begin checking out. If they are not logged in, they may be redirected to the login page to log in before the first checkout page loads.

  • ecommerce

  • item(s)

 

 

NOTE: For items that were added to the cart in a previous session, please note that there are some limits to the data that can be stored, including: , including

  • Whether the product was accessed through a related product, cross sell, or category

  • What category the product was accessed from if the product is added to >1 category

These will be resolved as we improve our data storage.

 

 

Events in the My Account Flow

Event

Event Type

GA4 Standard or Aspenware Custom

Trigger

Schema Included

Example

Event

Event Type

GA4 Standard or Aspenware Custom

Trigger

Schema Included

Example

awc_updateemail

Aspenware Custom Event

Fires when a user updates their email address from the Email Management tab in My Account.

 

 

Events in the Checkout Flow

Event

Event Type

GA4 Standard or Aspenware Custom

Trigger

Schema Included

Example

Event

Event Type

GA4 Standard or Aspenware Custom

Trigger

Schema Included

Example

awc_start_checkout

Aspenware Custom Event

Fires when /onepagecheckout (Assignment page) loads.

  • ecommerce

  • item(s)

 

 

add_shipping_info

GA4 Standard Event

Fires when the /delivery page loads for select items that require an address or pickup preference.

  • ecommerce

  • item(s)

(same as add_payment_info_ below)

add_payment_info

GA4 Standard Event

Fires when the /payment (Payment Details) page loads in checkout.

  • ecommerce

  • item(s)

 

 

awc_payment_selection

Aspenware Custom

This event is triggered when the user advances from the payment page to the confirm page.

  • ecommerce

  • item(s)

 

purchase

GA4 Standard Event

Fires when purchase is complete after the user confirms the order.

  • ecommerce

  • item(s)

 

 

error

GA4 Standard

Fires whenever a user encounters an error during checkout.

  • ecommerce

  • item(s)

 

transaction_complete

Note that this is an old Universal Analytics event that will be deprecated in the near future. Resorts should begin transitioning to the GA4 purchase event.

Aspenware Custom Event for GA4

Fires when purchase is complete after the user confirms the order.

 

 

 

Events in Identity v2

Event

Event Type

GA4 Standard or Aspenware Custom

Trigger

Schema Included

Example

Event

Event Type

GA4 Standard or Aspenware Custom

Trigger

Schema Included

Example

login

GA4 Standard

Fires when user is successfully authenticated in Identity.

 

 

error

GA4 Standard

Fires when a user encounters an error. (Currently only used in Identity, but will eventually be used for error handling across the platform.)

 

 

 

sign_up

GA4 Standard

Fires when /onepagecheckout loads after a user successfully creates an account.

 

 

Events in Identity v3

 

Event

Event Type

GA4 Standard or Aspenware Custom

Trigger

Example

Event

Event Type

GA4 Standard or Aspenware Custom

Trigger

Example

forgot_password_select

Aspenware Custom

User selects ‘forgot password’ in Auth0.

 

forgot_password_submitted

Aspenware Custom

User submits the form to have a password reset email sent in Auth0.

 

signin_attempt

Aspenware Custom

User selects ‘continue’ from sign in page in Auth0.

 

signin_error

Aspenware Custom

User experiences a sign in error, such as password didn’t match, account exists, etc. in Auth0.

 

authentication_success

Aspenware Custom

User has been successfully authenticated by Auth0.

 

successful_login

(now login)

Aspenware Custom

User has been authenticated and directed to the Aspenware shop successfully.

 

 

signup_selection

Aspenware Custom

Customer selects ‘sign up’ in Auth0.

 

signup_attempt

Aspenware Custom

Customer selects ‘continue’ after input email/password when creating a new account in Auth0.

 

signup_success

Aspenware Custom

Customer is successful in creating new account in Auth0. Fires at the same time as create_profile event.

 

auth0_account_error

Aspenware Custom

Error occurred during sign up in Auth0 such as email in use, API error.

 

customer_match

Aspenware Custom

Customer submits create profile and is matched to an existing customer in RTP (1 or many) in Aspenware Cloud UI. Fires sign_up success at the same time.

 

create_profile

Aspenware Custom

Customer is successful in creating new customer in Aspenware Cloud UI. Fires at the same time as sign_up success event.

 

Update_Customer_Profile_Error

Aspenware Custom

Customer experienced an error at creating a new customer in Aspenware Cloud UI.

 

account_lookup

Aspenware Custom

Customer selects ‘look up account with pass’ in Auth0.

 

account_found

Aspenware Custom

Customer inputs a valid pass and found an account in Auth0.

 

account_not_found

Aspenware Custom

Customer input an invalid pass or no account found in Auth0.

 

signupwithpass

Aspenware Custom

Customer selected ‘yes’ and hits continue.

 

signupwithpass_invitesent

Aspenware Custom

Customer inputs correct pass, has email on file, and has no auth profile in Auth0.

 

error

GA4 Standard

 

 

 

verify_account_view

Aspenware Custom

User was asked to verify their account.

 

resend_email

Aspenware Custom

User clicked the button to resend the email for password reset or email confirmation.

 

Events in Arrival

The following pages in Arrival have Page View events:

 

 

Related content

Aspenware Commerce and Cloud UI GA4 Data Layer Schemas and Dimensions
Aspenware Commerce and Cloud UI GA4 Data Layer Schemas and Dimensions
More like this
Commerce 3.7 / Cloud UI 2.0: Google Analytics Enhancements
Commerce 3.7 / Cloud UI 2.0: Google Analytics Enhancements
More like this
February 20, 2025 - Commerce 3.7, Cloud UI 2.0 and Unity 3.48 (Beta)
February 20, 2025 - Commerce 3.7, Cloud UI 2.0 and Unity 3.48 (Beta)
Read with this
Commerce 3.7/Cloud UI 2.0: Cloud UI PDP Updates
Commerce 3.7/Cloud UI 2.0: Cloud UI PDP Updates
Read with this
NEW Cloud UI: Dynamically-Priced Add-Ons
NEW Cloud UI: Dynamically-Priced Add-Ons
Read with this
Commerce 3.7/Cloud UI 2.0: Enhancements for Manage Your Group Members
Commerce 3.7/Cloud UI 2.0: Enhancements for Manage Your Group Members
Read with this