Google Analytics 4 Web Destination

Before you connect Segment to Google Analytics 4, configure a Google Analytics 4 property in your Analytics account and enable any Custom Definitions in your GA4 Admin Panel. For more information, see Google's article Set up Analytics for a website and/or app.

To connect the Google Analytics 4 Web destination:

1. From the Segment web app, click Catalog, then click Destinations.
2. Search for "Google Analytics 4 Web" in the Destinations Catalog, and select the destination.
3. Click Configure Google Analytics 4 Web.
4. Select the web source that will send data to Google Analytics 4 and follow the steps to name your destination. The web source chosen must use Analytics.js 2.0. For mobile source tracking, view the Firebase Destination.
5. On the Settings tab, under Basic Settings, enter in the Measurement ID associated with your GA4 web stream.
6. Set up your event mappings by following the steps in the Destinations Actions documentation on Customizing mappings.
7. Analytics.js requires an initial Page call to send data to Google Analytics 4 Web. The Segment snippet includes this initial call by default.
8. For GA4 to accept events on page, enable Set Configuration Mapping triggered by the first Segment event called after analytics.load(). Set Configuration Mapping calls the gtag('config') command to enable tracking to your GA4 Measurement ID.

After you've set up and enabled the Set Configuration Mapping, enable at least one event in your Mappings tab. From there, view your events and parameters using the Google Realtime or DebugView reports. These two reports show you the events users trigger on your website as they occur. The DebugView report requires additional configuration before you can use it. Additional tools for debugging are to view all your Google enabled tracking via Tag Assistant or in your browser's Dev Tools, view GA4 collect requests by filtering by /collect.

Google Analytics automatically populates some events and parameters. For example, there are Automatically Collected events collected by triggering the Set Configuration Mapping. Calling gtag('config') and enabling Enhanced Measurement events, which are controlled by toggling "on" in your GA4 Admin panel, use event listeners to send events. All events tracked via GA4 Web populate some commonly used parameters like page_location without additional configuration. Review the Google Analytics event parameters documentation for more information.

Google recommends that you use their Recommended events and properties to power certain built-in reports in Google Analytics 4. Segment's Google Analytics 4 Web destination provides prebuilt mappings to automatically map your Segment spec events to the corresponding Google Analytics 4 events and properties. If your Segment events don't follow the Segment spec exactly, you can modify the mappings. For example, Segment maps an Order Completed event to the Google Analytics 4 Purchase event, but if your company uses Products Purchase to indicate a purchase, you can map it in the Purchase action's Event Trigger instead.

Segment recommends using the prebuilt mappings when possible. However, the Segment spec doesn't have an equivalent event for every Google Analytics 4 Recommended event. If there are other recommended events you'd like to send, use the Custom Event action. For example, to send a spend_virtual_currency event, create a mapping for Custom Event, set up your Event Trigger criteria, and input a literal string of spend_virtual_currency as the Event Name. You can use the Event Parameters object to add fields that are in the spend_virtual_currency event such as value and virtual_currency_name. Remember to define custom parameters as custom dimensions and metrics within the GA4 Admin panel first.

Before you create a custom event, make sure the event you want to create isn't already collected through an Automatically Collected event or recommended as a Recommended event. Google Analytics 4 does not accept custom event names that include spaces. Segment replaces spaces in the Event Name in the Custom Event action with an underscore. As a result, you see custom events as snake_case in Google Analytics 4.

Event names are case-sensitive in Google Analytics 4. If you would like all event names to be lowercase, use the Lowercase Event Name setting when you create a Custom Event mapping and select Yes from the dropdown. If this setting is disabled, Google treats event names with different casing as distinct events.

Custom Events don't appear in some of Google's standard reports; you must set up custom reports for meaningful analysis.

With Google Analytics 4, you must create custom dimensions and metrics, also known as Custom Definitions, within the Google Analytics 4 Admin interface to link event parameters to the corresponding custom dimensions or metrics. When creating the dimension or metric, you can either select a parameter from the list of already collected fields or enter the name of the parameter you plan to collect in the future. For more information, see Google Analytics 4 Custom dimensions and metrics.

Similar to how properties relate to Segment events, parameters provide additional information about the ways users interact with your website. For example, when someone views a product you sell, you can include parameters that describe the product they viewed, like product_name, category, and price.

Automatically Collected and Enhanced Measurement events include a defined set of parameters by default. Google also provides a set of required and optional parameters to include with each Recommended event, and you can add more event parameters when you need them. Segment recommends that you review GA4's list of defined event parameters, as anything beyond that list is a custom event parameter. The Event collection limits also impact how many Custom Definitions your GA4 instance allows and how many parameters you can send with each event.

Some of Segment's prebuilt Available Actions that map to Google's recommended events are automatically marked as a conversion in your Analytics dashboard. For example, when you add an "Order Completed" event, it will show up in your Analytics dashboard as "purchase" with the Mark as conversion toggle toggled on by default. However, for other events, such as "Add to Cart", you must manually toggle the Mark as conversion setting on in your Analytics dashboard. If you don't mark the event as a conversion, it will not show up as a conversion in your built-in reports. You can read more about conversion events in Google's documentation.

Consent mode is a feature provided by Google in the context of its products, particularly the Gtag library and Google Analytics. As of March 6, 2024, Google announced that consent mode must function for European Economic Area (EEA) users, otherwise data from EEA users won't process.

Consent mode in the Gtag library and Google Analytics is designed to help website owners comply with privacy regulations, such as the General Data Protection Regulation (GDPR) in the European Union. It allows website owners to adjust how these tools use and collect data based on user consent.

With consent mode, you can configure your website to dynamically adjust the tracking behavior of the Gtag library and Google Analytics based on the user's consent status. If a user provides consent to data processing, both the Gtag library and Google Analytics can collect and use that data for analysis. If a user doesn't provide consent, both tools limit data collection to essential functions, helping businesses respect user privacy preferences.

Consent mode may involve updates to your sources outside of Segment, such as incorporating a consent management system for consent functionality.

See set up consent mode on websites for more information.

To enable consent mode for your Google Analytics 4 Web destination:

1. Navigate to Connections > Destinations and select your Google Analytics 4 Web** destination.

2. Go to the Settings tab of the destination.

3. Click the toggle on for Enable Consent Mode, this calls gtag('consent','default') with the defined parameters when the gtag library loads.

4. Set the following fields with your organization's determination of granted or denied:

   Field	Value
   Default Ad Storage Consent State	Granted or Denied
   Default Analytics Storage Consent State	Granted or Denied
   Ad User Data Consent State	Granted or Denied
   Ad Personalization Consent State	Granted or Denied

5. Use your consent management platform to prompt the visitor. Ask the visitor to grant or deny consent for the applicable types.

6. Pass the updated state as properties in the page() event after the next page load if you decide to change the consent defaults. For example,

   Copy code block

   1
   analytics.page('Consent Update', {
   2
       'Ads Storage Consent State': 'false',
   3
       'Analytics Storage Consent State': 'false'
   4
   });

7. As soon as the page loads and the set configuration fires to the Google Analytics SDK, Segment issues a consent mode update command. Map the properties you defined to collect consent state changes to the Set Configurations Fields mapping. You can choose to do this from 1 of 2 options in steps 4 and 5.

   1. Navigate to Connections > Destinations and select your Google Analytics 4 Web destination.
   2. Go to the mappings tab of the destination.
   3. Select the mapping you want to edit.
   4. (Option 1) Under the Select mappings section, select Granted for these fields:
      • Ads Storage Consent State
      • Analytics Storage Consent State
      • Ad User Data Consent State
      • Ad Personalization Consent State You can manually select Granted or Denied from the dropdown menu for Advanced consent mode settings, and type in granted or denied for basic consent mode settings.
   5. (Option 2) Under the Select mappings section, create an event variable to directly grab the value from the payload (for example, properties.adStorageConsentState). Ensure it translates to granted or denied. You can use an insert or replace function to translate other values to granted or denied. Do this for these fields:
      • Ads Storage Consent State
      • Analytics Storage Consent State
      • Ad User Data Consent State
      • Ad Personalization Consent State

When these properties are available, they send to the update command.

If you have any questions setting up consent mode, reach out to friends@segment.com.

Google Analytics 4 Web has the following presets

Build your own Mappings. Combine supported triggers with the following Google Analytics 4 Web-supported actions:

• Add to Cart
• Search
• Select Item
• View Item List
• Sign Up
• Custom Event
• Refund
• Add Payment Info
• View Cart
• Set Configuration Fields
• Purchase
• View Promotion
• Add to Wishlist
• Remove from Cart
• Generate Lead
• Select Promotion
• View Item
• Begin Checkout
• Login

This event signifies that an item was added to a cart for purchase.

Add to Cart is a Web action. The default Trigger is type = "track" and event = "Product Added"

The term that was searched for.

Search is a Web action. The default Trigger is type = "track" and event = "Products Searched"

This event signifies an item was selected from a list.

Select Item is a Web action. The default Trigger is type = "track" and event = "Product Clicked"

Log this event when the user has been presented with a list of items of a certain category.

View Item List is a Web action. The default Trigger is type = "track" and event = "Product List Viewed"

The method used for sign up.

Sign Up is a Web action. The default Trigger is type = "track" and event = "Signed Up"

Send any custom event

Custom Event is a Web action. The default Trigger is type = "track"

This event signifies when one or more items is refunded to a user.

Refund is a Web action. The default Trigger is type = "track" and event = "Order Refunded"

Send event when a user submits their payment information

Add Payment Info is a Web action. The default Trigger is type = "track" and event = "Payment Info Entered"

This event signifies that a user viewed their cart.

View Cart is a Web action. The default Trigger is type = "track" and event = "Cart Viewed"

Set custom values for the GA4 configuration fields.

Set Configuration Fields is a Web action. The default Trigger is type = "page"

This event signifies when one or more items is purchased by a user.

Purchase is a Web action. The default Trigger is type = "track" and event = "Order Completed"

This event signifies a promotion was viewed from a list.

View Promotion is a Web action. The default Trigger is type = "track" and event = "Promotion Viewed"

The event signifies that an item was added to a wishlist. Use this event to identify popular gift items in your app.

Add to Wishlist is a Web action. The default Trigger is type = "track" and event = "Product Added to Wishlist"

This event signifies that an item was removed from a cart.

Remove from Cart is a Web action. The default Trigger is type = "track" and event = "Product Removed"

Log this event when a lead has been generated to understand the efficacy of your re-engagement campaigns.

Generate Lead is a Web action. The default Trigger is type = "track"

This event signifies a promotion was selected from a list.

Select Promotion is a Web action. The default Trigger is type = "track" and event = "Promotion Clicked"

This event signifies that some content was shown to the user. Use this event to discover the most popular items viewed.

View Item is a Web action. The default Trigger is type = "track" and event = "Product Viewed"

This event signifies that a user has begun a checkout.

Begin Checkout is a Web action. The default Trigger is type = "track" and event = "Checkout Started"

Send event when a user logs in

Login is a Web action. The default Trigger is type = "track" and event = "Signed In"

The Google Analytics 4 debug mode, DebugView is supported with the Google Analytics 4 Web destination. DebugView displays the events and user properties that Analytics collects from a user in real-time. This can be helpful when troubleshooting your implementation.

With Google Analytics 4 Web, events are sent from the browser to GA4. If you use Segment's Google Analytics 4 Cloud destination to send events through the API and tie data between client-side and server-side, you need to pass the same Client ID from the browser and the server. To do this, fetch the Gtag-generated clientId on the web client and pass it to Segment as a property. For more information, see Google Analytics 4 destination: User Identification on the next steps. Additionally, when using Gtag, Google generates a session_id and session_number when a session begins. The session_id and session_number generated on the client can be passed as Event Parameters to stitch events sent through the API with the same session that was collected client-side, see Using Gtagjs and Google Analytics 4 Cloud Destination for more information and an example.

The client_id and the session_id are both cookies stored in the user browser. You can use Google gtag get commands or other cookie methods to parse these values from the _ga cookie and _ga_measurementId cookie:

• If your _ga cookie is GA1.1.1783165678.1701112990 then 1783165678.1701112990 is your client_id
• If your _ga_M12454XDR cookie is GS1.1.1710342977.347.1.1710343074.0.0.0 then 1710342977 is your session_id

You are not required to send a session number for server-side hits. Session metrics come from the client-side data after GA4 stitches server-side event data to the client-side session.

Google Analytics 4 collects events triggered by basic interactions with your site. For more information about which interactions are automatically collected, see Google Analytics 4 Automatically Collected events.

Google may take 24-48 hours to process data sent to Google Analytics. As a result, the Google Analytics user interface may not reflect the most current data. The Google Analytics Realtime report displays activity on your site as it happens; however, events seen in Realtime reports do not always equate to how the data is processed in the standard reports. This disconnect between events seen in Realtime reports and Standard reports happens when a Custom Definition is not defined in the GA4 Admin panel.

For event data to be sent downstream to Google Analytics:

1. Configure and enable the Set Configuration Fields mapping. This mapping is required for data to be sent downstream because it sets configuration to the GA4 Measurement ID indicated in the Settings and establishes data flow using the config command.
2. Confirm you call analytics.page() on page load. Analytics.js requires an initial Page call to send data to Google Analytics 4 Web. The Segment snippet includes this initial call by default.
3. Send data with an event: typically this is a page_view as your first event.

Google has introduced a feature for collecting user-provided data, which Segment doesn't support. If you've enabled this feature in your Google Analytics 4 account, it is irreversible and may cause issues with receiving data. If everything else is set up correctly but data is still not appearing, check if this feature is enabled. If it is, you'll need to create a new GA4 space to resolve the issue.

If no events are flowing to your GA4 instance, use one of the Debugging Tools to check the sequence of GA4 events.

If you are sending multiple gtag('config') commands called from Set Configuration mapping on one page before a new DOM has loaded, and you have defined send_page_view: true with each 'Config' event, you may see duplicate page_view events sent to your GA4 measurement id. If this is the case, see Google's documentation on Ignoring duplicate instances of on-page configuration.

If your site is a Single Page Application (SPA), you may want to leave the Ignore duplicate instances of on-page configuration toggle disabled in the Google Tag Admin as a new DOM is not called on each new page path. If you have a SPA, disabled the Ignore duplicate instances of on-page configuration toggle, and have multiple Set Configuration mappings, use Segment's new Send Page Views field mapping to override the send_page_view parameter in your Settings. This selection takes precedence over what is defined in the Segment Settings. If you leave the selection for your destination undefined, it will fall back to what you selected in the Segment Settings.

If you enabled Enhanced Measurement, you might see additional page_view events. This happens when you enable the Page changes based on browser history events feature in the Advanced settings section of the pageviews settings. To avoid double counting page views on history state changes, disable the Page changes based on browser history events feature. See Google's Manual pageviews documentation for more information.

If you prefer to keep the Page Views setting disabled and manually send page_view events, see Google's documentation, Manually send page_view events.

With Google Analytics 4 Web, you must configure a Custom Event mapping to manually send page_view events. When mapping the events, set the Event Name to page_view.

You can now override the send_page_view value defined in the Segment Settings for the GA4 destination. To override the send_page_view value, navigate to your Set Configuration Mapping, click "Show More Fields" to expose the field mapping, and select either True or False. This selection takes precedence over what is defined in the Segment Settings. If you leave this selection undefined, Segment uses the selection you made in the Segment Settings.

Segment automatically tracks UTM parameters when they are present in the URL and sends them to Google. For example, with the following URL, Segment would send email_variation1&utm_medium=email&utm_source=email_promo&utm_campaign=summer_sale&utm_id=abcd to Google: https://www.example.com/?utm_content=email_variation1&utm_medium=email&utm_source=email_promo&utm_campaign=summer_sale&utm_id=abcd

By default, if the UTM values are found in the page_location parameter, GA4 automatically maps the campaign parameters to their appropriate value. There is no additional configuration required, unless you want to override what GA4 defines. This is true for both Event mappings and the Set Configuration mapping. If you modify the output of the page_location and the UTM parameters are not included, this might result in erroneous acquisition and attribution mapping.

To observe this feature, trigger a Page call with UTM parameters present in the URL and navigate to the Realtime overview report in GA4 to see the resulting page_view event under the Event count by Event name card. The Acquisition card in the Realtime overview report reflects First User acquisition, but may not reflect the parameters of the event if this was a second session event.

To pass custom event parameters to all events on the page, navigate to your Set Configuration Mapping, click Show All Fields, and enter any custom Event Parameters, including page_view. Any event parameters that have the same parameter key as your other event mappings will take precedence over what is set in the Set Configuration Mapping.

To send custom item parameters, add the custom item parameter name in mappings where there is a Products array. Register your custom item parameter in the GA4 Admin panel if you would like this value processed in the GA4 UI. You can ONLY add custom item parameters in the Products array. If you add custom item parameters as an Event Parameter, they will be registered as an Event Parameter.

In each Event Mapping, there is a "Send To" parameter. Set this to "True" if you would like to include the send_to parameter and only send the event to the measurement_id configured in your settings. If you select "False" or do not enter a selection, GA4 Events will broadcast to all measurement IDs, including Google Ads IDs, on the page. These measurement IDs may be set outside of Segment. For more info on how the send_to parameter works, see Google's documentation on Group and Route Data.

Yes. In the Set Configuration Mapping, click Show All Fields and scroll to Send Page Views. Your selection overrides what is set within the Settings. This is helpful if you are updating the user_id or user_properties for all events on the page where you want to call the config command but do not want to send a page_view.

Segment's Google Analytics 4 Cloud server-side destination uses Google's Measurement Protocol API to send event data server to server, whereas Segment's Google Analytics 4 Web device-mode destination loads the gtag.js library client-side and uses Segment's event data to map to gtag.js events directly. Each destination has its own advantages and disadvantages. Your choice between the two depends on your specific use case, technical expertise, and the platforms from which you want to track data.

Google has introduced a beta feature for collecting data provided by users, User-provided data collection. Note that this feature is currently not supported by Segment, and, acknowledging this feature policy in your Google Analytics 4 Account has irreversible effects.