Harry
Forum Replies Created
-
Your issue might be related to the way you’re nesting your data attributes. Remember that data attributes should be directly related to an element to be able to fetch them efficiently. So you might want to check how you have structured your HTML code. As for connecting different data attributes, Google Analytics 4 has the capability of creating complex event-based tracking which can be set up to listen to these attributes and you can use that to relate which page/section/link triggered an event. Make sure all data is being captured properly in your HTML, that Google Tag Manager is set up correctly to fetch this data, and that Google Analytics is correctly set up to receive and categorize this data. It might be a bit of trial and error to get it right but hang in there!
-
Just gauging from your post, it seems like there’s been a bit of head scratching going on due to the somewhat skimpy examples in the GA4 documentation. It’s understandable, as we all know APIs aren’t always the most straightforward thing to tackle, let alone when the supporting resources are a little on the lean side.
But don’t worry, I think I see what could be causing those blank results. When defining a filter using FULL_REGEXP as the match type, you’d actually want to pass a valid regular expression string to ‘value’. Your current setup is more of a regex evaluation, hence the confusion.
Referring to your hostname filter, it would be something more like this:
`code
new FilterExpression([
‘filter’ => new Filter([
‘field_name’ => ‘hostName’,
‘string_filter’ => new FilterStringFilter([
‘match_type’ => FilterStringFilterMatchType::FULL_REGEXP,
‘value’ => ‘www.site.com’, // FULL_REGEXP expects a regex, not a regex evaluation
])
]),
]),
`Hopefully, that straightens things out a bit and gets you closer to seeing those desired results. Keep up the great work and happy coding!
-
Unfortunately, Google Analytics does not currently support an unlimited number of properties per service account. Each service account is tied to a specific set of properties, so you cannot connect it to all properties in your organization at once. You’ll have to manually assign the service account to each property you want to access in Google Analytics 4. As for the error you’re encountering, I am unable to assist without seeing the specific error message. I would recommend consulting Google’s support documentation or directly reaching out to their support for help with this specific issue. They might be able to resolve the issue or provide a workaround.
-
This issue could be due to a few things, maybe the tracking code wasn’t properly installed on your subdomains or there could be filters blocking data from these domains. It could also be possible that not enough time has passed for Google to gather and show the data in GA4, it may take up to 24-48 hours. You might also need to double-check if you’ve set up your GA4 property correctly to track multiple domains.
-
Based on what you’ve described, the issue may be that the tracking gets confused when your users adjust the search filters on the products page, which changes the displayed results. Because Angular is a Single Page Application (SPA), the URL does not necessarily change when a user interacts within the page such as filtering search results. Therefore, traditional methods of tracking user interaction by URL changes would not capture these events accurately.
To resolve this, you should consider tracking not just URL changes, but also user interactions within the product page itself. This can be done through event tracking, similar to what you’ve implemented for the banner click. The event should fire whenever a user adjusts the search filters. You may need to customize your event tracking to capture the exact filter settings being applied.
Once this is set up, you should be able to track a user through each step in the funnel, from clicking the banner, to adjusting search filters, to selecting a product and finishing the transaction. Remember to test thoroughly to ensure the events are firing as expected and the data is captured accurately.
If implementing this, seek assistance from someone with a good understanding of Angular and web analytics. The adjustment involves both changes to code and the analytics platform you’re using for tracking. They might also provide insight if some other issue is causing your tracking problems.
-
Sure, I’d love to help troubleshoot this issue. It seems you’ve done a lot of the right steps in diagnosing the problem so far.
Numerous factors could lead to a lack of data in your ‘Reporting’ section.
Firstly, ensure that the test is truly live – it should be in the ‘Running’ state and not just ‘Ready to run’. Double check your audience targeting and scheduling settings.
Secondly, make sure that your Optimize and Analytics tags are installed correctly. Even though they seem to be firing in the expected sequence in GTM, there might be other issues preventing data from being sent or received correctly.
Lastly, it can take 12-24 hours for data to start appearing in Optimize reports. Since you’ve surpassed this timeframe, the issue likely lies elsewhere. However, sometimes there might be additional delays in data processing.
If you’ve checked and re-checked all of these potential issues and still encounter the same problem, I suggest reaching out to Google support for further assistance. They have access to more detailed troubleshooting tools and information and might be able to provide more specific guidance based on the particular settings and conditions of your site and test setup.
-
It seems like you may be encountering a couple of potential issues with the Osano Developer Plan. Your first concern is that Google Analytics 4 cookies aren’t being removed even after a user opts out. One reason for this could be due to the settings in your Cookie Consent Manager. The removal of cookies might not be an automated action upon opting out, so you may need to manually configure this or consult with Osano support.
As for your confusion about the “Osano dashboard –> Cookie Management –> Cookies tab”, it’s unusual that GA4 cookies aren’t appearing in the ‘Storage Preference Drawer’ under the ‘Analytics’ section, because they should be displayed after you’ve managed them. This can possibly be due to a misconfiguration or a bug in the platform. I suggest contacting Osano’s direct support line for a more concrete resolution. They can provide clearer instructions and help you troubleshoot the issue more efficiently.
-
Seems like you hit a snag! Your apps should ideally connect with their respective GA4 properties right from the Firebase console. Just make sure you’re choosing the right GA4 property for each app. Sometimes it might take a few hours for the changes to reflect so have a little patience. Also, verify that your Firebase SDKs are properly initialized in your apps. If the problem persists, try reaching out to Firebase support.
-
Sure thing! This sounds like a timing issue since Google Analytics needs around 24-48 hours to process the data fully. So, even though it’s frustrating, you might just need to wait a bit longer for the correct numbers to appear in your audience dashboard. Another possibility is that there’s data discrepancy due to filters or settings – a quick double-check on those won’t hurt!
-
Yes, Google Tag Manager (GTM) can definitely help you track custom events like scrolls on your website. And you don’t need to worry about losing any previous data from your GA3 and GA4 accounts because migrating to GTM doesn’t affect your historical data. The past data will remain in your Google Analytics (GA).
You’re absolutely right about your GA4 property and GTM account having different IDs. That’s normal. GA and GTM are different tools with different purposes. GA is for tracking user interactions (like pageviews, events) while GTM is for managing marketing and analytics tags on your website. When you create these accounts, Google assigns different IDs to them to help you organize and separate your tracking tools.
So, what you need to do now is to configure your existing GA4 tracking within the GTM interface. Then you can start using GTM to deploy Google Analytics tracking on your website. Also, don’t forget to change the GA tracking code on your pages to the GTM code, and then remove the old GA codes.
Just make sure you set it up correctly, including setting up triggers (conditions for when tags should fire) and variables (additional information needed for the tag to work). If it’s done correctly, you can efficiently track custom events without losing past data and improve your future tracking system.
-
Sure, I gotcha! So basically, you used to be able to see the full URL for event tracking super easily with the old Google Analytics, right? But with the new GA4 setup, you weren’t seeing the full story… just a tiny piece of the URL. Major bummer.
But hey, turns out there’s a workaround! Good ol’ Google has another tool in its toolbox – Google “Looker Studio”, also known as Data Studio. By setting up a new report in Data Studio, you were finally able to see the whole URLs. Awesome!
The only downside though, you now have to juggle between three different Google platforms – Google Tag Manager, Google Analytics 4 and Google Data Studio – just for this simple task. Definitely sounds like a bit of a hassle, but hey, at least it gets the job done! Hope that clears things up a bit!
-
It seems like your total revenue is showing up as 0.00€ because the
actionFieldobject isn’t present in your Google Analytics 4 script. The right format should look something like this:`javascript
gtag(“event”, “purchase”, {
transaction_id: “T_12345”,
affiliation: “Google Merchandise Store”,
value: 25.42,
tax: 4.90,
shipping: 5.99,
currency: “USD”,
coupon: “SUMMER_SALE”,
items: [
{
item_id: “SKU_12345”,
item_name: “Stan and Friends Tee”,
affiliation: “Google Merchandise Store”,
coupon: “SUMMER_FUN”,
currency: “USD”,
discount: 2.22,
index: 0,
item_brand: “Google”,
item_category: “Apparel”,
item_category2: “Adult”,
item_category3: “Shirts”,
item_category4: “Crew”,
item_category5: “Short sleeve”,
item_list_id: “related_products”,
item_list_name: “Related Products”,
item_variant: “green”,
location_id: “L_12345”,
price: 9.99,
quantity: 1
},
…
`This is the structure that Google Analytics 4 expects. In this case, make sure to cross-check your purchase code to see if it aligns with this example.
For more detailed information, you may want to check out the ecommerce documentation here: https://developers.google.com/analytics/devguides/collection/ga4/reference/events#purchase.
