Skip to content

Commit 1c09d04

Browse files
Merge pull request #2312 from segmentio/develop
Release 22.1.2
2 parents 37cb062 + ba94afb commit 1c09d04

File tree

4 files changed

+45
-443
lines changed

4 files changed

+45
-443
lines changed

src/_includes/components/actions-fields.html

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -79,8 +79,8 @@
7979

8080

8181
{% if action.fields.size > 0 %}
82-
<p class="button button-fill button-fill--white" data-toggle="collapse" data-target=".settings-content-{{action.slug}}">Click to expand fields</p>
83-
<div class="collapse settings-content-{{action.slug}}">
82+
<p class="button button-hollow" data-toggle="collapse" data-target=".settings-content-{{action.slug}}">Click to show / hide fields</p>
83+
<div class="collapse settings-content-{{action.slug}} show">
8484
<table id="settingsTable">
8585
<thead>
8686
<tr>

src/connections/destinations/catalog/actions-google-analytics-4/index.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,5 +40,20 @@ To add the Google Analytics 4 destination:
4040

4141
{% include components/actions-fields.html %}
4242

43+
## Troubleshooting
4344

45+
### Custom Event Naming
4446

47+
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 will see custom events snakecased in Google Analytics 4.
48+
49+
Google Analytics 4 is also case sensitive. If you would like all event names lowercased, use the `Lowercase Event Name` setting in the Custom Event action. If this setting is disabled, Google will treat event names with different casing as distinct events. For more information, see [Google Analytics 4 Event name rules](https://support.google.com/analytics/answer/10085872?hl=en&ref_topic=9756175#event-name-rules&zippy=%2Cin-this-article.%2Cin-this-article){:target="_blank"}.
50+
51+
### User Metrics & Sessions
52+
53+
Segment sends a Google `clientId` in requests to the Measurement Protocol API, alongside other required API fields. However, user sessions are [not currently supported by the Measurement Protocol API](https://developers.google.com/analytics/devguides/collection/protocol/ga4/reference/limitations){:target="_blank"}, so user metrics might not appear on the Google Analytics 4 Realtime report or several other reports.
54+
55+
To validate your implementation, check users on the Events report and User Explorer. You can also confirm events are picked up in the Realtime report.
56+
57+
### Debug Mode
58+
59+
The Google Analytics 4 [debug mode](https://support.google.com/analytics/answer/7201382?hl=en){:target="_blank"} only works with a client-side implementation through gtag.js, Google Tag Manager, or Firebase. Because Segment’s Google Analytics 4 integration is server-side and uses the Measurement Protocol API, debug mode is not supported.

0 commit comments

Comments
 (0)