Skip to content

Commit cb9a497

Browse files
authored
Merge pull request #2460 from segmentio/ga4-more-notes
Add more to GA4 docs
2 parents 86cd71c + 938412b commit cb9a497

File tree

1 file changed

+13
-3
lines changed
  • src/connections/destinations/catalog/actions-google-analytics-4

1 file changed

+13
-3
lines changed

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

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

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

43-
## Troubleshooting
43+
## FAQ & Troubleshooting
4444

4545
### Custom Event Naming
4646

4747
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.
4848

4949
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"}.
5050

51+
### Custom Dimensions & Metrics
52+
53+
With Google Analytics 4, you must create custom dimensions and metrics within the Google Analytics 4 interface and link event parameters to the corresponding dimension or metric. 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](https://support.google.com/analytics/answer/10075209?hl=en)
54+
55+
### Debug Mode
56+
57+
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.
58+
59+
### Mobile Data
60+
61+
The Google Analytics 4 Measurement Protocol API is only compatible with web streams. Google requires use of their Firebase SDKs to send mobile data to Google Analytics 4. For more information on linking Google Analytics 4 properties to Firebase, see [Google Analytics 4 Firebase integration](https://support.google.com/analytics/answer/9289234?hl=en){:target="_blank"}.
62+
5163
### User Metrics & Sessions
5264

5365
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.
5466

5567
To validate your implementation, check users and events on the Events report and User Explorer.
5668

57-
### Debug Mode
5869

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)