• Resolved dgaudaen

    (@dgaudaen)


    Hi,
    I switched from Monsterinsights to Google Site Kit. I deactivated and deleted Monsterinsights.
    Installation of Site Kit was ok; search console is working.
    When activating Analytics, I get following error:

    We’ve detected there’s already an existing Analytics tag on your site (ID UA-xxxx), but your account doesn’t seem to have access to this Analytics property. You can either remove the existing tag and connect to a different account, or request access to this property from your team.

    I try to reuse the existing tag that was previously used by Monsterinsigts.
    The Google account used has admin rights.

    Any idea what might be wrong?

    Thanks
    Dirk

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Support James Osborne

    (@jamesosborne)

    Hi Dirk. Can you attempt the Analytics module setup from a browser incognito window. When asked you can then login to the same Google account which has access to that property from within your Google Analytics, which should be the same Google account with which you’ve setup Site Kit.

    Alternatively if you are able to locate the source of the Analytics integration on your site you can remove it. It may be added via a theme setting, another plugin, manual insertion or even from a website backup. I’m happy to assist if you want to share your domain.

    Thread Starter dgaudaen

    (@dgaudaen)

    Hi James,
    Thanks for your reply.
    I tried to activate analytics using an incognito window, but the result was the same. I also tried a complete reinstall/reset of the plugin with same negative result.
    Google Analytics was working correctly with the Monsterinsights plugin before so I guess there is nothing wrong at the Google side.

    I copied the site to my pc by unarchiving a Duplicator-backup. I searched all files for the UA- code and found it multiple times in the dup-database…sql file which is apparently a dump from the database created by Duplicator. But the code was not present in any other (readable) file…

    The url of the site is https://tolerant-vzw.be

    Best regards
    Dirk

    Plugin Support James Osborne

    (@jamesosborne)

    @dgaudaen Thanks for the update. Can you check the source code of your site and note the Analytics property ID. You can then log into your Google Analytics account and confirm the same Google Account which was used for Site Kit setup has access?

    If you have already confirmed from within you Google Analytics account then for testing purposes can you remove that Analytics code at present on your site (which looks like a manual code insertion) and attempt setup using an alternate property? If you are unable to locate the source of the tracking code then you can temporarily switch WordPress themes, the code may have been manually inserted into the theme.

    Thread Starter dgaudaen

    (@dgaudaen)

    Hi James,
    After a long search, I found the wrong tracking code.
    While inspecting the page sources of several pages, I noticed that the wrong tracking code only appeared on the home page. That explains why I did not find it in the header script. Apparently, somebody before my time added a script to the home page by using some kind of tag. I just noticed a small symbol that shouldn’t be there… I could not edit it either. I guess it was something from an earlier version of WP. Anyhow, I could delete it and the problem was fixed!
    Thanks for pointing me in the right direction!

    Dirk

    Plugin Support James Osborne

    (@jamesosborne)

    @dgaudaen Nice digging, glad you were able to locate it. Be sure to leave the plugin a review.

    Hi I am pankaj a have same problem
    Error: We’ve detected there’s already an existing Analytics tag on your site (ID UA-162016XXX-1), but your account doesn’t seem to have access to this Analytics property. You can either remove the existing tag and connect to a different account, or request access to this property from your team.
    this error seeing on screen.
    We’ve detected there’s already an existing Analytics tag
    can you please help me?

    Plugin Support James Osborne

    (@jamesosborne)

    @pankajsinghbisht I see you’ve created a new support topic, we can work with you from there. Thanks

    I need help with my site.Recently new to site building and just confused at the moment .Keep getting “Error: We’ve detected there’s already an existing Analytics tag on your site (ID UA-167415274-1), but your account doesn’t seem to have access to this Analytics property. You can either remove the existing tag and connect to a different account, or request access to this property from your team.”

    Tried to resolve it but getting more confused.

    Plugin Support James Osborne

    (@jamesosborne)

    @beejays53 Can you please open a new support topic as per forum guidelines and we would be happy to assist from there.

    Please include all relevant information to your support topic, including your Site Health Information, which can help us troubleshoot your specific case.

    Hi,

    I’m Edward and I have the same problem when I tried to install Site Kit by google yesterday. – 20th Sept 2020.

    Error: We’ve detected there’s already an existing Analytics tag on your site (ID UA-178503533-1), but your account doesn’t seem to have access to this Analytics property. You can either remove the existing tag and connect to a different account, or request access to this property from your team.

    Could you please help. Thank you.
    Regards, Edward.

    I have the same issue.
    A function on the plugin to be able to choose which one we want to use would be a time saver for everyone.

    Plugin Support James Osborne

    (@jamesosborne)

    @aptiv8 I see you’ve opened a new support topic, I’ve just responded to you there.

    @casteleiro Can you also please open a support topic as per WordPress guidelines and we’d be happy to assist you to ensure you get connected.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘We’ve detected there’s already an existing Analytics tag’ is closed to new replies.