Scarlett
Forum Replies Created
-
Unfortunately, as of my current knowledge, there seems to be no feature available to directly adjust the width of columns or panels within the Google Analytics 4 interface. The Google Analytics interface doesn’t provide an option for manual adjustments to column widths. However, you could consider exporting the data to a CSV file, where you could adjust column widths manually. Additionally, if you’re trying to analyze URL data, consider using a secondary dimension to split the URL between hostname and path, making it easier to read.
-
Certainly, you can integrate each of your Android apps with a unique GA4 property within your Firebase. Here are the steps that you should follow:
1. Log into your Firebase console, and select your project.
2. From the project settings, navigate to the “Integrations” section and you’ll find Google Analytics.
3. If Google Analytics is not linked, click on “Link” and then “Link to Google Analytics”.
4. Then select “Enable Google Analytics for this project” and click on “Next”.
5. You’ll be prompted to configure your Google Analytics account. If you have a GA4 property already, select that. If not, create a new account and GA4 property.
Repeat the same steps for your second app too, but make sure to use or create a different GA4 property.
Remember that your Firebase SDK version should be up-to-date for this to work, and it may take up to 24 hours for data to start appearing in Google Analytics.
If you’ve followed all these steps and are still struggling, it’s maybe an issue for Firebase support.
Please do overlap reporting as Firebase Analytics data is not the same as Google Analytics 4. Sometimes it’s better to look at each separately depending on the data you need.
-
Sure, let’s take a step back and look at what Google Tag Manager (GTM) and Google Analytics 4 (GA4)/gtag.js do.
At the core, think of GTM as a “container” that can hold numerous tracking codes (including GA4/gtag.js). So, you put all your tracking code inside GTM, and then you only need to install GTM on your website once. That’s why it’s popular – you can manage multiple tags from one location.
On the other hand, gtag.js is the JavaScript library that communicates directly with Google Analytics. It fires off the data you want to track to GA. You can run it independently, without GTM.
Ideally, you should only use GTM. Put your GA4 tracking inside GTM, along with any other tracking codes you want. GTM smartly manages all the codes, tracks the data you want, and sends it to your Google Analytics in the most efficient way.
But technically, you couldload both GTM and gtag.js separately on your site. While they won’t cause any syntax issues, it’s possible they could create some logical tracking conflicts. For instance, you may end up firing the same event twice – once from gtag.js and once from GTM – which can mess up your analytics. Also, they would use the same cookies.
So in short, while you technically “can” use gtag.js and GTM together, it’s simpler, cleaner and more efficient to just use GTM and manage your GA4 tracking from there.
-
Unfortunately, there is not currently a way to stop Google Analytics 4 (GA4) from automatically attaching “_gl=xxx” to the ends of your external links. This is an automated feature of GA4 and there are no settings or configurations that can turn it off. You’ve done everything correctly in your JS tracking code, but the “decorate_links” parameter doesn’t actually exist in GA4, which is why it’s not working. The best workaround at the moment would be to use a URL cleaning function to remove the parameters when needed. For example, if you’re using Google Tag Manager, you could create a Custom JavaScript variable that cleans the URL before sending it to GA4.
-
Hey there! It looks like you’re trying to make full use of ecommerce columns with a custom Tag Manager Event.
Unfortunately, if you’re using an appropriate EEC event, that’s the only way you’ll be able to send EEC values. When you use a regular event to send complex data structures, it means you’re bound to the limitations of event properties.
Yes, you’ve noticed correctly that GA4 lets you create and modify events based on other events, but this function is a bit on the simplistic and limited side. It mostly is due to Google trying to balance functionality against costs to keep the product free and accessible to everyone.
As for your question on handling large values for the table with a custom event, GA4 might not be as flexible as enterprise analytics solutions in the market when it comes to the number, size and the complexity of processing the dimensions. You might notice a bit of a bottleneck when trying to parse dimension values into sub-dimensions.
A workaround could be to split your dimensions into subdimensions with a little bit of ETL magic, but remember this would mean you have to process your data after it’s exported to BigQuery.
I hope this helps clarify things for you!
-
Yes, your understanding is correct. The process of migrating from Universal Analytics (UA) to Google Analytics 4 (GA4) does involve manually updating each tag from UA to GA4 in Google Tag Manager (GTM). This is because UA and GA4 are fundamentally different systems and they do not share the same data model. The Google Analytics Migration Assistant can guide you through this process but, unfortunately, an automatic conversion tool is not provided. So, yes, it can be quite a task, especially if there are numerous tags to be converted.
-
The issue seems to lie in the set-up of your RegEx table variable. The first issue could be related to the ‘Input Variable’. The ‘Variable Type’ is ‘Page Path’ which may not be the correct location to find ‘_form_23’. Make sure to select the correct input source. The second issue could be with the matching pattern. You are using ‘^div._form\_23$’ which will look for ‘_form_23’ at the start or end of the string, and it must be exact. The characters ‘> div._form_23 >’ wouldn’t match this pattern, and if they are part of the string you are searching then they wouldn’t count as a match and the variable would appear as undefined. Change your regex pattern to ‘div._form\_23’ and ensure it is in the correct form and you should have a match.
