[Grayson]

It seems like you’ve tried several potential solutions already without success. It might be worth checking if there are differences in the configurations between the production and staging websites. Also, confirm if the staging website can send data to other GA4 properties or not. If it can’t, this may imply there’s an issue with the staging website itself. If it can, it would suggest the data is somehow being filtered before it reaches the GA4 property.
Moreover, ensure that there’s no filter set up in your GA4 that could be blocking incoming data from the staging website. If none of these options seem to solve the issue, then it might be a good idea to try sending hits directly to the GA4 Measurement Protocol API from the staging site to bypass GTM and isolate the issue further. It could also help to check if there are any errors shown in the browser console for the staging site, as these might hint at what could be going wrong with the data transfer.

[Grayson]

Yo, sounds like your tag is firing before the dataLayer is ready, kind of like showing up to a party before the host’s even there. Try using a trigger to make sure your tag only fires when the dataLayer is complete and ready to go. Haste makes waste, right? So give that a shot, and see if your undefined values become a thing of the past.

[Grayson]

Hi Greg,

Yes, you’re on the right track. In order to track data on “another.website.com” using Google Analytics 4, you’ll need to implement the Google Tag Manager ID from GA4 into the site. The tool you’ve found, GTM4WP, could indeed be useful for this purpose as it’s designed to facilitate the integration of GTM with WordPress. This should enable GA4 to begin collecting and analyzing data from Server 2.

However, you might need to consider cross-domain tracking if you wish to track a user’s journey across both sites as a single session. Also, do remember to check whether ecommerce tracking (if required) is properly set up, especially since your first site is on Shopify. Additionally, you may also wish to verify that any filters you’ve constructed are appropriately configured in GA4.

So while the initial setup might be relatively straightforward, there may be some additional considerations depending on your specific needs and objectives. Always make sure to thoroughly test your setup to ensure that tracking is working as intended.

[Grayson]

You can use tools like the Facebook Pixel Helper and Google Tag Assistant to validate if the tracking events are firing correctly. These browser extensions display when your tags are firing, helping you troubleshoot any issues. It’s a bit more involved for ensuring a page doesn’t redirect until the event is sent, but one way could be checking the ‘send_to’ configuration in Google Analytics 4.

[Grayson]

In Google Analytics GA4, specific page view tracking over time might involve a different process as compared to Universal Analytics, but it’s still attainable. Firstly, you need to create a new “Event” for that specific page visit. Then you should configure your analytics account to record this event whenever someone visits your page. You can do this by adding the GA4 tracking code into your webpage’s HTML. Once the event is configured correctly, GA4 should start tracking every visit to this page. Over time, GA4 would present a graph displaying the trends for this particular event, effectively showing how many times that page was viewed on a daily basis. Remember, this might seem complicated at first read, but after some practice, it should be more manageable. If trouble persists, using how-to guides or seeking help from a trained professional might be necessary.