The annual cost of $120 for cookies will pose a challenge for our Brazilian customers to accept. Furthermore, your other cookie consent resource has been deprecated. While the solution from Finsweet is typically useful for sure, we will need to explore alternative approaches to simplify the sales process. A project which incorporates Webflow, Wized, Xano, and Finsweet, is becoming expensive for little teams. But I guess it's the no code price. Like in the real life, if you're not able to do something, pay someone who can do it for you. So, let's purchase it ! FS fan since 3 years
Absolutely agree. The tool is built up quite user friendly and beginners like me will be very thankful, but it is really necessary to take 10$ per month for annual subscriptions? You most probably have thousands of users. I should maybe just become a cookie consent tool developer, if it works like this. And what if I get a cookie your tool does not cover? I will have to look for an alternative.
Hey @jonas! We just pushed an update to our app. The Cookie Consent solution now detects RUclips videos and offers the option to make them compliant. You can check the documentation here: finsweet.com/components/cookie-consent/video-embed.
Will the attributes turn to paid features too ? I understand the company needs. But force users to use your new paid solution removing the old one, that was perfectly working...bad move. I just get you're taking attributes like range slider, modal or star Rating and make them paid too finally...arf
This is amazing! Thank you very much. I'm having an issue with Safari for iOS where the popup shows on every page load, even when the user already accepted or rejected the cookies... any idea why?
Great idea, but way too expensive; try a one-time donation-like payment system might work to get more people to install it, I feel the subscription model is a poor choice for this kind of thing
Is there a reason why you guys are no longer using the original cookie consent besides this solution being integrated into the new components solutions?
To remove the old cloneable and force users to use this paid option is completely against what i thought Finsweet was about. To bad greed got the best of them :(. Sure you need to make some money, but you have been the powerhouse of enabling Webflow users to create the website that they need. But now you begin lock and hide things behind a paywall. Hmm that sucks big time.
The annual cost of $120 for cookies will pose a challenge for our Brazilian customers to accept. Furthermore, your other cookie consent resource has been deprecated. While the solution from Finsweet is typically useful for sure, we will need to explore alternative approaches to simplify the sales process.
A project which incorporates Webflow, Wized, Xano, and Finsweet, is becoming expensive for little teams. But I guess it's the no code price. Like in the real life, if you're not able to do something, pay someone who can do it for you. So, let's purchase it !
FS fan since 3 years
damn facts
Does anyone know another cookie consent solution for webflow that is cheaper or free?
Absolutely agree. The tool is built up quite user friendly and beginners like me will be very thankful, but it is really necessary to take 10$ per month for annual subscriptions? You most probably have thousands of users. I should maybe just become a cookie consent tool developer, if it works like this. And what if I get a cookie your tool does not cover? I will have to look for an alternative.
How do you block iFrames like a RUclips video inside of a Webflow Rich Text element and show a placeholder instead?
Hey @jonas! We just pushed an update to our app. The Cookie Consent solution now detects RUclips videos and offers the option to make them compliant. You can check the documentation here: finsweet.com/components/cookie-consent/video-embed.
Ok but why did this video release on the EXACT day I was looking for this?? Doing god's work!
Nevermind... It's $12 to have a component on your site, smh
@@AbelHaddis-h8h yeah I was so happy at the beginning until I saw its a subscription and not only that, its a subscription per each website 🙄
excellent video @finsweet, will get to it now! complete beginner! awhh
Will the attributes turn to paid features too ? I understand the company needs. But force users to use your new paid solution removing the old one, that was perfectly working...bad move.
I just get you're taking attributes like range slider, modal or star Rating and make them paid too finally...arf
a cookie component about the same price per month of the hosting of the entire website with webflow ? too expensive
Does this work with Google Tag Manager as well?
This is amazing! Thank you very much. I'm having an issue with Safari for iOS where the popup shows on every page load, even when the user already accepted or rejected the cookies... any idea why?
pay this pay that pay this pay that f that
Great idea, but way too expensive; try a one-time donation-like payment system might work to get more people to install it, I feel the subscription model is a poor choice for this kind of thing
Damn, this is so nice and easy to use! But will miss the old finsweet cookies, rip, but clever move
Is there a reason why you guys are no longer using the original cookie consent besides this solution being integrated into the new components solutions?
$$
Webflow became like Wordpress too much addons and pretty expensive not even free tool switching bach to WP
sick!
I appreciate all the good work you did guys, but removing the old clonables, is kinda a dick move.
Please put them back.
it's unfortunate that this used to be free... but appears not to be anymore.
To remove the old cloneable and force users to use this paid option is completely against what i thought Finsweet was about. To bad greed got the best of them :(. Sure you need to make some money, but you have been the powerhouse of enabling Webflow users to create the website that they need. But now you begin lock and hide things behind a paywall. Hmm that sucks big time.
I follow the video step by step, and it just hides automatically after a second
I assume It's because you have to pay $10 a year for it to work on a domain site, free to work on a .webflow site only