Google Analytics Triggered Events

Google Analytics Triggered Events

Overview

During onboarding, you can provide a Google Analytics tracking code for your website. If you do not currently have a tracking code, follow the steps in this related article. This is the standard set up we use for all sites.

Below is a list of the universal events that are triggered on Google Analytics, Google Tag Manager, and Google Analytics eCommerce:

Google Analytics (GA 3, GA 4)

  1. PageView - code will pass:
    1. page (Root relative url of page)
    2. eventAction (event name i.e. PageView)
    3. title (Page's title)
    4. is_user_authenticated (flag i.e. true/false)
    5. user_id (Logged in user's ID)
    6. store_id (Selected store ID)
    7. store_number (Selected store Number)
    8. store (Selected store name)
  2. UserRegistration - code will pass:
    1. hitType (event)
    2. eventAction (event name i.e. UserRegistration) 
    3. eventLabel (event label. i.e. User Registration)
    4. eventCategory (Account)
  3. AddToCart - code will pass:
    1. hitType (event)
    2. eventAction (event name i.e. AddToCart) 
    3. eventLabel (the name of the product added to the cart)
    4. eventCategory (Product)
  4. InitiateCheckout - code will pass:
    1. hitType (event)
    2. eventAction (event name i.e. InitiateCheckout) 
    3. eventLabel (event label. i.e. Initiate Checkout)
    4. eventCategory (Checkout)
  5. Purchase - code will pass:
    1. hitType (event)
    2. eventAction (event name i.e. Purchase) 
    3. eventLabel (event label. i.e. Purchase)
    4. eventCategory (Checkout)
  6. StoreChanged - code will pass:
    1. hitType (event)
    2. eventAction (event name i.e. StoreChanged) 
    3. eventLabel (event label. i.e. Store Changed)
    4. eventCategory (Store)
  7. PrintResults - code will pass:
    1. hitType (event)
    2. eventAction (event name i.e. PrintResults) 
    3. eventLabel (event label. i.e. Print Results)
    4. eventCategory (Print)
  8. DownloadPDF - code will pass:
    1. hitType (event)
    2. eventAction (event name i.e. DownloadPDF) 
    3. eventLabel (event label. i.e. Download PDF)
    4. eventCategory (Download)
  9. EmailList - code will pass:
    1. hitType (event)
    2. eventAction (event name i.e. EmailList) 
    3. eventLabel (event label. i.e. Email List)
    4. eventCategory (Email)
  10. PrintList - code will pass:
    1. hitType (event)
    2. eventAction (event name i.e. PrintList) 
    3. eventLabel (event label. i.e. Print List)
    4. eventCategory (Print)

Google Universal Analytics (GA 2)

  1. PageView - code will pass:
    1. event (event name i.e. PageView)
    2. page_title (Page's title)
    3. page_path (Root relative url of page)
    4. is_user_authenticated (flag i.e. true/false)
    5. user_id (Logged in user's ID)
    6. store_id (Selected store ID)
    7. store_number (Selected store number)
    8. store (Selected store name)
  2. UserRegistration - code will pass:
    1. event (event name i.e. UserRegistration)
    2. label (event label. i.e. User Registration)
    3. category (Account)
  3. AddToCart - code will pass:
    1. event (event name i.e. AddToCart)
    2. label (the name of the product added to the cart)
    3. category (Product)
  4. InitiateCheckout - code will pass:
    1. event (event name i.e. InitiateCheckout)
    2. label (event label. i.e. Initiate Checkout)
    3. category (Checkout)
  5. CheckoutStep - code will pass:
    1. event (event name i.e. CheckoutStep)
    2. label (event label. i.e. Checkout Step)
    3. category (Navigation)
  6. Initiate Purchase - code will pass:
    1. event (event name i.e. InitiatePurchase)
    2. label (event label. i.e. Initiate Purchase)
    3. category (Checkout)
  7. Purchase - code will pass:
    1. event (event name i.e. Purchase)
    2. label (event label. i.e. Purchase)
    3. category (Checkout)
  8. StoreChanged - code will pass:
    1. event (event name i.e. StoreChanged)
    2. label (event label. i.e. Store Changed)
    3. category (Store)
  9. PrintResults - code will pass:
    1. event (event name i.e. PrintResults)
    2. label (event label. i.e. Print Results)
    3. category (Print)
  10. DownloadPDF - code will pass:
    1. event (event name i.e. DownloadPDF)
    2. label (event label. i.e. Download PDF)
    3. category (Download)
  11. EmailList - code will pass:
    1. event (event name i.e. EmailList)
    2. label (event label. i.e. Email List)
    3. category (Email)
  12. PrintList - code will pass:
    1. event (event name i.e. PrintList)
    2. label (event label. i.e. Print List)
    3. category (Print)
  13. PrintResults - code will pass:
    1. event (event name i.e. PrintResults)
    2. label (event label. i.e. Print Results)
    3. category (Print)
  14. AddToFavorites - code will pass:
    1. event (event name i.e. AddToFavorites)
    2. label (event label. i.e. Add To Favorites)
    3. category (Product)
  15. AddToMyRecipes - code will pass:
    1. event (event name i.e. AddToMyRecipes)
    2. label (event label. i.e. Add To My Recipes)
    3. category (Recipe)

GA Enhanced eCommerce

  1. add_to_cart - code will pass:
    1. hitType (event)
    2. eventAction (event name i.e. add_to_cart)
    3. eventLabel (the name of the product added to the cart)
    4. eventCategory (Product)
  2. remove_from_cart - code will pass:
    1. hitType (event)
    2. eventAction (event name i.e. remove_from_cart)
    3. eventLabel (the name of the product removed from the cart)
    4. eventCategory (Product)

GA eCommerce

  1. addTransaction - code will pass:
    1. id (order ID)
    2. affiliation (selected store name)
    3. revenue (order total)
    4. currency
  2. addItem - code will pass:
    1. id (order ID)
    2. name
    3. sku (order total)
    4. price
    5. quantity

Help

For assistance, please submit a ticket in the Freshop Support Portal at https://support.freshop.com.
    • Related Articles

    • Google Analytics: Hosted Payment Provider Referral Exclusions

      Common Issue Customers leave the merchant’s website to make their payment on a 3rd party hosted payment provider’s website. After they complete their payment, customers are then redirected back to the URL provided by the merchant. When customers ...
    • Impersonate a User

      What can you do as an Impersonator? You can: View a list of Customers/Users Search for a particular account by name or email Unsubscribe a Customer/User Take phone call orders Leverage a customer’s past shopping history, favorites, etc. Type in a ...
    • Obtaining Google API Keys for Stores to Enable Auto-Complete

      Google has changed the way their pricing works - for example where Google Maps used to be free, they are now charging and it can be based on the traffic of the site. If a store is now interested in enabling Google Maps lookahead they will have to ...
    • Creating a Freshop Admin User Account

      Admin Users are different than Customer Users. If you created a shopping account through your shopping website, this will not create an Admin User. Creating Admin User Account: 2 step process Step 1: To access the Freshop Admin you need to create an ...
    • PayPal: Account Setup / Integrating API Keys

      Create Account To create a business PayPal account go to https://www.paypal.com/us/webapps/mpp/merchant.  Once your account has been created you will need to follow the below steps to get the API keys integrated.  Integrating API Keys Please Note: If ...