Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
Client side consent management library by Finsweet designed for Webflow that gates third party scripts until consent is captured.
Consent Pro is part of the Finsweet Attributes ecosystem of Webflow add ons. It is a client side consent management library that displays a cookie banner, stores the visitor preferences in localStorage and a first party cookie, and gates third party scripts (Google Analytics, Meta Pixel, embeds) until the appropriate category is accepted.
The library writes a first party cookie (fs_consent) that holds the categories the user accepted, plus a localStorage entry as a backup. No data is sent to Finsweet servers; the library is fully client side.
The fs_consent cookie qualifies as strictly necessary under recital 66 of the ePrivacy Directive because it stores the user choice. Consent Pro itself can be loaded without prior consent. Each gated tracker keeps its own legal basis and must only fire after consent.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
Finsweet OU is established in Estonia. The Consent Pro library JS runs entirely in the visitor browser and is loaded from the operator Webflow site. The Webflow site itself is hosted on AWS, with EU edges available. Document the Webflow region and any tracker transfers in your RoPA.
Configure granular categories that match your trackers, label every Webflow embed with the appropriate fs_consent attribute, document fs_consent as strictly necessary, surface a clear withdrawal mechanism and review the configuration whenever you add a new tracker.
Websites using Consent Pro by Finsweet must obtain user consent under GDPR regulations.
DPIA considerations
A DPIA is generally not required for Consent Pro itself because it acts as a strictly necessary consent gate. The DPIA may be relevant if the gated trackers themselves trigger one (Meta Pixel, advertising DMPs, behavioural analytics).
Sample consent text
We use Consent Pro by Finsweet to gather your cookie preferences. The consent record is stored on your device and used to gate optional analytics and marketing scripts.
Third-party domains contacted
finsweet.comcdn.finsweet.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| fs_consent | first_party | 1 year | Stores the visitor consent preferences (accepted categories) so Consent Pro can decide which third party scripts to load. |
| fs_consent_ts | first_party | 1 year | Timestamp of the latest consent decision used as a proof of consent for the accountability principle. |
Consent Pro by Finsweet is an essential service, but transparency matters. Manage all your consent with FlowConsent.
A first party fs_consent cookie that stores accepted categories, plus a localStorage entry as a backup. No third party Finsweet cookies are set.
No. The fs_consent cookie is strictly necessary under recital 66 of the ePrivacy Directive because it stores the user choice. The library can load without prior consent.
Legitimate interest (Art. 6(1)(f)) and the strictly necessary ePrivacy exemption for the consent record itself. Each gated tracker keeps its own legal basis.
The library itself does not. The Webflow site that hosts it may use AWS regions outside the EU; document the chosen Webflow region in your RoPA.
Generally no for Consent Pro itself. Yes for the gated trackers if they trigger one.
Configure granular categories, label every Webflow embed with the appropriate fs_consent attribute, document fs_consent as strictly necessary, surface a clear withdrawal mechanism and review when adding trackers.
Other Webflow ready CMPs include Cookiebot, Iubenda, Termly, OneTrust, Axeptio, Klaro and the open source CookieConsent.
List fs_consent and the localStorage entry as strictly necessary. Then list every gated tracker (Google Analytics, Meta Pixel, embeds) with name, purpose, retention and processor.