[Oliver]

It sounds like you are having trouble setting up custom events in Google Analytics for your SPA (Single Page Application) and viewing the data in the desired format. When you send events to Google Analytics, make sure you’re sending them in a format that Google Analytics can recognize, and that they align with your custom definitions for ‘meal’ and ‘food’. Lack of synchronization might result to improper reflections. Regarding the pulling of the data in the required format, if Google Analytics default reports won’t allow this, you might have to pull the data through APIs and customize it outside of Google Analytics using tools like Google Sheets or Data Studio. This might require deeper technical knowledge. Ensure that guides you are following are up-to-date as Google Analytics updates often and some methods may become obsolete. As there is no attachment available here, if issues persist, you may need to consult with a technical expert with more detailed information.

[Oliver]

As of now, the Google Analytics Admin API doesn’t support creating and setting up conversion events with additional parameters beyond eventName. Unfortunately, there isn’t a workaround even using Google Tag Manager API. We’ll likely have to wait for Google to add this functionality in the future.

[Oliver]

The problem you are experiencing could be due to a number of factors and it’s difficult to identify the exact issue without further analysis. It’s possible that the events are getting filtered out during the rollup process due to some filtering settings, or there might be a delay in processing the event data. If the amount of data being sent is large, some events may be dropped due to throttling. You should also verify if there’s a discrepancy between your raw data set and BigQuery’s exported data. It’s also worth noting that GA4 filters out bots and spiders, so some traffic may not get recorded. Another possibility is that GA4 discards sessions with events that have out-of-bounds timestamps. It’s suggested to seek support from Google Cloud Support for a more in-depth analysis of your situation.

[Oliver]

Hey there! The “page_view” details you’re after are actually already part of the document you referred to. You can find it on the “page_view” section. It’s fully devoted to this event.

Now about “events” in Google Analytics 4 (GA4), it’s all about making everything an event, unlike in Universal Analytics (UA) where you have distinct types such as “pageview”, “event”, “timing”, and so on. This means you have the freedom to customize all your events according to your needs.

If you’re still not sure, Google has put together a list of recommended events you can use as a guide. You can find that document here: “Recommended events“.

Explore and have fun with it!

[Oliver]

The issue you’re experiencing might be brought on by Google Analytics 4’s tracking of ‘history change’ events. This is a feature primarily introduced for SPAs (Single Page Applications). However, it’s known for not always working as smoothly as planned. I have a solution that you can try. Simply turn off this option. You can find it under ‘Admin’ and then go to ‘Stream’, ‘Enhanced Measurement Settings’ and ‘Show Advanced Settings’. This might resolve the odd event counting you’re encountering.

[Oliver]

Sure, happy to explain it again! What if I told you that you could sort of put a single tag or trigger to cover all your components, instead of making individual tags for each one? Sounds great, right? Well, this can actually be achieved very easily and is common practice with the dataLayer implementation in GTM!

Let me explain a little bit further. Consider you have different components like buttons, accordions, dialogues, messages and so on. You can actually group these components and create a specific tag/triggers for each group.

Take the messages as an example. But first, let’s say, a message can be of four types: success, info, warning or errors. Now, what you can do is create a structure like this using the data layer:

`
dataLayer.push({
‘event’: ‘message’,
‘action’: ‘shown or dismissed’,
‘type’: ‘success, info, warning, error’,
‘message’: ‘the actual text of the message’,
‘location’: ‘something like header, body, footer, console’
});
`

This structure essentially allows you to cover all your message components with just one dataLayer message template and one single tag/trigger in GTM. And the same goes for your other grouped components.

Essentially, this approach makes component handling a lot simpler from both, the front-end and the Google Tag Manager’s perspective. Hope this helps streamline your processes!

[Oliver]

Hey, so looking at your code I spotted this bit:

dataLayer.push({ ecommerce: null });

The issue here is that the word “null” is actually making the dataLayer not work. Think of “null” like a giant off switch. By including it, you’re essentially pressing pause on all things dataLayer. What you should do is take out that line and it should be functioning properly then.