Isabella
Forum Replies Created
-
It sounds like you’re experiencing quite the predicament with your GA4 Properties and BigQuery. My suggestion would be to look over your configurations again and ensure that these properties are all in the correct timezone. I would also suggest verifying your data stream and BigQuery link setups, as they might be hindering your properties. If this still doesn’t work, it might be worth seeking Google’s support directly, give them clear details about your issue and they should be able to help.
-
The problem seems to be that Google Analytics 4 (GA4) doesn’t provide the built-in dimension defaultChannelGrouping that was available in Universal Analytics. GA4 uses a different approach for reporting and doesn’t come with pre-processed data, hence things like Acquisition channels are not readily available. It is recommended to use traffic sources dimension instead. Since GA4 seems to focus more on raw data, it provides more data handling possibilities but requires more processing. You may have to build your own defaultChannelGrouping dimension using the available dimensions in GA4. For Organic search data specifically, you can also consider sending utm parameters to Google Analytics to categorize the traffic, which could be done using the Medium dimension to identify the organic traffic. However, one key is to remember that reports/data pulling might be a bit different with GA4 as it requires a bit more of pre-processing.
-
The problem here seems to be with trying to manage cookies and other scripts that come from various tags, specifically non-Google ones like Facebook. Updating the tags to ‘granted’ should allow the cookies and scripts to function as normal once the user gives their consent. But this isn’t always the case, with the Facebook tag still not firing even when it’s set to be granted additional consent. The current process isn’t working as smoothly as expected, so some new insight or solutions would be very helpful. The goal is to make these tags update correctly on both Google and non-Google tags when user consent is given, thereby allowing cookies and scripts to work as they should.
-
It seems you’re encountering an unexpected issue where GA4 is producing duplicate link clicks after having setup Outbound clicks tracking in Enhanced Measurement and creating an Auto Event variable for internal clicks through GTM. Some possible reasons might be discrepancies between your Debug View and Live Report figures, or a glitch in the system causing the duplication. However, as the same issue doesn’t appear when you test on a live site with the Live Report, it might also be an issue specifically related to the Debug View. I suggest you check if the debug mode is working properly. If the issue continues, you might want to consult directly with Google support or a professional with technical expertise in GA4.
-
In essence, for Chrome extensions, you aren’t allowed to import scripts from external links within background scripts, content scripts, or any new HTML page or pop-up HTML. The ideal way to handle this is to bring whatever resources or scripts you need into your own chrome extension files and then reference those local files instead. So rather than linking directly to external scripts within your HTML code, you’d link to a local file containing that script. This method ensures your scripts are correctly imported within your chrome extension.
-
While it might seem more complicated to handle multiple GTM containers, the consultant’s advice holds value in terms of accuracy and avoiding unintended GDPR-related conflicts or mistakes happening for non-GDPR sites. The level of risk might be small, but GDPR non-compliance comes with severe penalties which might outweigh the effort of maintaining distinct containers.
Also, handling GDPR domains separately could actually simplify your work, as it would segregate the data and tags that need explicit user consent from the ones that do not, making organization and control easier.
Your idea to use a condition based consent trigger for checking GDPR domain is clever and might offer some protection for non-GDPR sites, but human errors could still occur. Maintaining two separate GTM environments reduces these risks as the margin for error becomes less when you are handling these domains separately. In essence, think of the increased effort in maintaining two containers as an investment in risk mitigation.
-
Hey there! I totally feel where you’re coming from. But worry not; I might have a solution for you. You know when you dive into your GA4 setting (Google Analytics 4), there’s this particular option? It’s sort of like a switch, and it says “Enhanced measurement”. You need to ensure that this one is turned on.
Have a super quick look at this picture for clarity:
Give this a go, and fingers crossed, your problem will disappear! -
Ah, I see! It does seem a bit tricky, doesn’t it? There’s one method I know of to backfill previous data, and that is by utilizing a tool called the Supermetrics Analytics connector. It’s available on the GCP Marketplace. As far as I’m aware, there isn’t another way currently to achieve this. Hope this helps!
-
Hey, I checked out Google’s documentation on “[Automatically collected events](https://support.google.com/analytics/answer/9234069)” and it turns out that these parameters: language, page_location, page_referrer, page_title, and screen_resolution are actually collected by default with every event. So, you might not need to write any additional code. This could be why ‘language’ is being overwritten.
Also, for the Page-View, it should be automatically logged if you turn on the ‘Advance Measurement’ feature. So, your best bet might be to remove the additional codes you’ve added. Here’s an image to help you find and toggle on ‘Advance Measurement’: [Link](https://i.stack.imgur.com/cO8na.png)
Hope this helps, mate!
