[Jaspreet]

Sure, it could be a bit tricky, but nothing you can’t handle! You might be able to override some default dimensions. You can take a gander at it here. Similar steps might work for other dimensions as well.

You could also peek at the network request and see if deviceCategory can be given a new look by setting it as an event property.

And remember, there’s always the option to lean on GTM for overriding any field. But, that might be using a sledgehammer to crack a nut, you know? It’s not really worth bringing it in just to minutely tweak the field value.

So, maybe just let it be? Unless, of course, it’s for data points, in which case a custom dimension/event property to track it should serve you well. Give it a shot!

[Jaspreet]

Absolutely, you can leverage Google Analytics or similar tools for this. These tools categorize users based on their device. So, you can directly find the number and percentage of users visiting your site via mobile or desktop. You just set the dimension to “Device Category” and this reveals the necessary statistics. Creating or calculating a ratio might require a bit more manipulation of the data.

[Jaspreet]

Hey, no worries, we’ve all been there! You’re right, the numbers seem to be dancing on different beats in GA4 and BigQuery. But hey, let’s see if we can get them to tango together.

One area to peek into might be your source table. If your website is rolling with a consent mode, you might find some ‘user_pseudo_id’s that have turned out to be shy and ended up blank. These elusive ones might count their dance steps in GA4, but give BigQuery the cold shoulder. Hence, the awkward difference.

Another possibility that might throw your dance off rhythm could be that BigQuery and GA4 are swinging to different time zone tunes. BigQuery has a thing for UTC, but your GA4, well, it might have its own preferences.

So, shine your spotlight on these possibilities and see if they transform this awkward dance-off into a graceful ballet. Cheers mate!

[Jaspreet]

Based on what’s included here, it’s possible that the issue might be occurring due to the regular expression not being correctly configured. It seems from your screenshot that you are using the regex validator in the text field of your variable configuration. This may only validate if the input matches the regular expression, rather than extracting the matches from the string. Ensure the configuration is correctly set to extract matches from your Form Element string. Furthermore, check how you are recalling your variable in your code, as this could also be a potential source of the issue. If possible, try to provide a little more context or code snippets for further clarification of the problem.