Proposal To setup GA4 E-commerce Tracking
This proposal covers the development steps for setup tracking events add to carts, begin checkout, purchase event in GA4. This proposal also covers the engagement scope of Jobin and Jismi It Services LLP, as official implementation partner of Oracle NetSuite.
Proposal Summary
This proposal explains how to add extra tracking features to monitor specific actions, like adding items to the cart, starting the checkout process, and completing a purchase on the www.blvdca.com website. We’ll include a GA4 script tag to track these events on the checkout, shopping, and cart pages
Requirement
The requirement is to enable advanced e-commerce monitoring via Google Analytics 4 (GA4) deployment to improve insights into user behaviour and optimise the online purchasing experience.
Pre-Request
We require access to GA4 account (which has already been granted).
Deliverables
When we add the GA4 Events on the website it helps to track the details from the website to its GA4 account.
Begin checkout
The script will be added to checkout page header section. It will capture the “checkout” event when users begin to checkout process. To understand user behaviour during the checkout process.
Purchase event
To implement a Purchase Event, a script tag will be added to the Order Confirmation page header.
Add to Cart
The script will be added to cart page header section. It will capture the “add to cart” event when users view their cart. Using this event Details of Currency, item id, item name, coupons details, discount etc will be captured.
Assumptions
- We have estimated the effort for setting the variables in the Events.
- We have enhanced several events that will significantly benefit our analytics system. Considering and implementing these events collectively will greatly contribute to the overall effectiveness of our analytics infrastructure
- Choosing the three events provides detailed insights into cart activities and purchases.
- Excluding other events may lead to a less comprehensive overview and miss match in analytics.
- For Example, if a user adds two items to the cart and later removes one, the data discrepancy arises. The “Add to Cart” event registers two items, while the “Purchase Event” only reflects one item. This mismatch can impact the accuracy of the analysis.
- The changes will move to production once it is verified in Sandbox Account.
- Any additional changes to the UI or functionality will be considered extra.
Scope Limitation
- We only considered add to carts, begin checkout and purchase event.
- Apart from the functionalities mentioned in the SOW, no other changes will be considered.
- Updating or adding contents to the existing pages will be extra.
- Any additional changes to the UI or functionality will be considered extra.
- Excluding other events may lead to a less comprehensive overview and miss match in analytics.
- For Example, if a user adds two items to the cart and later removes one, the data discrepancy arises. The “Add to Cart” event registers two items, while the “Purchase Event” only reflects one item. This mismatch can impact the accuracy of the analysis.
Enhancement
We strongly recommend the proposed enhancement enable a detailed view of user behaviour and facilitate precise segmentation for targeted data analysis. These events will enhance the accuracy of data collection, empowering data-driven decision-making. Additional events, such as the ‘Remove from Cart’ event, we can gain the user behaviour of a including small details. For instance, tracking when and why a user removes an item from the cart provides valuable data for understanding user preferences and improving engagement. Excluding these events may lead to a less comprehensive overview and miss match in analytics. For Example, if a user adds two items to the cart and later removes one. The “Add to Cart” event registers two items, while the “Purchase Event” only reflects one item. This mismatch can impact the accuracy of the data analysis.
Below are our recommendations for improving specific events to provide more meaningful insights:
View item list:
The “view item list” event could be used to track when users browse through a list of products, or any other items on your website. This information can be valuable for analytics purposes
Remove from Cart Event:
The “Remove from Cart” event allows to understand user behaviour related to the shopping cart. By tracking this event, you can gather insights into the number of times users remove items from their carts, the specific items being removed, and potentially the reasons behind those removals.
Add shipping info Event:
We can trace the details of shipping states that are most used, and we can find the matrix of the most-ordered and least-ordered states. This way, we can expand the business in those states and investigate why fewer orders are coming in those specific states.
Add payment info Event:
This information could include details about the payment method selected, the number of payment attempts, or any errors encountered during the payment information submission.
View cart event:
This event provides valuable data for us to understand user behaviour related to the shopping cart, and it plays a crucial role in analytics.
View item
When a user interacts with a product page, its information about the viewed item. This information may include details such as the item ID, name, category, and other attributes. Capturing these details allows businesses to analyse user behaviour, understand which products are being viewed most frequently, and make data-driven decisions to improve the user experience or marketing strategies.
Select item event:
when a user selects or interacts with a specific item on website. This could be associated with actions like clicking on a product, choosing an option from a list, or any other user engagement with items on website.
Why Consider This Enhancement?
- Provide a more detailed view of user behaviour.
- Enable precise segmentation for targeted analysis.
- Improve attribution accuracy, empowering data-driven decision-making.
- Excluding these events may lead to a less comprehensive overview and miss match in analytics.
- For Example, if a user adds two items to the cart and later removes one, the data discrepancy arises. The “Add to Cart” event registers two items, while the “Purchase Event” only reflects one item. This mismatch can impact the accuracy of the analysis.
- If you consider Enhancement, it will be helpful for implementing both implementations at the same time. Alternatively, it might extend the time needed for handling. How do you feel about it?