May 14th, 2026
Hi there,
This notification serves as to let you know that we have remove Intercom, Inc. from our list of subprocessors.
The data stored with Intercom was only from our Customers - you - for the purpose of helping you with your support inquiries and sending e-mail notifications, either about updates to our services or for transactional purposes. Data of End-Users was not included, unless provided by you (i.e. for support inquiries). The data stored with Intercom will be removed by the 18th of May, 2026.
We have used Intercom to enable our customer service efforts since our founding in early 2024. As European alternatives mature, the decision to migrate to Featurebase, which is operated by CORDNET OÜ in Estonia, came naturally. The addition of CORDNET OÜ to our list of subprocessors was included in the legal updates of April 10 this year. Feel free to view the full overview of our Subprocessors at any time.
We wish you a pleasant day and thank you for your continued trust in our platform!
The Consent Studio team
May 10th, 2026
Hi there,
If your Consent Studio site was registered before 20 September 2025, the consent banner was previously detecting the visitor's language only from their browser, ignoring the page's <html lang> attribute.
As per our upcoming change, these sites will start using the same hybrid detection of all later registered domains: the banner first reads the page's <html lang> attribute (for example, <html lang="nl-NL">), and falls back to the visitor's primary browser language when the attribute isn't set.
This matches the behaviour described under Banner → Behaviour which before only applied to domains that were registered later.
No action is required on your side. The change applies automatically. Just make sure the languages you want to support are enabled under your domain's language settings, and that your pages set the appropriate <html lang> attribute when relevant.
If you have any questions or run into anything unexpected, our support team is happy to help.
The Consent Studio team
May 8th, 2026
Hi there!
One of the most common questions we receive is whether it's possible to change the button order in your consent banner, across different screen sizes. If you've asked us this before, you may remember we used to solve it by sharing a Custom CSS snippet for the Styling settings panel.
Starting today, you can reorder buttons directly from the Behaviour settings panel by simply dragging and dropping them into the desired position.
Buttons that aren't enabled will appear greyed out, but you can still set their order ahead of time so they're ready whenever you decide to turn them on.
As always, if you have any questions or run into anything unexpected, our support team is happy to help.
The Consent Studio team
May 6th, 2026
New
Consent Studio Launcher is our new consent-aware tag manager for client-side tags on websites. One script loads both your consent banner and your marketing tags.
Just like our existing product suite, Consent Studio Launcher is 100% Sovereign European. This means that our cloud infrastructure is run by European companies, which prevents overseas transfer of European data.
We’re really hyped to finally share what we have been working on with you, for real! Check out the highlights below.
Product Highlights
Template Library
Ready-made setups for Google Analytics 4, Google Tag Manager, Meta Pixel, HubSpot, LinkedIn Insight, Microsoft Clarity, Matomo, Piwik PRO, Reddit Pixel, Hotjar, and more.
Rich Tag Triggers
All Pages, DOM Ready, DataLayer Event, Click, Form Submission, Timer, Scroll Depth, and Element Visibility.
Consent? Built-In!
Configure a tag’s consent rules using our Neutral, Defer and Configure settings. Consent Studio Web CMP is bundled in Launcher’s main script. Everything loads with a single request - including your configuration.
🚀 Your CMP and Tag Manager load in a single request. That is something that we believe is huge for performance!
Google Consent Mode v2
Of course, Google Consent Mode v2 is included and supported out of the box. All Consent Mode v2 tags that you are used to manage in other tag managers, can be configured in the always-included Consent Studio CMP script.
DataLayer Forwarding & Variables
Pull live values into event parameters in your tags via placeholders by using variables like {{event.currency}}.
And Much More!
Test your configuration live on your own website before publishing using the Preview mode, which comes with a live variables inspector and debug log. Modify a tag’s settings based on a visitor’s geographic location using Geotargeting.
Pricing: Free
Consent Studio Launcher is available on every Consent Studio plan: Essential, Essential Plus, Professional, Tailored and Enterprise.
Each per-country Geotargeting override on a tag counts as one Geotargeting Rule against your plan's limit.
Current Phase: Testing
Launcher is stable enough for day-to-day use, but some rough edges remain. We invite early adopters to join our testing phase and share feedback in our dedicated portal.
Thanks for being part of the journey. We can't wait to see what you build with Consent Studio Launcher and to learn how we can tagging as easy as possible for you!
Best regards,
Thierry Maasdam
Head of Product at Consent Studio
April 24th, 2026
Fixed
Hi there,
This changelog notification is to inform you about an update that's now available for our Google Tag Manager Community Gallery Template. (Quite a mouthful, we know.)
The update resolves an issue with Regional Overrides for Google Consent Mode default signals. In short: we referenced a non-existing variable, which caused Regional Overrides not to work as intended. A special thanks to Koen at AdPage for reporting this.
Tags in Google Tag Manager do not update automatically. Instructions on how to accept incoming updates can be found here.
This release is recommended if you intend to use, or are actively using, Regional Overrides. If you don't, it is safe to postpone the update at your convenience.
Kind regards,
The Consent Studio team
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.