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

rchinn1 · web-flow · commit 0a944dcbcb41 · 2022-05-02T10:24:27.000-07:00
diff --git a/src/connections/destinations/catalog/actions-google-analytics-4/index.md b/src/connections/destinations/catalog/actions-google-analytics-4/index.md
@@ -67,7 +67,7 @@ In addition to recommended events, you can also send custom events using the [Cu
 > info "Event naming limitations"
 > Google Analytics 4 requires that all event names contain only alpha-numeric characters and underscores, and must start with an alphabetic character. Segment replaces spaces in Event Names with an underscore, so that these events are accepted by GA4. For example, Segment renames an event named `Home Profile` to `Home_Profile`. In some cases, GA4 may reject an event outright, due to unsupported characters. For example, an event named `Home | Profile` will be silently rejected due to the pipe character.
 > 
-> In all cases, event names in GA4 are case sensitive. The Custom Event action includes a **Lowercase Event Name** option, to ensure consistency of all events sent to Google. For more information, see Google's articles [Google Analytics 4 event name rules](https://support.google.com/analytics/answer/10085872?hl=en&ref_topic=9756175#event-name-rules){:target='_blank'} and [Event name limitations](https://developers.google.com/analytics/devguides/collection/protocol/ga4/sending-events?client_type=firebase){:target="_blank"}
+> In all cases, event names in GA4 are case sensitive. The Custom Event action includes a **Lowercase Event Name** option, to ensure consistency of all events sent to Google. For more information, see Google's articles [Google Analytics 4 event name rules](https://support.google.com/analytics/answer/10085872?hl=en&ref_topic=9756175#event-name-rules){:target='_blank'} and [Event name limitations](https://developers.google.com/analytics/devguides/collection/protocol/ga4/sending-events?client_type=firebase){:target="_blank"}.
 
 #### Custom Dimensions & Metrics
 With Google Analytics 4, you must create custom dimensions and metrics within the Google Analytics 4 interface and link 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. Custom dimensions can be either event-scoped or user-scoped, and custom metrics must always be event-scoped. To send parameters to Google Analytics 4, use the Event Parameters or User Properties object available on every action. Google will silently drop any events that include nested parameters so please ensure you are only passing flat key-value pairs in the Event Parameters and User Properties objects.

Original file line number	Diff line number	Diff line change
`@@ -67,7 +67,7 @@ In addition to recommended events, you can also send custom events using the [Cu`
`67`	`67`	`> info "Event naming limitations"`
`68`	`68`	> Google Analytics 4 requires that all event names contain only alpha-numeric characters and underscores, and must start with an alphabetic character. Segment replaces spaces in Event Names with an underscore, so that these events are accepted by GA4. For example, Segment renames an event named `Home Profile` to `Home_Profile`. In some cases, GA4 may reject an event outright, due to unsupported characters. For example, an event named `Home \| Profile` will be silently rejected due to the pipe character.
`69`	`69`	`>`
`70`		-> In all cases, event names in GA4 are case sensitive. The Custom Event action includes a Lowercase Event Name option, to ensure consistency of all events sent to Google. For more information, see Google's articles [Google Analytics 4 event name rules](https://support.google.com/analytics/answer/10085872?hl=en&ref_topic=9756175#event-name-rules){:target='_blank'} and [Event name limitations](https://developers.google.com/analytics/devguides/collection/protocol/ga4/sending-events?client_type=firebase){:target="_blank"}
	`70`	+> In all cases, event names in GA4 are case sensitive. The Custom Event action includes a Lowercase Event Name option, to ensure consistency of all events sent to Google. For more information, see Google's articles [Google Analytics 4 event name rules](https://support.google.com/analytics/answer/10085872?hl=en&ref_topic=9756175#event-name-rules){:target='_blank'} and [Event name limitations](https://developers.google.com/analytics/devguides/collection/protocol/ga4/sending-events?client_type=firebase){:target="_blank"}.
`71`	`71`
`72`	`72`	`#### Custom Dimensions & Metrics`
`73`	`73`	With Google Analytics 4, you must create custom dimensions and metrics within the Google Analytics 4 interface and link 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. Custom dimensions can be either event-scoped or user-scoped, and custom metrics must always be event-scoped. To send parameters to Google Analytics 4, use the Event Parameters or User Properties object available on every action. Google will silently drop any events that include nested parameters so please ensure you are only passing flat key-value pairs in the Event Parameters and User Properties objects.