Google Analytics 4 Integration

In today’s digital age, website analytics is crucial in helping businesses understand their customers, measure performance, and make data-driven decisions. Google Analytics (GA) is one of the most popular web analytics tools businesses of all sizes use to track and analyze their website traffic.

GA provides valuable insights into user behavior, demographics, interests, and much more.
However, Google announced the termination of Universal Analytics (UA), its current web analytics platform, and encouraged businesses to migrate to its new analytics platform, Google Analytics 4 (GA4).


Is it necessary to migrate to GA4?

Yes, it is highly recommended that businesses migrate to GA4 as soon as possible. Not only does GA4 provide more detailed and accurate insights into customer behavior, but it also offers enhanced features such as audience segmentation, predictive analytics, and automated reporting. Additionally, Universal Analytics will become unsupported on July 1, 2023, so businesses need to make sure they have migrated to GA4 by that time.

Are there any consequences of not migrating from UA to GA4?

Until July 1, 2023, you can continue to use and collect new data in your Universal Analytics properties. After July 1, 2023, you’ll be able to access your previously processed data in your Universal Analytics property for at least six months, but your UA property won’t be processing any new data.

After this future date, you’ll no longer be able to see your Universal Analytics reports in the Analytics interface or access your Universal Analytics data via the API.

Now, what does it mean to migrate from UA to GA4 in SuiteCommerce?

The solution breakdown is composed of a couple of different activities that need to happen: installing and connecting the GTM bundle, creating a new GA4 property, migrating your data from GUA to GA4 and a bunch of dataLayer enhancements on the different events that get sent from your site into GTM to ensure a complete tracking of your users’ behavior.

Project Scope

Google Tag Manager Activities
Google Tag Manager activities involve the following tasks:
Using Analytics Data to Refine Strategies​

DataLayer Enhancements

What is dataLayer and what are dataLayer enhancements? The dataLayer is basically a mechanism used in websites to pass over data from your site into the Tag Manager container. Specifically in SuiteCommerce, the dataLayer sends over relevant tracking information from actions your customers perform on the site into GTM which you can then use for marketing purposes.

The dataLayer enhancements are customizations performed over the native layer
which, when connecting GA4, are necessary to provide GTM with the correct
information from SCA in the format that it is expected to be sent and received in
order to have a complete tracking experience.

The solution for dataLayer developed by Unlock,
includes enhancements on all of the following events:


GA4 Configuration Tag

The GA4 Configuration tag ensures data flow from your website to Google Analytics.


Page View

This event is triggered each time the page loads or the browser history state is changed by the active site - in normal load websites it’s collected automatically and the collection can’t be turned off.


Product List

This event is sent when the user sees a list of items in a dedicated product list. A product list could be something like search results or category product listing.


Product List Event

This works in the same way as the normal Product List but it’s used for product lists that do not trigger a virtual load on the site and only generate events, such as a “related items” list on an item page or the “recently viewed items” on the cart.



This event is sent when the user searches on the site or when the user changes the filters of the search. On each search event the term searched will be sent to GA alongside the different default and custom parameters.


Product Click

This event is sent when the user actually clicks or selects an item after viewing the item’s impression(s) in a list.


Product View

This event is sent when the user views the details of any given product.


Add to Cart

This event is sent when the user adds a product to the cart, either by adding a new product to the cart or by increasing the quantity of an existing item in the cart.


Remove from Cart

This event is sent when the user removes something from the cart or decreases the quantity of an item in the cart.


Cart View

This event is sent when the user views the cart contents. This does not have an analogy in Enhanced Ecommerce. It’s a completely new Ecommerce event type.


Add to Wishlist

This event is sent when the user adds a product to a wishlist. This does not have an analogy in Enhanced Ecommerce. It’s a completely new Ecommerce event type.



This event is to signify that a user has logged in.



This event indicates that a user has signed up for an account. It’s used to understand the different behaviors of logged in and logged out users.


Checkout as a Guest

This event indicates that a user has proceeded to the checkout as a guest. It’s used to differentiate a user that hasn’t logged nor registered on the website.


Proceed to Checkout

This event is sent when the user starts the checkout flow.


Checkout Steps

This event replicates the pageView event logic on the checkout but the pageView event is also present on checkout steps, therefore, there’s no need to add a fake event. In this case, the Checkout Steps tag in GTM will be removed in favor of the Page View one.


Shipping Information

This event is sent when the user has selected and submitted a shipping method.


Payment Information

This event is sent when the user has selected and submitted a payment method.



This event is sent when the user makes a purchase on the site.

Project Timeline

Phase 1 [Required]

Our Methodology

Note: this may be subject to change depending on whether you are already using
GA4 / have a GA4 property configured / have a data migration process initiated. In
any of these cases, we might need to perform other actions which will cause
changes on timeline and scope.

Week 1


Week 2


Week 3


Week 4



Phase 2 [Optional]

As noted above, if any custom aspects are needed besides what is specified in the Project Scope section of this document, they will need to be considered separately. The best approach is to tackle this in a second phase, just after the first one is completed. 

The scope of work for a Phase 2 would be an analysis of custom aspects within Google Analytics, besides the tracking covered in Phase 1. The outcome of this analysis will be a status report of the aspects that need to be migrated, together with the hours for carrying out this custom part of the migration to GA4.

The estimated hours to carry out the analysis and deliver the status report is
between 2-3hs.

Share this post

You may also like

SKU CSV Import into Cart for SuiteCommerce

We are thrilled to announce the launch of our latest SuiteCommerce extension: the SKU CSV Import into Cart. This powerful feature enhances the SuiteCommerce shopping experience by enabling users to upload items directly to their