We’ve recently set up a server container to route all GA4 events through Stape, and it’s working well. However, I’d like to stop sending page_view events from the server container to reduce unnecessary event volume and focus only on key actions (like purchase, add_to_cart, etc.).
Could you please confirm the best way to prevent page_view from being sent server-side — either by:
Disabling or filtering this event in the server container settings, or
Adding a condition/exclusion in the client or tag configuration?
I’ve already disabled other non-essential events like user_engagement and form_start.
Please let me know the recommended approach to exclude page_view cleanly without impacting other event types.
My suggestion for you. The best way to exclude page_view is by adding a filter in your server GA4 tag trigger, set it to fire only when the event name does not equal page_view. This will keep all key events (like purchase, add_to_cart, etc.) working normally.
I wouldn’t recommend filtering out page_view events.
The page_view event carries important information about how users land and navigate your site. GA4 relies heavily on it for tracking sessions. In fact, a new session typically starts when a page_view is logged.
If you remove all page_view events, you risk losing session data and potentially breaking attribution since parameters like gclid, fbclid, UTMs, referrer information are captured during the first page view.
1 Like