Skip to content

Commit e27bcd6

Browse files
Add limitation 'Event Type is Page'
Adding a note about the limitation around using condition 'Event Type is Page' with GA4 mappings.
1 parent 2793b7d commit e27bcd6

File tree

1 file changed

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

1 file changed

+3
-2
lines changed

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

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -75,8 +75,9 @@ Google may take [24-48 hours](https://support.google.com/analytics/answer/933379
7575
### Data is not sent to Google
7676

7777
In order for data to be sent downstream to Google Analytics, check your mappings to ensure that:
78-
1. The **setConfigurationFields** mapping is enabled in your mappings
79-
2. You've added at least one other event mapping for an event you want to send to Google Analytics.
78+
1. The **setConfigurationFields** mapping is enabled in your mappings.
79+
2. You've added at least one other event mapping for an event you want to send to Google Analytics.
80+
3. Your event mapping doesn't use the condition 'Event Type is Page,' which depends on the page event that's triggered when your site loads. The initial 'Page' event is claimed by the GA config command, so it can't be used for triggering additional events in GA4. We recommend using [analytics.track()](https://segment.com/docs/connections/spec/track/) for any extra events you'd like to appear in GA4. This ensures your events go through after the initial 'config' has loaded.
8081

8182
The **setConfigurationFields** mapping is required in order for data to be sent downstream. If no other mappings are enabled, the destination does not send events.
8283

0 commit comments

Comments
 (0)