-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EDU-13804 - Review: Setting up Google Tag Manager #1599
Open
barbara-celi
wants to merge
4
commits into
main
Choose a base branch
from
EDU-13804-Review-Setting-up-Google-Tag-Manager
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
45181b2
Create store-framework-analytics-setting-up-google-tag-manager.md
barbara-celi b066768
New translations store-framework-analytics-setting-up-google-tag-mana…
GeorgeLimaDev 8a13dd5
Merge pull request #1640 from vtexdocs/l10n_EDU-13804-Review-Setting-…
barbara-celi 784445f
moving file to correct folder
barbara-celi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
102 changes: 102 additions & 0 deletions
102
...front-best-practices/store-framework-analytics-setting-up-google-tag-manager.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change | ||||||
---|---|---|---|---|---|---|---|---|
@@ -0,0 +1,102 @@ | ||||||||
--- | ||||||||
title: "Setting up Google Tag Manager" | ||||||||
slug: "store-framework-analytics-setting-up-google-tag-manager" | ||||||||
hidden: false | ||||||||
createdAt: "2020-06-03T16:02:44.272Z" | ||||||||
updatedAt: "2024-12-18T16:04:22.033Z" | ||||||||
category: "Storefront development" | ||||||||
excerpt: "Explore how to track and analyze store data using Google Analytics 4" | ||||||||
--- | ||||||||
|
||||||||
After installing the VTEX IO [Google Tag Manager app](https://developers.vtex.com/docs/apps/vtex.google-tag-manager), configure the necessary variables, triggers, and tags to set it up in your store. | ||||||||
|
||||||||
In this guide, you will learn how to track and analyze store data using Google Analytics 4 (GA4). The guide covers: | ||||||||
- Configuring GA4 events by downloading and importing a container file; adding the necessary tags, triggers, and variables; and updating the Measurement ID field with your Google tag ID. | ||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [markdownlint-fix] reported by reviewdog 🐶
Suggested change
|
||||||||
- Testing the GA4 Configuration tag to ensure it fires correctly on every page and confirming that GA4 Event tags accurately track user actions, such as viewing a product or adding a product to the cart. | ||||||||
- Using Google Analytics DebugView and Reports to check if events are being received and data is populating your reports. | ||||||||
- Tracking key user actions — including product impressions, add-to-cart events, and completed orders — by leveraging Pixel Apps and GA4 events. | ||||||||
|
||||||||
## Before you begin | ||||||||
|
||||||||
<Steps> | ||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [markdownlint] reported by reviewdog 🐶 |
||||||||
|
||||||||
### Get the VTEX IO Google Tag Manager app | ||||||||
|
||||||||
Install and configure the VTEX IO Google Tag Manager app. For more information, see the guide [Installing Google Tag Manager](https://developers.vtex.com/docs/guides/store-framework-analytics-installing-google-tag-manager). | ||||||||
carolinamenezes marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||||
|
||||||||
### Create a Google Analytics 4 (GA4) Configuration tag | ||||||||
|
||||||||
Create a Google Analytics 4 (GA4) Configuration tag using your Measumerent ID in [Google Tag Manager (GTM)](https://tagmanager.google.com/). For more information, see the Google article [Set up the Google Analytics 4 Configuration tag](https://support.google.com/tagmanager/answer/9442095). | ||||||||
|
||||||||
</Steps> | ||||||||
|
||||||||
## Instructions | ||||||||
|
||||||||
### Step 1 - Setting up GA4 events | ||||||||
|
||||||||
After creating the GA4 Configuration tag, set up GA4 events as follows: | ||||||||
|
||||||||
1. Download the [GTM container file](https://developers.vtex.com/container-template.json) to preload all necessary tags, triggers, and variables. | ||||||||
2. Import the container file by following Google’s [Import a container](https://support.google.com/tagmanager/answer/6106997?#import) guide. This will add all the necessary tags, triggers, and variables to the workspace. | ||||||||
|
||||||||
![import-container](https://vtexhelp.vtexassets.com/assets/docs/src/new-ga4-tags-variables___b2619df57689429d97a8abd56a5f7d83.png) | ||||||||
|
||||||||
3. In the GTM container, go to the GA4 Configuration tag, and edit the **Measurement ID** field with your Google tag ID (G- ID). | ||||||||
|
||||||||
> ℹ️ To find your Google tag ID, check the [Find your Google tag ID](https://support.google.com/analytics/answer/9539598?sjid=16676572490197811169-SA#find-G-ID) guide. | ||||||||
|
||||||||
### Step 2 - Testing tags in Google Tag Manager | ||||||||
|
||||||||
To test if the GA4 Configuration tag is firing correctly on every page, use the [Preview mode](https://support.google.com/tagmanager/answer/6107056) in GTM. Additionally, check if the GA4 Event tags are firing accurately for user actions, such as viewing a product or adding a product to the cart. | ||||||||
|
||||||||
### Step 3 - Testing events sent to Google Analytics 4 | ||||||||
|
||||||||
To check if the events are being received and the reports are populated with data, go to the Google Analytics Admin and use the [DebugView](https://support.google.com/analytics/answer/7201382) to make sure the events are arriving and the [Reports](https://support.google.com/analytics/answer/9212670) are getting the data. | ||||||||
|
||||||||
![gtm-debug-view](https://vtexhelp.vtexassets.com/assets/docs/src/gtm-debug-view___e2dc572dcc33e2e23e81749583226ec8.png) | ||||||||
|
||||||||
To see the available events that GA4 can track, check the [Overview of trackable events](#overview-of-trackable-events) section. | ||||||||
|
||||||||
## Overview of trackable events | ||||||||
|
||||||||
This section provides a list of events that GA4 can track and explains the `view_promotion` event, which is usually attached to the promotion banner carousel displayed by the [Slider Layout](https://developers.vtex.com/docs/apps/vtex.slider-layout) block. | ||||||||
|
||||||||
### View promotion | ||||||||
|
||||||||
The [GA4 view_promotion](https://developers.google.com/analytics/devguides/collection/ga4/reference/events?client_type=gtm#view_promotion) event expects the product name or ID associated with it. | ||||||||
|
||||||||
This event is commonly attached to the promotion banner carousel displayed by the Slider Layout block. For example, you can use Site Editor to configure the `Product ID` and `Product Name`. To access Site Editor, go to **Storefront > Site Editor** in the VTEX Admin. | ||||||||
|
||||||||
![gtm-site-editor-fields](https://vtexhelp.vtexassets.com/assets/docs/src/gtm-site-editor___bc52365aafad63deb5bfed1d74f307c0.png) | ||||||||
|
||||||||
### Supported events | ||||||||
|
||||||||
Check the available events that [Pixel Apps](https://developers.vtex.com/docs/guides/pixel-apps) can listen to, along with their corresponding names in Universal Analytics (UA) and Google Analytics 4 (GA4): | ||||||||
|
||||||||
| VTEX | UA | GA4 | | ||||||||
|------------------------|-------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------| | ||||||||
| vtex:promoView | promoView | [view_promotion](https://developers.google.com/analytics/devguides/collection/ga4/reference/events?client_type=gtm#view_promotion) | | ||||||||
| vtex:promotionClick | promoClick | [select_promotion](https://developers.google.com/analytics/devguides/collection/ga4/reference/events?client_type=gtm#select_promotion) | | ||||||||
| vtex:productImpression | impressions | [view_item_list](https://developers.google.com/analytics/devguides/collection/ga4/reference/events?client_type=gtm#view_item_list) | | ||||||||
| vtex:productClick | click | [select_item](https://developers.google.com/analytics/devguides/collection/ga4/reference/events?client_type=gtm#select_item) | | ||||||||
| vtex:productView | detail | [view_item](https://developers.google.com/analytics/devguides/collection/ga4/reference/events?client_type=gtm#view_item) | | ||||||||
| vtex:addToCart | add | [add_to_cart](https://developers.google.com/analytics/devguides/collection/ga4/reference/events?client_type=gtm#add_to_cart) | | ||||||||
| vtex:removeFromCart | remove | [remove_from_cart](https://developers.google.com/analytics/devguides/collection/ga4/reference/events?client_type=gtm#remove_from_cart) | | ||||||||
| vtex:viewCart | Not applicable | [view_cart](https://developers.google.com/analytics/devguides/collection/ga4/reference/events?client_type=gtm#view_cart) | | ||||||||
| vtex:beginCheckout | checkout | [begin_checkout](https://developers.google.com/analytics/devguides/collection/ga4/reference/events?client_type=gtm#refund) | | ||||||||
| vtex:addShippingInfo | Not applicable | [add_shipping_info](https://developers.google.com/analytics/devguides/collection/ga4/reference/events?client_type=gtm#add_shipping_info) | | ||||||||
| vtex:addPaymentInfo | Not applicable | [add_payment_info](https://developers.google.com/analytics/devguides/collection/ga4/reference/events?client_type=gtm#add_payment_info) | | ||||||||
| vtex:orderPlaced | purchase | [purchase](https://developers.google.com/analytics/devguides/collection/ga4/reference/events?client_type=gtm#purchase) | | ||||||||
| vtex:refund | Not applicable | [refund](https://developers.google.com/analytics/devguides/collection/ga4/reference/events?client_type=gtm#refund) | | ||||||||
| vtex:search | Not applicable | [search](https://developers.google.com/analytics/devguides/collection/ga4/reference/events?client_type=gtm#search) | | ||||||||
| vtex:share | Not applicable | [share](https://developers.google.com/analytics/devguides/collection/ga4/reference/events?client_type=gtm#share) | | ||||||||
| vtex:addToWishlist | Not applicable | [add_to_wishlist](https://developers.google.com/analytics/devguides/collection/ga4/reference/events?client_type=gtm#add_to_wishlist) | | ||||||||
|
||||||||
### Partially supported events | ||||||||
|
||||||||
The following events are not fully supported yet. Although the GTM app will listen and format them into GA4, corresponding VTEX event triggers have not been implemented yet: | ||||||||
|
||||||||
| VTEX | GA4 | | ||||||||
|-------------|----------------------------------------------------------------------------------------------------------------------| | ||||||||
| vtex:login | [login](https://developers.google.com/analytics/devguides/collection/ga4/reference/events?client_type=gtm#login) | | ||||||||
| vtex:signUp | [sign_up](https://developers.google.com/analytics/devguides/collection/ga4/reference/events?client_type=gtm#sign_up) | |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[markdownlint] reported by reviewdog 🐶
MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Configuring GA4 events by do..."]