I build WordPress sites for clients, most on theme.co's Pro theme with the Cornerstone builder. Consently's plugin conflicted with and errored out the builder. Every element threw a markup error when Consently was active. That's a dealbreaker. I'm in the builder daily.

Emailed support. Was expecting the usual "we'll pass it along." Al Amin replied the next day asking for screenshots. Himel came back with a workaround through Tag Manager. That didn't fit me or my clients since we run GA4 directly. I said so. Instead of leaving it there, they put it on the roadmap. Two days later it was in testing. Nine days after that, Himel emailed to say they'd added a data-exclude-paths attribute to the embed script. Dropped it in my child theme, builder works, banner works. Done.

I've bought a lot of deals on this site over the last decade. Support that listens, keeps you posted without being asked, and turns a bug report into a product change in under two weeks is rare. Taco worthy. Al Amin and Himel, thank you.

The product itself: easy setup, easy to customize the banner to match the site, clean and simple. No bloat, no gimmicks. Exactly what a consent tool should be.

One thing to know for other WordPress builder Sumolings: the exclusion attribute only works with the embed script, not the WordPress plugin (yet). I deployed via child theme. Super simple.

Glad I bought it. Now rolling it out to client sites.