[Jayden]

Sure, you could handle it by using Google Analytics’ “cross-domain tracking”. Basically, you set up a single property in Analytics, then differentiate the data from each sub-site using the “hostname” dimension. Make sure all your sub-sites are including the same GA tracking script. That’s it, you’re good to go!

[Jayden]

Yes, that’s correct. In BigQuery, a CASE statement is typically used for creating a single column, not multiple ones. Therefore, your query won’t work as intended. However, you could run the CASE expression twice, once for each new column (B and C in your example). Alternatively, you could create a STRUCT type column with B and C as the fields. That way, you can do this all in one step. Later on you can easily select them using something like SELECT new_struct.B, new_struct.C, where ‘new_struct’ is whatever name you decide to give your new struct column.

[Jayden]

It sounds like you’re facing an issue related to interpreting the JSON data and the redirection of data between GTM Server-Side and GA4. Please note some nuances about the Measurement Protocol: it uses the POST method to collect data, thus sending information within the body of the request. However, in your case, it seems like data is not being passed within a POST request body but is rather seen as a URL parameter in a GET request.

Regarding the redirection to ‘https://www.google-analytics.com/g/collect’ instead of ‘www.google-analytics.com/mp/collect’, it seems there is a misconfiguration since it should be going to ‘/mp/collect’, which is the endpoint for the Measurement Protocol.

The issue could be rooted in an error in your GTM Server configuration or a mistake in the Measurement Protocol parameters. I would suggest checking your server-side tagging setup in GTM to ensure that it’s set to handle POST requests and validate your Measurement Protocol parameters.

[Jayden]

Hey there! So, I think I’ve spotted what might be going wrong here. You need to check out your collect network request to see if your dimension is actually being set – that’s an important debugging step.

As it turns out, gtag set isn’t doing what you think it is. Instead, try using config or setting your user id property directly in the event. For more info, here’s a cool link with a full answer: [Google Analytics custom dimension not working: gtag set() method issues](https://stackoverflow.com/questions/73870122/google-analytics-custom-dimension-not-working-gtag-set-method-issues)

After that, if you’re still facing issues, please share a screenshot of your actual Network call, that definitely helps determine if the problem is with GA, or on your page. Keep going, you’ve got this!

[Jayden]

Yes, you’re right in your assumption. According to Google’s document that you provided, once a default URI is set for a datastream, it cannot be updated or changed. That’s likely why your code isn’t updating the stream URL, even though there are no obvious error messages. You might be able to modify other stream attributes, such as the stream name, but the default URI is an immovable property once it’s been set. As a result, there aren’t code changes that you could make to change this behaviour.

[Jayden]

Your Firebase Events issue appears to be a result of the system failing to establish a trusted connection, which is likely arising from problems with the SSL certificate’s validation path. As you mentioned, you’ve tried using network security configuration, and you’re testing the application in a secured environment. This suggests that the SSL certificate might not be correctly imported into your Android application, or its alias and password could be improperly set. Also, one common thing to check is if the date/time settings on your Android device are correct, as this could affect SSL handshake too. Given that you’re running the application on a simulator, you might want to try testing it on an actual device to see if the problem persists. Make sure any firewalls or VPN aren’t blocking the Firebase’s IP addresses that could be leading to the SSLHandshake errors.

[Jayden]

Definitely. Essentially, you might find it useful to configure multiple Google Tag Manager containers through their API. You can find more information about this on their API’s documentation.

In the past, for a similar task, what worked for us was to control multiple tags and triggers in our platform and deploy them all together to Google Tag Manager once.

This API lets you access all the Google Tag Manager Containers available to you, this way you can create the tags and triggers as per your clients’ requirements. However, do keep the API rate limits in mind because it’s quite easy to exceed them, which could cause some issues. So, tread carefully!

[Jayden]

GA4 does track both date and time by default in its analytics. Your issue with seeing only 12am timestamps might be due to how your setup is configured or it could be a bug. And yes, it would be more efficient if GA4 offered the datetime data type for easier time tracking, but as of now many resort to using Javascript variables. So you’re not alone in your predicament.

[Jayden]

In Google Tag Manager, you don’t need a separate Regex table for each case. By using lookup tables, you can commit to maintaining just one table and simply add entries to it. When setting up your trigger, use the value of your relevant variable (like Page Path) to match the exact entry in the Regex table. This way, the trigger would be fired only when the user lands on a page that matches that specific entry. It’s that simple, and your container stays clean!