Error: Your Connection Is Not Private
This article will assist with the following error:
"Your connection is not private" pop-up when attempting to connect to a data source.
Cause
Power My Analytics will always make sure our security certificates are current. If you are receiving this error, your terminal may be having difficulty verifying security certificates.
Solution
Your workplace IT department will be able to help you best, but here are some steps you can try on your own:
- Turn off your antivirus software.
- Check that your date and time are accurate.
- Clear your browser's cache and try again.
Still having issues?
Send us a ticket and we will get back to you.
Related Articles
Error Connecting to Instagram Media Insights
You may encounter the error "This Instagram account is not connected to a Facebook page" when attempting to connect your Instagram Insights account to Power My Analytics for data reporting. This guide addresses the common error and provides ...
Error 400: admin_policy_enforced
You may encounter an authorization error when connecting your Google account as a data source. This guide will help you understand the cause of this error and provide step-by-step instructions to resolve it, ensuring you can seamlessly integrate your ...
Error: Missing GA4 Scopes
When creating a report using your Google Analytics 4 (GA4) account in Power My Analytics, you may encounter an error message stating "Missing Google Analytics 4 Scopes." This guide will help you understand the cause of this error and provide ...
Unauthorized Access Error When Connecting to Shopify
This article will assist with the following error: Cause Many Shopify accounts have more than one URL that redirects to the store. Only the "myshopify.com" URL can be used to fetch data. You may have entered the wrong Shopify URL during the ...
Bad Request: Error 400
When adding a new data source to your Power My Analytics hub, you may encounter a "Bad Request: Error 400" message. This guide will help you understand the cause of this error and provide simple steps to resolve it. Error "Bad Request: Error 400" ...