-
-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wappalyzer - Cookie Compliance results observations #2292
Comments
@rockeynebhwani Thanks for raising it. Indeed I see the following issues:
Let me know if you need assistance fixing 1 and 2. We will consider these in our analysis in #2149. |
Thanks @max-ostapenko 1 - I agree and I have raised a fix to issue this - https://github.com/AliasIO/wappalyzer/issues/4301 |
When I query for 'HubSpot Analytics', I get 72,813 results -
But querying for 'HubSpot Cookie', I get 15,246 results -
This makes me think that HubSpot by default doesn't include the 'consent' script. I am not familiar with HubSpot but is it a possibility that site owners are leaving some setting in HubSpot ON by mistake which results in inclusion of cookie consent script without site owners realising this? Just a thought.. |
@rockeynebhwani I still see the library is included by default and provides some core consent management API. For the needs of the privacy chapter, I would be interested in what consent management is actually used on the website, not what functionality is loaded and the JS performance insights. I also see that even when the policy banner is shown to visitors it's not identified correctly: Please comment on the adjustments proposed: https://github.com/AliasIO/wappalyzer/pull/4335 |
@max-ostapenko - I am seeing 'HubSpot Cookie banner' being identified by Wappalyzer for following sites - https://blog.ardesia.it/ Sometimes it just take time for chrome extension to pick this up depending upon how script is loaded. I typically wait for some time before clicking on chrome extension. |
I didn't know there is a Wappalyzer extension, thanks. So hopefully the state of technology just was changed on all those websites since July, which is the cause of the difference between extension and dataset. P.S. Did you saw the case when the Wappalyzer extension shows the Hubspot Analytics but doesn't show Hubspot Cookie? |
Thanks for raising this issue @rockeynebhwani. Is there any remaining work on our end or is it ok to close it? |
@rviscomi - I think @max-ostapenko should query the Sep-21 tables and check if he is still seeing anything odd. If not, we can close this. |
@max-ostapenko - I ran my original query against Sep-21 tables and now I see 5,374 origins with more than one cookie compliance solution compared to 15,109 origins against Jul-21 tables |
@rockeynebhwani I've checked the apps in the Cookie Compliance category: Most of apps have expected statistic:
The only issue:
@rviscomi may it be the issue on parsing or BigQuery side? |
Doesn't seem like a BigQuery issue. For example Seems like an upstream detection bug with WebPageTest. In this test of the page I'm seeing similar results as the September data, with Borlabs Cookie omitted. @pmeenan could you investigate if anything has changed between Wappalyzer and WPT detections? |
Borlabs Cookie information data is available starting Nov 2022. Other issues discussed above also seem fine throughout past months. |
While browsing some sites using Wappalzyer chrome extension, I was seeing multiple Cookie Consent Solutions being reported for a site. So, I ran this query on July 2021 mobile table
15,109 sites found where more than one Cookie consent solutions are being reported. Maximum being 4 such solutions on a single site. Output of the query is attached below -
More than 1 Cookie consent solutions.xlsx
Now, this will be unusual for a site to have more than one cookie consent management solutions. This indicates two possibilities -
OR
At this stage, I don't know the exact reason behind this and need more time to look into this... but this is what I found so far.
Let's take an example of a site which is reporting 4 CMPs - http://www.formadoresit.es/
Looking at this, I think detection for 'QuanCast Choice' may be incorrect - https://github.com/AliasIO/wappalyzer/pull/4115/commits/0c761309c1b0ae8f124b8c5fc9973a98523bb6e4 as it's just looking for __tcfapi. I had reported the original issue against which this commit was done but I didn't realise that presence of '__tcfapi' was added in detection.
I am raising this issue if others have any observations and knowledge of these CMPs. If I notice, anything I will comment.
Tagging @max-ostapenko and @ydimova as they have plan to cover CMPs in Privacy chapter
The text was updated successfully, but these errors were encountered: