Skip to content

Commit 720610a

Browse files
authored
Minor changes
1 parent b4290d7 commit 720610a

File tree

1 file changed

+1
-1
lines changed
  • src/connections/destinations/catalog/actions-google-analytics-4-web

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ With custom parameters, you must create [custom dimensions and metrics](https://
3737

3838
### Custom Events
3939

40-
Before you create a custom event, make sure the event you want to create isn't already collected through an [automatically collected event](https://support.google.com/analytics/answer/9234069?sjid=7831609405656395105-NA){:target="_blank"} or recommended as a [recommended event](https://support.google.com/analytics/answer/9267735?sjid=7831609405656395105-NA){:target="_blank"}. It's always better to use an existing event because these events automatically populate dimensions and metrics that are used in your reports.
40+
Before you create a custom event, make sure the event you want to create isn't already collected through an [automatically collected event](https://support.google.com/analytics/answer/9234069?sjid=7831609405656395105-NA){:target="_blank"} or recommended as a [recommended event](https://support.google.com/analytics/answer/9267735?sjid=7831609405656395105-NA){:target="_blank"}. Segment recommends using an existing event, because these events automatically populate dimensions and metrics that are used in your reports.
4141

4242
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 snake cased in Google Analytics 4.
4343

0 commit comments

Comments
 (0)