AI-generated Key Takeaways
-
This guide helps developers move the Cloud Retail tag from client-side to a server-side container in Google Tag Manager.
-
Before starting, ensure you have set up a server container, a tagging server, and the data flow between web and server containers in Tag Manager.
-
The setup involves creating a new Cloud Retail tag in your server container, configuring it with your API key and project details, and mapping it to relevant triggers based on Google Analytics 4 events.
-
It's crucial to provide a unique visitor ID and optionally include search queries for enhanced tracking in your Cloud Retail tag configuration.
This article is for developers who want to move their Cloud Retail tag off of the client and into a server container. Refer to the Google Cloud documentation for the Cloud Retail web container tag.
Before you begin
This guide assumes that you have done the following:
- Set up a server container in Tag Manager
- Set up a tagging server
- Set up the data flow from the web container to the server container
Set up the Cloud Retail tag
In your server container, open the Tags menu and create a New tag.
In Tag Configuration, select the Cloud Retail tag.
Set up the Cloud Retail tag:
- Under API Key, enter a valid Cloud Retail API key that supports the
projects.locations.catalogs.userEvents.collect
method. - Under Project Number, enter the Google Cloud Project number for your Cloud Retail project.
- Under Fields to Overwrite, set up a visitor ID:
- Field Selector:
visitorId
- Field Value: Enter a variable that resolves into a unique visitor ID from a GA4 event, for example, the client ID.
- Field Selector:
- Optional: To measure search events:
- Field Selector:
searchQuery
- Field Value: Enter a variable that extracts the search query.
The search event is constructed by combining the search event query
with the impressions for the query, which are sent in
view_item_list
.
- Field Selector:
- Under API Key, enter a valid Cloud Retail API key that supports the
In Triggering, select when the tag should trigger. Refer to the Google Cloud documentation for mappings between Google Analytics 4 trigger events and Cloud Retail events.
Name and Save your tag.