The**Page Views** setting in the GA4 Web destination settings is toggled on by default. This means that the default**Set Configuration Fields** mappingwill senda`page_view` for you when you enable GA4 Web as a destination. If you don't want to send a`page_view` by default, you can toggle the**Page Views** setting off in your destination settings. However, if you toggle the**Page Views** setting off, you will need to account for the`page_view` to happen after the`config` since session attribution sets on the first event after the config is loaded, which is usally a`page_view`.

The**Page Views** setting in the GA4 Web destination settings is toggled on by default. This means that the default**Set Configuration Fields** mappingsendsa`page_view` for you when you enable GA4 Web as a destination. If you don't want to send a`page_view` by default, you can toggle the**Page Views** setting off in your destination settings. However, if you toggle the**Page Views** setting off, you need to account for the`page_view` to happen after the`config` since session attribution sets on the first event after the config is loaded, which is usally a`page_view`.

This means that`config`should fireat`analytics.page()`, and`page_view`should fire after on a`track` call (i.e.`analytics.track("Viewed Content"`). For proper tracking, the`config` must load prior to any GA4 event. For further troubleshooting, go to your DevTools console and type in “dataLayer” to view the order of events sent to Google Analytics. You can read more about[Manual Pageviews](https://developers.google.com/analytics/devguides/collection/ga4/views?client_type=gtag#manual_pageviews){:target='_blank'} in Google's documentation.

This means that`config`firesat`analytics.page()`, and`page_view`fires after on a`track` call (i.e.`analytics.track("Viewed Content"`). For proper tracking, the`config` must load prior to any GA4 event. For further troubleshooting, go to your DevTools console and type in “dataLayer” to view the order of events sent to Google Analytics. You can read more about[Manual Pageviews](https://developers.google.com/analytics/devguides/collection/ga4/views?client_type=gtag#manual_pageviews){:target='_blank'} in Google's documentation.

Segment's[Google Analytics 4 Cloud](/docs/connections/destinations/catalog/actions-google-analytics-4/) server-side destination uses Google's Measurement Protocol API to send event data server to server, whereas Segment's[Google Analytics 4 Web](/docs/connections/destinations/catalog/actions-google-analytics-4-web/) device-mode destination loads the gtag.js library client-side and uses Segment's event data to map to gtag.js events directly. Each destination has its own advantages and disadvantages. Your choice between the twowill depend on your specific use case, technical expertise, and the platforms from which you want to track data.

Segment's[Google Analytics 4 Cloud](/docs/connections/destinations/catalog/actions-google-analytics-4/) server-side destination uses Google's Measurement Protocol API to send event data server to server, whereas Segment's[Google Analytics 4 Web](/docs/connections/destinations/catalog/actions-google-analytics-4-web/) device-mode destination loads the gtag.js library client-side and uses Segment's event data to map to gtag.js events directly. Each destination has its own advantages and disadvantages. Your choice between the twodepends on your specific use case, technical expertise, and the platforms from which you want to track data.