Hi @awjensen,

Thanks for reaching out. So we can determine more on this, and ensure you can select an existing Analytics account or create a new one during Analytics set up within Site Kit, please share the following:

1. 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. 
2. A screen recording of your experience. You can use a service such as Loom or RecordIt to share a screen recording, while using the this form to share this privately. 

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

Many thanks for sharing the recording, and your Site Health information. Very useful to see what’s occurring. As we don’t have any recent reports of this, let’s perform another couple of checks. Firstly, as you have some plugins which could, with particular configuration impact Site Kit set up, please follow the steps below:

1. Login to your live site from a Chrome browser incognito window once more.
2. Install and activate the Health Check & Troubleshooting plugin.
3. Navigate to “Plugins > Health Check & Troubleshooting > Troubleshoot”.
4. 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“.
5. Attempt to connect the Analytics module once more.

Note that one possible workaround, is to create a new Analytics account and property over on the Analytics platform. When doing so, submit your own site address where requested. This may result in Site Kit pre selecting this account and property. Of course, this isn’t ideal if you already have a property with data. If so you may wish to check the default URL for the property you wish to connect.

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

Glad to hear it @awjensen, many thanks for the update. I can’t be sure what happened in this case also, as there were no changed on the plugin or service side. It may have been a temporary host related issue. Otherwise, if you followed the steps above in order to connect, this would indicated a third party plugin or browser related conflict.

If you run into any further issues, be sure to reach out. Best of luck!