Ashton
Forum Replies Created
-
Based on your question, it seems like you’ve set up everything correctly but aren’t seeing the search term value appear in Google Analytics 4. This is most likely an issue with the variable configuration in Google Tag Manager.
In your variable settings in GTM, you’re trying to get the value of the parameter ‘tx_kesearch_pi1[sword]’. However, according to the URL example you provided, the parameter in the URL is ‘tx_kesearch_pi[sword]’. There seems to be an extra ‘1’ in your GTM variable. This could be why GTM isn’t able to retrieve the correct search term value.
Please update your GTM variable and change ‘tx_kesearch_pi1[sword]’ to ‘tx_kesearch_pi[sword]’. Test it again to see if the search term is correctly being sent to Google Analytics 4.
If you’re still having problems after making this change, please check if you’re properly capturing the variable value in both the Tag and the Trigger settings. There might be an error in your Regex configuration, too.
Remember that GTM is sensitive to changes, so make sure all the configurations are identical to your webpage URLs, parameter names, and Regex settings.
-
Unfortunately, if you’ve been sending data with incorrect mapping on your custom dimensions, the raw data Google Analytics 4 (GA4) received before you corrected the issue is not retrievable in the correctly mapped format. GA4 only processes data as it’s received; it doesn’t reprocess data based on changes you make to your configuration down the line.
In GA4, custom dimensions and metrics use the parameter name you provide in events. That’s why it’s necessary to set up ‘custom_map’ to map the parameter names of the events to the corresponding custom dimensions or metrics. If the data was sent in an incorrect format, GA4 couldn’t recognize it as the corresponding dimension or metric.
The page URLs with the language and the module will still be accessible, but they wouldn’t be mapped to the named custom dimensions you’d set up now. You’ll only start getting the correctly reported data from the time the issue was fixed forward. There’s unfortunately no workaround to apply the new custom mapping retroactively. The best course of action is to correct the implementation as you have done and move forward with the correct data collection.
-
From what you’ve described, it seems Google Analytics 4 (GA4) is trying to encode your URLs that have non-latin characters, which is causing problems for your data analysis. To address this, it might be helpful to implement URL rewriting rules on your website’s server. There’s a way in web servers to automatically rewrite URLs before they are sent to the user’s browser. This is done with the help of a module called mod_rewrite in Apache servers, or using Rewrite module in NGINX servers.
You’ll likely need to work with your webmaster or web hosting provider to create URL rewriting rules to ensure that URLs are displayed in a more “friendly” format, ideally the same as displayed in the browser, therefore making them more recognizable and efficient for your use in GA4 and Looker Studio. This process can also go under the name “URL normalization,” where you map multiple accesses to a resource to a single canonical URL.
Please remember that making these changes could potentially impact your SEO, so make sure to proceed carefully, likely incorporating 301 redirects to maintain SEO rankings.
Alternatively, if rewriting URLs at source is not feasible, you can create code within GA4 to decipher the URLs during or after data ingestion. This will require code modifications which should be done by an experienced developer.
As a final thought, for optimal compatibility with diverse systems, having URLs primarily in English (where feasible) is a generally recommended web development practice.
-
Hey there! You might want to check your GTM Tag Configuration. There should be a trigger for ‘All Pages’, which usually has ‘Page View’ as the default type. Make sure this is activated. Here let me show you an image for it: [photo](https://i.stack.imgur.com/7lGld.png).
Just give that a look and hopefully that should get your Page View events firing off again! Let me know how it goes! -
To correct your GA4 setup across two websites, you would need to accurately setup cross-domain tracking. Since you’re dealing with two sites (one of which is embedded via an iFrame), proper attribution is necessary to avoid ‘direct’ sources. Consider creating separate GA cookies for each site, which will contribute to more accurate tracking. You may have to modify the way you generate client_id and session_id. The issue you’re having with both sites sharing the same GA cookie value suggests that the sites are not being seen as distinct by Google Analytics, hence causing attribution issues. If the debugger shows an already existing client id for the embedded site but not a session cookie, it signifies a possible error in the way these elements are being generated or tracked. You might need to bring in a developer with expertise in Google Analytics tracking to fix these issues.
-
The person is experiencing difficulty in triggering GA4 events for their website when it goes live. The events work perfectly in the preview mode but not otherwise. The setup for GA4 configuration tag seems to be perfectly fine as it’s triggering every time a cmpEvent goes off. While they have double-checked the Google Tag Manager container and it is published, they suspect the issue could be with GA4 and may have possibly missed giving some sort of consent it requires. They are seeking any advice or solution to this problem.
-
Sure, I got you. Instead of going to Reports in GA4, use the Explorer view. You see, Reports in GA4 aren’t as flexible as they used to be in Universal Analytics where you could add filters and secondary dimensions. Here’s a way around it:
1. Go to the Explorer view. Be aware, though, that it’s subject to your data retention settings. You might need to change this setting if it’s currently set at 2 months default to something longer like 14 months.
2. In Explorer, you only need the pageviews metric so no need to add any dimensions. This is how it looks like for a property I just recently switched from Universal Analytics:
3. Adding a dimension will break down the graph by that dimension. But you can still filter without adding dimensions to your graph.
Now, let me walk you through the steps to reconstruct your graph from Universal Analytics in Explorer:
1. Go to the Explorer option.
2. Click ‘New exploration’.
3. Click ‘Add metric’.
4. Go to the ‘Page’ section under Metrics and import Views.
5. Change your data visualization to line graph.
6. Drag and drop your views metric in the Rows section.
GA4 might take a little getting used to but it offers a lot of similar functionalities as UA. They set out to make it like Adobe Analytics, but it’s not quite there. Still, it has its own merits. Let’s just focus on optimizing that!
