No trackers or beacons found
How it works
Trackers are loaded together with the webpage you are viewing and as a result send your Ip address and other data point to the 3rd party
Cookies are used together with the beacon in order to record repeat visits or activity across different websites.
The audit record all pages that have trackers and what the actual reference is on the page.
Are these trackers malicious or not?
Many trackers that the Wasp record are not malicious and are intentional, just like Google analytics or other marketing software.
However, when open source libraries are used, it often occurs that your webpages loads unexpected 3rd party libraries.
Many cookie-consent trackers for example, load 3rd party recourse to analyse the country of origin and geolocate the IP address of your users
Whether this is intentional, wanted or a malicious script is difficult to predict. That is way the Wasp records both loaded and referenced libraries in the code.
How to fix?
Define which trackers are required and needed. If any trackers are loaded without the knowledge of the developer or webmaster, locate the pages and the snippet and delete the referenced library.