Skip to content

Commit b19e3dd

Browse files
authored
Remove "Resolving duplicate page_views" paragraph
1 parent eab8675 commit b19e3dd

File tree

1 file changed

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

1 file changed

+0
-8
lines changed

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

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -44,14 +44,6 @@ The automatically collected and enhanced measurement events include parameters b
4444

4545
## FAQ & Troubleshooting
4646

47-
### Resolving Duplicate Page Views
48-
49-
When enabled, the **Page Views** setting sends the `page_view` event from Segment triggered by the **Set Configuration Fields** mapping. It does not prevent sending the `page_view` event included Google's gtag.js snippet. If you enable this setting, once the page loads, Segment sends two `page_view` events to the GA4 SDK, one from the Segment snippet and one from the gtag.js snippet. If you see duplicate `page_view` events in your GA4 dashboard, you can either
50-
51-
1. Disable the **Page Views** setting (set it to *False*) so only the `page_view` included in the gtag.js snippet sends to the GA4 SDK. Or,
52-
2. The GA4 SDK also tracks a native `page_view` event if you have the [following setting enabled](https://developers.google.com/analytics/devguides/collection/ga4/views?client_type=gtag#measure_virtual_pageviews){:target='_blank'} in your GA4 account. To avoid the native GA4 `page_view` event, disable **Page changes based on browser history events** under the advanced settings of the **Page views** section.
53-
54-
5547
### Custom Event Naming
5648

5749
Google Analytics 4 does not accept custom event names that include spaces. Segment replaces spaces in the Event Name in the Custom Event action with an underscore. As a result, you will see custom events snake cased in Google Analytics 4.

0 commit comments

Comments
 (0)