@martinsauter Thanks for the additional confirmation. I’ll relay that back to the team and follow up with you here with any updates.
@samoya22 If you’d like to create a new post as per WordPress guidelines we’d be happy to assist. Alternatively you can add your details to the related GitHub issue.
I now seem to be running into this issue as well. I thought rolling back to version 1.8.1 might resolve the issue but no it didn’t. I’m not sure if something with the GA platform or the recent changes sine 1.8.0 are causing a problem.
Here is a screenshot of my output with the Query Explorer.
View post on imgur.com
I have had this exact same issue for hours tonight. It could pick up and find my primary Analytics account for my primary site. But I was trying to link a second account through a second website and getting the same result. “Error: User does not have sufficient permissions for this account.”
I JUST GOT IT TO WORK! Try this. Complete the setup allowing the plugin to use the default analytics account that it picks up. THEN – under site kit click on SETTINGS, select the drop down by analytics (far right). Then on the far left click EDIT. It will show the defaulted property that is already connected, but should not allow you to select a different property and view. Select the property and view that you want and click CONFIRM CHANGES.
This finally worked for me and I correctly have my two websites, connected to the two different and proper analytics accounts. (Seems to be a programming bug).
Good luck, hope it works out for you.
@leadtheteam nice troubleshooting and thanks for sharing! We believe the fix planned in this Github issue will address that bug. We’ll keep this thread updated when it is out.
@martinsauter Hello! We released a fix for this issue in the most recent version 1.12.0. Can you please update to the new version and inform us if the issue persists? Thank you.
@jamesosborne @reneesoffice @luckynasan Thank you for taking care of this issue. Unfortunately, my client refused to be without analytics data for more than two months, so I had to implement an alternative solution without the Site Kit plug-in in the meantime. And now that everything finally works I obviously won’t touch it. But hopefully other users can benefit from the fix.
@luckynasan tried v1.12.0 this morning and can confirm I still get the same error, so not fixed for me.
It’s a site where analytics property was moved from one account to other, which is the same criteria for the fix released today but still couldn’t get it to work.
Please let me know if I can help diagnose it with any information you may need.
Thanks a lot!
Cheers.
@akinomotto ugh, I hope that your setup is somehow more unique. The problem property I have also had moved accounts. I was very hopeful this would finally be fixed so that I could close my standing ticket with a client. 😕
-
This reply was modified 3 years, 9 months ago by
Tim Nolte.
@martinsauter thanks for the update and we understand. Hopefully future sites will not experience this issue.
@akinomotto @tnolte thanks also for following up and sorry the hear that the issue still persists. We’ve gotten report that it has been resolved for another user with this fix.
Could you attempt to reset Site Kit anew and reconnect Analytics?
If the issue still persists, it would be great if you could open a new topic so we can continue to investigate your cases specifically.
We sincerely appreciate everyone’s patience and feedback as we work to resolve this.
