Site Kit – Google Analytics not connecting

Thanks for reaching out @iskconwhitefielddigital. It’s not uncommon for users to encounter a “User Rate Limited exceeded” if various changes were made in a short space of time. This usually resets after one hour, and these limits are set by the Analytics API.

In relation to the Internal error you referenced, I’d be happy to check this further with you should the error remain after a short wait to account for any API limits. Please attempt to connect Analytics within Site Kit after one hour, and should the same “Internal error” message appear, please share the following:

1. Your Site Health information. You can use this form to share privately if preferred.??
2. When checking the Site Kit dashboard from a Chrome browser incognito window does the same occur? If so, please share any browser console errors that appear.?
3. Do you see any warnings or errors when checking your Site Health status? (Tools > Site Health > Status), which differs from your Site Health information requested above? Such errors may include REST endpoint references.

Let me know if you have any questions with the above.

Thank you @jamesosborne I have shared details in the form. I have uploaded console errors here – https://pasteboard.co/OHkKoQtl6Kvd.jpg

There is one critical issue when lookign at Site Health status – “Page cache is not detected and the server response time is slow”

Thanks for sharing this additional information @iskconwhitefielddigital. From reviewing your Site Health information and inspecting your site, I don’t see anything out of the ordinary that may be resulting in issues when connecting Analytics.

As it’s been a while since you reported this, with user API quota limits typically refreshed after some time, can you share whether you’re encounter the same when trying to connect Analytics now?

There is one critical issue when lookign at Site Health status – “Page cache is not detected and the server response time is slow”

Appreciate you sharing this. I don’t suspect this was contributing to the issue you encountered, but we can certainly review this further should the same occur. Thank you.

Thank you @jamesosborne I tried again and ran into same issue again – internal error. Any thoughts on what can be done?

Appreciate the update @iskconwhitefielddigital, and sorry to hear that the issue remains. Regarding what we can check next, we can check for any conflicts with your installed plugins by following the steps below:

1. Login to your live site from a Chrome browser incognito window.
2. Navigate to “Plugins > Health Check & Troubleshooting > Troubleshoot” (I can see, based on your Site Health info, that you already have this plugin activated)
3. From the same screen click on the “Available Plugins” tab at the top right and then click on the “Enable” option next to “Site Kit by Google“.
4. Check for the same error when visiting the Site Kit dashboard.

If the same error remains, please share whether you encounter the same when attempting Site Kit setup from this disposable WordPress site? This will help indicate a possible host related issue if you are able to compete set up from this site. 

Thank you @jamesosborne Yes, I was able to setup Site Kit on the disposable WordPress Site. And with troubleshooting mode turned on, I still had the same error with Analytics setup in Site Kit.

Any thoughts on what server restrictions could be responsible for this issue? Also, would you recommend setting up Google Analytics via Google Tag Manager as a backup option?

Guess what! After setting up Site Kit for the disposable WordPress site in incognito mode, when I tried connecting our site with GA – it worked! Thank you so much for all your help and assistance.

Excellent, thanks for the update @iskconwhitefielddigital. Given your experience, it’s possible that there may have been a temporarily issue at host level impacting setup.

If you have a moment free please also consider leaving a review. We’d love to hear you’re feedback as it sounds like you’ve been a Site Kit user for some time before reporting this, if this occurred only after resetting.

Best of luck.