Skip to content

Commit 78ffad2

Browse files
committed
minor edits and casing fixes
1 parent 1c4776c commit 78ffad2

File tree

1 file changed

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

1 file changed

+6
-6
lines changed

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ After you've set up at least one event in your **Mappings** tab, you can see you
3333

3434
Some parameters automatically populate prebuilt [dimensions and metrics](https://support.google.com/analytics/answer/9143382){:target="_blank"} in Google Analytics. For example, the parameters on the automatically collected and enhanced measurement events and the required and optional parameters you send with the recommended events both populate pre-built dimensions and metrics.
3535

36-
### Recommended Events
36+
### Recommended events
3737

3838
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.
3939

@@ -65,7 +65,7 @@ Some of Segment's prebuilt [Available Actions](https://segment-docs.netlify.app/
6565

6666
{% include components/actions-fields.html settings="true"%}
6767

68-
## FAQ and Troubleshooting
68+
## FAQ and troubleshooting
6969

7070
### Debug mode
7171

@@ -85,11 +85,11 @@ Google may take [24-48 hours](https://support.google.com/analytics/answer/933379
8585

8686
### Data is not sent to Google
8787

88-
In order for data to be sent downstream to Google Analytics, all of the following conditions must be met:
88+
For data to be sent downstream to Google Analytics, all of the following conditions must be met:
8989

90-
1. Check that the **Set Configuration Fields** mapping is configured and enabled in your mappings. The **Set Configuration Fields** mapping is required for data to be sent downstream because it sets configuration to Measurement ID and establishes data flow using the `config` command.
91-
2. Check that the **Page Views** setting is toggled on. When the **Page Views** setting is toggled on, a `page_view` will be sent to Google Analytics 4 Web. If you are manually sending `page_view` events instead, see below for additional settings needed in your Analytics workspace.
92-
3. Ensure that you are calling `analytics.page()` on page load. Analytics.js requires an initial Page call to send data to Google Analytics 4 Web. The Segment snippet includes this initial call by default.
90+
1. The **Set Configuration Fields** mapping must be configured and enabled in your mappings. This mapping is required for data to be sent downstream because it sets configuration to Measurement ID and establishes data flow using the `config` command.
91+
2. The **Page Views** setting must be toggled on. When the **Page Views** setting is toggled on, a `page_view` event will be sent to Google Analytics 4 Web. If you're manually sending `page_view` events instead, see below for additional settings needed in your Analytics workspace.
92+
3. Ensure that you're calling `analytics.page()` on page load. Analytics.js requires an initial Page call to send data to Google Analytics 4 Web. The Segment snippet includes this initial call by default.
9393

9494
### Duplicate `page_view` events in GA4
9595

0 commit comments

Comments
 (0)