The consent management platform provides the following categories for both scripts and cookies:
Essential (Strictly Necessary)
These cookies and scripts are essential for enabling a user to move around the website and use its basic features, such as accessing secure areas of the website, opening navigation, displaying content. The easy rule of thumb for whether a cookie or script is strictly necessary is whether the site would not function without that cookie or script or whether your customer would be unable to access the CMP features without it.
- Examples of scripts and/or cookies that are likely considered essential: Query, Bootstrap, React, and of course, Osano.
These cookies and scripts are not essential to the functioning of the website but are used to identify (in aggregate) how visitors use your website, which pages are most popular, where traffic originates from, and how long visitors spend on each page of your website. Alternatively, some analytics providers primarily serve the purpose of tracking system health, identifying technical issues with the website, and reporting errors to the website owners.
- Examples of scripts and/or cookies that are likely considered analytics: Google Analytics, Newrelic, Pingdom, and Matomo.
These cookies and scripts allow for the delivery of advertisements more relevant to your visitors and their interests. They may also be used to limit the number of times you see an advertisement as well as help measure the effectiveness of the advertising campaign. Advertising networks usually place them on the page with the website operator’s permission. An easy rule of thumb for whether a cookie or script is in this category is that your site would function without it, but you might have less information about your visitors or make less money on advertisements.
- Examples of scripts and/or cookies that are likely considered marketing (advertising): Tracking and retargeting pixels such as Adroll, Facebook, and most social network components.
These cookies and scripts allow the website to remember choices you make (such as your user name, language, or the region you are in) and provide enhanced, more personal features.
- Examples of scripts and/or cookies that are likely considered personalization: Cookies used to identify regional locations to deliver localized weather reports or traffic news, Scripts/Cookies used for remembering the shopping cart contents of a visitor between sessions, or displaying a list of favorited items.
These are cookies and scripts that you, the Osano administrator, have decided you do not ever want to be used on your website. When you blocklist a vendor, no code from that vendor and no cookies from that vendor will ever load on your website. Use this category carefully as blocklisting a vendor can have unintended consequences if your site depends on that vendor for functionality.
- Examples of scripts and/or cookies that are likely considered for blocklisting: Scripts/cookies placed by vendors you determine have particularly poor privacy practices, have had security issues, or do not meet your organization's compliance goals.
These are cookies and scripts that Osano has identified as existing on your website pages but are not yet classified/managed (in Strict mode) or that Osano can not automatically categorize for you (via classification rules). When scripts or cookies exist in this category, you will receive email and app alerts asking you to categorize them. As a general rule of thumb, you should never leave items uncategorized. You may like to think of uncategorized items as a "to-do" list of items that require identification and classification.