[Ava]

It sounds like you’re having issues with setting up item scoped parameters on GA4 via ‘Google Analytics: GA4 Event’ Tag Type in GTM. As of now, there’s no direct support for item parameters on this tag type. You might have to use a DataLayer push as a workaround, despite the inconvenience it might bring with your current setup.

[Ava]

These errors you’re seeing are often due to attempted access or invocation of properties or methods from an undefined variable in your code. ‘TypeError: Cannot read properties of undefined’ implies that somewhere in your code, you might be trying to access the ‘id’ property of an object that is undefined. Similarly, ‘o is not a function’ implies that you’re trying to execute ‘o’ like a function while it’s not actually a function. These could occur due to errors in your conversion from Google Analytics 3 to 4, such as not correctly initializing a variable or missing parameters. Debugging the codebase to identify where these undefined references originate is a good start to resolve these issues. It is also possible that some parts of your application may not be compatible with Google Analytics 4 hence causing these issues. It would be a good idea to cross-check your implementation against the official documentation of Google Analytics 4 or Firebase. It’s always helpful to ensure the libraries and packages being used are updated and compatible with each other.

[Ava]

Of course, I’d be happy to simplify this for you.

There might be an issue with the title of your event not being set correctly, and that’s why it reads as “not set” on your GA4 interface. Here are two possible solutions.

1. First, you could tweak your code a little. Currently, your function triggers the event even when there’s no title attached to it. Would you be okay if the event didn’t trigger at all when that happens? If so, you can just add an if statement to your function checking if the title is not empty, like this:

`javascript
function ebooksGA4new(title) {
if(!title || title==””)
return false;
gtag(‘event’, ‘ebooks’, {
‘titolo’: title
});
}
`
This code will prevent the function from running when title is not set.

2. Second, you can investigate what’s happening by using a tool such as Chrome devtools to inspect your webpage’s interactions with GA. This should also give you a visual representation of your data on your GA4 real-time report.

Here’s how your page might look like on devtools: [Image here](https://i.stack.imgur.com/GgLKo.png)

In the picture, you can check all the interactions between your website and Google Analytics. If your event is correctly firing off with the title parameter, it should appear here.

So, those are your two potential ways of finding out what’s going on when your custom event is fired.

[Ava]

Sorry, but I can’t provide the help you need without actually being able to view the images you’ve linked. However, I’d suggest double checking that your API key is correct and that the event you’re trying to send aligns with Google Analytics 4’s event model. Ensure your json format is correct too, as it could be a very simple formatting error hindering your success.

[Ava]

Based on the errors and details you’ve described, it seems like an SSL certificate issue related to the grpc communications for your Python project. It appears that the script you’re running is trying to communicate via a secure channel with a remote server with IP address: 142.250.190.10, yet the SSL handshake is failing. The cause is either because the server is not properly SSL provisioned or there is a misconfiguration on your side. This kind of issue can also occur when the client (your machine running the script) is not capable of trusting the SSL certificate presented by the server during the handshake because it cannot identify the certificate authority (CA) that signed the server’s certificate.

You’ve already tried installing Google certificates locally which should ideally have worked, but it seems like this IP address is not trusted. You can check to see if you can manually trust the certificate coming from that IP address, but I would also suggest reaching out to the team responsible for the server the script is trying to reach, to check that everything is correctly configured on their side. You may also try to run a diagnostic with a tool such as OpenSSL to get more details about the server’s SSL setup.

Remember, bypassing SSL verification for the sake of avoiding this error could pose significant security risks such as exposing sensitive information being sent over the network, so approach that possible solution with caution.

[Ava]

Sure thing! If you can’t see the “Page path + querystring” option, here is a neat workaround you could try using the “Explore” feature.

So, what you do is this: On the left-hand menu, you click “Explore,” and then “Free form.” This will open up a work area, where you have dimensions and metrics on the left. You’ll need to pick “Page path + querystring” from dimensions. Then click the ‘import’ button, which is at the top right.

Next, you have to choose the metric, and for that, you pick “Views” in the “Page/Screen” section.

Once that’s set, it’s just a matter of organizing the data. You’ll see areas called ‘Rows’ and ‘Values.’ Drag and drop your chosen dimension (Page path + querystring) to ‘Rows’. Move your chosen metric (Views) to ‘Values.’

That’s about it. It may take a bit of getting used to, but once you’ve got the hang of it, you’ll find this can be a powerful tool to work with data. It’s quite similar to the Google Data Studio, but conveniently set right within GA4. And the best part? It seems to work faster and offers more options, including pathing.

[Ava]

The problem you’re encountering might be linked to Google Ads Hotel campaigns having difficulties interacting with Google Analytics 4. There are some reporting mismatches between these two platforms at times. Specifically, the new GA4 tends to handle data differently, so it may not report in the exact same manner as Universal Analytics. As for the GCLID, it should indeed stay constant across the entire customer journey, including all booking engine pages, to ensure proper tracking. You might need to check your website and make sure the gtag events and GCLIDs are properly implemented across all pages. If the problem persists, consider reaching out directly to Google’s support for assistance, as the issue seems technical in nature.