Alin Marcu

Hi,

The default report for each site is set using a cookie.

I’ve tested on our multisite test environment and a production network setup and was unable to reproduce the issue. The only difference is that the networks on which I tested are subfolder based rather than subdomains.

Since the entire functionality of the feature is based on cookies, please try using a different browser and see if you can replicate the issue.

Fixed on 6.3.9. Only SameSite attribute was added, because beside None, the other two settings don’t require isSecure.

If there are further questions let me know.

Thanks again for your detailed feedback on the issue.

• This reply was modified 3 months, 2 weeks ago by Alin Marcu.

Thank you for the detailed report.

It will be implemented on next release.

Thanks again!

Under OAuth consent screen, if you don’t have a Workspace account, you need to set/have:

• User type set to External
• Publishing Status set to In Production
• Verification Status set to Needs verification (by clicking on the PUBLISH APP button)

Afterwards, reauthorize the plugin and you’ll get rid of the 7 days refresh token expiration.

Hi,

Are you using your own Google Cloud Console project?

If you do, while the app is set to Testing, refresh token will expire every week. Publish the app without necessarily verifying it and reauthorize the plugin to avoid 7 days timeout.

Hi,

Please contact your CDN provider about the issue and let me know if there’s something to update on the plugin’s code, which I doubt.

You could also point us to the website you’re having issues with to see if we can identify potential issues.

It looks like a CDN issue rather than a plugin issue.

Hi, please update to 6.3.8 which was just released.

Thanks for reporting!

Hi and thanks for the feedback.

At the moment excluding logged in users feature isn’t available. I added it to our to-do list. I will let you know when it gets implemented.

As for the last question regarding UIDs the best place to ask would be on clicky.com.

Thanks again for the feedback!

Hi,

On your website the tracking seems to work properly, if you’re referring to that small widget on the bottom-right of the page, your client just needs to login and select the option to keep it logged in. That small, black widget is available while you’re logged in.

No, but you can use instead our plugin for Clicky Analyitics. This service will display the visitor’s IP.

• This reply was modified 8 months, 3 weeks ago by Alin Marcu.

Thanks for the feedback!

Hi,

Please check if you can replicate the issue with v6.3.6. While I wasn’t able to replicate it, I found a few issues based on the above details which could have caused problems.

After all everything adds up without necessary new limitations. If we’re considering that lately the latency on API requests is high (reason for the PHP cURL timeouts) multiple concomitent requests are very possible on repeated refreshes.

Hi,

IMHO considering the behavior described above you may be hitting the Realtime Concurrent Requests Per Property, which is 10.

Please note that a token doesn’t equal a request. Depending on request complexity it can consume more than a token. So if the plugin is trying to make a request for real-time reports and at the same time you force the retrieval by doing consecutive requests it can hit that limit.

Please try not to force refreshes and see how it goes. Also considering the issue you had with Safari, clearing the cache for the domain and disabling browser extensions would be helpful.

This issue was fixed on latest version. Please update and use the Reset Errors button from General Settings screen. If the issue reappears let us know by posting back here.