[Roman]

It sounds like you’re on the right track, trying to find the event frequency as a percentage of the total views. The “xyz” event might not be captured correctly, or there could be an issue in how you’re setting up your Google Analytics 4 or Google Data Studio. You should ensure your tracking tag for the “xyz” event is installed correctly and working as expected. You might need to refine your filters or create a new report that focuses specifically on “xyz” and “page_view” events to get the clear picture you’re after. Google’s online help resources or forums could also provide some valuable guidance. You might even need to consult with a data analyst or a specialist in Google’s tools if you’re still having trouble.

[Roman]

Indeed, the response body of your requests doesn’t currently appear on Google Cloud Log Explorer as a default option. This is a standard design due to privacy and costs, regarding logging everything by default. However, you can enable body logging in some Google Cloud services like Google Cloud Functions and Cloud Run by modifying the function’s code according to the function’s documentation.

For instance, in GTM Server-Side, if the changes you make get compiled into JavaScript and executed, you can add custom logs to your code using the “console” object. After doing this, you’ll be able to see these logs in the Log Explorer under the “textPayload” field. Keep in mind, when adding extra logs, you have to watch out for User Privacy and Google’s usage costs (always depending on the amount of data you’re logging, and how long you retain these logs).

On the other hand, for the error catching and alerting system, Google Cloud Logging offers the option to create metrics based on the logs and then set up alerts based on these metrics in Google Cloud Monitoring.

Remember that making these changes should be carefully done, especially when it comes to user privacy and cost management.

[Roman]

You’re correct in surmising that it may be due to not specifying exactly which Google Analytics property you wish to send the event to. When you call gtag('event',...), it sends that event to all configured properties, hence the double reporting. To send an event to a specific property, you should use the following syntax: gtag('config', 'GA_MEASUREMENT_ID'); followed by your desired gtag('event',...). Remember to replace ‘GA_MEASUREMENT_ID’ with your actual Google Analytics Measurement ID. This will make sure that the event is sent only to the specified property.