Wrong Property ID

@caldiatech thanks for opening a topic and I’m sorry to hear about the issue you encountered.

1) Were you using version 1.1.4 before the update to 1.2.0?

2) Were you using Site Kit to insert the code snippet alone or another method to integrate the Analytics code before (theme, plugin, etc.)?

We were just using the Site Kit and yes, I think we did have the older version installed. It looks to me like around December 17th/18th 2019 is when it dropped the correct ID.

The ID that is currently showing is not one that I even know the property. I have no idea what it is.

Again, right now I have the correct ID hard-coded into the WordPress theme.

@caldiatech thanks so much for this information. 1.1.4 was released around that time and there were a couple modifications to the Analytics feature. While we haven’t had other reports of this occurring, I’m curious if this was a factor.

It is odd that a wrong property you weren’t aware of was chosen. Are there other administrators for the website who have access to Site Kit and its settings with their respective Google Accounts?

Additionally, if you reset the Analytics connection (Site Kit > Settings > Analytics > Edit > Disconnect Analytics from Site Kit then connect again under Connect More Services), does it still pull up the wrong property?

(if you could attempt it with and without your current snippet that would be most helpful to know the outcome).

I am the only one with access to the backend. I did decouple the GA portion and then recouple it and it still pulls up an ID that I have never seen….I have no idea what property UA-130569087-3 belongs to. I did login to GA with a master login where we have access to some 75-100 different properties…but I selected the correct property from the corresponding account.

Again, for now, I have manually coded the correct ID directly into the site theme for now so we don’t lose anymore data.

@caldiatech thanks so much for your feedback. We’ll do some further investigation and follow up as soon we have more information.

@caldiatech are you able to provide your Site Health information? Currently, we’re not able to replicate the issue, but perhaps that will help provide some insights on what is occurring.

@caldiatech just a follow up that we’re still tracking your topic. We’ve release version 1.3.0. If the issue still persists after the update, could you provide the information requested above? We’ll continue to look into this further.

We also get UA-130569087-3 on the site when we enable Site Kit. It’s not ours.

@accesshire thanks for the report! Please open a new support topic with any details so we can investigate this further.

Done.

@caldiatech just circling back that the tracking code referenced UA-130569087-3 is for Site Kit’s anonymous tracking that can be opted into or out anytime from the plugin’s settings. It does not impact the Analytics service connection that you configure and is only visible while you’re logged into your website. We’ll resolve your topic, but feel free to open a new topic with any further questions.

My site has the exact same GA code on it from this plugin – UA-130569087-3. Seems like a larger issue needs to be resolved vs these site-by-site fix tickets. What is causing this on so many sites?

Ok, saw the last message – all set. This is a strange way for Google to track things. You’ll get a lot of webmasters wondering why some random GA code is on their website

I’m having the same issue. I will be forced to connect my Google Analytics account outside of Site Kit (Currently on 1.6.0) because the plugin is pulling the wrong profile and not allowing me to choose the correct one. It’s disappointing that there’s no resolution even after so many people are having the same problem.

@dmutty and @ygruszynski Sorry for the delayed response.

@dmutty thanks for your feedback. I’ll share this with the team.

@ygruszynski you may be experiencing something different. Please open a new support topic so that we can assist.

A new support topic ensures we see your inquiries sooner especially since this topic has been resolved. It is also in accordance with forum guidelines.