GA4 Timezone Issue
CompletedHi!
When connecting my GA4 to Journey, I am getting the “to-do” “Fix the GA4 Property Timezone”. What do I have to change here?
Thank you! All the best,
Nora
-
Nora Breyer You'll want to change to the New York time zone or make a new GA4 account in this time zone and connect it to your site to get the most accurate reporting data since Journey's ad server reporting is in the New York time zone. You can read more about that here.
Thanks!
0 -
Hi!
Just to confirm…. I just changed the time zone in my GA4 and this should fix the issue? I hadn't been having an issue then got the notice to fix it. Then I looked and yesterday my analytics were off my about 200 sessions.
I didn't want to creat a second property. I'm just making sure changing the time zone in my current property is enough.
Thanks!0 -
Hey Kimberly Grimmett - if you're seeing this notice in your Journey dashboard, adjusting the timezone on your Google Analytics property will take care of this. Setting your Google Analytics property's timezone to the East Coast allows Journey to more accurately provide RPM data to your dashboard.
0 -
Thanks for the quick reply! I just wanted to make sure adding a second property wasn't mandatory. So sounds like I'm good! I changed the time zone. Perfect.
0 -
My time zone is set to this, and always has been, but I'm still getting the error.
0 -
I had the time zone set to New York from the start. Apparently, connecting GA4 with Journey only took a little time. The next day, everything was fine again. Thanks! :)
0 -
Support According to what you mentioned, can you please update the article, considering that we don't necessarily have to create a new property, as this is confusing?
"If this is set to an EST timezone, then you are all set.
If it is set to anything other than New York time, please proceed with the steps below.How to setup a secondary GA4 property in the New York time zone"
0 -
Hi Helene M. ! We recommend creating a new property so that you still have your historical data from your view in your own timezone, but this is just a recommendation and it's ultimately up to your discretion. Here's the relevant snippet from the article:
Instead of changing your timezone on your existing view, we recommend setting up a secondary property in your Google analytics. That gives the Journey Dashboard the data it needs to work correctly, and also allows you to maintain the historical data and the view that you are used to, in your home timezone.
Thank you!
0 -
Hi - I also had this issue and set up a new property and linked it.
Now I am getting an error to say my ad script is out of date. I had to add the txt manually as for some reason the grow plugin has stopped working and wont stay connected.
I checked and the url for the ad script works and I can see the code in the header code plugin I used. I'm assuming it's something to do with the GA4 change?
thanks
0 -
Hey paula hall - checking on your site's ads.txt file this afternoon, I am seeing an out of date file. This behavior isn't tied to the recent GA4 change, instead, Journey routinely has updates to this file, and it just hasn't been updated since the most recent update. To update, we have more information on this help article.
Thank you!
0 -
Hello, I've gone ahead and added a second property in NY time zone as suggested in Google Analytics. Also tested it as suggested but I am still getting the “GA4 Property timezone must be US Eastern Time for accurate analytics” message. I signed out and in again but still there. Any suggestions?
0 -
Hey Maria Paravantes - if you've created that second property, you'll want to be sure you also switch over to this property on your Grow Dashboard. Currently, I still see the property connected to your dashboard has a ‘Athens’ timzone.
To switch, select ‘Switch Account’ under Site Settings > Integrations, followed by signing into the Google Account associated with the new property you've created.0 -
Hi, Ryan. Just did that. Thank you very much for your help.
Maria
0
Journey is Self Supported
Please sign in to leave a comment.
Comments
13 comments