April 14th, 2026
Improved
Hi everyone! This changelog update is to let you know that our JavaScript SDK just got a meaningful upgrade: the window.consentStudio.api.consentState SDK now lets you write the consent state directly from your own code, not just read it.
New methods include set(), acceptAll() and denyAll(), plus a hideBanner option on every write method, so you can drive consent from custom preference UIs or external flows without touching the banner's internal DOM.
A full reference of our JavaScript API can be found on https://learn.consent.studio/en/help/articles/11114257.
And a full reference of JS browser events can be found on https://learn.consent.studio/en/articles/10316000.
If there’s anything that we can assist you with for advanced set-ups that require custom javascript on your end, do not hesitate to reach out to us by contacting support@consent.studio!
April 10th, 2026
Hi there,
We have made changes to Consent Studio's legal documentation.
Clearer audience targeting
We have split our privacy policies into two distinct versions: one for End-Users and one for Customers. This makes it easier for everyone to find the information that applies to them.
New subprocessor: Cordnet OÜ
We have moved from Intercom to Featurebase for our customer service software, as part of our ongoing commitment to European-first operations. Featurebase is developed by Cordnet OÜ, a company registered in Estonia.
Cordnet OÜ uses a combination of European and U.S.-based cloud infrastructure. Their services do not process End-User data unless you provide it (e.g. for diagnostics).
For clarity: the stack that Consent Studio End-Users interact with remains fully dependent on infrastructure owned and operated by European companies.
Cordnet OÜ is now listed in our subprocessors with full details of their data processing arrangements.
Full overview of Subprocessors »
No action is required on your end. If you have any questions, feel free to reach out. We’re here to help!
Best regards,
On behalf of the Consent Studio team,
Thierry Maasdam
Head of Product
March 19th, 2026
New
Wildcard support for Tracking Technology names (e.g. cookies) has been expanded.
Previously, only a single trailing wildcard was supported, allowing patterns like:
ga_*…to match cookies such as ga_1234, ga_1235, ga_1236, and so on.
You can now place multiple wildcards anywhere in the name, enabling patterns like:
lorem_*_ipsum_*…which would match lorem_test_ipsum_x, lorem_x_ipsum_y, lorem_x_ipsum_, and similar variations.
March 17th, 2026
Improved
We've optimized how the consent banner responds to user interactions. These changes significantly improve Interaction to Next Paint (INP), a Core Web Vital, bringing it back to 64ms, which is well within Google's recommended threshold. No action required on your end.