Skip to content

Commit fa733c2

Browse files
authored
Minor rewording
1 parent a037892 commit fa733c2

File tree

1 file changed

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

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,9 +34,9 @@ Some parameters automatically populate prebuilt [dimensions and metrics](https:/
3434

3535
### Recommended Events
3636

37-
Google Analytics 4 requires the use of [recommended events](https://support.google.com/analytics/answer/9267735){:target="_blank"} and properties to power certain built-in reports. 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 Order Completed events to the Google Analytics 4 Purchase event by default. If your company uses Products Purchase to indicate a purchase, this can be mapped in the Purchase action’s Event Trigger instead.
37+
Google Analytics 4 requires the use of [recommended events](https://support.google.com/analytics/answer/9267735){:target="_blank"} and properties to power certain built-in reports. 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 `Order Completed` events to the Google Analytics 4 `Purchase` event by default. If your company uses `Products Purchase` to indicate a purchase, you can map it in the Purchase action’s Event Trigger instead.
3838

39-
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 would like to send, please use the [Custom Event action](https://segment-docs.netlify.app/docs/connections/destinations/catalog/actions-google-analytics-4-web/#custom-event). 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. Keep in mind that any custom parameters will need to be defined as [custom dimensions and metrics](https://segment-docs.netlify.app/docs/connections/destinations/catalog/actions-google-analytics-4-web/#custom-dimensions-and-metrics) in your GA4 workspace first.
39+
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](/docs/connections/destinations/catalog/actions-google-analytics-4-web/#custom-event). 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`. You'll need to define custom parameteres as [custom dimensions and metrics](/docs/connections/destinations/catalog/actions-google-analytics-4-web/#custom-dimensions-and-metrics) in your GA4 workspace first.
4040

4141
### Understanding Event Parameters
4242

0 commit comments

Comments
 (0)