You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/actions-google-analytics-4-web/index.md
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ After you've set up at least one event in your **Mappings** tab, you can see you
33
33
34
34
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.
35
35
36
-
### Recommended Events
36
+
### Recommended events
37
37
38
38
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.
39
39
@@ -65,7 +65,7 @@ Some of Segment's prebuilt [Available Actions](https://segment-docs.netlify.app/
65
65
66
66
{% include components/actions-fields.html settings="true"%}
67
67
68
-
## FAQ and Troubleshooting
68
+
## FAQ and troubleshooting
69
69
70
70
### Debug mode
71
71
@@ -85,11 +85,11 @@ Google may take [24-48 hours](https://support.google.com/analytics/answer/933379
85
85
86
86
### Data is not sent to Google
87
87
88
-
In order for data to be sent downstream to Google Analytics, check your mappings to ensure that:
89
-
1. The **Set Configuration Fields** mapping is enabled in your mappings.
90
-
2. You've added at least one other event mapping for an event you want to send to Google Analytics.
88
+
For data to be sent downstream to Google Analytics, all of the following conditions must be met:
91
89
92
-
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. If you have no enabled mappings other than **Set Configuration Fields**, the GA4 destination does not send events downstream.
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.
0 commit comments