• Resolved Martin Sauter

    (@martinsauter)


    Site Kit does not allow me to connect my Google Analytics account but shows the message ?Error: User does not have sufficient permissions for this account.? But this cannot be the case, I am the owner of that account.

    What I tried so far:

    • I tried to connect my Google Search Console account – works.
    • I tried to connect another Google Analytics account which belongs to the same Google account – works.
    • I tried to connect to the same Google Analytics account through another Google account (which has full access to this Google Analytics account as well) – does not work.
    • I tried to reconnect my Google account to my Google Analytics account – does still not work.

    Since I have all rights I can think of, this is either a bug of the Site Kit plug-in, or my Google Account is corrupt. What can I do?

    The page I need help with: [log in to see the link]

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

    (@jamesosborne)

    @martinsauter Thanks for opening a support topic. Can you inform me of the the following and we can hopefully assist:

      1. When signing into Google Analytics are you using the same Google account which you used to setup Site Kit – while logged in as the same WordPress user?
      2. When selecting the different Analytics accounts using the dropdown does the notice appears for just one of the accounts which are available?
      3. Can you please share your Site Health information

      If you have any questions on the above please ask.

    Thread Starter Martin Sauter

    (@martinsauter)

    Thanks @jamesosborne

    1. Yes, I use the same Google account to access Google Analytics and to set up Site Kit. But I don’t fully understand what you mean by ?the same WordPress user?? There is only one WordPress user.

    2. The error message does not disappear when I switch to the other GA account using the dropdown, but I am able to connect to this other GA account anyway.

    3. You will find this information below.

    ### wp-core ###
    
    version: 5.4.1
    site_language: de_DE
    user_language: de_DE
    permalink: /%postname%/
    https_status: true
    user_registration: 0
    default_comment_status: open
    multisite: false
    user_count: 33
    dotorg_communication: true
    
    ### wp-paths-sizes ###
    
    wordpress_path: /home/swisslao/public_html/swisslaos2018
    wordpress_size: 74,93 MB (78574474 bytes)
    uploads_path: /home/swisslao/public_html/swisslaos2018/wp-content/uploads
    uploads_size: 282,66 MB (296388293 bytes)
    themes_path: /home/swisslao/public_html/swisslaos2018/wp-content/themes
    themes_size: 37,01 MB (38810891 bytes)
    plugins_path: /home/swisslao/public_html/swisslaos2018/wp-content/plugins
    plugins_size: 143,04 MB (149983878 bytes)
    database_size: 32,15 MB (33708960 bytes)
    total_size: 569,79 MB (597466496 bytes)
    
    ### wp-dropins (1) ###
    
    advanced-cache.php: true
    
    ### wp-active-theme ###
    
    name: Swiss Laos Hospital Project (Divi Child) (swisslaos2016)
    version: 3.0.17.1478332722
    author: Martin Sauter
    author_website: https://www.martinsauter.ch
    parent_theme: Divi (Divi)
    theme_features: custom-background, automatic-feed-links, post-thumbnails, menus, title-tag, post-formats, woocommerce, wc-product-gallery-zoom, wc-product-gallery-lightbox, wc-product-gallery-slider, customize-selective-refresh-widgets, editor-style, widgets
    theme_path: /home/swisslao/public_html/swisslaos2018/wp-content/themes/swisslaos2016
    
    ### wp-parent-theme ###
    
    name: Divi (Divi)
    version: 4.4.5
    author: Elegant Themes
    author_website: https://www.elegantthemes.com
    theme_path: /home/swisslao/public_html/swisslaos2018/wp-content/themes/Divi
    
    ### wp-themes-inactive (2) ###
    
    Twenty Nineteen: version: 1.5, author: WordPress-Team
    Twenty Twenty: version: 1.2, author: WordPress-Team
    
    ### wp-mu-plugins (3) ###
    
    ET Support Center :: Must-Use Plugins Autoloader: author: Elegant Themes, version: (undefined)
    Health Check Troubleshooting Mode: author: (undefined), version: 1.7.0
    WP Migrate DB Pro Compatibility: version: 1.1, author: Delicious Brains
    
    ### wp-plugins-active (45) ###
    
    Activity Log: version: 2.5.2, author: Activity Log Team
    Admin Menu Tree Page View: version: 2.7.1, author: P?r Thernstr?m
    BackWPup: version: 3.7.1, author: Inpsyde GmbH
    Better Font Awesome: version: 1.7.1, author: Mickey Kay
    BJ Lazy Load: version: 1.0.9, author: Bj?rn Johansen, Aron Tornberg, angrycreative
    Broken Link Checker: version: 1.11.12, author: WPMU DEV
    Change Password Protected Message: version: 1.2.5, author: pipdig
    Child Theme Configurator: version: 2.5.2, author: Lilaea Media
    Classic Editor: version: 1.5, author: WordPress Contributors
    Content Aware Sidebars: version: 3.12, author: Joachim Jensen - DEV Institute
    Featured Image Admin Thumb: version: 1.5.3, author: Sean Hayes
    GDPR Cookie Consent Banner: version: 2.3.15, author: termly
    Header Footer Code Manager: version: 1.1.7, author: 99robots
    Health Check & Troubleshooting: version: 1.4.4, author: The www.ads-software.com community
    Inline Google Spreadsheet Viewer: version: 0.13.2, author: Meitar Moscovitz <[email protected]>
    Language Fallback: version: 1.0.5, author: Bernhard Kau
    Leaflet Maps Marker: version: 3.12.3, author: MapsMarker.com e.U.
    LiteSpeed Cache: version: 3.0.8.6, author: LiteSpeed Technologies
    Loco Translate: version: 2.3.3, author: Tim Whitlock
    MainWP Child: version: 4.0.7.1, author: MainWP
    MC4WP: Mailchimp Activity: version: 1.1.0, author: ibericode
    MC4WP: Mailchimp for WordPress: version: 4.7.7, author: ibericode
    M Chart: version: 1.7.8, author: Jamie Poitra
    M Chart Highcharts Library: version: 1.0.5, author: Jamie Poitra
    Members: version: 3.0.8, author: MemberPress
    Ninja Forms: version: 3.4.24.2, author: Saturday Drive
    PDF Image Generator: version: 1.5.6, author: Mizuho Ogino
    Plugin Notes Plus: version: 1.2.2, author: Jamie Bergen
    Post Duplicator: version: 2.20, author: Metaphor Creations
    Rank Math SEO: version: 1.0.42.3, author: Rank Math
    Redirection: version: 4.7.2, author: John Godley
    Sidebar Login: version: 2.7.3, author: Mike Jolley
    Site Kit by Google: version: 1.8.0, author: Google
    Smash Balloon Custom Facebook Feed: version: 2.14.1, author: Smash Balloon
    Sucuri Security - Auditing, Malware Scanner and Hardening: version: 1.8.24, author: Sucuri Inc.
    WordPress Importer: version: 0.7, author: wordpressdotorg
    WP Cerber Security, Antispam & Malware Scan: version: 8.6.3, author: Cerber Tech Inc.
    WPCore Plugin Manager: version: 1.9.0, author: Stuart Starr
    WP First Letter Avatar: version: 2.2.8, author: Dev49.net
    WP Migrate DB Pro: version: 1.9.10, author: Delicious Brains
    WPML Media: version: 2.5.5, author: OnTheGoSystems
    WPML Multilingual CMS: version: 4.3.12, author: OnTheGoSystems
    WPML String Translation: version: 3.0.9, author: OnTheGoSystems
    WPML Translation Management: version: 2.9.6, author: OnTheGoSystems
    WP Notification Bars: version: 1.0.5, author: MyThemeShop
    
    ### wp-plugins-inactive (2) ###
    
    Enhanced Media Library: version: 2.7.2, author: wpUXsolutions
    Google Analytics Dashboard for WP (GADWP): version: 6.0.2, author: ExactMetrics
    
    ### wp-media ###
    
    image_editor: WP_Image_Editor_Imagick
    imagick_module_version: 1684
    imagemagick_version: ImageMagick 6.9.4-10 Q16 x86_64 2017-05-23 https://www.imagemagick.org
    imagick_limits: 
    	imagick::RESOURCETYPE_AREA: 141 GB
    	imagick::RESOURCETYPE_DISK: 1.844674407371E+19
    	imagick::RESOURCETYPE_FILE: 37500
    	imagick::RESOURCETYPE_MAP: 141 GB
    	imagick::RESOURCETYPE_MEMORY: 71 GB
    	imagick::RESOURCETYPE_THREAD: 1
    gd_version: bundled (2.1.0 compatible)
    ghostscript_version: unknown
    
    ### wp-server ###
    
    server_architecture: Linux 3.10.0-962.3.2.lve1.5.26.9.el7.x86_64 x86_64
    httpd_software: LiteSpeed
    php_version: 7.1.33 64bit
    php_sapi: litespeed
    max_input_variables: 1000
    time_limit: 30
    memory_limit: 256M
    max_input_time: 60
    upload_max_size: 16M
    php_post_max_size: 16M
    curl_version: 7.62.0 OpenSSL/1.0.2k
    suhosin: false
    imagick_availability: true
    server-headers: 
    	set-cookie: Array
    	expires: Wed, 11 Jan 1984 05:00:00 GMT
    	cache-control: no-cache, must-revalidate, max-age=0
    	content-type: text/html; charset=UTF-8
    	link: Array
    	x-litespeed-cache-control: private,max-age=1800
    	x-litespeed-tag: 58a_tag_priv,public:58a_HTTP.200,public:58a_front,public:58a_URL.6666cd76f96956469e7be39d750cc7d9,public:58a_F,public:58a_Po.2,public:58a_PGS,public:58a_
    	etag: "17325-1589219017;gz"
    	x-litespeed-cache: miss
    	content-encoding: gzip
    	vary: Accept-Encoding
    	date: Mon, 11 May 2020 17:43:37 GMT
    	alt-svc: quic=":443"; ma=2592000; v="43,46", h3-Q043=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-Q050=":443"; ma=2592000, h3-25=":443"; ma=2592000, h3-27=":443"; ma=2592000
    htaccess_extra_rules: true
    
    ### wp-database ###
    
    extension: mysqli
    server_version: 5.7.26-log-cll-lve
    client_version: mysqlnd 5.0.12-dev - 20150407 - $Id: 38fea24f2847fa7519001be390c98ae0acafe387 $
    
    ### wp-constants ###
    
    WP_HOME: undefined
    WP_SITEURL: undefined
    WP_CONTENT_DIR: /home/swisslao/public_html/swisslaos2018/wp-content
    WP_PLUGIN_DIR: /home/swisslao/public_html/swisslaos2018/wp-content/plugins
    WP_MAX_MEMORY_LIMIT: 256M
    WP_DEBUG: false
    WP_DEBUG_DISPLAY: true
    WP_DEBUG_LOG: false
    SCRIPT_DEBUG: false
    WP_CACHE: true
    CONCATENATE_SCRIPTS: undefined
    COMPRESS_SCRIPTS: undefined
    COMPRESS_CSS: undefined
    WP_LOCAL_DEV: undefined
    
    ### wp-filesystem ###
    
    wordpress: writable
    wp-content: writable
    uploads: writable
    plugins: writable
    themes: writable
    mu-plugins: writable
    
    ### google-site-kit ###
    
    version: 1.8.0
    php_version: 7.1.33
    wp_version: 5.4.1
    reference_url: https://www.swisslaos.ch
    amp_mode: no
    site_status: connected-site
    user_status: authenticated
    active_modules: site-verification, search-console, analytics
    required_scopes: 
    	openid: ?
    	https://www.googleapis.com/auth/userinfo.profile: ?
    	https://www.googleapis.com/auth/userinfo.email: ?
    	https://www.googleapis.com/auth/siteverification: ?
    	https://www.googleapis.com/auth/webmasters: ?
    	https://www.googleapis.com/auth/analytics: ?
    	https://www.googleapis.com/auth/analytics.readonly: ?
    	https://www.googleapis.com/auth/analytics.manage.users: ?
    	https://www.googleapis.com/auth/analytics.edit: ?
    search_console_property: https://www.swisslaos.ch/
    analytics_account_id: 5981????
    analytics_property_id: UA-5981??????
    analytics_profile_id: 9804????
    analytics_use_snippet: yes

    @martinsauter thanks for the details! Interestingly, your Site Health information is showing that Site Kit has inserted the snippet for your Analytics property staring with: UA-5981??????

    Could you confirm that this property the one experiencing the issue?

    I currently don’t see this snippet on the site, which may correlate with the error you are receiving.

    Could you try the following:

    1) Clear any caching plugins or server-side caching and attempt to connect Analytics in an incognito browser window?

    2) If that does not work, send us a screenshot of any browser console errors you see when the error occurs.

    You can provide a link to screenshots using a service like Imgur or Jumpshare.

    Thread Starter Martin Sauter

    (@martinsauter)

    No, the property that I need to connect and that does not work is UA-4588xxxx-x.

    The property UA-5981xxxx-x is the one that I have successfully connected for testing purposes.

    I did the following:

    • I have reset Site Kit on my WP website.
    • I have revoked any rights for Site Kite from my Google account.
    • I have cleared my server cache.
    • I have re-configured Site Kit from the start.

    The problem remains: I can connect Google Search Console, but not Google Analytics. Here is what I can see in the console: https://imgur.com/a/pkZttq8

    And this is the log: https://www.dropbox.com/s/wi4jjnm37ulmzx4/www.swisslaos.ch-1589271890210.log?dl=0

    By the way: On thing to mention is that with the Google Account in question I do not see all of my views in the dropdown far right.

    • This reply was modified 4 years, 9 months ago by Martin Sauter.
    Plugin Support James Osborne

    (@jamesosborne)

    @martinsauter Many thanks for the update, and very useful additional context. While you may have already performed this check can you visit that the Analytics web interface and confirm full access under both “Account User Management” and “Property User Management”?

    After confirming access please restart the setup process using a browser incognito window, so browser caching or extensions don’t interfere.

    Thread Starter Martin Sauter

    (@martinsauter)

    @jamesosborne My Google account has all rights on all levels in Google Analytics (account, property, view). And the error messages from above were created using an incognito window.

    Plugin Support James Osborne

    (@jamesosborne)

    @martinsauter Thanks for the additional information. I’ve created a GitHub issue so we can investigate further.
    https://github.com/google/site-kit-wp/issues/1548

    I’ll keep you posted here with any updates.

    Plugin Support James Osborne

    (@jamesosborne)

    @martinsauter Thanks for your patience. In order to troubleshoot further can you access the Analytics Query Explorer and fill in the required information based on the same property which you’re unable to access?

    After running the query please inform whether you see any results.

    Thread Starter Martin Sauter

    (@martinsauter)

    This is the result I get: https://imgur.com/a/KNXYmbT

    Plugin Support James Osborne

    (@jamesosborne)

    @martinsauter Thanks for providing that additional information, which I’ll add to the respective GitHub issue.

    We’ll report back to you here with any updates.

    Thread Starter Martin Sauter

    (@martinsauter)

    @jamesosborne I just learned that there is a vulnerability in Site Kit 1.7 which was patched in Site Kit 1.8. Can I update my plug-in in the meantime or would this affect your investigations?

    Plugin Support James Osborne

    (@jamesosborne)

    @martinsauter You can update the plugin no problem, we’re still investigating the issue from our side.

    Plugin Support James Osborne

    (@jamesosborne)

    @martinsauter Many thanks for your patience on this issue. To keep you up to date we we’ve been testing out different scenarios and ran into the same issue thus far only with modifications at Analytics permissions level.

    Could you confirm the levels of user permissions the Google Account in question has at account, property and view level in the admin area of your Analytics account?

    Here’s an example of what the permissions screens will look like when clicking on any of the user management sections and then your email (the same email associated with your Google account).

    I’m having the same issue here with Analytics not verifying my ownership of the site. I even generated a new piece of Analytics code on howtocleanthings.com. Where before it was giving me a permissions error, now it’s giving me this error:

    “Error: We’ve detected there’s already an existing Analytics tag on your site (ID UA-26735861-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.”

    I am the owner. I created that code with the account that it is connected to. I don’t know what else it could want from me.

    Thread Starter Martin Sauter

    (@martinsauter)

    @jamesosborne As I have confirmed already three weeks ago: The Google account in question has all rights in the Google Analytics account (on the account level, the property level, and the view level). Google Analytics has been set up with this very same Google account, and I am the only person with access to all these accounts.

    The only extra information I can provide is that we were using the ExactMetrics plugin before we switched to Site Kit.

Viewing 15 replies - 1 through 15 (of 25 total)
  • The topic ‘Error: User does not have sufficient permissions for this account.’ is closed to new replies.