Google Analytics 4 Proxy Multi-Config Reference

Configuration considerations when using multiple Google Analytics measurement IDs in an environment

By default, built in page_view, scroll, and user_engagement events will be sent to all configured measurement IDs in a given environment, for every page where the Freshpaint Autotrack snippet is loaded. The Google Analytics first_visit and session_start events are derived from properties sent to the page_view event in this case.

So, for example, if you have 15 measurement IDs for a single environment, on any page where you load Freshpaint with your environment ID, a page_view event will be sent to all 15 measurement IDs in Google Analytics.

In some scenarios, such as where each measurement ID is intended to be for only a specific page or subdomain, this can result in duplicate events in Google Analytics.

If you would like to have a view of a given page go to just one particular measurement ID, and not others, then you would not want to use the built in page_view event, and possibly not the built-in scroll and user_engagement events.

Even when you have only a single measurement ID, you might not want these built-in events to be sent from every page the Freshpaint Autotrack snippet is loaded.

You can instead create custom page_view, scroll, and user_engagement events, to be sent only for the conditions you choose (such as page URL), as detailed below.

Built in event setup options:

There are 3 ways a user can set up page_view or a built-in event so that they get Google Analytics first_visit and session_start tracking.

1. Enable "Send Page View Event". This will send page_view events (along with the necessary properties for first_visit and session_start events) , from all pages where the Freshpaint Autotrack snippet is loaded, to every measurement ID.

2. Disable "Send Page View Event", and create your own custom page_view event. When this is sent, it will automatically include the necessary properties for first_visit and session_start events. Note this will require you to edit your website code or add it to Google Tag Manager. If you name it something other than page_view, you can use Transformations to rename it to page_view when sending to GA4.

3. If you have disabled "Send Page View Event" and choose not to send custom page_view events, then please reach out to [e-mail] to enable "Session tracking" for your environment, which sends a built-in event with the necessary properties for first_visit and session_start events from all pages where the Freshpaint Autotrack snippet is loaded.

There are 2 ways a user can set up scroll events.

1. Enable "Send Scroll Event". This will send scroll events from all pages where the Freshpaint Autotrack snippet is loaded to every measurement ID.

2. Disable "Send Scroll Event", and optionally create your own custom scroll event. Note this will require you to edit your website code or add it to Google Tag Manager. If you name it something other than scroll, you can use Transformations to rename it to scroll when sending it to GA4. Sending scroll events is not strictly necessary.

There are 2 ways a user can set up user_engagement events.

1. Enable "Send User Engagement Event". This will send user_engagement events from all pages where the Freshpaint Autotrack snippet is loaded to every measurement ID.

2. Disable "Send User Engagement Event", and optionally create your own custom user_engagementevent. Note this will require you to edit your website code or add it to Google Tag Manager. If you name it something other than user_engagement, you can use Transformations to rename it to user_engagement when sending it to GA4. Sending user_engagement events is not strictly necessary.

How to access GA4 configuration:

Navigate to the apps page and click Manage for the GA4 destination.

Click Configure in the Base Configuration row.

From here you can enable or disable the built in Send Page View Event, Send Scroll Event, and Send User Engagement Event.