Skip to main content
All CollectionsDeveloper Tools
Google Analytics Custom Events & Dimensions
Google Analytics Custom Events & Dimensions
Wendy avatar
Written by Wendy
Updated over a month ago

This article outlines a full list of the custom events and properties sent by Lantern to Google Analytics:

Welcome Screen Page

  • load_welcome_screen

    • properties: store_id, quiz_id, lantern_session_id, page

    • triggered when the welcome screen is loaded

  • leave_welcome_screen

    • properties: store_id, quiz_id, lantern_session_id, page

    • triggered when the user leaves the welcome screen to start the quiz (typically by clicking on or tapping on the Start button)

    • it doesn’t get triggered if the user leaves the quiz

Question Page

  • Email Page

    • load_email_page

      • properties: store_id, quiz_id, lantern_session_id, page, question_id

      • triggered when the email optin page is loaded

    • submit_email

      • properties: store_id, quiz_id, lantern_session_id, page, question_id, email, first_name, marketing_consent, is_required

      • triggered when the user submits the email optin form

    • skip_optin

      • properties: store_id, quiz_id, lantern_session_id, page, question_id

      • triggered if the user clicks on “No Thanks” or a similar link or button which allows them to skip the email page without providing an email address

  • Transition Screen

    • load_transition_screen

      • properties: store_id, quiz_id, lantern_session_id, page, question_id

      • triggered when a transition screen is loaded (the exact screen can be identified through the question_id)

    • leave_transition_screen

      • properties: store_id, quiz_id, lantern_session_id, page, question_id

      • triggered when a transition screen is left through a direct action (e.g. clicking on a button to proceed to the next question)

    • timeout_transition_screen

      • properties: store_id, quiz_id, lantern_session_id, page, question_id

      • triggered when a transition screen is left through a timeout (e.g. the transition screen disappears after 3 seconds, and the next question is displayed automatically)

  • Question / One-Line Input / Multi-Line Input

    • load_question_page

      • properties: store_id, quiz_id, lantern_session_id, page, question_id, question_type

      • triggered when a question page is loaded (the exact question can be identified through the question_id)

    • submit_answer

      • properties: store_id, quiz_id, lantern_session_id, page, question_id, question_type, title, is_required, options, answers, property_id

      • triggered when a question is answered

    Results Page

    • load_results_page

      • properties: store_id, quiz_id, lantern_session_id, page

      • triggered when the results page is loaded

    • restart_quiz

      • properties: store_id, quiz_id, lantern_session_id, page

      • triggered if the user chooses to restart the quiz (after reaching the results page)

    • display_results

      • properties: store_id, quiz_id, lantern_session_id, page, results, content_block_results, answers, email, first_name, marketing_consent

      • triggered when the results are displayed on the results page - this event includes properties with full details about the product recommendations being made

    • add_all_to_cart

      • properties: store_id, quiz_id, lantern_session_id, page

      • triggered if the user clicks on the “Add All To Cart” button

    • add_to_cart

      • properties: store_id, quiz_id, lantern_session_id, page, variant_id, sku, title, price

      • triggered when an “Add To Cart” button is clicked (a product is added to cart) - this event includes properties with full details about the product being purchased

    • go_to_product_page

      • properties: store_id, quiz_id, lantern_session_id, page, link, variant_id, sku, title, price

      • triggered when the user goes to a product page from the results page (e.g. by clicking on “Choose Options”)

    • go_to_cart

      • properties: store_id, quiz_id, lantern_session_id, page

      • triggered if the user visits the cart page from the results page

Did this answer your question?