[Olivia]

In Google Analytics 4 (GA4), events and parameters have replaced the previous scope of dimensions and metrics in Universal Analytics. So, you will be working with the concept of events (like “phone_capture”) and their parameters. For event_category and event_label, these are more specific parameters that can be linked with an event.

To see the “phone_capture” event in GA4, you would need to create a custom event for it in your GA4 settings. Once it’s been set up, you should be able to see it in your real-time report or in your “Events” report.

In a similar vein, if you want to see the event_category and event_label, in GA4 it’s recommended to replace these with custom parameters for your events. But please note that GA4 only records the parameters that you specifically register, you can do this in the events settings within GA4.

Remember to verify the data in the DebugView in GA4 to ensure the custom events and parameters are appearing correctly. If you’re still unable to find the respective events and parameters, it may be worth checking the setup on your website to verify that the correct code is firing for these events.

[Olivia]

Absolutely, I’d be happy to clarify it for you. The thing is, it’s really a matter of how the code is formatted. Your current code might not be doing what you want it to because it’s in the incorrect format.

Instead of the code gtag('set', 'dimension2', 'test'), it should actually be written as gtag('set', {'dimension2', 'test'}). That just means we’re incorporating the dimension and its value together between curly braces.

Once you tweak that, everything should work as you expect. It’s a straightforward change that should have you seeing those custom dimensions in no time. So just make the switch and you’re good to go!

[Olivia]

The error might be due to the unavailability of the function google_analytics_4_properties() as part of the googleAnalyticsR package which you’re likely using. This package supports Universal Analytics. For GA4, you may need to access the Google API directly with the googleAuthR or another package. It’s also possible that you have to set up a new project in the Google Cloud Console, enable the Google Analytics Data API and make sure the ID you’re using has proper access to the GA4 property. It would also help to check the exact error message you’re receiving for more information about the issue. A more specific error message might enable you to troubleshoot the issue accurately.

[Olivia]

Yes, it’s possible to avoid creating a large number of dataLayer variables with different index values in Google Tag Manager (GTM). An alternative approach is to use JavaScript within GTM to iterate over the form elements and push the values to the dataLayer in a more structured and understandable way. You can create custom JavaScript variables that can access form values dynamically based on their context of use. This way, there’s no need to create a new variable for each form element — you can simply reuse the same variables as needed. Remember: JavaScript can get quite complex, so you might want to consider seeking help from someone with JavaScript and GTM experience if needed.

[Olivia]

Of course, Tom! Sounds like you’re doing everything right, but sometimes with Google’s GA4 platform, it can take a tad longer for data to appear in reports. Contrary to Universal Analytics, in GA4, stable data may show up after about 48 to 72 hours. So, a bit of patience might be needed here. However, if after that window you’re still not seeing your data, then we might need to dig a bit deeper.

[Olivia]

It can be trickier to solve issues when you can’t reproduce them locally. However, you should consider a few points. Firstly, ensure that the ‘login’ event is being fired in all scenarios, as unexpected user behavior or application states could prevent this. Moreover, check if there might be a timing issue, with the configuration tag firing before the dataLayer is fully loaded with user_id. From your description, the issue seems to be irregular, so it’s possible that these tags are racing, with one establishing the client_id first. Alternatively, you might be facing an issue with how the user_id is stored, you could look at using local storage or cookies if it is appropriate and secure for your application. It’s tough to ensure that the user_id is being set correctly across different browsers, devices, and over time. Lastly, it’s advisable to try with hardcoded values but you should also consider coding for unexpected scenarios to ensure resilient tagging. If the condition is tricky to test, consider using a mock ‘login’ event.