Implement in Webflow Applying attributes to elements on the page
Below is a list of elements and options that are used to create this Attributes functionality. Click any of them to see more details.
Setup option 1 — Informational cookie message
'Informational message', or 'implied disclosure', is a type of cookie compliance that informs users that cookies will be used on the site.
The user does not have the option to accept or deny the cookies. The user only has the option to close the cookie banner. The banner is simply informing the user of the use of cookies on the website.
This is the most simple option to implement. It requires the least amount of steps when building a cookie bar. Understand that the user does not have access to turn on and off cookies using the 'informational message' option.
Recommended for companies that require basic compliance. This option is not fully compliant with GDPR regulations.
Important: The preference manager does not work with this option, as there are no cookie options or preferences to manage.
Required for minimum setup
Below is a list of the Attributes that are required for this option.
![how to add cms filter list attribute](https://cdn.prod.website-files.com/6132770a5e2efb2a37b68270/618815cf2b77c77fc751e616_cms-filter-list-min-min.webp)
Setup option 2 — Opt-out of cookies
'Opt-out of cookies' is a type of cookie compliance that loads cookies by default on the user's first visit to the site. The user then has the option to continue browsing the site with the cookies or deny cookies.
If the user chooses the option to continue browsing with cookies, nothing happens. The user continues to use cookies.
If the user chooses to deny cookies, we remove the cookies from their browser. We allow them to continue browsing the site and disable all use of scripts that issue non-essential cookies.
This option is not GDPR compliant. For full GDPR compliance, use Option 3.
Recommended for companies concerned about EU Cookie Law, CCPA, GDPR, and other privacy laws but do not need full compliance. Option 2 gives an additional layer of protection to privacy laws by allowing the user to opt-out of cookie use as well as update their preferences.
Option 2 has the same implementation steps as Option 3. The key difference between Option 2 and Option 3 is when the cookies are given to the user. Option 2 gives cookies on load. Option 3 gives cookies on the user's acceptance.
Required for minimum setup
Below is a list of the Attributes that are required for this option.
![how to add cms filter list attribute](https://cdn.prod.website-files.com/6132770a5e2efb2a37b68270/618815cf2b77c77fc751e616_cms-filter-list-min-min.webp)
![how to add cms filter list attribute](https://cdn.prod.website-files.com/6132770a5e2efb2a37b68270/618815cf2b77c77fc751e616_cms-filter-list-min-min.webp)
We prevent scripts from running. In Option 3, we can not load scripts that give cookies when the site loads. Adding this attribute will prevent these scripts from loading on the page until the user specifically selects "Allow" cookies. This is required to be cookie compliant. In Option 2, adding this attribute will allow us to prevent scripts from running when the user visits a new page on the site.
Adding these attributes will tell the library which scripts to turn on and off based on the user's cookie consent selection.
Do not do this if you are using Google Tag Manager. We have a special setup unique to Google Tag Manager! Follow it here. (<- we need an anchor link to GTM setup)
<noscript> tags are specifically designed to run when a user has Javascript disabled on the browser. This means that Finsweet Cookie Consent, or any javascript-based cookie consent solution, cannot interact with noscript tags. Since we can not prevent them from running, they are no GDPR compliant.To be fully compliant, remove all <noscript> tags included in your third-party scripts. See the Facebook Pixel example below.
![how to add cms filter list attribute](https://cdn.prod.website-files.com/6132770a5e2efb2a37b68270/6190f46b7e2f73636ecca2c3_cmsfilter-filters-min.webp)
The preferences button on the initial cookie bar is not required and is optional for cookie compliance.
![how to add cms filter active attribute](https://cdn.prod.website-files.com/6132770a5e2efb2a37b68270/61a508eeff9085721139156b_cms-filter-active-min.webp)
Setup option 3 — Opt-in to cookies
'Opt-in to cookies' is a type of cookie compliance that requires the user to specifically accept the use of cookies on the site before we issue cookies. There are no cookies given to the user until they click "Accept" (or a similar confirmation button). This is the highest level of compliance.
If the user chooses to "Accept" cookies, we run all of the scripts that use cookies. The user continues to use the site with cookies. Understand that scripts that use cookies are not loaded on the page until the user specifically accepts the cookie message.
If the user chooses to "Deny" cookies, we allow them to continue browsing the site and disable all use of scripts that issue non-essential cookies. They are never given cookies and will continue to not get cookies throughout their time on your website.
This is required for full compliance. Recommended for companies who must be fully compliant with EU Cookie Law, CCPA, GDPR, and other privacy laws.
Option 3 has similar implementation steps as Option 2. The key difference between Option 2 and Option 3 is when the cookies are given to the user. Option 2 gives cookies on load. Option 3 gives cookies on the user's acceptance.
Required for minimum setup
Below is a list of the Attributes that are required for this option.
![how to add cms filter list attribute](https://cdn.prod.website-files.com/6132770a5e2efb2a37b68270/618815cf2b77c77fc751e616_cms-filter-list-min-min.webp)
![how to add cms filter list attribute](https://cdn.prod.website-files.com/6132770a5e2efb2a37b68270/618815cf2b77c77fc751e616_cms-filter-list-min-min.webp)
We prevent scripts from running. In Option 3, we can not load scripts that give cookies when the site loads. Adding this attribute will prevent these scripts from loading on the page until the user specifically selects "Allow" cookies. This is required to be cookie compliant. In Option 2, adding this attribute will allow us to prevent scripts from running when the user visits a new page on the site.
Adding these attributes will tell the library which scripts to turn on and off based on the user's cookie consent selection.
Do not do this if you are using Google Tag Manager. We have a special setup unique to Google Tag Manager! Follow it here.
<noscript> tags are specifically designed to run when a user has Javascript disabled on the browser. This means that Finsweet Cookie Consent, or any javascript-based cookie consent solution, cannot interact with noscript tags. Since we can not prevent them from running, they are no GDPR compliant.To be fully compliant, remove all <noscript> tags included in your third-party scripts. See the Facebook Pixel example below.
![how to add cms filter list attribute](https://cdn.prod.website-files.com/6132770a5e2efb2a37b68270/6190f46b7e2f73636ecca2c3_cmsfilter-filters-min.webp)
The preferences button on the initial cookie bar is not required and is optional for cookie compliance.
![how to add cms filter active attribute](https://cdn.prod.website-files.com/6132770a5e2efb2a37b68270/61a508eeff9085721139156b_cms-filter-active-min.webp)
Preferences Manager
Add-on for option 2 and option 3
The preferences button on the initial cookie bar is not required and is optional for cookie compliance.
![how to add cms filter active attribute](https://cdn.prod.website-files.com/6132770a5e2efb2a37b68270/61a508eeff9085721139156b_cms-filter-active-min.webp)
More attributes to use
Below is a list of Attributes that can help you customize your filter system.
Accepts:
"essential"
"marketing"
"personalization"
"analytics"
![how to add cms filter active attribute](https://cdn.prod.website-files.com/6132770a5e2efb2a37b68270/61a508eeff9085721139156b_cms-filter-active-min.webp)
Accepts both absolute URLs
fs-cc-source="https://example.com/components"
and relative paths
fs-cc-source="/components"
![how to add cms filter active attribute](https://cdn.prod.website-files.com/6132770a5e2efb2a37b68270/61a508eeff9085721139156b_cms-filter-active-min.webp)
Avaiable properties are: block, flex, grid, inline-block, inline.
Defaults to flex.
![how to add cms filter active attribute](https://cdn.prod.website-files.com/6132770a5e2efb2a37b68270/61a508eeff9085721139156b_cms-filter-active-min.webp)
If placed on the Preferences component, the body locks and page scrolling is disabled when Preferences are visible.
![how to add cms filter active attribute](https://cdn.prod.website-files.com/6132770a5e2efb2a37b68270/61a508eeff9085721139156b_cms-filter-active-min.webp)
Frequently Asked Questions
Everything you need to know about this attributes solution.