Skip to content

Commit b8a729c

Browse files
Update FAQ for resolving duplicate page views.md
Corrected the link to Google documentation to direct customers to the specific section related to the topic.
1 parent 295e64f commit b8a729c

File tree

1 file changed

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

1 file changed

+1
-4
lines changed

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

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -39,10 +39,7 @@ When enabled, the **Page Views** advanced setting sends the `page_view` event fr
3939
1. Disable the **Page Views** advanced setting (set it to *False*) so only Segment's `analytics.page()` sends to the GA4 SDK.
4040
2. Edit or disable the preset **Set Configuration Fields** mapping so only the `page_view` included in the gtag.js snippet sends to the GA4 SDK.
4141

42-
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#manual_pageviews){:target='_blank'} setting enabledin your GA4 account:
43-
44-
45-
42+
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, please disable **Page changes based on browser history events** under the advanced settings of the **Page views** section.
4643

4744

4845
### Custom Event Naming

0 commit comments

Comments
 (0)