Detection of MS Clarity is broken again (former issue 265)

[googleanalyticsresoneo]

See for example https://www.cora.fr/

https://www.clarity.ms/tag/uet/19004077 https://n.clarity.ms/s/0.6.34/clarity.js https://n.clarity.ms/collect

Thanks for your attention

[philipp-classen]

Should be detected now:

Thanks for reporting!

[googleanalyticsresoneo]

@philipp-classen

I have been waiting a few days to be sure the update had been pushed live, but I still don't see it as detected

https://www.clarity.ms/tag/uet/19004077 https://www.clarity.ms/eus2-b/s/0.6.35/clarity.js https://e.clarity.ms/collect

What could help understand what is the issue there ??

Regards

[philipp-classen]

From what I see, there are only request to MS Clarity on the page once you granted consent. Depending how Ghostery is configured, the consent dialog might be blocked. One way that works for me, is to temporarily pause Ghostery. Then it will not block but only reports trackers. After a page reload, there should be a consent dialog. Once you allow it, there should be requests coming from MS Clarity, which should then be reported in the Ghostery UI.

To make sure that you got the latest version of the patterns, you can also try it in a fresh browser profile. But that should not be necessary, since your existing one should have been updated already.

[philipp-classen]

We just found a bug with the update mechanism: https://github.com/ghostery/broken-page-reports/issues/117

That is very likely the explanation for the problem. A temporary workaround is to clear browser caches (for details can be found in the issue). We are working on a fix for the next Ghostery release.

[googleanalyticsresoneo]

I was able to force the database update and now it's properly detected indeed

That update issue sounds serious

[philipp-classen]

Indeed, it is a nasty bug. We merged a fix for it, today: https://github.com/ghostery/ghostery-extension/pull/846

I'll close this one for now. Thank you for confirming!