[Lincoln]

Sure, I can certainly explain it in a more casual way!

It sounds like the issue might be related to permissions. When you’re given access to view the data, there are a whole bunch of different settings that can be adjusted to control what you can see. One of these settings lets you hide the revenue information. So it might be a good idea to double check that the settings allowing you to view the revenue haven’t been hidden. Just think of it like being given a VIP pass to a concert – but the pass might not give you access to all the backstage areas!
Is there a picture with a ‘hide revenue’ option on it? If yes, just find it and see if it’s turned on. If not, then maybe ask the person who gave you access for some help.

[Lincoln]

Yes, that is correct. GA4 displays tax and shipping details as numerical values rather than the traditional $ format. This is because GA4 treats these as numerical metrics which can be calculated and analyzed, rather than as monetary values. If you want to see them in a $ format, it might be best to calculate these on your own or within your e-commerce platform.

[Lincoln]

When you’re using the Measurement Protocol to send data, the geographical information like “City” and “Country” are automatically determined by Google Analytics through the IP address from where the hit originated. If you are seeing “(not set)” for “City” and “Country”, it could be because the IP address from the hit can’t be geo-located. Google Analytics won’t be able to determine the geographical information for IP addresses that belong to a private network or a local network. Therefore, ensure that the hits you’re sending are coming from a location that can be geo-located.

[Lincoln]

Google Analytics Data API should be capable of handling multibyte characters like Japanese in event names. However, the “Bad Request” error you’re encountering may be related to incorrect encoding, misconfiguration, or the API doesn’t understand the request due to incorrect syntax. Please double-check the request you’re sending to ensure it is properly formatted and encoded. If you’re using a library or module to interact with the API, ensure it supports multibyte characters. Alternatively, there could be a bug or limitation in the API itself. In this case, you might want to contact Google support or look for documentation about handling multibyte characters.

[Lincoln]

Looks like you’ve bumped into GA4’s character limit for regular expressions, which tops off at 256 characters. If your expression runs over this, it’s likely the culprit behind why you’re seeing less events come through than expected.

But don’t worry, there’re a few workarounds to this. One method is to use Looker Studio where you can handle your data filtering. If Looker isn’t an option, you could also consider importing the data to a spreadsheet tool like Excel or Google Sheets. From there, you can manage your computations in a more unrestricted environment.

Hope this helps and best of luck with your custom reporting!